8315 questions

9779 answers

15562 comments

13903 members

0 votes
1,353 views 3 comments
by

Hi all

I just setup a RUT240 (FW ver.: RUT2XX_R_00.01.04.1) and a third party router as a VRRP pair. RUT240 is BACKUP and the third party router is MASTER.

Now, when I unplug the third party router from the network, the RUT240 takes the virtual address and everything is fine. Log:


Thu Dec 27 11:28:31 2018 kern.info kernel: [  538.930000] br-lan: port 2(wlan0) entered disabled state
Thu Dec 27 11:28:31 2018 kern.info kernel: [  538.940000] br-lan: port 1(eth0) entered disabled state
Thu Dec 27 11:28:31 2018 daemon.notice netifd: bridge 'br-lan' link is down
Thu Dec 27 11:28:31 2018 daemon.notice netifd: Interface 'lan' has link connectivity loss
Thu Dec 27 11:28:31 2018 kern.info kernel: [  538.950000] br-lan: port 2(wlan0) entered forwarding state
Thu Dec 27 11:28:31 2018 kern.info kernel: [  538.960000] br-lan: port 2(wlan0) entered forwarding state
Thu Dec 27 11:28:31 2018 kern.info kernel: [  538.960000] br-lan: port 1(eth0) entered forwarding state
Thu Dec 27 11:28:31 2018 kern.info kernel: [  538.970000] br-lan: port 1(eth0) entered forwarding state
Thu Dec 27 11:28:31 2018 daemon.notice netifd: bridge 'br-lan' link is up
Thu Dec 27 11:28:31 2018 daemon.notice netifd: Interface 'lan' has link connectivity
Thu Dec 27 11:28:31 2018 user.warn syslog: VRRP ID 72 on br-lan: 11.1.98.10 is down, we are now the master router.
Thu Dec 27 11:28:32 2018 user.info Messaged[10050]: Start from new event "VRRP" "Router is in master mode"
Thu Dec 27 11:28:33 2018 kern.info kernel: [  540.960000] br-lan: port 2(wlan0) entered forwarding state
Thu Dec 27 11:28:33 2018 kern.info kernel: [  540.970000] br-lan: port 1(eth0) entered forwarding state

The problem starts, when I plug the third party router back in. The RUT240 is no longer reachable from the LAN and restarts all the interfaces for about 5 minutes. After this up-and-down it ends at the eth0 being DOWN and no LAN IP configured. Output of the command `ip a`:


root@Teltonika-RUT240:~# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether 00:1e:42:18:c7:34 brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 00:1e:42:18:c7:35 brd ff:ff:ff:ff:ff:ff
    inet 10.82.1.111/24 brd 10.82.1.255 scope global eth1
       valid_lft forever preferred_lft forever
    inet6 fe80::21e:42ff:fe18:c735/64 scope link
       valid_lft forever preferred_lft forever
4: ip6tnl0@NONE: <NOARP> mtu 1452 qdisc noop state DOWN group default
    link/tunnel6 :: brd ::
5: ifb0: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN group default qlen 32
    link/ether 5e:94:79:60:45:14 brd ff:ff:ff:ff:ff:ff
6: ifb1: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN group default qlen 32
    link/ether 66:41:fa:a5:6c:7e brd ff:ff:ff:ff:ff:ff
7: gre0@NONE: <NOARP> mtu 1476 qdisc noop state DOWN group default
    link/gre 0.0.0.0 brd 0.0.0.0
8: gretap0@NONE: <BROADCAST,MULTICAST> mtu 1462 qdisc noop state DOWN group default qlen 1000
    link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
10: wwan0: <BROADCAST,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000
    link/ether ce:64:33:7f:08:75 brd ff:ff:ff:ff:ff:ff
240: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master br-lan state UP group default qlen 1000
    link/ether 00:1e:42:18:c7:36 brd ff:ff:ff:ff:ff:ff
241: br-lan: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default
    link/ether 00:1e:42:18:c7:36 brd ff:ff:ff:ff:ff:ff

I then have to reboot the RUT240 to access it again from the LAN.

Do you experience such problems too?
Thanks in advance.
Regards, 
Roland Rusch
 

by

This is the log file from the RUT240, extracted by the command logread. Exactly at the time, the other router is plugged in and the RUT240 should degrade to BACKUP state.

Log files can not be uploaded to this forum and the comment is limited to 12000 chars. To see more log, check this gist: https://gist.github.com/rrusch/b81f5b17eabbde98bce4a3dd0dd58a9f


Fri Dec 28 15:30:12 2018 daemon.notice netifd: Interface 'lan' is now down
Fri Dec 28 15:30:12 2018 kern.info kernel: [94477.130000] br-lan: port 2(wlan0) entered disabled state
Fri Dec 28 15:30:12 2018 kern.info kernel: [94477.130000] br-lan: port 1(eth0) entered disabled state
Fri Dec 28 15:30:12 2018 kern.info kernel: [94477.140000] device eth0 left promiscuous mode
Fri Dec 28 15:30:12 2018 kern.info kernel: [94477.150000] br-lan: port 1(eth0) entered disabled state
Fri Dec 28 15:30:12 2018 kern.info kernel: [94477.160000] eth0: link down
Fri Dec 28 15:30:12 2018 kern.info kernel: [94477.160000] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Fri Dec 28 15:30:12 2018 kern.info kernel: [94477.170000] device wlan0 left promiscuous mode
Fri Dec 28 15:30:12 2018 kern.info kernel: [94477.170000] br-lan: port 2(wlan0) entered disabled state
Fri Dec 28 15:30:12 2018 daemon.notice netifd: Interface 'lan' is disabled
Fri Dec 28 15:30:12 2018 daemon.notice netifd: Network device 'eth0' link is down
Fri Dec 28 15:30:12 2018 daemon.notice netifd: bridge 'br-lan' link is down
Fri Dec 28 15:30:12 2018 daemon.notice netifd: Interface 'lan' has link connectivity loss
Fri Dec 28 15:30:13 2018 kern.info kernel: [94477.480000] device eth0 entered promiscuous mode
Fri Dec 28 15:30:13 2018 kern.info kernel: [94477.480000] device wlan0 entered promiscuous mode
Fri Dec 28 15:30:13 2018 kern.info kernel: [94477.520000] br-lan: port 2(wlan0) entered forwarding state
Fri Dec 28 15:30:13 2018 kern.info kernel: [94477.520000] br-lan: port 2(wlan0) entered forwarding state
Fri Dec 28 15:30:13 2018 kern.info kernel: [94477.530000] br-lan: port 1(eth0) entered forwarding state
Fri Dec 28 15:30:13 2018 kern.info kernel: [94477.530000] br-lan: port 1(eth0) entered forwarding state
Fri Dec 28 15:30:13 2018 local1.info hotplug-gsmstate[17582]: envACT: ifdown
Fri Dec 28 15:30:13 2018 local1.info hotplug-gsmstate[17582]: envINT: lan
Fri Dec 28 15:30:13 2018 daemon.notice netifd: Interface 'lan' is enabled
Fri Dec 28 15:30:13 2018 daemon.notice netifd: Interface 'lan' is setting up now
Fri Dec 28 15:30:13 2018 daemon.notice netifd: Interface 'lan' is now up
Fri Dec 28 15:30:13 2018 daemon.notice netifd: bridge 'br-lan' link is up
Fri Dec 28 15:30:13 2018 daemon.notice netifd: Interface 'lan' has link connectivity
Fri Dec 28 15:30:13 2018 kern.info kernel: [94477.700000] eth1: link down
Fri Dec 28 15:30:13 2018 daemon.notice netifd: Network device 'eth1' link is down
Fri Dec 28 15:30:13 2018 daemon.notice netifd: Interface 'wan' has link connectivity loss
Fri Dec 28 15:30:13 2018 kern.info kernel: [94478.140000] br-lan: port 1(eth0) entered disabled state
Fri Dec 28 15:30:14 2018 user.info Messaged[17631]: Start from new event "Port" "LAN cable is unplugged"
Fri Dec 28 15:30:14 2018 daemon.warn dnsmasq[14505]: no servers found in /tmp/resolv.conf.auto, will retry
Fri Dec 28 15:30:14 2018 daemon.notice netifd: wan (15708): udhcpc: received SIGTERM
Fri Dec 28 15:30:14 2018 user.notice root: stopping ntpclient
Fri Dec 28 15:30:14 2018 daemon.notice netifd: bridge 'br-lan' link is down
Fri Dec 28 15:30:14 2018 daemon.notice netifd: Interface 'lan' has link connectivity loss
Fri Dec 28 15:30:14 2018 kern.info kernel: [94478.950000] br-lan: port 2(wlan0) entered disabled state
Fri Dec 28 15:30:14 2018 kern.info kernel: [94478.980000] br-lan: port 2(wlan0) entered forwarding state
Fri Dec 28 15:30:14 2018 kern.info kernel: [94478.980000] br-lan: port 2(wlan0) entered forwarding state
Fri Dec 28 15:30:14 2018 daemon.notice netifd: bridge 'br-lan' link is up
Fri Dec 28 15:30:14 2018 daemon.notice netifd: Interface 'lan' has link connectivity
Fri Dec 28 15:30:14 2018 user.warn syslog: VRRP ID 72 on br-lan: 11.1.98.10 is up, we are now a backup router.
Fri Dec 28 15:30:14 2018 kern.info kernel: [94479.080000] eth0: link up (1000Mbps/Full duplex)
Fri Dec 28 15:30:14 2018 kern.info kernel: [94479.080000] br-lan: port 1(eth0) entered forwarding state
Fri Dec 28 15:30:14 2018 kern.info kernel: [94479.090000] br-lan: port 1(eth0) entered forwarding state
Fri Dec 28 15:30:14 2018 daemon.notice netifd: Network device 'eth0' link is up
Fri Dec 28 15:30:14 2018 kern.info kernel: [94479.410000] device wlan0 left promiscuous mode
Fri Dec 28 15:30:14 2018 kern.info kernel: [94479.410000] br-lan: port 2(wlan0) entered disabled state
Fri Dec 28 15:30:15 2018 daemon.notice netifd: Network device 'wlan0' link is down
Fri Dec 28 15:30:15 2018 user.info Messaged[17691]: Start from new event "VRRP" "Router is in backup mode"
Fri Dec 28 15:30:15 2018 daemon.notice netifd: Network device 'eth1' link is up
Fri Dec 28 15:30:15 2018 daemon.notice netifd: Interface 'wan' has link connectivity
Fri Dec 28 15:30:15 2018 daemon.notice netifd: Interface 'wan' is setting up now
Fri Dec 28 15:30:15 2018 kern.info kernel: [94479.700000] eth1: link up (100Mbps/Full duplex)

....

Regards,

Roland

by
Hey,

Possibly it is a bug. I would report it to Teltonika with following evidence:

- current topology diagram (IP scheme, VRRP peer router details)

- VRRP settings  (e.g ID, VIP etc)

- PCAP while issue was happening

- troubleshooting log file from RUT

- additional observation

Good luck,

Myky

1 Answer

0 votes
by
Hey,

l do not have 2 routers to test but I would start from the PCAP ( l assume routers share common L2 switch downstream). Just attach a laptop and fire up Wireshark. Traffic is multicast so you should be able to see VRRP exchange (routers` fight). This at least should give you some indication (more visibility l would say) on what is going on.

Thanks,

Myky
by

Hi and thank you for your answer.

I already tried that. VRRP protocol works as expected until the RUT240 should fall back to BACKUP state. Then all interfaces of the RUT240 (eth0, eth1, wlan) flap between up and down in about 5 to 10 seconds interval. For every interval, VRRP sends exactly one (lower prio) advertisement, because of the VRRP instance startup. The other router sends his (higher prio) advertisements every second.

Because of the up and down it is almost impossible to access the RUT240. But if I disconnect the third party router again, the RUT240 enters MASTER state and the flapping stops again.

It looks to me as if the RUT240 has a bug when switching from MASTER to BACKUP state.


This is only a small part of what gets logged to event log. I'll post the log file in a separate comment.


3287S
2018-12-28 15:32:02
Port
Wired WAN connection operational
3286S
2018-12-28 15:31:58
VRRP
Router is in master mode
3285S
2018-12-28 15:31:56
VRRP
Router is in backup mode
3284S
2018-12-28 15:31:56
Port
Wired WAN connection non operational
3283S
2018-12-28 15:31:55
Port
LAN cable is unplugged
3282S
2018-12-28 15:31:52
VRRP
Router is in master mode
3281S
2018-12-28 15:31:51
VRRP
Router is in backup mode
3280S
2018-12-28 15:31:49
Port
Wired WAN connection operational
3279S
2018-12-28 15:31:49
Port
LAN cable is plugged in
3278S
2018-12-28 15:31:46
VRRP
Router is in master mode
3277S
2018-12-28 15:31:44
VRRP
Router is in backup mode
3276S
2018-12-28 15:31:40
VRRP
Router is in master mode
3275S
2018-12-28 15:31:38
VRRP
Router is in backup mode
3274S
2018-12-28 15:31:38
Port
LAN cable is unplugged
3273S
2018-12-28 15:31:34
VRRP
Router is in master mode
3272S
2018-12-28 15:31:32
Port
Wired WAN connection non operational
3271S
2018-12-28 15:31:32
VRRP
Router is in backup mode
3270S
2018-12-28 15:31:28
VRRP
Router is in master mode
3269S
2018-12-28 15:31:26
VRRP
Router is in backup mode
3268S
2018-12-28 15:31:22
VRRP
Router is in master mode
3267S
2018-12-28 15:31:22
Port
LAN cable is plugged in
3266S
2018-12-28 15:31:20
VRRP
Router is in backup mode
3265S
2018-12-28 15:31:16
VRRP
Router is in master mode
3264S
2018-12-28 15:31:15
Port
Wired WAN connection operational
3263S
2018-12-28 15:31:14
Port
LAN cable is unplugged
3262S
2018-12-28 15:31:14
VRRP
Router is in backup mode
3261S
2018-12-28 15:31:10
VRRP
Router is in master mode
3260S
2018-12-28 15:31:09
Port
Wired WAN connection non operational
3259S
2018-12-28 15:31:08
VRRP
Router is in backup mode
3258S
2018-12-28 15:31:04
VRRP
Router is in master mode
3257S
2018-12-28 15:31:02
VRRP
Router is in backup mode
3256S
2018-12-28 15:30:58
VRRP
Router is in master mode
3255S
2018-12-28 15:30:56
VRRP
Router is in backup mode
3254S
2018-12-28 15:30:53
Port
Wired WAN connection operational
3253S
2018-12-28 15:30:52
VRRP
Router is in master mode
3252S
2018-12-28 15:30:50
VRRP
Router is in backup mode
3251S
2018-12-28 15:30:47
Port
Wired WAN connection non operational
3250S
2018-12-28 15:30:46
VRRP
Router is in master mode
3249S
2018-12-28 15:30:44
VRRP
Router is in backup mode
3248S
2018-12-28 15:30:40
VRRP
Router is in master mode
3247S
2018-12-28 15:30:38
VRRP
Router is in backup mode
3246S
2018-12-28 15:30:34
VRRP
Router is in master mode
3245S
2018-12-28 15:30:32
VRRP
Router is in backup mode
3244S
2018-12-28 15:30:31
Port
LAN cable is plugged in
3243S
2018-12-28 15:30:28
VRRP
Router is in master mode
3242S
2018-12-28 15:30:26
VRRP
Router is in backup mode
3241S
2018-12-28 15:30:25
Port
LAN cable is unplugged
3240S
2018-12-28 15:30:22
VRRP
Router is in master mode
3239S
2018-12-28 15:30:20
VRRP
Router is in backup mode
3238S
2018-12-28 15:30:19
Port
LAN cable is plugged in
3237S
2018-12-28 15:30:16
VRRP
Router is in master mode
3236S
2018-12-28 15:30:14
VRRP
Router is in backup mode
3235S
2018-12-28 15:30:13
Port
LAN cable is unplugged



Regards,

Roland