Quote:
Originally Posted by win32sux
Only for traffic headed toward another network segment. He/she will be free to attack all hosts on all of your subnets if they're on the same segment, regardless of your firewall rules. If you really want to firewall the two subnets from each other, put each in its own segment (use a dedicated NIC on the firewall for each).
|
Shit, i was about to add another NIC to my box and well, i dont have any more PCI slots...
Regardless of that security issue discussed in the thread, check please if this is "enough"
eth2 -> 192.168.1.0
eth2:0 ->192.168.50.0
eth1 and eth0 are the net interfaces, 1 router each to provide wan failover (not implemented here)
Hosts:
Quote:
loc1 eth2:192.168.1.0/24
loc50 eth2:192.168.50.0/24
|
Interfaces
Quote:
net6 eth0 detect
net7 eth1 detect
- eth2 192.168.1.255,192.168.50.255
|
Masq
Quote:
eth0 eth2
eth1 eth2
eth2 eth2
|
Policy
Rules
SECTION NEW
Zones
Quote:
fw firewall
net6 ipv4
net7 ipv4
loc1 ipv4
loc50 ipv4
|
Problems / Doubs:
1) Is the hosts file required?
2) I guess i need doing masq from local to each external, and also from local to local even if they share the same interface, hence the eth2 eth2 in the masq file...
3) So is shorewall well implemented in these scritps to handle aliases?
