23 Jul
2000
23 Jul
'00
16:42
Anyone knows how to handle an "IP-aliased system" with SuSEfirewall? I've setup eth0:0....eth0:4 with Yast and configured Bind8. The system works well. Problem is that with SuSEfirewall routing/masquerading has to be set to "yes" and eth0:0....eth0:4 are treated as non-local (routing/masquerading "no" --> DENY). Filling FW_DEV_INT with "eth0 eth0:0 eth0:1..............." and making FW_DEV_INT_eth0:0....... FW_DEV_INT_eth0:4 leads to some ipchains error in which .168.10.1 cannot be found. How to handle ? thank you, peter
8689
Age (days ago)
8689
Last active (days ago)
0 comments
1 participants
participants (1)
-
Peter ten Have