[OpenVPN home] [Date Prev] [Date Index] [Date Next]
[OpenVPN mailing lists] [Thread Prev] [Thread Index] [Thread Next]
Google
 
Web openvpn.net

Re: [Openvpn-users] --// FreeBSD4.11 gateway <---> WindowsServer2003 gateway // *MYSTERIOUS* problem


  • Subject: Re: [Openvpn-users] --// FreeBSD4.11 gateway <---> WindowsServer2003 gateway // *MYSTERIOUS* problem
  • From: Erich Titl <erich.titl@xxxxxxxx>
  • Date: Thu, 05 Oct 2006 23:00:31 +0200

Hello Leonid

Leonid Satanovsky wrote:
> Greetings, people. My name is Leonid. 
> 
> -----------------------------------------------------------------
> OUR CONFIGURATION:
> 
>     <LAN_1> <-->  {FreeBSD4.11 <tun>} <----o----> {<tun> WindowsServer2003} <--> <LAN_2> 
> 
> -----------------------------------------------------------------
> 
> THE PROBLEM:
> 
>     After openvpn daemons/services are up and all the stuff is ready ... 
> 
> (case 1 (the problematic situation))
> 
>     I am not able to get ``icmp-echo'' answer while pinging 
>     {WindowsServer2003} gateway from FreeBSD gateway or any machine in LAN_1.
> 
>     While analysing arp-tables at {WindowsServer2003} I find that MAC address for the
>     FreeBSD's tun adapter is wrong: 00-00-00-00-00-00... 
> 
> (case 1.1)
>     If I ping any machine (except the gateway) in <LAN_2> from any machine in <LAN_1>
>     something happends and I recieve the ``icmp-echo'' answer ...
>     and after this I get ability (just for a while) to 
>     ping {WindowsServer2003} (the gateway of <LAN_2>)
> 
> (case 2)
>     I am always able to ping any machine in <LAN_1> from any machine of <LAN_2>
> 
> ----------------------------

What a beautiful world this could be if we would not get assumptions but
facts. Please get some hard facts on your failures, e.g. let us know
your exact configuration (including addresses of the networks in question).

If you want to disguise them, do it consistently, please.

Please also add tcpdump snippets or even better files for us to analyze
of all interfaces (including tun interfaces) with reasonable timestamps.
We, or rather you, need to know where a packet comes from, where it is
supposed to go and which way it is supposed to take. A little bit of
ascii art is fine, but often the details only tell the whole story. And
while we're at it, please also include the configs and routing tables
before and after the tunnel got up.

Most of the time these problems stem from either routing or firewalling
misconfiguration. It is very possible that you find the reason yourself
while preparing all the information for the list.

> 
>     I really hope there is some solution,

Oh there is, (most of the time at least :-) )  the collective knowledge
in this list is amazing.

Good luck

Erich


Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Openvpn-users mailing list
Openvpn-users@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/openvpn-users

Warning: require_once(../../../archive_common.php) [function.require-once]: failed to open stream: No such file or directory in /home/openvpn/domains/openvpn.net/public_html/archive/openvpn-users/2006-10/msg00062.html on line 245

Fatal error: require_once() [function.require]: Failed opening required '../../../archive_common.php' (include_path='/usr/local/lib/php') in /home/openvpn/domains/openvpn.net/public_html/archive/openvpn-users/2006-10/msg00062.html on line 245