Messages in this thread |  | | From | Stefan Bosnjakovic <> | Subject | Again: Maquerading FireWall Feature and New Init behaviour ! | Date | Wed, 8 Jan 1997 01:16:28 +-100 |
| |
Hi Everybody !
Sorry for posting it again - but I received no answer until now. Maybe this time! Anyway I added some more info to it. So here we go again:
Please excuse me if I´m wasting bandwidth and this question is already answered elsewhere already, but I would need to get the Masquerading IP-Firewall feature together with the Traffic Shaper function (that´s the reason why I use the 2.1.x kernels) to work. The transparent masquerading works quite well for me with the 2.0.25/27 kernel, but it does not seem to forward anything with 2.1.17-2.1.19. Any ideas? I use the SuSE distribution rel 4.4, but installed the following patches: LibC: 5.4.1.7 LibC++: 2.7.2.1 BinUtils: 2.7.0.3 Insmod: 2.0.0 Procps: 1.01 SysVinit: 2.69 ld.so: 1.8.5 SysKlogd: 1.3-3 Mount: 2.5p Net-Tools: 1.32-alpha Kbd: 0.91
I can ping stations on both ethernets, and "netstat -r" shows everything OK. If i boot kernel 2.0.25 it forwards and masques packets, with the 2.1.x it doesn´t.
I compile all option directly into the kernel - not as a loadable module, if that matters. Also those that make modules would generate, I changed that.
Other odd thing: with the new init it obviously does not start /sbin/init.d/boot automatically, as it did with my original distribution. No matter if I use the 2.0.x or 2.1.x kernel. So I added an "ln -s /sbin/init.d/boot /sbin/init.d/rc2.d/S00boot". That seems to fix that problem - is that a viable solution ?
Also the /etc/route.conf needs editing when I switch the two kernel releases. Cheers, Stefan !
stefan@nces.co.at
|  |