Quoting Dale Hartung <[EMAIL PROTECTED]>: > John > > Don't go off and enable policy match if you don't have to! Policy match > is has been my bane for the last year. I just wanted to make sure it > wasn't the source of your problems....., because it was the source of > mine at one point. I also had problems with the kernel < 2.6.11 which > I see you are running.....but Tom would know more about that.... > > Your remote system should allow traffic "opposite" of what you are > allowing on the client system. Perhaps you could review my configs: > http://scope.dghartung.com/index.php/Shorewall_Config_for_VPN > > bear in mind these may not be perfect or apply to your situation > > Dale
Too late, arrghhh!! Only joking. By getting OpenVPN to push it's route as the default gateway to the client machine and then testing port 5500 works, I have proved that the setup works in principle I think. Getting the traffic back from the VPN client to the VPN server and on to the remote system without a default route seems to be the crux of my problem. I will take a look at your configs and see if that throws anything up. Thanks again, John. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
