On Tuesday 09 December 2003 22:09, Peter Onion wrote:
Anyone using this combination ?
Nope, but.......
The modem has a DHCP server , which initially gives a 192.168.0.X address on a short lease. It waits until it actually has traffic to send it until using DHCP to get the real (ADSL interface) address. Then it updates the 192.168.0.X address for the real one.
Changing eth0's address like this breaks the rules in the firewall. It can easily be fixed by running "rcSuSEfirewall2 restart", but it is a bit of a pain.
Any other solutions ?
No idea, SuSEfirewall seems to make the assumption that once an interface is up, it's ip address will never change. Worse than that I've had problems with things like hotplug interfaces (My Zaurus for example) where it will only work if the Zaurus is present at boot (or at a restart of SuSEfirewall). I can only think that you should use something other than SuSEfirewall or replace your ADSL modem for a NAT capable ADSL router. (therefore keeping a static IP on your machine regardless of the dynamic IP your ISP assigns)
Sorry
Wayne