lang
DD-WRT Novice
Joined: 18 Dec 2008
Posts: 32
|
 Posted: Sun Dec 28, 2008 16:29 Post subject: WAN PPTP connection |
 |
Hi,
I have asus WL-500GPV2 and pptp Internet connection. I am using dd-wrt.v24-11218_NEWD_std-nokaid_usb.bin
firmware now which provides support for my USB printer and my USB HDD, but tried some other firmware
versions before. All works great, except I had some problems with pptp Internet access that I solved with custom script.
What I have discovered, makes me to think about a possible bug. As I understand the matter,
there are two ways to set up pptp connections in DD-WRT:
1st - on the Setup->Basic Setup tab
2nd - on the Services->PPTP Client tab
The first is intended for Internet access, and the second - for mastering VPN tunnels.
The second way works fine, but it is not suitable for Internet access.
Likely most people who have pptp Internet connection use the second way and have
some minor problems which I had too. Most noticeable of them are:
- port forwarding does not work
- time synchronization delays for 1 hour after reboot
At the first glance, setting up PPTP Internet connection on Setup->Basic Setup tab does not work at all.
After making all settings for PPTP on Setup->Basic Setup tab, no connection can be established as usual.
To see, what happens, I issue following commands:
| Code: |
nvram set wan_ipaddr=192.168.23.14
nvram set wan_ipaddr_buf=192.168.23.14
nvram set wan_netmask=255.255.255.0
nvram commit
reboot
|
Here 192.168.23.14 - my IP address in provider's network.
After rebooting the router pptp connection is established (this is the output of ifconfig):
| Code: |
ppp0 Link encap:Point-to-Point Protocol
inet addr:62.63.87.119 P-t-P:10.0.20.2 Mask:255.255.255.255
UP POINTOPOINT RUNNING MULTICAST MTU:1460 Metric:1
RX packets:1384 errors:0 dropped:0 overruns:0 frame:0
TX packets:1081 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:451970 (441.3 KiB) TX bytes:185732 (181.3 KiB)
vlan1 Link encap:Ethernet HWaddr 00:1F:C6:78:0C:BC
inet addr:192.168.23.14 Bcast:192.168.23.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5989 errors:0 dropped:0 overruns:0 frame:0
TX packets:2797 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1041415 (1017.0 KiB) TX bytes:363943 (355.4 KiB)
|
We can see that wan_ipaddr and wan netmask go to vlan1. Let us check nvram:
| Code: |
nvram get wan_ipaddr
62.63.87.119
nvram get wan_ipaddr_buf
62.63.87.100
nvram get wan_netmask
255.255.255.255
|
Original IP address (192.168.23.14) is not present. After rebooting no connection is established (of course, if I do not correct again the variables in nvram), and the output of ifconfig vlan1 is as follows:
| Code: |
vlan1 Link encap:Ethernet HWaddr 00:1F:C6:78:0C:BC
inet addr:62.63.87.119 Bcast:62.63.87.119 Mask:255.255.255.255
UP BROADCAST RUNNING 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:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
|
Can anybody explain this? I can't undersatand this behavior in other way than a bug.
Custom script, which replaces original program, completely solves the problem for me. It uses settings on Setup->Basic Setup tab, kills redial program, and starts custom redial script that launches pppd with custom ip-up and ip-down scripts. All works fine for a couple of month. (I put the script in the attachment, just in case)
Thanks for any response. |
|
