Simon On Wed, Mar 15, 2017, at 02:06 PM, Simon Hobson wrote: > There's a fundamental issue there,
and THEN some! :-/ > you have two separate networks sharing the same subnet and that's a big > no-no. I'd thought that to add both interfaces to the same some, that had to be the case. Got THAT wrong. > If you want the two networks separate, then they need to have non-overlapping > IP subnets. Ok, got that now. Need to get dhcp etc sorted here in a minute. > I suspect that if you do some packet sniffing, you'll find that the reason > the wireless clients don't have a working connection is because the return > packets are being sent out on eth1 rather than wlan1. I did tcpdump on the wlan interface -- and saw lots of packets going OUT, but not returning. Couldn't even get a ping response when pinging from my phone to the AP ip. Which has me confused, since I'm obviously "hearing" from the DHCP server. Let me get that non-overlapping bit straightened out ... DT ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Shorewall-users mailing list Shorewall-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/shorewall-users
