Topic: 4.0b3 adapter problems???

[Jon Thiele]

My 3.1 version of e-smith have been working flawlessly for quite some time now(!).  

But, in anticipation of the 4.0 final, I thought I'd try out the 4.0b3 version just to see what's new.  Unfortunately, I never got it installed.

As suggested in the manual, I'm running 2 Kingston EtherX KNE100TX adapters - one is connected to my cable modem and the other connected to my hub.  I configured my 4.0b3 in exactly the same way I did in 3.1 - dedicated server and gateway, using a static IP (24.112.23.37), no internal DHCP, Gateway is 24.112.22.1, and using the discovered adapter drivers (Tulip).  As far as I can tell, I installed my server exactly like 3.1.  However, when I rebooted after the setup, I had all kinds of problems:  it appears that the ethernet adapters aren't configured correctly.  Although I get the "O.K." message on bootup, I could not ping my server, I could not connect to the Internet, and I'm not sure what was happening with my modem connection, because it started to reset itself over and over.  (To make sure this wasn't some one-time problem, I re-installed 3.1, got it working, and then re-installed 4.0b3 - same problems as before.)

Did anything change with the Tulip adapters???  Any suggestions would be appreciated...

[Charlie Brady]

Jon Thiele wrote:

> But, in anticipation of the 4.0 final, I thought I'd try out
> the 4.0b3 version just to see what's new.  Unfortunately, I
> never got it installed.
>
> As suggested in the manual, I'm running 2 Kingston EtherX
> KNE100TX adapters - one is connected to my cable modem and the
> other connected to my hub.  I configured my 4.0b3 in exactly
> the same way I did in 3.1 - dedicated server and gateway, using
> a static IP (24.112.23.37), no internal DHCP, Gateway is
> 24.112.22.1, and using the discovered adapter drivers (Tulip).
> As far as I can tell, I installed my server exactly like 3.1.
> However, when I rebooted after the setup, I had all kinds of
> problems:  it appears that the ethernet adapters aren't
> configured correctly.  

What may be different is that the allocation of which network card is considered eth0 and which eth1 may be different between the two different systems. The e-smith 4.0 beta includes an option to swap the allocation of adaptors between eth0 and eth1 - it might be worth enabling that option to see if that fixes your problem.

Otherwise you will need to  go through some diagnostic steps to work out exactly what is working and what isn't. If you need help with that process you probably should join the developers mailing list devinfo@e-smith.net and report your troubles there.

As to your modem connection problems, again we would need more precise information to help diagnose the problem. Have you looked at the /var/log/messages log file?

Charlie

[Joseph Morrison]

Charlie Brady wrote:
> What may be different is that the allocation of which network
> card is considered eth0 and which eth1 may be different between
> the two different systems.

Charlie is right (as always The two ethernet card assignments have been switched in e-smith 4.0 so you either need to:

(A) switch the ethernet connectors (i.e. the card that used to go to your hub now needs to be plugged into the cablemodem, and vice versa) or

(B) use the console "swap ethernet assignment" feature.

Have you tried either of these? Please let us know what happens!

Best regards,
- Joe Morrison

[Joseph Morrison]

Wait a minute, I think I posted too quickly! The assignments switched from e-smith 2.0 -> 3.0, not 3.0 -> 4.0. The 4.0 installation should have worked without modification.

Can you try getting your IP address using DHCP? Some newer cablemodem setups now require this and do not work correctly otherwise.

Also, I'm curious - can you ping your e-smith server from your workstations on the local network?

Finally, what happens if you log into your e-smith server (Ctrl-Alt-F3, login as "root", use the current system password) and type:

ifconfig

Is there a reasonable configuration for all ethernet interfaces?

Also, when you said it "reset itself over and over" do you mean that the modem was resetting? Or the e-smith server rebooting?

Last question: what type of cablemodem are you using? Is it one of the Terayon modems? (Those are the ones where we've found DHCP to be important.)

Thanks for any more clues. We'll keep working on it.

By the way as far as adapters, e-smith 4.0 uses Red Hat 6.1 with the tulip drivers that shipped with Red Hat.

- Joe Morrison