🚀 go-pugleaf

Rhasta,

Thanks for letting me know that the 2.2.16 would still work.  But I still
cannot get over the port forwarding problem.  I can issue the command the IP
masqerading command with any error messages:

   ipmasqadm portfw -a -P tcp -L $external_IP 1800 -R $internal_IP 23

However, there is no forwarding occurs.  Also I am still getting these error
messages after "ipmasqadm portfw -l":
    Could not open "/proc/net/ip_masq/portfw"
    Could not open "/proc/net/portfw"
    Check if you have enabled portforwarding

Joe



"lincoln" <rutledge@greenapple.com> wrote in message
news:3B6DF789.430EFC46@greenapple.com...
> Rhasta wrote:
>
> > On Sun, 5 Aug 2001 17:54:55 -0400, "JP" <pangjo@hotmail.com> wrote:
> >
> > >I have been trying to set up port forwarding using ipmasqadm but could
not
> > >make it work.  I have the following error when I issued the command
> > >"ipmasqadm portfw -l":
> > >
> > >Cound not open "/proc/net/ip_masq/portfw"
> > >Cound not open "/proc/net/portfw"
> > >Check if you have enabled portforwarding
> > >
> > >But I have no error messages when I set up the rules using "ipmasqadm
> > >portfw".  Also, ip_forward has the value of 1.  But I cannot find
> > >"/proc/net/ip_masq/portfw".  How can I enable portfowarding on
Slackware
> > >2.2.16?
> > >
> > >Joe
> > >
> >
> > First, you should upgrade to the latest kernel, as 2.2.16 has a
> > vulnerability.
> >
> > Then, for portfw to work with ipmasqadm, you have to compile it either
> > in the kernel or as a module. If you compile it as  a module and you
> > do not use kmod to load modules on demand, you have to manually insert
> > it before doing a port forwarding with ipasqadm.
>
> I am running 2.2.16 and I just compiled it into the kernel, and voila, it
> works!  I tried it with a newer kernel, but then I was getting messages
and I
> had to download the newest ppp and compile it in, etc, etc.  I reinstalled
> with the 2.2.16 kernel, compiled it in, and it works with no other
tweaking
> (slackware 7.1).  Just follow the usual instructions in the Howtos and
you'll
> be fine.
> If you're really worried about security, then you may have to use the
newer
> kernel, but it opens up a pandora's box of other things that have to be
> updated, and I haven't read anything that warns you or tells you
everything
> you have to upgrade.
>
> Hope this helps, let me know if I can help,
> rutledge_almostaranch
>