[Shorewall-users] Problem with routing

2006-10-09 Thread Jan van der Vyver
Hi All I have the following setup Users --- Machine A --- Machine B --- Machine C From machine A to B: Ipsec VPN Allows 192.168.10.0/24 (Users) to connect to 192.168.20.0/24 (Network on machine B) From machine B to C: Ipsen VPN Allows 196.44.33.118 to coccent to

Re: [Shorewall-users] Problem with routing

2006-10-09 Thread Tom Eastep
Jan van der Vyver wrote: Hi All I have the following setup Users --- Machine A --- Machine B --- Machine C From machine A to B: Ipsec VPN Allows 192.168.10.0/24 (Users) to connect to 192.168.20.0/24 (Network on machine B) From machine B to C: Ipsen

Re: [Shorewall-users] FW: Problem with routing

2006-10-09 Thread Jan van der Vyver
DNAT:info net:192.168.10.0/24 net:192.168.241.65 all - - 192.168.20.33 But for that packets to go to 192.168.241.65 the source must be also rewritten to 196.44.33.118. Any ideas? In Shorewall, all source address rewriting is accomplished using entries in

Re: [Shorewall-users] FW: Problem with routing

2006-10-09 Thread Tom Eastep
Tom Eastep wrote: Jan van der Vyver wrote: I am trying to ssh from a machine (192.168.10.198) behind machine A (192.168.10.200) to 192.168.20.33. Between machine A and machine B there is a ipsec vpn. Config for this vpn: conn in2one-to-adept type=tunnel

Re: [Shorewall-users] FW: Problem with routing

2006-10-09 Thread Jan van der Vyver
I got a bit ahead of myself -- I'm correct that to do this right, you need policy match. But you should be able to get it to work if we can determine why your ruleset drops most traffic to/from 192.168.241.65. Please send me a tar-ball of your /etc/shorewall/ directory. Ah -- I see.