RE: RE: [leaf-user] Shorewall Port Forwarding

2005-01-20 Thread Joey Officer
Yes, because the system is performing NAT, then (even at the most basic level) a firewall is in place. What you will need to do is find the configuration to disable, and make the netgear a passthrough device, so that it doesn't perform any inspection at all, and treats the eth1 connection strictly

RE: RE: [leaf-user] Shorewall Port Forwarding

2005-01-20 Thread Barry Baldwin
Hey Joey, You are correct, the Netgear has an uplink or WAN port that is connected to eth1 of the LEAF box. The Netgear router has 4 wired ports and my game server is connected to one of them. The Netgear hands out IP's to wireless clients and to clients connected to the wired ports as well. The

Re: [leaf-user] Shorewall Port Forwarding

2005-01-20 Thread Tom Eastep
Barry Baldwin wrote: > > > Would a better solution be to turn my leaf box into a wireless router and > get rid of the Netgear? > > Or run your LEAF box as a bridge (which is fundimentally like a switch). See http://shorewall.net/Bridge.html. -Tom -- Tom Eastep\ Nothing is foolproof to a s

Re: RE: [leaf-user] Shorewall Port Forwarding

2005-01-20 Thread jofficer
Sorry for comming late to this thread, but I thought I'd add my 2 cents. Barry, from your earlier description of your setup, I have a question and a possibly suggestion. The Netgear device, I assume has atleast the one uplink port, which is what's tied into the LEAF box, from there, the Netgea

RE: [leaf-user] Shorewall Port Forwarding

2005-01-20 Thread Barry Baldwin
Thanks Tom and Huy for your responses. I tried changing my leaf box to forward port 6112 to 192.168.1.4 and then set the Netgear router to port forward 6112 to my game server (192.168.2.3). This didn't seem to work either. The FORWARD:REJECT errors went away though. :) I'm not sure what is mea