We have the following configuration: 2 ISP''s, an interface connecting to our internal lan (loc) and another connecting to a Wireless Netwrok (PWiFi). computers on the loc are able to access the internet just fine, but users in PWiFi cannot, though they used to in a previous version we were running (3.2 I think) We are currently running 4.0.5 using shorewall-perl. I have attached the output of shorewall dump. Hopefully this will help. The policy file shows: $FW net ACCEPT $FW loc ACCEPT $FW PWiFi ACCEPT loc net ACCEPT PWiFi net ACCEPT net $FW DROP info net all DROP info all all REJECT info The Masq File Shows: eth0 209.121.98.100 70.68.128.150 eth1 70.68.128.150 209.121.98.100 #VPN Support eth0 192.168.42.6 70.68.128.150 47 eth1 192.168.42.6 209.121.98.100 47 eth4 192.168.42.6 192.168.44.254 47 eth0 eth4 eth0 eth3 eth1 eth4 eth1 eth3 Can any on help? ------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
drz@zeron.ca wrote:> We have the following configuration: > > 2 ISP''s, an interface connecting to our internal lan (loc) and another > connecting to a Wireless Netwrok (PWiFi). computers on the loc are able > to access the internet just fine, but users in PWiFi cannot, though they > used to in a previous version we were running (3.2 I think) > > We are currently running 4.0.5 using shorewall-perl. > > I have attached the output of shorewall dump. Hopefully this will help.You have failed to include eth4 in the COPY column in /etc/shorewall/providers. -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ teastep@shorewall.net PGP Public Key \ https://lists.shorewall.net/teastep.pgp.key ------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
On Thu, 29 Nov 2007 09:59:02 -0800, Tom Eastep <teastep@shorewall.net> wrote:> drz@zeron.ca wrote: >> We have the following configuration: >> >> 2 ISP''s, an interface connecting to our internal lan (loc) and another >> connecting to a Wireless Netwrok (PWiFi). computers on the loc are able >> to access the internet just fine, but users in PWiFi cannot, though they >> used to in a previous version we were running (3.2 I think) >> >> We are currently running 4.0.5 using shorewall-perl. >> >> I have attached the output of shorewall dump. Hopefully this will > help. > > You have failed to include eth4 in the COPY column in > /etc/shorewall/providers. >Thanks, I figured it would be something the simple, but couldn''t find it. It is working well now. ------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4