Check the following for help with this message:
setsockopt: Protocol not available
#1 make sure that experimental code is enabled in the kernel.
#2 make sure that ip forwarding/masquerading is enabled in the kernel
#3 make sure you have downloaded the ipautofw application
#4 run ipautofw as
OK, I have been getting closer, but there are problems.
Some problems: After I rebooted to make sure all was starting correctly on
bootup, my hard drive access light never went off, it stayed on until I
disabled my script that enabled my ipfw rules.
Which leads me to the other problem. it
Partly out of ignorance and partly setting everything I could trying to get
port forwarding to work.
-Original Message-
From: Fuzzy Fox [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 14, 1999 2:54 PM
To: Linux IP Masquarede
Subject: Re: [masq] port forwarding
Jim Montague
I recently aquired a DEC Multia (Alpha) computer and was fooling around
with Linux on it. I was hoping I could use it to replace my existing Linux
server that I use for IP masquerading. However, I noticed when doing a
'make menuconfig' that IP masquerading does not even appear as it did
[EMAIL PROTECTED] said:
} I bet you are right on this one. As it stands, I pushed up my UDP
} timeout to something lame like 5hrs because ICQ was flapping. It was
} only later that I learn that you can change ICQ's refresh directly.
} I'll try putting my UDP timeout to somthing like 80 seconds
Fuzzy Fox [EMAIL PROTECTED] wrote:
} Chris Ruvolo [EMAIL PROTECTED] wrote:
}
} In specific, the X server is behind the masq (on the private network)
} and the X client (the machine running the apps) is out on the
} internet.
}
} This is the problem. An X client opens a connection to the X
On 15 Jan 99, at 0:01, benjamin j snyder wrote about
"[masq] getting close":
|...
| Which leads me to the other problem. it doesnt work. I am using the script
| in the ip_masquerading how to (section 4.4 of the how to?), although I have
| modified it somewhat. Here it is:
|
|
|
Hi all. This really ought to be a FAQ, but I found no information about it
on the net, whatsoever, so here I go...
Is it possible to get rlogin (or preferably rsh) to work through a
masq'ing firewall? The server says "Illegal port", as it is mapped to a
non-priviledged port on its way. Hacking
Hi All;
I am currenly running IP-Masq. Slackware, 2.0.34, clients are Win95. Most
things work great. except... E-mail is hosted by my ISP, to which a dialup
from the Linux IP-masq box connects. Often, if an e-mail attachment
approaches or exceeds 1 meg, my linux box disconnects from the
Recently I've been having some trouble with my network, so I started
monitoring the traffic that I'm sending out. I noticed the following in
the kernel log:
kernel: Packet log: output ACCEPT ppp0 PROTO=1 209.44.42.47:0 \
204.92.54.110:0 L=1500 S=0x00 I=11995 F=0x T=255
I see
I have never bothered even investigating this because there is a better
solution.
Use ssh as your transport, proxy the X over ssh. This goes through masq
beautifully, enables you to keep things rather more secure, optionally
compresses (works wonderfully over ISDN) and is an all round good
What are the main differences between using ipautofw, and
ipportfw? Can everythin achieved by one be achieved also by the
other? Which is "the lists" choice?
IPPORTFW.
This is what Fuzzy Fox had to say...
--
Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm
Delivered-To:
On Thu, 14 Jan 1999, Stomper wrote:
Date: Thu, 14 Jan 1999 16:11:09 -0700
From: Stomper [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: [masq] Battle.net masq module.
Anyone that is a programmer game to attempt a battle.net masq module.
Looks like Blizzard finally got smart and
13 matches
Mail list logo
