Talk:OpenVPN - Site-to-Site Bridged VPN Between Two Routers

From DD-WRT Wiki

(Difference between revisions)
Jump to: navigation, search
Revision as of 19:15, 28 October 2008 (edit)
Valnar (Talk | contribs)
(Frame sizes?)
← Previous diff
Revision as of 03:47, 15 April 2009 (edit) (undo)
Samuraijack (Talk | contribs)

Next diff →
Line 14: Line 14:
Does this method support that? If not, can it be tweaked further? Does this method support that? If not, can it be tweaked further?
 +
 +I followed the guide and it worked like a charm. My setup:
 +Server: Asus Wl-520gu with IP address range 192.168.10.100 to 192.168.10.150 and router IP:192.168.10.1
 +Client: WRT54G V2 with IP address range 192.168.10.151 to 192.168.10.200 and router IP:192.168.10.2
 +Now everything works fine from the clients but there is a small problem. When a client is connected through one of the ethernet ports of the client router then the IP and gateway of the client is fine but when a wireless user connects then strangely the IP address is given from the server routher's IP range and also the gateway is set to the Server router's IP address. Could someone please help me resolve this. Oh by the way I did not have any trouble connecting to the internet even with this setup. But I was wondering what if the server router is down then how will the wireless clients will be affected under this scenario.

Revision as of 03:47, 15 April 2009

Contents

Same subnets doesn't work

When I connect to a router that has same subnet 192.168.1.x as the router I can connected to locally, I cannot ping any remote machine, or the remote router. If I set the remote router to 192.168.2.x, then everything works fine. (I am talking about connecting from a client machine to a remote router, I haven't tried router to router because I couldn't get it going when I followed this guides steps). - Jeffman 22:49, 9 Jul 2007 (CEST)

Help!

We have put in all the information exactly how it shows in the instructions. one router is 192.168.1.X and the other is 192.168.11.X. Still cant ping any hosts on the remote side. Is there a way to check the status? Anything will help. Thanks

Solution

The two routers have to be in the same sub-domain for the bridging to work, make both of them in the 11.x subdomain or the 1.x subdomain. Then make sure that the DHCP servers on each end issue IP addresses that do not overlap with those on the other end. (Added by xnok)

Frame sizes?

I've used L2TPv3 on Cisco before and always ran into the same problem - it didn't support frame sizes around 1500. Since L3 packet + VPN overhead usually pushes it over the MTU threshold for the Internet, I need some way to fragment packets (errr...frames) either after or before it's bridged through the tunnel.

Does this method support that? If not, can it be tweaked further?

I followed the guide and it worked like a charm. My setup: Server: Asus Wl-520gu with IP address range 192.168.10.100 to 192.168.10.150 and router IP:192.168.10.1 Client: WRT54G V2 with IP address range 192.168.10.151 to 192.168.10.200 and router IP:192.168.10.2 Now everything works fine from the clients but there is a small problem. When a client is connected through one of the ethernet ports of the client router then the IP and gateway of the client is fine but when a wireless user connects then strangely the IP address is given from the server routher's IP range and also the gateway is set to the Server router's IP address. Could someone please help me resolve this. Oh by the way I did not have any trouble connecting to the internet even with this setup. But I was wondering what if the server router is down then how will the wireless clients will be affected under this scenario.