[Shorewall-users] Wireless - routing or bridging - Part Deux

[<Bil...@kp...>]

I have added a 4th NIC to my setup, and want to set up wireless.  I have 
stared at the configuration Tom has for the last week, and my eyes are 
crossing.

eth0 "net" goes to my internet connected firewall with a 192.168 address
eth1 "loc" goes to my switch connected to local switch also 192.168.x
eth2 "work" goes to my office with a 172. address

eth3  Trying to follow Tom's "My Shorewall Configuration" I gave the eth3 
NIC 192.168.y.1 and a Cisco AP350 a 192.168.y.2 address.  In trying to be 
"visitor friendly" (the intent is just add your MAC address) and let the 
visitor act like they're at their local Starbucks and get a DHCP address.

The Cisco hands out a 169. something address via DHCP.

So, I'll ask the question and duck....  Am I looking at solving routing, 
or do I have to do bridging ?   Or, which section of the RTFM did I miss?

My test laptop can browse the AP350, and this shorewall box can browse the 

AP350.  I can also browse the AP350 from other local machines (windoze or 
linux).  I am running shorewall 2.2.0.

- Bill

========================

By "browse" I mean I can see the Cisco AP350 setup screens...

NOT browse the internet from the laptop

========================