search for: eth2_masq

...work with kernel 2.6.11, but to no avail :( There seems to be some problem with nat, whereupon iptables cannot set it up. Kernel compiled on base of mandrake kernel-source, patched with ipp2p and the ipsec patches from Tom''s contrib. Here''s the error: /sbin/iptables -t nat -A eth2_masq -s 192.168.0.0/23 -d 0.0.0.0/0 -j MASQUERADE iptables: Invalid argument error_message ''ERROR: Command "/sbin/iptables -t'' nat -A eth2_masq -s 192.168.0.0/23 -d 0.0.0.0/0 -j ''MASQUERADE" Failed'' Attached are: output of "shorewall debug restar...

...ination net_dnat all -- 0.0.0.0/0 0.0.0.0/0 net_dnat all -- 0.0.0.0/0 0.0.0.0/0 loc_dnat all -- 0.0.0.0/0 0.0.0.0/0 Chain POSTROUTING (policy ACCEPT) target prot opt source destination eth1_masq all -- 0.0.0.0/0 0.0.0.0/0 eth2_masq all -- 0.0.0.0/0 0.0.0.0/0 Chain OUTPUT (policy ACCEPT) target prot opt source destination Chain eth1_masq (1 references) target prot opt source destination MASQUERADE all -- 192.168.0.0/24 0.0.0.0/0 Chain eth2_masq (1 references) target...

...destination net_dnat all -- anywhere anywhere net_dnat all -- anywhere anywhere loc_dnat all -- anywhere anywhere Chain POSTROUTING (policy ACCEPT) target prot opt source destination eth1_masq all -- anywhere anywhere eth2_masq all -- anywhere anywhere Chain OUTPUT (policy ACCEPT) target prot opt source destination Chain eth1_masq (1 references) target prot opt source destination masq2 all -- 192.168.2.0/24 anywhere Chain eth2_masq (1 references) target...

...ALHOSTA 192.168.0.142 We now want to route all traffic coming from another host through that link too _but_ only for a specific port, all other traffic is to still flow through ISP1. I added a rule just like the one that is generated by shorewall for the above entry: iptables -t nat -I eth2_masq -p tcp -s InternalhostA --dport 2525 -j SNAT --to-source 192.168.0.142 In the tcrules file I mark all traffic that I want to route through ISP2. /etc/shorewall/tcrules: 1:P $INTERNALHOSTA 0.0.0.0/0 tcp 2525 Then I tell iproute to route everything with that mark to...

...41240 wiredc_dnat all -- eth2 * 0.0.0.0/0 0.0.0.0/0 4 478 wave_dnat all -- eth3 * 0.0.0.0/0 0.0.0.0/0 Chain POSTROUTING (policy ACCEPT 846 packets, 50852 bytes) pkts bytes target prot opt in out source destination 0 0 eth2_masq all -- * eth2 0.0.0.0/0 0.0.0.0/0 0 0 eth3_masq all -- * eth3 0.0.0.0/0 0.0.0.0/0 Chain OUTPUT (policy ACCEPT 782 packets, 51316 bytes) pkts bytes target prot opt in out source destination Chain eth2_masq (1 references) pk...

Hi folks, Has anyone tested the changes to multiple ISPs/load balancing or routestopped in 2.4.0-RC1 yet? We need to talk about what criteria we will use for determining whether 2.4.0 is ready for release. I''ve started configuring a firewall at work with the multiple ISPs support, but its kernel doesn''t have connection marking support, so it''s going to be a couple of