Topic: Static IP Problems

[Justin]

I was running E-smith 3.1 and 4 without a hitch on @home cable service using DHCP. When I took the exact same server and hooked it up to wave using a static IP the server can assign DHCP to internal network, see all other computers in the network but cannot see the Internet. It was suggested that the subnet may be the problem I had both the internal and external settings at 255.255.255.0. Can this be causing it?

I also ran "route" at home and showed etho at 255.255.255.0 and eth1 at 255.255.254.0. I am going to try setting the static box with a different subnet address but if anyone has any insight or suggestions I would like to hear them.

Thanks,

[Joseph Morrison]

Hi Justin,

There are multiple implementations of the @home service, and some require that you use DHCP. (Long-winded explanation omitted.)

The latest e-smith beta includes two options for DHCP - you can choose whether the DHCP client sends the MAC address or the machine name as the client identifier. One of these options should work for you.

Good luck! (Let us know if this solves your problem.)

Best regards,
- Joe

[Justin]

The cable service is not using DHCP, I am using DHCP internally. The problem is in setting up the static IP service with wave.

Thanks,

[Joseph Morrison]

Hi Justin,

Sorry, I'm not sure I wrote that clearly. I meant to say that recent cablemodem installations sometimes *require* that you get your external IP address using a DHCP client.  They simply won't work with a static IP configuration. The new @home setups in Ontario (with Terayon modems) are like this.

Best regards,
- Joe

[Justin]

I may be misunderstanding you as well. This service requires a static configuration DHCP is not an option. I would prefer DHCP since I am not running a web server or email but static service is the only option.Joseph Morrison wrote:

> Hi Justin,
>
> Sorry, I'm not sure I wrote that clearly. I meant to say that
> recent cablemodem installations sometimes *require* that you
> get your external IP address using a DHCP client.  They simply
> won't work with a static IP configuration. The new @home setups
> in Ontario (with Terayon modems) are like this.
>
> Best regards, - Joe
>

[Joseph Morrison]

Hi Justin,

I understand now.  Could it be one of those setups where the cablemodem memorizes the MAC address of the ethernet card? In that case, unplugging the cablemodem for a few minutes and then plugging it in again will help.

It's important to get the external subnet address correct, but it has no relation to the internal subnet address. For example it doesn't matter if they're the same.

Good luck!
- Joe

[Justin]

It may be....thanks I'll try that too.

[Justin]

Its going now...turned out the cable modem captured the MAC address internally and had to be unplugged for 20 seconds before it would recognize a new adapter. Kinda makes you wonder why the Cable providers don't volunteer that information.

J.