Hi,

First: do you have two server instances listening on both proto/port 
combinations ?

Second: Your config will cycle through each connection block until it 
connects
(presuming you do not use --remote-random)

A MUCH more appropriate solution would be to have TWO separate config files
and use them as and when appropriate. IE Manual Fallback ...

NOTE: Just because you specify HTTP port 80 does not mean an intervening
firewall is not capable of detecting a NON HTTP protocol and blocking you 
anyway.

regards


----- Original Message ----- 
From: "Stefan Szabo" <stefan.sz...@rcs-rds.ro>
To: <openvpn-users@lists.sourceforge.net>
Sent: Tuesday, October 20, 2015 8:58 PM
Subject: [Openvpn-users] client config fallback from 1194 udp to 80 tcp


>
>>
>> hi to you all,
>>
>>
>> does anyone knows how it’s possible to put in client config declarations 
>> to fallback from udp port 1194 to tcp port 80?in case i’m in a place 
>> where udp is filtered to be able to conect over tcp 80.
>>
>> i tried all the possibilities but nothing seems to work for me.i tested 
>> with tunnelblick, are this options openvpn client dependent?
>>
>> the last cfg:
>>
>> <connection>
>> remote x.x.x.x
>> port 80
>> proto tcp
>> </connection>
>> <connection>
>> remote x.x.x.x
>> port 1194
>> proto udp
>> </connection>…...
>>
>> thanks!
>>
>>
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Openvpn-users mailing list
> Openvpn-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/openvpn-users
> 


------------------------------------------------------------------------------
_______________________________________________
Openvpn-users mailing list
Openvpn-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-users

Reply via email to