[masq] Starcraft with kernels 2.2.x

1999-01-31 Thread Kristopher A. Kersey

OK, I'm looking to get some strait answers on IP Masq for kernel
versions 2.2.x.  I'm currently have my kernel configured with the
following "Network Options" related stuff:

Packet socket
Network firewalls
Unix domain sockets
TCP/IP networking
IP: firewalling
IP: always defragment
IP: masquerading
IP: ICMP masquerading
IP: masquerading special modules support
IP: ipautofw support
IP: drop source routed frames
IP: allow large windows

And all I'm doing to enable masqurading is typing:

ipchains -A forward -s 192.168.1.0/24 -j MASQ
echo "1"  /proc/sys/net/ipv4/ip_forward

My MASQ as a whole all works, but Starcraft seems still not be working
right.  I though the UDP bug was fixed.  Is this all correct?  What
should be changed?

Thanks in advance,
Kris Kersey
[EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
For daily digest info, email [EMAIL PROTECTED]



Re: [masq] Starcraft with kernels 2.2.x

1999-01-31 Thread mumford

On Sun, 31 Jan 1999, Kristopher A. Kersey wrote:

 Date: Sun, 31 Jan 1999 03:21:41 -0500
 From: "Kristopher A. Kersey" [EMAIL PROTECTED]
 To: MASQ Mail List [EMAIL PROTECTED]
 Subject: [masq] Starcraft with kernels 2.2.x
 
 OK, I'm looking to get some strait answers on IP Masq for kernel
 versions 2.2.x.  I'm currently have my kernel configured with the
 following "Network Options" related stuff:
 
 Packet socket
 Network firewalls
 Unix domain sockets
 TCP/IP networking
 IP: firewalling
 IP: always defragment
 IP: masquerading
 IP: ICMP masquerading
 IP: masquerading special modules support
 IP: ipautofw support
 IP: drop source routed frames
 IP: allow large windows
 
 And all I'm doing to enable masqurading is typing:
 
 ipchains -A forward -s 192.168.1.0/24 -j MASQ
 echo "1"  /proc/sys/net/ipv4/ip_forward
 
 My MASQ as a whole all works, but Starcraft seems still not be working
 right.  I though the UDP bug was fixed.  Is this all correct?  What
 should be changed?

Are you doing port forwarding?  You need to forward udp port 6112 from the
masquerading machine to the gaming machine.  Forwarding tcp port 6112 might
also be a good idea.

Glenn Lamb - [EMAIL PROTECTED]  Finger for my PGP Key.
Email to me must have my address in either the To: or Cc: field.  All other
mail will be bounced automatically as spam.
PGPprint = E3 0F DE CC 94 72 D1 1A  2D 2E A9 08 6B A0 CD 82

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
For daily digest info, email [EMAIL PROTECTED]



[masq] tunneling

1999-01-31 Thread John Lord

Here what I have , not sure if this will work

I have a network with a linux redhat 5.1 box doing IP masq. I have a router
hooked to the net via isdn . The linux has 2 nics. One on the net side
206.xxx.xxx.xxx and the other on the inside 192.168.25.1. This linux box is
also the mail server. everyone on the inside can access the net just fine.
What I need to setup is this. I have users who need to access files on the
NT and Novell servers on the inside on the network from home. Can users
dialin to there ISP and tunnel from a win95/98 system to the linux box and
get an internal IP on the tunnel interface that will in turn give them
access to everything on the inside network? I know if I had a WinNT box as
the firewall/proxy This would work pretty good with pptp, but I don't want
to put the NT box directly on the net.

Is mobleip what I need to setup? 

And also would it be possible to tunnel from a Cisco router to a linux box.
with the same setup instead of a windows system

John Lord([EMAIL PROTECTED])
Network Administrator
Byte Size Inc.
www.beachin.net

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
For daily digest info, email [EMAIL PROTECTED]



Re: [masq] [masq] Problems with 2.2.0-kernel MASQ

1999-01-31 Thread Charles Curley

At 01:20 AM 1/30/99 +0100, Christoph Monig wrote:


Fuzzy Fox wrote:

 What type of loader format are you using?  zImage or bzImage?  Some
 systems don't seem to work right with bzImage.

I tried zImage and it worked !
Thank you for your help. I don't understand it, though.

Glad it worked. B2 (bzImage) is a fairly new compression algorithm, where
GZIP (zImage) is much older. I suspect that the B@ implementation has a bit
of debugging to go, and that may be what you hit.


-- C^2

I have sworn upon the altar of God eternal hostility against every form of
tyranny over the mind of man.
-- Thomas Jefferson, letter to Benjamin Rush, 1800 A.D.

Thomas Jefferson, Patron Saint of the Internet:
http://w3.trib.com/~ccurley/Jefferson.html
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
For daily digest info, email [EMAIL PROTECTED]



[masq] IP encap with masquerade?

1999-01-31 Thread wf3r

I'm new to linux (a few weeks) and have an "oddball" problem with IP
masquerading I can't figure out. I won't go into a long explanation of
my problem because it may be so specialized I'm afraid to waste
everyones time and bandwidth.

The quick explanation is I have a ham radio TCP/IP application called
JNOS that I've always used. It uses IP encapsulation to route packets
through a gateway, allowing my system to be reached from the internet.
It does the dialing and routing and establishes a "link" (setting the
encapped route back to me) to this net connected gateway via my regular
dynamic assigned ppp account. I have been routing my linux native TCP/IP
and another SLIP linked box through this. The problem is that ALL this
traffic goes through this gateway when I really only need to route my
class C net through it.

This weekend I set up linux ppp dialing, a means of keeping my
connection up and IP masquerading. It all works beautifully and now
my linux kernel, my SLIP linked box and my JNOS program can all reach
the internet. The problem is that I now see nothing coming back from
the gateway that I link to that should be sending my encapped packets
back to me. Normally my packets go out to this gateway using my ppp
dynamic address but return from this gateway with a second IPIP
header which is the ecapsulated packet. I see nothing coming back. This
means either I'm never reaching the gateway with my UDP packet that
sets up the routing on his end, or his encapsulated packets are not
reaching me through IP masquerading. Anyone have any clues? If you're
familiar with the JNOS program, it would help. This was long but
believe me, after 18 hours of fooling with it, I could have added A
LOT! I'll be glad to add details to anyone interested, on or off
the list. TIA...


-- 
Scott Felton - Mount Joy, PA USA
Slackware Linux v.3.6.0
[EMAIL PROTECTED]
http://www.k3ir.ampr.org


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
For daily digest info, email [EMAIL PROTECTED]



Re: [masq] [masq] Starcraft with kernels 2.2.x

1999-01-31 Thread mumford

On Sun, 31 Jan 1999, Kristopher A. Kersey wrote:

 Date: Sun, 31 Jan 1999 12:29:40 -0500
 From: "Kristopher A. Kersey" [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Cc: MASQ Mail List [EMAIL PROTECTED]
 Subject: Re:  [masq] Starcraft with kernels 2.2.x
 
 Actually I'm not.  I was wondering what utility I should use with 2.2.x,
 ipportfw or ipmasqadm.  Also that means I need to enable it in the
 kernel right?  What's a simple command to enable that?  Also, do I need
 to have ipautofw enabled in the kernel?  Do have have to run anything to
 turn it on?  I hope I don't sound ignorent but I just am not fluent in
 the area and nothing I read I strait forward.

You should be using ipmasqadm.  The commands are
# ipmasqadm portfw -a -P tcp -L $1 6112 -R $2 6112
# ipmasqadm portfw -a -P tcp -L $3 6112 -R $2 6112
# ipmasqadm portfw -a -P udp -L $1 6112 -R $2 6112
# ipmasqadm portfw -a -P udp -L $3 6112 -R $2 6112

Replace $1 with the internal IP address of your gateway machine, $2
with the address (internal again, but it should be the only) of the
machine you're playing starcraft on and $3 with the external IP ad-
dress of the gateway machine.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
For daily digest info, email [EMAIL PROTECTED]