Hello Group..
Out of the blue one my AP’s RB/333 F/W v 3.10 (just updated) decided it’s Gateway Address is invalid?
Connectivity is -65 Tx/Rx CCQ 95/95%
The default gateway is 10.0.0.13, the IP is pingable from the AP terminal, yet when viewing the routes in the MT AP the default route remains blue.
From the gateway device 8 miles away I am able to ping all IP’s within the AP having gateway issues.
Likewise from the gateway device I can ping the world.
Has anyone got a clue as to why this would happen and possibly how to resolve the issue?
Thanks
Regards
Hmm, no takers on this question huh?
could you post a complete routing table. interface and address lists could also be important.
Thank you for your time…
My routing table:
0 S ;;; DEFAULT GATEWAY
dst-address=0.0.0.0/0 gateway=10.0.0.13 interface=Network gateway-state=reachable distance=1 scope=30
target-scope=10
1 ADS dst-address=0.0.0.0/0 gateway=192.168.1.1 interface=Network gateway-state=reachable distance=0 scope=30
target-scope=10
2 ADC dst-address=10.0.0.0/24 pref-src=10.0.0.16 interface=Network distance=0 scope=10
3 A S ;;; Route to Tower 1 From Tower 3 (serves 900Mhz AP)
dst-address=10.0.100.0/24 pref-src=10.0.0.16 gateway=10.0.0.10 interface=Network gateway-state=reachable
distance=1 scope=30 target-scope=10
4 A S ;;; Route to Tower 2 From Tower 3 (serves 900Mhz AP)
dst-address=10.0.101.0/24 pref-src=10.0.0.16 gateway=10.0.0.13 interface=Network gateway-state=reachable
distance=1 scope=30 target-scope=10
5 ADC dst-address=10.0.102.0/24 pref-src=10.0.102.1 interface=Network distance=0 scope=10
6 ADC dst-address=192.168.1.0/24 pref-src=192.168.1.103 interface=Network distance=0 scope=10
7 A S ;;; 192.168.80.x Tie-In Route
dst-address=192.168.80.0/24 pref-src=10.0.0.16 gateway=10.0.0.13 interface=Network
gateway-state=reachable distance=1 scope=30 target-scope=10
8 A S ;;; 192.168.90.x Tie-In Route
dst-address=192.168.90.0/24 pref-src=10.0.0.16 gateway=10.0.0.13 interface=Network
gateway-state=reachable distance=1 scope=30 target-scope=10
9 ADC dst-address=192.168.100.0/24 pref-src=192.168.100.1 interface=Network distance=0 scope=10
10 A S ;;; Yarrow Route to 10.0.0.x Subnet
dst-address=192.168.100.1/32 pref-src=10.0.0.16 gateway=10.0.0.13 interface=Network
gateway-state=reachable distance=1 scope=30 target-scope=10
11 ADC dst-address=192.168.101.0/24 pref-src=192.168.101.1 interface=ether2 distance=0 scope=200
The Interfaces:
Flags: X - disabled, R - running, D - dynamic, S - slave
0 ;;; Ether 1 PoE (Yarrow Port)
name="ether1" mtu=1500 type="ether"
1 name="ether2" mtu=1500 type="ether"
2 name="ether3" mtu=1500 type="ether"
3 ;;; 900Mhz AP 1 WDS 2442 (922Mhz-5Mhz)
name="wlan1" mtu=1500 type="wlan"
4 R ;;; Primary Communication Bridge
name="Network" mtu=1500 type="bridge"
5 R ;;; 5Ghz P2P Tower 3 <--> 4
name="wlan2" mtu=1500 type="wlan"
6 R name="wds1" mtu=1500 type="wds"
The Address list
0 ;;; Ether 1 (Yarrow Port)
address=192.168.100.1/24 network=192.168.100.0 broadcast=192.168.100.255 interface=ether1
actual-interface=Network
1 ;;; Ether 2
address=192.168.101.1/24 network=192.168.101.0 broadcast=192.168.101.255 interface=ether2
actual-interface=ether2
2 ;;; Ether 3
address=192.168.102.1/24 network=192.168.102.0 broadcast=192.168.102.255 interface=ether3
actual-interface=ether3
3 ;;; 900Mhz AP 1
address=10.0.102.1/24 network=10.0.102.0 broadcast=10.0.102.255 interface=wlan1 actual-interface=Network
4 ;;; 5Ghz Tower 3 <--> 4 P2P
address=10.0.0.16/24 network=10.0.0.0 broadcast=10.0.0.255 interface=wlan2 actual-interface=Network
5 D address=192.168.1.103/24 network=192.168.1.0 broadcast=192.168.1.255 interface=ether1
actual-interface=Network
A note on the gateway device that this AP is connected to:
The link which ties into this AP is connected to another router at it’s tower by ethernet.
The ethernet addresses are 192.168.80.5 & 192.168.90.5.
I don’t understand why this was all working for a couple weeks and out of the blue it just quit gatewaying?
Thank you
Regards
Hmmm…
This is weird, When I completely remove the Default Gateway from this AP it is able to gateway the world!!??
I’m confused how exactly this thing is gatewaying without a default route…
Thanks for the your help
Regards
I see two default gateways there:
0 S ;;; DEFAULT GATEWAY
dst-address=0.0.0.0/0 gateway=10.0.0.13 interface=Network gateway-state=reachable distance=1 scope=30
target-scope=10
1 ADS dst-address=0.0.0.0/0 gateway=192.168.1.1 interface=Network gateway-state=reachable distance=0 scope=30
target-scope=10
So, of course one of them is not active.
I never held any stock in the dynamic gateway, so that was causing the issue.
Now my routs look like:
0 A S ;;; DEFAULT GATEWAY
dst-address=0.0.0.0/0 gateway=10.0.0.13 interface=Network gateway-state=reachable distance=1 scope=30 target-scope=10
1 ADC dst-address=10.0.0.0/24 pref-src=10.0.0.16 interface=Network distance=0 scope=10
2 A S ;;; Route to Tower 1 From Tower 3 (serves 900Mhz AP)
dst-address=10.0.100.0/24 pref-src=10.0.0.16 gateway=10.0.0.10 interface=Network gateway-state=reachable distance=1 scope=30 target-scope=10
3 A S ;;; Route to Tower 2 From Tower 3 (serves 900Mhz AP)
dst-address=10.0.101.0/24 pref-src=10.0.0.16 gateway=10.0.0.13 interface=Network gateway-state=reachable distance=1 scope=30 target-scope=10
4 ADC dst-address=10.0.102.0/24 pref-src=10.0.102.1 interface=Network distance=0 scope=10
5 ADC dst-address=192.168.100.0/24 pref-src=192.168.100.1 interface=Network distance=0 scope=10
6 A S ;;; Yarrow Route to 10.0.0.x Subnet
dst-address=192.168.100.1/32 pref-src=10.0.0.16 gateway=10.0.0.13 interface=Network gateway-state=reachable distance=1 scope=30 target-scope=10
7 ADC dst-address=192.168.101.0/24 pref-src=192.168.101.1 interface=ether2 distance=0 scope=200
8 ADC dst-address=192.168.102.0/24 pref-src=192.168.102.1 interface=ether3 distance=0 scope=200
So I assume the dynamic gateway was set at some point prior to my loosing gateway from 10.0.0.13.
I appreciate your help with this matter very much, thank you for your time..
Regards