PPTP/L2TP WAN connection types: allowed to specify separate gateway for physical WAN connection when not using DHCP.
But after resting to default setting DHCP Client for WAN does not work. If I load config from Build 52 - all work fine.
Tomato Firmware v1.28.9053 MIPSR2-beta K26 USB vpn3.6
Post your WAN connection settings when it's not working - after you reset to defaults and configure them manually.
If they are exactly the same in the GUI as after loading the config from build 52, please also post the output of the following command:
nvram find wan
after loading config from build 52
block_wan=1 dhcp_domain=wan dr_wan_rx=0 dr_wan_tx=0 http_wanport=8080 mac_wan= script_wanup=ifconfig br0 hw ether `nvram get lan_hwaddr` vpn_server1_ca=-----BEGIN CERTIFICATE----- -----END CERTIFICATE----- wan_dns= wan_domain=Home wan_gateway=10.199.40.1 wan_gateway_buf=10.199.40.1 wan_gateway_get=22.214.171.124 wan_get_dns=126.96.36.199 188.8.131.52 wan_get_domain= wan_hostname=WNR3500L wan_hwaddr=C0:3F:0E:--:--:-- wan_hwname= wan_iface=ppp0 wan_ifname=vlan2 wan_ifnameX=vlan2 wan_ifnames=vlan2 wan_ipaddr=10.199.47.253 wan_ipaddr_buf=184.108.40.206 wan_islan=0 wan_lease=604800 wan_msroutes= wan_mtu=1460 wan_netmask=0.0.0.0 wan_primary=1 wan_proto=l2tp wan_routes1=220.127.116.11/24 10.199.47.253 10.0.0.0/8 10.199.40.1 18.104.22.168/24 10.199.40.1 22.214.171.124/24 10.199.40.1 126.96.36.199/28 10.199.40.1 188.8.131.52/27 10.199.40.1 184.108.40.206/22 10.199.40.1 220.127.116.11/28 10.199.40.1 18.104.22.168/32 10.199.40.1 22.214.171.124/32 10.199.40.1 126.96.36.199/24 10.199.40.1 188.8.131.52/28 10.199.40.1 184.108.40.206/28 10.199.40.1 220.127.116.11/28 10.199.40.1 18.104.22.168/30 10.199.40.1 wan_routes2=22.214.171.124 10.199.40.1 126.96.36.199 10.199.40.1 188.8.131.52 10.199.40.1 184.108.40.206 10.199.40.1 220.127.116.11 10.199.40.1 18.104.22.168 10.199.40.1 22.214.171.124 10.199.40.1 126.96.36.199 10.199.40.1 188.8.131.52 10.199.40.1 184.108.40.206 10.199.40.1 220.127.116.11 10.199.40.1 18.104.22.168 10.199.40.1 22.214.171.124 10.199.40.1 wan_routes= wan_run_mtu=1460 wan_speed=4 wan_unit=0 wan_wins=0.0.0.0 wandevs=et0
wan_gateway=10.199.40.1 wan_gateway_buf=10.199.40.1 wan_gateway_get=126.96.36.199
This is obviously after loading the config from build 52. I actually need the output of this command after erasing the nvram and without reloading the config - sorry if I was not clear.
BTW, I could not reproduce this problem either (with PPTP, but it should be the same as L2TP). Also - what do you mean exactly by "DHCP Client for WAN does not work" - what happens? And what's in your log?
Teddy, I have the same problem.
My provider use PPTP connection to Internet and my router obtain internal provider network settings by DHCP. In fact, if I just choose in my WAN type connection "DHCP" - my router will be in my provider's network (like 10.X.X.X). So, on build 53 if i erase nvram after flashing - my router don't obtain network settings on WAN port (if I choose DHCP or PPTP - it doesn't matter). On build 52 after erasing nvram router obtain network settings on WAN port by DHCP.
If I on build 52 after erasing nvram (default settings on 52 build - when DHCP client work on WAN port) backup configuration (default configuration) in file, and after flashing build 53 (with erasing nvram again) restore default configuration from this file (yes, I save default configuration in build 52 and apply it to default configuration in build 53) - DHCP client on WAN port works fine. After that, I can change my connection type (I mean DHCP, or PPTP) - everything working fine.
And, rebooting router after flashing build 53 doesn't help. Only restore any working configuration (include default - it's working too) from build 52 helps.
So, what's the problem?