Re: ipmasq problem -- fixed
The problem apparently was that I had finally updated my configuration
/from etc/init.d/network to the newer /etc/init.d/networking and ran
'update-rc.d networking defaults', which caused networking to be run
after ipmasq. A look at netbase.postinst was illuminating.
On Thu, Sep 07, 2000 at 11:23:11PM -0700, Bob Nielsen wrote:
> I upgraded my potato system to kernel 2.2.17 and my networking (all
> networking, not just masquerading) failed with messages in syslog like:
>
> Sep 7 22:55:11 bob kernel: Packet log: output DENY eth0 PROTO=17
> 192.168.1.1:513 192.168.1.255:513 L=88 S=0x00 I=1 F=0x0000 T=64 (#2)
>
> ipchains -L shows:
>
> Chain input (policy DENY):
> target prot opt source destination
> ports
> ACCEPT all ------ anywhere anywhere n/a
> DENY all ----l- localnet/8 anywhere n/a
> DENY all ----l- anywhere anywhere n/a
> Chain forward (policy DENY):
> target prot opt source destination
> ports
> DENY all ----l- anywhere anywhere n/a
> Chain output (policy DENY):
> target prot opt source destination
> ports
> ACCEPT all ------ anywhere anywhere n/a
> DENY all ----l- anywhere anywhere n/a
>
>
> If I issue the commands:
>
> /etc/init.d/ipmasq restart && /etc/init.d/ipmasq-kmod restart
>
> networking works correctly and ipchains-L gives the correct information.
>
> ipmasq and ipmasq-kmod are run by symlinks in /etc/rcS.d at boot time
> and dmesg verifies this. Does anyone know why they aren't working
> until I rerun them later from runlevel 2? I didn't have this problem
> with 2.2.16.
--
Bob Nielsen, N7XY nielsen@oz.net
Bainbridge Island, WA http://www.oz.net/~nielsen
Reply to: