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

Re: [Openvpn-users] snmp over vpn


  • Subject: Re: [Openvpn-users] snmp over vpn
  • From: Jon Bendtsen <jon.bendtsen@xxxxxxxxxx>
  • Date: Wed, 5 Apr 2006 20:04:12 +0200

Please dont do top postings.

Den onsdag 5.apr kl. 17:27 skrev ... ...:

First and foremost, I'm enormously grateful for your
effort of trying to help me. Thank you.

Below is my network.
10.13.38.6   - IP of VPN client
10.13.38.1   - IP of VPN server
10.11.38.100 - LAN IP of VPN server
10.11.38.101 - LAN IP
10.11.38.202 - LAN IP of SNMP box

Here's what I found: from the VPN client I can ping
everything on the LAN, ie. 10.11.38.100, 10.11.38.202,
etc. I can also telnet and ftp into 10.11.38.102. I
can telnet, ftp, and ssh into 10.11.38.101.

from SNMP box I can ping 10.11.38.100, 10.13.38.1 (VPN
side of server) but I cannot ping 10.13.38.6 (watching
packet sniffer I can say that 10.13.38.6 receives the
request but never replies). This box has 10.11.38.100
as its gateway.

does it send the reply to the 10.11.38.100 gateway? Is there a firewall somewhere that prevents the answer?



from VPN server I can ping 10.11.38.202, but I cannot
across the VPN tunnel ping 10.13.38.6 (I can ping
10.1.1.8, which is the 'regular' IP of the VPN client
but not the VPN interface).

sounds a little like a firewall problem.



JonB

____________________________________________
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-04/msg00092.html on line 201

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-04/msg00092.html on line 201