First, thanks to everyone who lent assistance.
Second, I believe I owe the list an apology, since it turns out that I
have probably not had ipportfw working right since I started with 2.1.x.
It looks like I set up ipportfw using 2.0.34, not 2.1.12[79], and the
version of ipmasqadm I had installed was under-versioned. I updated my
copy of ipmasqadm this evening and everything appears to be working fine.
My router now has three X displays, which are hosted on three different
machines!
-----Original Message-----
From: Allison, Bob [mailto:BOB.allison@qwest.net]
Sent: Sunday, January 03, 1999 12:51 AM
To: 'Jim Pick'
Cc: Kernel Mailing List
Subject: RE: Linux 2.2.0pre2 and ipportfw
Yes, I am using ipmasqadm. That's how I am getting this to work
while running a 2.1.129 kernel.
-----Original Message-----
From: Jim Pick [mailto:jim@jimpick.com]
Sent: Saturday, January 02, 1999 3:42 PM
To: Allison, Bob
Cc: Kernel Mailing List
Subject: Re: Linux 2.2.0pre2 and ipportfw
"Allison, Bob" <BOB.allison@qwest.net> writes:
> I now have 2.2.0-pre2 running on my 386 firewall (THANKS Linus), but...
>
> IP port forwarding does not work. When I use the ip-up script, I get
> portfw: setsockopt failed: Protocol not available
>
> Any ideas on what might be causing this? I have not rebuilt anything
> other than the kernel, and the script works if I boot 2.1.129.
Are you using ipmasqadm? That replaces ipportfw.
It looks like you may need to patch the kernel, or maybe not.
Cheers,
- jim
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/