Hi Joe On 25-08-2015 16:39, Joe Patterson wrote: > What does the routing table look like? The fact that you can ping makes > this seem unlikely, but other than that it sounds like it *might* be > getting dropped by urpf. (that's the only place I can think of between > where libpcap would see it but a listening socket wouldn't, other than > iptables which you've already covered.)
Here are the relevant client's routing table entries: Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.8.0 0.0.0.0 255.255.255.0 U 0 0 0 br0 172.31.0.1 172.31.0.5 255.255.255.255 UGH 0 0 0 tun0 172.31.0.5 0.0.0.0 255.255.255.255 UH 0 0 0 tun0 192.168.1.0 172.31.0.5 255.255.255.0 UG 0 0 0 tun0 The route to 192.168.1.0/24 is there. Regarding Reverse Path Filtering (server side): $ for i in /proc/sys/net/ipv4/conf/*/rp_filter ; do > echo -n "$i: "; cat $i > done /proc/sys/net/ipv4/conf/all/rp_filter: 1 /proc/sys/net/ipv4/conf/br0/rp_filter: 0 /proc/sys/net/ipv4/conf/default/rp_filter: 0 /proc/sys/net/ipv4/conf/eth0/rp_filter: 0 /proc/sys/net/ipv4/conf/eth1/rp_filter: 0 /proc/sys/net/ipv4/conf/lo/rp_filter: 0 /proc/sys/net/ipv4/conf/ppp0/rp_filter: 0 /proc/sys/net/ipv4/conf/sit0/rp_filter: 0 /proc/sys/net/ipv4/conf/tun0/rp_filter: 0 /proc/sys/net/ipv4/conf/vlan0/rp_filter: 0 /proc/sys/net/ipv4/conf/vlan1/rp_filter: 0 On the client side, the rp_filter of all interfaces is also 0. Thanks, Tiago ------------------------------------------------------------------------------ _______________________________________________ Openvpn-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openvpn-users
