Re: no ipchains with 2.2/no network with 2.4
I removed it, but it has no effect. (I just added it in my "tests" sessions,
but without success).
In fact, the same network config is used without ipchains and with ipchains,
so routing with that config worked with the kernel-image-2.2.20-idepci and
doesn't work with kernel-image-2.2.20.
p.s. when you suggest a modification, could you also explain what the
expected effect would be ?
In that case, all the computers from my internal network have the gateway
specification of 192.168.1.1, so I don't know what harm it could have to
specify it also on the gateway itself.
If it was using DHCP (but with a reserved address), it would receive that
same info also.
Thanks for your suggestions anyway, it allows me to have 15 minutes of hope
while restarting the alternate kernel ;-)
From: Gian Piero Carrubba <firstname.lastname@example.org>
Subject: Re: no ipchains with 2.2/no network with 2.4
Date: Tue, 11 Jan 2005 01:05:24 +0100
Il giorno lun, 10-01-2005 alle 22:35 +0100, Pierre A. Damas ha scritto:
> The interface file contains:
> # /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)
> auto eth1
> iface eth1 inet static
> address 192.168.1.1
> netmask 255.255.255.0
> network 192.168.1.0
> broadcast 192.168.1.255
> gateway 192.168.1.1
Remove this last line ( gateway 192.168.1.1 ), so that `route -n` (after
appropriate ifdown/ifup) should list:
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use
> 192.168.254.0 0.0.0.0 255.255.255.240 U 0 0 0
> 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0
> 0.0.0.0 192.168.254.1 0.0.0.0 UG 0 0 0
without the following line:
> 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0
To UNSUBSCRIBE, email to debian-firewall-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact
Free e-mail? Try MSN Hotmail ! http://www.hotmail.com