Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Router problems with VPN
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Networking & Security
View previous topic :: View next topic  
Author Message
jbo5112
n00b
n00b


Joined: 16 Nov 2005
Posts: 19

PostPosted: Mon Feb 11, 2008 10:18 pm    Post subject: Router problems with VPN Reply with quote

For work I'm doing, I have to connect through a Juniper Networks VPN. They previously had everything misconfigured so the route table was constantly being set to send all your internet data through the vpn as a gateway, when the other end of the gateway didn't care about routing to anything other than their lan. They've migrated to a different version, with a client that says "Secure Application Manager Version 6.0.0.12.141". Now the internet works while signed in, but it works with very few of our systems. It doesn't do anything on a Windows XP x64 box, every linux box I've tried just says the OS/platform isn't supported (even on machines that were working with it), and the worst is that it won't work with some routers. We have some routers at the office that function just fine, along with my parent's cheap D-Link wi-fi router, but there's a cheap Netgear router that won't work with the VPN. My Gentoo box that doubles as a router at home doesn't work either. I have every single option enabled under Netfilter. Everything else routes just fine and the VPN will even sign in, but the VPN link is dead. I don't know where to begin debugging this.

Currently, my options are:
1) Fix my Gentoo router so I can use my well put together system and work quickly.
2) Remote desktop to a machine at work, then go to a different one on work's LAN that functions with the VPN, and interact with remote desktop running through two extra computers and connection speeds around 4kB/s
3) Spend too much time at the Office and don't get to see my wife or 4 month old daughter for a week or more.

*update* The routers at the office all function with the VPN. All the computers attached to the cheaper router don't work with the VPN themselves for one reason or another (mostly an unsuppported OS).


Last edited by jbo5112 on Fri Feb 15, 2008 4:39 pm; edited 1 time in total
Back to top
View user's profile Send private message
Hu
Administrator
Administrator


Joined: 06 Mar 2007
Posts: 23062

PostPosted: Tue Feb 12, 2008 4:05 am    Post subject: Reply with quote

You say "the VPN link is dead." What do you mean by this? Are you unable to pass traffic over the VPN? Is traffic sent over the VPN unable to reach your system? Start with posting the output of ip route; ip addr. If you have some way of controlling remote machines, run emerge net-analyzer/tcpdump locally and use it to sniff traffic on the VPN interface while a remote machine pings your VPN IP address. That will identify whether the traffic from the peer is reaching you at all. If it is reaching you, then you may have a firewall problem and should post the output of iptables-save -c. If it is not reaching you, then the routing on the remote end is still wrong.
Back to top
View user's profile Send private message
jbo5112
n00b
n00b


Joined: 16 Nov 2005
Posts: 19

PostPosted: Fri Feb 15, 2008 4:08 pm    Post subject: Reply with quote

I haven't been able to send information to the remote computer and get a response back. I'm having trouble figuring out how to get the remote machine to try contacting me so I can check if the packets are getting lost in my router, but it doesn't seem too easy. The remote machine is in another state so there's no direct access, I only have 1 login (but I might be able to commandeer another late at night), and I can't find my VPN IP address anywhere on the computer running the VPN client. If it's any help, the remote LAN is using IP addresses of 172.18.0.0/16 (not entirely sure on the netmask). I'm not using most of my tap devices (and probably never will), but I left them configured in case I want them for vmware. I also know my routing should be made more secure, but that's further down on my to-do list and the few services running should be secure themselves. I've also tried running the VPN on another machine that dual-boots into Windows XP Home Edition, but the following info is from one of my virtual machines running Windows 2000.

route on computer running VPN client:
Code:

===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x1000003 ...00 0c 29 52 11 98 ...... vmxnet5 VMware Accelerated AMD PCNet Adapter
===========================================================================
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0      192.168.0.1    192.168.0.10       1
        127.0.0.0        255.0.0.0        127.0.0.1       127.0.0.1       1
      192.168.0.0    255.255.255.0     192.168.0.10    192.168.0.10       1
     192.168.0.10  255.255.255.255        127.0.0.1       127.0.0.1       1
    192.168.0.255  255.255.255.255     192.168.0.10    192.168.0.10       1
        224.0.0.0        224.0.0.0     192.168.0.10    192.168.0.10       1
  255.255.255.255  255.255.255.255     192.168.0.10    192.168.0.10       1
Default Gateway:       192.168.0.1
===========================================================================
Persistent Routes:
  None


iptables /all
Code:

Windows 2000 IP Configuration

        Host Name . . . . . . . . . . . . : 32-bit_develop
        Primary DNS Suffix  . . . . . . . :
        Node Type . . . . . . . . . . . . : Hybrid
        IP Routing Enabled. . . . . . . . : No
        WINS Proxy Enabled. . . . . . . . : No
        DNS Suffix Search List. . . . . . : way.shacknet.nu

Ethernet adapter Local Area Connection:

        Connection-specific DNS Suffix  . : way.shacknet.nu
        Description . . . . . . . . . . . : VMware Accelerated AMD PCNet Adapter
        Physical Address. . . . . . . . . : 00-0C-29-52-11-98
        DHCP Enabled. . . . . . . . . . . : Yes
        Autoconfiguration Enabled . . . . : Yes
        IP Address. . . . . . . . . . . . : 192.168.0.10
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 192.168.0.1
        DHCP Server . . . . . . . . . . . : 192.168.0.1
        DNS Servers . . . . . . . . . . . : 192.168.0.1
        Primary WINS Server . . . . . . . : 192.168.0.1
        Lease Obtained. . . . . . . . . . : Wednesday, February 13, 2008 11:27:13 PM
        Lease Expires . . . . . . . . . . : Friday, March 14, 2008 11:27:13 PM


route on gentoo router:
Code:

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.0.0     *               255.255.255.0   U     0      0        0 br0
CPE-65-31-192-0 *               255.255.240.0   U     0      0        0 eth4
loopback        *               255.0.0.0       U     0      0        0 lo
default         CPE-65-31-192-1 0.0.0.0         UG    0      0        0 eth4


ifconfig (gentoo router)
Code:

br0       Link encap:Ethernet  HWaddr 00:06:29:6E:B7:10
          inet addr:192.168.0.1  Bcast:192.168.0.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1767531 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2634158 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:381091251 (363.4 Mb)  TX bytes:2483619557 (2368.5 Mb)

eth0      Link encap:Ethernet  HWaddr 00:06:29:6E:B7:10
          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:616804 errors:1 dropped:0 overruns:0 frame:1
          TX packets:646646 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:98208238 (93.6 Mb)  TX bytes:465989192 (444.4 Mb)
          Interrupt:20 Base address:0xb000

eth1      Link encap:Ethernet  HWaddr 00:06:29:6E:B7:11
          UP BROADCAST PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:19 Base address:0xb100

eth2      Link encap:Ethernet  HWaddr 00:06:29:6E:B7:12
          UP BROADCAST PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:18 Base address:0xb200

eth3      Link encap:Ethernet  HWaddr 00:06:29:6E:B7:13
          UP BROADCAST PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:16 Base address:0xb300

eth4      Link encap:Ethernet  HWaddr 00:1A:4D:56:4E:F4
          inet addr:65.31.196.94  Bcast:255.255.255.255  Mask:255.255.240.0
          UP BROADCAST RUNNING MULTICAST  MTU:576  Metric:1
          RX packets:44143365 errors:0 dropped:0 overruns:0 frame:0
          TX packets:20420164 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:15466078478 (14749.6 Mb)  TX bytes:3444975315 (3285.3 Mb)
          Interrupt:16 Base address:0x2000

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:10837179 errors:0 dropped:0 overruns:0 frame:0
          TX packets:10837179 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:12785871970 (12193.5 Mb)  TX bytes:12785871970 (12193.5 Mb)

tap0      Link encap:Ethernet  HWaddr 00:FF:4D:40:D7:0F
          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:3161304 overruns:0 carrier:0
          collisions:0 txqueuelen:500
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

tap1      Link encap:Ethernet  HWaddr 00:FF:4F:4E:27:CA
          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:22971 overruns:0 carrier:0
          collisions:0 txqueuelen:500
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

tap2      Link encap:Ethernet  HWaddr 00:FF:F7:05:AF:3D
          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:22971 overruns:0 carrier:0
          collisions:0 txqueuelen:500
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

tap3      Link encap:Ethernet  HWaddr 00:FF:66:F0:1E:4D
          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:22969 overruns:0 carrier:0
          collisions:0 txqueuelen:500
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

tap4      Link encap:Ethernet  HWaddr 00:FF:33:24:15:86
          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:22969 overruns:0 carrier:0
          collisions:0 txqueuelen:500
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

tap5      Link encap:Ethernet  HWaddr 00:FF:AA:B4:43:B9
          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:22969 overruns:0 carrier:0
          collisions:0 txqueuelen:500
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

tap6      Link encap:Ethernet  HWaddr 00:FF:D5:8A:CD:1F
          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:22969 overruns:0 carrier:0
          collisions:0 txqueuelen:500
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

tap7      Link encap:Ethernet  HWaddr 00:FF:BE:05:9E:B7
          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:22965 overruns:0 carrier:0
          collisions:0 txqueuelen:500
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

tap8      Link encap:Ethernet  HWaddr 00:FF:53:97:7D:90
          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:22965 overruns:0 carrier:0
          collisions:0 txqueuelen:500
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

tap9      Link encap:Ethernet  HWaddr 00:FF:24:41:D0:87
          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:22965 overruns:0 carrier:0
          collisions:0 txqueuelen:500
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)


iptables-save -c (on router)
Code:

# Generated by iptables-save v1.3.8 on Fri Feb 15 09:21:46 2008
*raw
:PREROUTING ACCEPT [198753056:114402595017]
:OUTPUT ACCEPT [136014238:39820411746]
COMMIT
# Completed on Fri Feb 15 09:21:46 2008
# Generated by iptables-save v1.3.8 on Fri Feb 15 09:21:46 2008
*nat
:PREROUTING ACCEPT [407933:49227394]
:POSTROUTING ACCEPT [20068:3855261]
:OUTPUT ACCEPT [1123274:75777476]
[59062:4334041] -A POSTROUTING -o eth4 -j MASQUERADE
COMMIT
# Completed on Fri Feb 15 09:21:46 2008
# Generated by iptables-save v1.3.8 on Fri Feb 15 09:21:46 2008
*mangle
:PREROUTING ACCEPT [198753044:114402594293]
:INPUT ACCEPT [194300985:112443601563]
:FORWARD ACCEPT [4570894:1948995803]
:OUTPUT ACCEPT [136014222:39820410822]
:POSTROUTING ACCEPT [140609954:41775196426]
COMMIT
# Completed on Fri Feb 15 09:21:46 2008
# Generated by iptables-save v1.3.8 on Fri Feb 15 09:21:46 2008
*filter
:INPUT ACCEPT [1277146:331251653]
:FORWARD DROP [40:13330]
:OUTPUT ACCEPT [6914403:2999733881]
[5178304:2278387388] -A INPUT -i lo -j ACCEPT
[255273:110427750] -A INPUT -i br0 -j ACCEPT
[0:0] -A INPUT -i ! br0 -p udp -m udp --dport 67 -j REJECT --reject-with icmp-port-unreachable
[0:0] -A INPUT -i ! br0 -p udp -m udp --dport 53 -j REJECT --reject-with icmp-port-unreachable
[39950:6075590] -A FORWARD -d 192.168.0.0/255.255.255.0 -i ! eth4 -j ACCEPT
[243421:32489982] -A FORWARD -s 192.168.0.0/255.255.255.0 -i ! eth4 -j ACCEPT
[278489:256508212] -A FORWARD -d 192.168.0.0/255.255.255.0 -i eth4 -j ACCEPT
COMMIT
# Completed on Fri Feb 15 09:21:46 2008
Back to top
View user's profile Send private message
jbo5112
n00b
n00b


Joined: 16 Nov 2005
Posts: 19

PostPosted: Fri Feb 15, 2008 4:34 pm    Post subject: Reply with quote

*update* The cheap office router works with the VPN too. It's just that none of the computers using it will connect to the VPN for one reason or another.
Back to top
View user's profile Send private message
Hu
Administrator
Administrator


Joined: 06 Mar 2007
Posts: 23062

PostPosted: Sat Feb 16, 2008 3:40 am    Post subject: Reply with quote

In your first post, your second option implied that you could control remote machines, albeit with very poor responsiveness. If so, you could use that to ping your VPN IP address to test connectivity.

However, before we get that far, it appears that the VPN client is not configuring your interfaces correctly. I expect that the VPN server is issuing addresses of 172.x.x.x, but no such address appears anywhere on any of your interfaces. Can you enable or increase the verbosity of the VPN client's logging? It may be experiencing some error that causes it to leave your system in a partially configured state. You could try to emerge dev-util/strace and use it to monitor the system calls made by the VPN client. Run it as strace -f -tt -o vpn.strace -v -p pid-of-VPN-client. Once strace is attached, direct the VPN client to connect. If it insists on automatically connecting when you start it, then you should attach strace to a shell and have the shell start the VPN client. The strace output may be quite verbose. It may also contain authentication secrets, so it may be unsuitable to post publicly. Search it for any indication that a system call has failed. If you find any such failures, try to understand the reason for the failure. The errors should be safe to post here.
Back to top
View user's profile Send private message
jbo5112
n00b
n00b


Joined: 16 Nov 2005
Posts: 19

PostPosted: Mon Feb 18, 2008 10:58 am    Post subject: Reply with quote

Just when I was watching tcpdumps and finding the VPN to be sending all the traffic through the https website I use to sign in, it magically starts working. First http access opened up, now remote desktop has started working. Maybe their engineers were running a bunch of patches tonight and fixed something broken on their end, or Time Warner fixed something in their standard Road Runner package that was working for business class customers. Maybe early Monday morning is the only time when the networks are clear enough for my connections to not time out. We had the VPN people extend the length of our session earlier this week, but remote desktop wasn't working an hour ago. Sorry to be of a bother, but their VPN sure has been frustrating.

Without the proprietary application from Juniper Networks, would there be a way to get my router to handle the VPN connection for all attached computers? It would be nice if I didn't need a for XP Pro x64 for development and a different one for running remote desktop.
Back to top
View user's profile Send private message
Hu
Administrator
Administrator


Joined: 06 Mar 2007
Posts: 23062

PostPosted: Mon Feb 18, 2008 4:50 pm    Post subject: Reply with quote

That depends, but probably you can make it work. In theory, it should be as simple as configuring the Gentoo machine to route traffic from the LAN to the VPN, and MASQUERADE the traffic at the same time so that the VPN server does not get confused by connections coming from LAN IP addresses. After that is set up, then the systems on the LAN should see the VPN as just another network. You might run into problems if the IT department is using the same IP addresses as your LAN, since then your LAN systems would connect to each other instead of going over the VPN.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Networking & Security All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum