1 May 2008 17:56
Need help getting IPSEC VPN to work with Shorewall
Timothy Selivanow <timothy.selivanow <at> virtualxistenz.com>
2008-05-01 15:56:28 GMT
2008-05-01 15:56:28 GMT
I've looked at a number of docs for a couple of days now, and while I've made some progress, I've hit a wall that is baffling me. I've attached the output of `shorewall dump` from the two machines. Both are running CentOS 5, Shorewall 3.4.6 (I'm willing to upgrade, but I didn't think that the conf would be too different than 4.x, so I wanted to get the VPN up first), and both are using the 'Red Hat' way of configuring IPSEC (as you can see from the output of `shorewall dump`, the VPN does negotiate...) and it is a network-to-network tunnel. On one host (calling it 'host1' in this email) when ever I try to ping the other network (other is 192.168.42.0, and it doesn't matter what host I try to ping, from what host), I get logs like the following: Shorewall:all2all:REJECT:IN= OUT=eth0 SRC=192.168.47.1 DST=192.168.42.1 LEN=84 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=ICMP TYPE=8 CODE=0 ID=55376 SEQ=1 On the other host (calling it 'host2'), I get a completely different log: Shorewall:OUTPUT:REJECT:IN= OUT=eth0 SRC=69.30.99.148 DST=69.30.46.20 LEN=136 TOS=0x00 PREC=0x00 TTL=64 ID=25966 DF PROTO=ESP SPI=0xccd0a1c Host1 is a Xen server, with the following network configurations: #Interface Xen bridge Role/routing/forwarding eth0 xenbr0 plain bridge, 69.30.46.0/24 dummy0 xenbr1 NAT to eth0, 192.168.47.0/24 dummy1 xenbr2 nothing, 10.42.47.0/24(Continue reading)
RSS Feed