Am 27.04.2014 15:01, schrieb Michael Kress: > > Once the connection is up, it's fine with the above effect (martian). > After a while, the connection drops and cannot reconnect. > From that moment, the two counters "TX dropped" and "Tx bytes" go up.
... that is resolved now, the openvpn connection is working flawlessly - I had to tell shorewall: ok, if you synchronize your connection to the vpn server over udp, don't do that over tun1 (which makes noch sense) but over provider tonline (so it comes to the right interface). Thus, my rtrules looks like this: #################################################################################### #SOURCE DEST PROVIDER PRIORITY MARK 192.168.0.0/24 - tonline 1002 2 - x.x.x.x.18/32 tonline 1000 - x.x.x.x.245/28 ipev 1001 whereas .18 is the vpn server and .245 is the ip address of my side of the vpn tunnel on tun1; the /28 spans tun1 and it's p-t-p remote address .254. Now there is no openvpn reconnect issue anymore. ==> great. Remaining issue: Hosts from 192.168.0.0/24 LAN cannot ping outbound or do anything outbound. There's no drop, no reject, the packets arrive on eth0 (192.168.0.1) of shorewall and won't get forwarded to the gateway 192.168.2.1 via shorewall's eth1 (192.168.2.251). ==> Do I need another line in rtrules for that or how can I accomplish that? Please don't forget, that I use USE_DEFAULT_RT=Yes TIA Michael ------------------------------------------------------------------------------ Start Your Social Network Today - Download eXo Platform Build your Enterprise Intranet with eXo Platform Software Java Based Open Source Intranet - Social, Extensible, Cloud Ready Get Started Now And Turn Your Intranet Into A Collaboration Platform http://p.sf.net/sfu/ExoPlatform _______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
