I have everything filtered. and the problem is that I should this from the
server, and that's not what I need, I need to check from the client if the
server is running. But probably this server works as NMAP or NC, look at
this part of man nmap:

UDP scan works by sending an empty (no data) UDP header to every targeted
port. If an ICMP port unreachable error (type 3, code 3) is
              returned, the port is closed. Other ICMP unreachable errors
(type 3, codes 1, 2, 9, 10, or 13) mark the port as filtered. Occasionally,
a
              service will respond with a UDP packet, proving that it is
open. If no response is received after retransmissions, the port is
classified
              as open|filtered. This means that the port could be open, or
perhaps packet filters are blocking the communication. Versions scan (-sV)
can
              be used to help differentiate the truly open ports from the
filtered ones.

On Mon, Jan 11, 2010 at 6:59 PM, Thomas Reifferscheid <
tho...@reifferscheid.org> wrote:

> Point your browser to http://www.utorrent.com/testport?port=1194
> to get an idea if there is a [openvpn] daemon listening on udp/1194
>
> HTH
> T
>
> Lucas Mocellin schrieb:
>
>  Hello,
>>
>> again I fell in this problem, I must solve this now, so if someone has a
>> better idea than trying to reproduce the OpenVPN protocol begin and see if
>> there is any answer, I will have to figure out how to send the OpenVPN
>> protocol by UDP manually.
>>
>> I would like to see if there is a simpler manner to check if OpenVPN is
>> listenning and accepting connections.
>>
> ...
>
>

Reply via email to