Asus RT-AC68R, Merlin_380.57.0, WAN IP - Gateway IP conflict

[portlsteve]

THE PROBLEM WAS SOLVED BY ENTERING A PROPER GATEWAY IP ADDRESS INTO THE ROUTER CONFIGURATION. THIS WAS CONFIGURATION ERROR. THE HARDWARE AND FIRMWARE WERE NOT AT FAULT

I am unable to connect my streaming media service devices and my VOIP telephone to the internet. The problem arises only with Asus and Asus-Merlin firmware.

I'm running an Asus RT-AC68R router. I uploaded Asus-Merlin RT-AC68U_380.57_0 and installed it successfully. I encountered a problem in configuring the router. I have a PPPoE account with my ISP. I have a single static IP for my network. Because I have only one static IP, my WAN IP address and my Gateway address are the same. When I configured the WAN settings of my router, I entered my static IP for my WAN IP and I tried to enter the same IP for my Gateway. Identical IPs for the WAN and Gateway were rejected by the firmware because "an internet connection might not be possible." I proceeded by leaving the Gateway IP blank.

After configuring, I am able to connect to the internet with all my computers, both wired and wireless devices, including devices on both wireless bands of the router. I am unable to connect to the internet with other devices, including Roku streaming media service devices and an OOMA VOIP telephone service. When I look at the list of clients on the router all my devices, both computers, and streaming media and VOIP devices are listed. I have disabled the firewall on the router.

I encountered the same problem (Identical WAN and Gateway IP rejected) with the Asus stock firmware, so I believe it is not the Merlin firmware. I have configured and used successfully the same collection of devices with an ISP provided modem/router (Actiontec C1000A) and the Asus RT-AC68R running with dd-wrt firmware, so it appears that both the router and the arrangement of IPs, Gateway, etc. are ok.

I believe the problem is in the lack of a Gateway IP, because both the Roku and OOMA depend on internet provided DNS services. By the way I use OpenDNS address in the router configuration.

Two ideas: Now the Actiontec C1000A is configured as a transparent bridge and the PPPoE logging is handled by the RT-AC68R. I could configure the C1000A to handle the PPPoE logging and use the Asus RT-AC68R as a switch, but that would reduce the network services not available through the Actiontec that make the RT-AC68R useful. Another possibility: If the problem is the lack of a Gateway IP because of the identical WAN and Gateway IPs, perhaps a way around the problem is some ip forwarding. I don't know how to do that.

Any suggestions?

 

[L&LD]

I do not see that you performed a reset to factory defaults and then minimally and manually configure the router again?

http://www.snbforums.com/threads/no...l-and-manual-configuration.27115/#post-205573

If you haven't already done so, I recommend it before you continue what may be phantom issues.

 

[portlsteve]

I do not see that you performed a reset to factory defaults and then minimally and manually configure the router again?

http://www.snbforums.com/threads/no...l-and-manual-configuration.27115/#post-205573

If you haven't already done so, I recommend it before you continue what may be phantom issues.

I think the process I followed is consistent with the thread referenced.

Prior to exhibiting the problem described, the Asus RT-AC68R was loaded with dd-wrt firmware. I flashed the Asus-Merlin firmware, configured it (minimally, as described in the referenced posting) and then observed the problem I described. In addition this is not the first Asus router I've owned that had the problem. Earlier, I had a new Asus RT-AC68W which I configured using the wizard without any other additions (except enabling telnet) and I observed the same problem. At that time, I spent some time with the Roku tech service trying to fix it. They advised me to use the OpenDNS servers. I did but that did not help. In both the instances where I have had the problem the, the firmware refused to accept the Gateway IP (assigned by my ISP) because it was the same as the WAN IP (assigned by my ISP). Every other combination of router and firmware treated the WAN IP/Gateway IP identity without problem and the two services (Roku and OOMA) worked out of the box when hooked up, no additional configuration required.

I don't know what is the distinction between the Gateway IP and the WAN IP. In my naivete I imagine that Roku and OOMA use the Gateway IP to access DNS servers to provide IP addresses for the destinations of the packets that are part of their process, and they get the packets destined for them through the WAN IP. But regardless of how these two are used by the router, I expect that leaving one of them blank in the configuration when both are expected must be a problem.

 

[L&LD]

I think the process I followed is consistent with the thread referenced.

Prior to exhibiting the problem described, the Asus RT-AC68R was loaded with dd-wrt firmware. I flashed the Asus-Merlin firmware, configured it (minimally, as described in the referenced posting) and then observed the problem I described. In addition this is not the first Asus router I've owned that had the problem. Earlier, I had a new Asus RT-AC68W which I configured using the wizard without any other additions (except enabling telnet) and I observed the same problem. At that time, I spent some time with the Roku tech service trying to fix it. They advised me to use the OpenDNS servers. I did but that did not help. In both the instances where I have had the problem the, the firmware refused to accept the Gateway IP (assigned by my ISP) because it was the same as the WAN IP (assigned by my ISP). Every other combination of router and firmware treated the WAN IP/Gateway IP identity without problem and the two services (Roku and OOMA) worked out of the box when hooked up, no additional configuration required.

I don't know what is the distinction between the Gateway IP and the WAN IP. In my naivete I imagine that Roku and OOMA use the Gateway IP to access DNS servers to provide IP addresses for the destinations of the packets that are part of their process, and they get the packets destined for them through the WAN IP. But regardless of how these two are used by the router, I expect that leaving one of them blank in the configuration when both are expected must be a problem.

Again, I fail to see that after flashing the firmware you then performed a reset to factory defaults?

You may be implying that you did, but this is the important step.

 

[portlsteve]

Again, I fail to see that after flashing the firmware you then performed a reset to factory defaults?

You may be implying that you did, but this is the important step.

I have fixed the problem in the configuration and the router now supports all connected devices. The ISP tech who twice told me that a PPPoE account with a single static IP uses the same IP as the Gateway was simply wrong. Using a working connection and the traceroute command, I identified a Gateway address appropriate to my ISP and entered it into the RT-AC68R WAN settings. On reboot everything connected and functioned.

Thanks for the help. I downloaded your detailed instructions for router configuring and used them. It is interesting that most lists of configuring, flashing, etc., while detailed, don't describe what each step accomplishes. I though my RT-AC68R was bricked when every attempt to flash the Merlin firmwear failed until I finally did the 30-30-30 procedure (including unplugging the power line). Then everything worked fine. Make sure your nvram is cleared!

 

[L&LD]

I have fixed the problem in the configuration and the router now supports all connected devices. The ISP tech who twice told me that a PPPoE account with a single static IP uses the same IP as the Gateway was simply wrong. Using a working connection and the traceroute command, I identified a Gateway address appropriate to my ISP and entered it into the RT-AC68R WAN settings. On reboot everything connected and functioned.

Thanks for the help. I downloaded your detailed instructions for router configuring and used them. It is interesting that most lists of configuring, flashing, etc., while detailed, don't describe what each step accomplishes. I though my RT-AC68R was bricked when every attempt to flash the Merlin firmwear failed until I finally did the 30-30-30 procedure (including unplugging the power line). Then everything worked fine. Make sure your nvram is cleared!

Glad you have everything working. Just note that Asus routers do not respond (well) with a 30-30-30 reset; as RMerlin says, that is an DD-WRT-ism.

http://www.snbforums.com/threads/rt...t-and-10s-wps-button-reset.19048/#post-136280

 

[portlsteve]

Glad you have everything working. Just note that Asus routers do not respond (well) with a 30-30-30 reset; as RMerlin says, that is an DD-WRT-ism.

http://www.snbforums.com/threads/rt...t-and-10s-wps-button-reset.19048/#post-136280

I noted the advice when I was attempting to flash the Asus Merlin firmware onto the Asus RT-AC68U that I had previously flashed with dd-wrt. I tried everything I could - direct flash though GUI firmware upgrade, Asus recovery mode, and whatever else I could find - but nothing worked. I prepared to throw the router in the trash (no warranty) but saved it instead, planning to take it apart later and study its insides. Then I realized that I hadn't done the 30-30-30 and, just to be thorough, I did it. The router emerged in the CFE miniServer mode and in that mode I was able to flash Asus Merlin. Now I'm using it and at least for one day of service, it's fine. Routers are a mystery to me and anything I believe I know I also believe is provisional.