search

lixuewei / rt-n56u

Automatically exported from code.google.com/p/rt-n56u
0 stars 0 forks source link

VPN Broadcast Traffic Relay not working #1188

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Connected vpn clients get their own local ip (e.g. 192.168.2.245). This ip is 
displayed in the webinterface, but can't be accessed locally, so it's not set.
If I ping 192.168.2.245 from the local network nothing happens, but if I ping 
the hostname of the vpn-client the router gets pinged (ping to *hostname* 
192.168.2.1), but 192.168.2.1 is the ip of the router and not of the client 
(which has 192.168.2.245).
I think its an issue with the Broadcast Traffic Relay, which has no effect at 
all. I can set it to anything (e.g. disabled, both directions) but it has no 
effect.

What version of the product are you using? On what operating system?

3.0.3.7-079 (newest)

Original issue reported on code.google.com by maxi.sie...@gmail.com on 14 Mar 2014 at 6:40

GoogleCodeExporter commented 9 years ago 
Forgot to say: VPN server is PPTP

Original comment by maxi.sie...@gmail.com on 14 Mar 2014 at 6:49

GoogleCodeExporter commented 9 years ago 
Okay I found this: 
http://code.google.com/p/rt-n56u/issues/detail?id=442&can=1&q=bcrelay

I have the exact same issue. This post is from 2012, why isn't this fixed yet?

Original comment by maxi.sie...@gmail.com on 14 Mar 2014 at 7:41