/* HINT: Search archives @ http://www.indyramp.com/masq/ before posting! /* ALSO: Don't quote this header. It makes you look lame :-) */
<snip> > Message: 1 > Date: Thu, 8 Aug 2002 06:54:22 -0500 > From: "Jamin W. Collins" <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > > - What kernel are you running? (2.2.x or 2.4.x) 2.4.x > - What tool are you trying to use? (ipchains or iptables) ipchains > - What steps have you taken so far? Well, ipmasq is working ok...I have everything set to enable forwarding..(ipmasq, portfw,) I just don't know what rules I should add to ipchains(?) or how to configure ipmasqadm properly... > > Forwarding the internal machines out and allowing their responses in > will > most likely be no problem. However the reverse gets a bit tricky. > With > only one external IP, there is little to no way to know what internal > machine an external request is for unless the internal machine > initiated > communication. It is possible to route external requests to a > dedicated > internal machine. Actually, forwarding from the router (udp packets destined to port 6112 of masqd machines) and vice versa towards the internet is the problem. I can see icmp port unreachables error messages being generated by the router to the src hosts who sent those udp packets, assuming that the router does not know how to forward that to the internal machines, however tcp packets gets thru ok... __________________________________________________ Do You Yahoo!? HotJobs - Search Thousands of New Jobs http://www.hotjobs.com _______________________________________________ Masq maillist - [EMAIL PROTECTED] Admin requests can be handled at http://www.indyramp.com/masq-list/ -- THIS INCLUDES UNSUBSCRIBING! or email to [EMAIL PROTECTED] PLEASE read the HOWTO and search the archives before posting. You can start your search at http://www.indyramp.com/masq/ Please keep general linux/unix/pc/internet questions off the list.
