Simon Hobson wrote:
> Tom Eastep wrote:
>
>> Or, you can turn of NAT in your wireless router. But if you do, you need
>> to update your routing on the firewall.
>
> Do you think :
>
> Turn off NAT in wireless router & put it's WAN IP on a different
> subnet to the 'loc' subnet.
>
> would be be
> See? You don't even have a route to 192.168.2.0/24!
>>
>> # cat /etc/shorewall/hosts (comments removed)
>> loc eth5:192.168.168.0/24
>> loc2eth5:192.168.2.0/24
>
> So the definition of loc2 is completely silly. It should be
> eth5:192.168.168.13.
>
> Now, loc2 will be a sub-zone of loc an
Tom Eastep wrote:
>Or, you can turn of NAT in your wireless router. But if you do, you need
>to update your routing on the firewall.
Do you think :
Turn off NAT in wireless router & put it's WAN IP on a different
subnet to the 'loc' subnet.
would be better/easier to manage ?
Ie, the connectio
Tom Eastep wrote:
> lounds wrote:
>> Hello everyone! I am a relatively newbie to Shorewall, but have been
>> fruitlessly trying to get two "local zones" that cannot access the
>> each other. My Shorewall box is maxed out with 4 NICs, so I cannot
>> just add another NIC.
>>
>> http://www.shorewall.n
lounds wrote:
> Hello everyone! I am a relatively newbie to Shorewall, but have been
> fruitlessly trying to get two "local zones" that cannot access the
> each other. My Shorewall box is maxed out with 4 NICs, so I cannot
> just add another NIC.
>
> http://www.shorewall.net/Multiple_Zones.html#Pa
Hello everyone! I am a relatively newbie to Shorewall, but have been
fruitlessly trying to get two "local zones" that cannot access the
each other. My Shorewall box is maxed out with 4 NICs, so I cannot
just add another NIC.
http://www.shorewall.net/Multiple_Zones.html#Parallel
I have a wireless
