🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Thread View: comp.os.linux.networking
2 messages
2 total messages Started by Hugh A Livingston Fri, 02 May 1997 00:00
Re: can't seem to configure ipfw
#258
Author: Hugh A Livingston
Date: Fri, 02 May 1997 00:00
48 lines
2558 bytes
woody@{spam.bites}.daemon.apana.org.au (Terry Wood) writes: > 
> On 2 May 1997 08:21:11 GMT, Hugh A Livingston
> <hugh_livingston@edinburgh.ccmail.compuserve.com> wrote:
> 
> >I am also experiencing this problem although I'm using ipfwadm.... so I
> >don't think that's the problem. I get the error message:
> >setsockopt failed: Protocol not available, when I try any set of policy's,
> >i.e., ipfwadm -F -p deny. Again any help appreciated.
> 
> For your info the Australian Mirror of the IP Masquerading pages are
> located on http://jart.traralgon.netspace.net.au/ipmasq/
> 
> I had to use ipfw when i was using a 1.2.13 kernal with slackware but
> as soon as i upgraded to Redhat 4.1 with 2.0.29 kernal ipfw went out
> the window and i recompiled the kernal with the info off the above
> pages and got it working within about 1/2 hour.  Have a good read as
> its all there.
> 
> Im not an expert, but ill help if i can as it works aok for me.
> 
> 
> Catch ya,
>           Woody   <woody@netspace.net.au>
>                    Note: remove {spam.bites} to reply
> --
> Terry J. Wood,
> Located at Traralgon, Gippsland
> Country Victoria, Australia


     Thanks for that Woody, however I have already visited that site
and am still experiencing problems with the ipfwadm command as previously
detailed.

I am running Slackware Linux 2.0.0, and have gone through all the usual
Kernel compilations etc. I am wondering if it's got something to do with
the fact that I am not using a modem.... I am connecting straight into
a 3Com Accessbuilder RemoteUser 400 router to link to my ISP. Presumably
I don't need to worry about setting up PPP under Linux as the router
should handle it. I can ping my router fine, and can ping local LAN
addresses fine too. Just can't get the ipfwadm to work..... says Protocol
not available all the time.

Sorry for long message however, if anyone can shed any light on my ensuing
plight I would be very grateful.

P.S. The router is connected to 64K ISDN line.
Re: can't seem to configure ipfw
#259
Author: Terry Wood
Date: Fri, 02 May 1997 00:00
72 lines
3513 bytes
On 2 May 1997 11:49:20 GMT, Hugh A Livingston
<hugh_livingston@edinburgh.ccmail.compuserve.com> wrote:

>> For your info the Australian Mirror of the IP Masquerading pages are
>> located on http://jart.traralgon.netspace.net.au/ipmasq/
>> 
>> I had to use ipfw when i was using a 1.2.13 kernal with slackware but
>> as soon as i upgraded to Redhat 4.1 with 2.0.29 kernal ipfw went out
>> the window and i recompiled the kernal with the info off the above
>> pages and got it working within about 1/2 hour.  Have a good read as
>> its all there.
>
>     Thanks for that Woody, however I have already visited that site
>and am still experiencing problems with the ipfwadm command as previously
>detailed.
>
>I am running Slackware Linux 2.0.0, and have gone through all the usual
>Kernel compilations etc. I am wondering if it's got something to do with
>the fact that I am not using a modem.... I am connecting straight into
>a 3Com Accessbuilder RemoteUser 400 router to link to my ISP. Presumably
>I don't need to worry about setting up PPP under Linux as the router
>should handle it. I can ping my router fine, and can ping local LAN
>addresses fine too. Just can't get the ipfwadm to work..... says Protocol
>not available all the time.
>
>Sorry for long message however, if anyone can shed any light on my ensuing
>plight I would be very grateful.

Your right, it shouldnt matter at all how you are connected to the
net, be it via a modem or other device.  I initialise all my ip
forwarding/masqing before i have any connection to the outside world
at all on bootup (modem hasnt dialed) and as soon as that link goes up
the masqing works great.

Something to check is if you are using one of the very first options
when compiling the kernal when it asks if you want to use
'experimental, blah' drivers.  I got caught on this the first time too
as it looks like you are adding everything into the kernal for
forwarding/masquerading but you are missing things and it wont work if
you forget this 1st option.

Once you have the kernal right I use this to setup forwarding in my 
boot time:

ipfw-on:

#!/bin/sh
ipfwadm -F -p deny
ipfwadm -F -a m -S 192.168.1.0/24 -D 0.0.0.0/0


Have you also thought about getting 2.0.29 or higher kernal and using
that as it has a LOT of the patches installed and shouldnt give you
trouble.

I had trouble use the ipfw tool under slackware linux 1.2.13 as there
was some code in the original source that didnt allow proper
forwarding/masqing but with a 2.x kernal you should be right.

Failing the above, i would strongly suggest you get the latest kernal
2.0.31? and install that EXACTLY as outlined in the masquerading FAQ
and ill go hop if it wont work :)...


Catch ya,
          Woody   <woody@netspace.net.au>
                   Note: remove {spam.bites} to reply
--
Terry J. Wood,
Located at Traralgon, Gippsland
Country Victoria, Australia
Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads