No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

couldn't access AR129's web from public network side

Publication Date:  2016-03-02 Views:  569 Downloads:  0
Issue Description

Customer has an AR129 device, he could normally access device's web from internal network side. when he visit web from public network side, the login GUI could show normally, but customer will get "timeout" prompt when then login and waiting for some times.


Solution

I checked customer's configuration and found there are two public IP.

Interface                         IP Address/Mask      Physical   Protocol

Atm0/0/0                          unassigned           up         up

Cellular0/0/0                     unassigned           down       down

Ethernet0/0/0                     X.*.*.30/30     up         up

GigabitEthernet0/0/0              unassigned           down       down

NULL0                             unassigned           up         up(s)

Virtual-Template1                 Y.*.*.184/32   up         up

Vlanif1                           10.0.0.138/24        up         up

Vlanif10                          192.168.10.1/24      up         up

 and there are two static route with default priority.

#

ip route-static 0.0.0.0 0.0.0.0 Ethernet0/0/0 X.*.*.29

ip route-static 0.0.0.0 0.0.0.0 Virtual-Template1

#

Since the equal priority route exist, affect the WEB normal use.

After suggest customer to change one route's priority, then this issue resolved.(the master link with high priotiry: 60, the slave link with low priority: 70)

#

ip route-static 0.0.0.0 0.0.0.0 Ethernet0/0/0 X.*.*.29

ip route-static 0.0.0.0 0.0.0.0 Virtual-Template1 preference 70

#


 

END