Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.dcom.vpn    |    VPN protocols, clients, awesomeness    |    2,349 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 1,643 of 2,349    |
|    Mark Alexander Bertenshaw to All    |
|    Re: Routing problem over VPN from Vigor     |
|    02 Jun 05 01:02:21    |
      From: newsthang@mbertenshaw.plus.com              Sorry about the diagram - I thought it newlined at 78 chars!              Anyhow, it turned out to be an issue with the Draytek Vigor 2600+. When I       added my static route, I had only one item in the dropdown for Network       Interface (LAN) - and I didn't notice this. Of course, if I want       10.0.0.0/24 to go down the VPN tunnel, this is the wrong interface. So how       do I get to see further interfaces in this dropdown? Well, it seems that       you can't. Instead you have to go to the setup for the outgoing VPN tunnel,       and scroll right to the bottom to Section 4 (TCP/IP Network Settings).       Below "Remote Network IP" and "Remote Network Subnet", there is a button       saying "More". Pressing this takes you to a dialogue where you can       associate as many Address/Subnet values as you like with this tunnel. But       this is the sneaky thing: these values only take effect when you reboot the       the Vigor 2600+ !! Now, if you go to the Static Routing table, you will see       the addresses have been added as static routes, with IF = 4+. After       reinstating the routing on the Netscreen 5XP (10.0.0.0/24 -> Trust), you       can ping 10.0.0.0/24; and interestingly, this also fixes the 10.0.0.0/24 ->       192.168.2.0/24 pinging problem. Fantastic!              --       Mark Bertenshaw       Kingston upon Thames       UK              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca