Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
Sarah McGlinchey wrote: > Are you using a routed or bridged VPN? How are you determining that > these packets are never reaching the DNS server? > > Since pings work, it is unlikely this is an OpenVPN issue or a > networking issue. If OpenVPN is using a different subnet, you want to > verify the nameserver will respond to queries from the new subnet. > Check the service for IP restrictions, as well as any firewall rules > on the nameserver and OpenVPN server. I'm using the routing mode, with the tun interface. I did add a route to the default router that passes all packets for the vpn subnet to the vpn server's real ip address. I opened port 1194 for both tcp and udp on the vpn server and on the pix firewall. I echoed a "1" into /proc/sys/net/ipv4/ip_forward on the vpn server. When I set up a tunnel from my machine at home, nslookup and dig both time out without returning information from the nameserver, which tells me the nameserver either isn't receiving the queries, or isn't responding to them. -- John Abreau / Executive Director, Boston Linux & Unix ICQ 28611923 / AIM abreauj / JABBER jabr at jabber.org / YAHOO abreauj Email jabr at blu.org / WWW http://www.abreau.net / PGP-Key-ID 0xD5C7B5D9 PGP-Key-Fingerprint 72 FB 39 4F 3C 3B D6 5B E0 C8 5A 6E F1 2C BE 99
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |