On 5/1/2014 11:07 AM, Marcello Giordano wrote: > Hi, > > I edited the providers file to this : > > #NAME NUMBER MARK DUPLICATE INTERFACE GATEWAY > OPTIONS COPY > Coop 1 1 - wlan1 192.168.1.1 > track,balance > VPN 2 2 - tun0 detect > track,fallback > > and removed the 998 routing rule. USE_DEFAULT_ROUTE is still set to Yes. > As soon as I start the VPN and restart shorewall, all traffic is still > routed by default through the vpn interface... > I attach a dump-pull.gz for this configuration. > > I tried to insert a route-nopull option into the ovpn config file. When > i restart shorewall, all traffic is correctly routed through wlan1 by > default, and through the vpn if i bind applications to tun0. The mark in > tcrules for user rtorrent is still not working though.. the user has no > network access whatsoever.
So this is a user running processes on the firewall itself? If so, packet marking is unreliable as clearly described at http://www.shorewall.org/MultiISP.html#Local. What exactly does 'no network access whatsoever' mean? Can the user ping 10.8.0.5, for example? How about 192.168.1.1? -Tom -- Tom Eastep \ When I die, I want to go like my Grandfather who Shoreline, \ died peacefully in his sleep. Not screaming like Washington, USA \ all of the passengers in his car http://shorewall.net \________________________________________________
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available. Simple to use. Nothing to install. Get started now for free." http://p.sf.net/sfu/SauceLabs
_______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
