Topic: problem configuring NIC for DHCP

[oliver lentil]

When booting up I get the following error:"

Bringing up interface eth1 [Failed]
dhcp(245) time out waiting for valid DHCP server

I am trying to access Videtron using my Motorola Cybersurfer Wave Cable Modem.
I am using the same settings that worked on my WIN95 station - Obtain internet
connection parameters dynamically.

I 've configure my e-msith as a dedicated server and gateway and with "Use DHCP
without dynamic DNS service". I have 2 NICS: 3c590 and 3c509 both configured automatically using the 3C59x driver in e-smith.

Does e-smith automatically assign eth0 and eth1 to appropriate NICs. That is,
is eth1 - internet and eth0 - local LAN.

I get the same error regardless of which NIC is connected to the CAble Modem

[Charlie Brady]

oliver lentil wrote:

> When booting up I get the following error:"
>
> Bringing up interface eth1 [Failed] dhcp(245) time out waiting
> for valid DHCP server
>
> I am trying to access Videtron using my Motorola Cybersurfer
> Wave Cable Modem. I am using the same settings that worked on
> my WIN95 station - Obtain internet connection parameters
> dynamically.
>
> I 've configure my e-msith as a dedicated server and gateway
> and with "Use DHCP without dynamic DNS service". I
> have 2 NICS: 3c590 and 3c509 both configured automatically
> using the 3C59x driver in e-smith.

I think you should be using the 3c509 driver with the 3c509.

> Does e-smith automatically assign eth0 and eth1 to appropriate
> NICs. That is, is eth1 - internet and eth0 - local LAN.

Well, eth0 is configured as the local LAN and eth1 is configured as the internet connection, and there is no confusion as to which NIC becomes eth0 and which eth1 as long as the NICs use a different driver. If they are identical, or even if they use the same driver, then linux allocated eth0 to the first NIC it locates and eth1 to the other NIC. These might be the reverse of the way that you have the NICs cabled.

> I get the same error regardless of which NIC is connected to
> the CAble Modem

It doesn't sound like the problem is which NIC is eth0 and which eth1. Check that you have the correct drivers, check you cables and the link light on your NICs. Keep an eye on /var/log/messages for clues.

Charlie

[J.Oliver]

"Check that you have the correct drivers, check you cables and the link light on your NICs."

I'll bet you that isn't the problem.

Cable internet access has some sort of mechanism or anamoly that prevents people from using IPchains and kernel IP masquerading on a linux box to share access with a private numbered internal LAN. (which is what your product depends on)

I'm currently looking for a solution.   Doubt I'll find it.  That's why I came here, but you told him to check that his power is on.  Did you used to work for AOL?  LOL.

I think you should check your compatibility with Rogers@Home service.  

Good luck with this one.

[Charlie Brady]

J.Oliver wrote:

> Cable internet access has some sort of mechanism or anamoly
> that prevents people from using IPchains and kernel IP
> masquerading on a linux box to share access with a private
> numbered internal LAN. (which is what your product depends on)

As far as I am aware, there are no problems with using IPchains and IP masquerade, but there *are* variations with the parameters required for DHCP to work correctly. E-smith 4.0 will include a variety of options to allow use with a wider range of cable services.

> I'm currently looking for a solution.   Doubt I'll find it.

I'm sorry that you are so pessimistic.

> That's why I came here, but you told him to check that his
> power is on.

Oh really, I didn't notice that.

> Did you used to work for AOL?  LOL.

Are you always rude to people you have not meant?

> I think you should check your compatibility with Rogers@Home
> service.

Some combination of the -h and -I arguments to dhcpcd should work. Some experiementation may be required, or you might get lucky with the technical support people form the cable company.

> Good luck with this one.

Persistence should help too.

Regards

Charlie

[oliver lentil]

Thanks everyone!

I Plugged the eth1 to the internet and eth0 to my LAN.
I also specified my Primary and Secondary DNS. Now every
machine on my LAN can access the internet!