FOR TIPS, gUIDES & TUTORIALS

subscribe to our Youtube

GO TO YOUTUBE

14254 questions

16893 answers

27804 comments

54549 members

0 votes
207 views 7 comments
by
RUT300: WAN is and has been down since installing the router and it sets no IP from ISP. The delivered firmware was RUT30X_R_00.07.02.7. The WAN status was stopped from the beginning. Resetting to factory settings and upgrading to RUT30X_R_00.07.03.2 did not solve the problem. Now, the WAN status is Down, according to Network interfaces, with no IP. Strange enough both the system and the kernel logs tell WAN is up.

The last lines in the kernel log:

[  906.094750] eth1: link down

[ 1814.384440] eth1: link up (100Mbps/Full duplex)

[ 3301.230718] eth1: link down

[ 3316.016372] eth1: link up (100Mbps/Full duplex)

[ 3316.021973] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready

Attached is the system log. The last lines in it are:

Wed Jan 11 08:09:26 2023 kern.info kernel: [ 1814.384440] eth1: link up (100Mbps/Full duplex)

Wed Jan 11 08:09:26 2023 daemon.notice netifd: Network device 'eth1' link is up

Wed Jan 11 08:09:26 2023 daemon.notice netifd: Interface 'wan' has link connectivity

Wed Jan 11 08:09:26 2023 daemon.notice netifd: Interface 'wan' is setting up now

Wed Jan 11 08:09:26 2023 daemon.notice netifd: Interface 'wan6' has link connectivity

Wed Jan 11 08:09:26 2023 daemon.notice netifd: Interface 'wan6' is setting up now

Wed Jan 11 08:09:26 2023 kern.notice Port link state of port WAN changed to UP

Wed Jan 11 08:09:26 2023 daemon.notice odhcp6c[8293]: (re)starting transaction on eth1

Wed Jan 11 08:09:26 2023 daemon.info odhcp6c[8293]: Interface eth1 sending router solicitation message

Wed Jan 11 08:09:26 2023 daemon.notice netifd: wan (8292): udhcpc: started, v1.34.1

Wed Jan 11 08:09:26 2023 daemon.notice netifd: wan (8292): udhcpc: broadcasting discover

Wed Jan 11 08:09:26 2023 daemon.notice odhcp6c[8293]: Starting SOLICIT transaction (timeout 4294967295s, max rc 0)

Wed Jan 11 08:09:29 2023 daemon.notice netifd: wan (8292): udhcpc: broadcasting discover

Wed Jan 11 08:09:32 2023 daemon.notice netifd: wan (8292): udhcpc: broadcasting discover

Wed Jan 11 08:26:45 2023 kern.notice kernel: vuci configuration has been changed

Wed Jan 11 08:30:45 2023 daemon.err uhttpd[3422]: Failed to open /var/lib/luci-bwc/load: No such file or directory

Wed Jan 11 08:34:10 2023 kern.info kernel: network configuration has been changed

Wed Jan 11 08:34:10 2023 kern.info kernel: mwan3 configuration has been changed

Wed Jan 11 08:34:13 2023 kern.info kernel: [ 3301.230718] eth1: link down

Wed Jan 11 08:34:13 2023 daemon.notice odhcp6c[8293]: carrier => 0 event on

Wed Jan 11 08:34:13 2023 daemon.notice odhcp6c[8293]: (re)starting transaction on eth1

Wed Jan 11 08:34:13 2023 daemon.info odhcp6c[8293]: Interface eth1 sending router solicitation message

Wed Jan 11 08:34:13 2023 daemon.notice netifd: Network device 'eth1' link is down

Wed Jan 11 08:34:13 2023 daemon.notice netifd: Interface 'wan' has link connectivity loss

Wed Jan 11 08:34:13 2023 daemon.notice netifd: Interface 'wan6' has link connectivity loss

Wed Jan 11 08:34:13 2023 kern.notice Port link state of port WAN changed to DOWN

Wed Jan 11 08:34:13 2023 daemon.notice odhcp6c[8293]: Starting SOLICIT transaction (timeout 4294967295s, max rc 0)

Wed Jan 11 08:34:13 2023 daemon.notice netifd: Interface 'wan6' is now down

Wed Jan 11 08:34:13 2023 daemon.notice netifd: wan (8292): udhcpc: received SIGTERM

Wed Jan 11 08:34:13 2023 daemon.notice netifd: Interface 'wan' is now down

Wed Jan 11 08:34:13 2023 kern.notice Port link state of port WAN changed to DOWN

Wed Jan 11 08:34:13 2023 daemon.notice netifd: Interface 'wan' is disabled

Wed Jan 11 08:34:13 2023 kern.notice Port link state of port WAN changed to DOWN

Wed Jan 11 08:34:13 2023 kern.notice Port link state of port WAN changed to DOWN

Wed Jan 11 08:34:13 2023 daemon.notice netifd: Interface 'wan' is enabled

Wed Jan 11 08:34:17 2023 user.warn mwan3-hotplug[12676]: hotplug called on wan6 before mwan3 has been set up

Wed Jan 11 08:34:19 2023 user.warn mwan3-hotplug[12949]: hotplug called on wan before mwan3 has been set up

Wed Jan 11 08:34:27 2023 kern.info kernel: [ 3316.016372] eth1: link up (100Mbps/Full duplex)

Wed Jan 11 08:34:27 2023 kern.info kernel: [ 3316.021973] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready

Wed Jan 11 08:34:27 2023 daemon.notice netifd: Network device 'eth1' link is up

Wed Jan 11 08:34:27 2023 daemon.notice netifd: Interface 'wan' has link connectivity

Wed Jan 11 08:34:27 2023 daemon.notice netifd: Interface 'wan' is setting up now

Wed Jan 11 08:34:27 2023 kern.notice Port link state of port WAN changed to UP

Wed Jan 11 08:34:28 2023 daemon.notice netifd: wan (13069): udhcpc: started, v1.34.1

Wed Jan 11 08:34:28 2023 daemon.notice netifd: wan (13069): udhcpc: broadcasting discover

Wed Jan 11 08:34:31 2023 daemon.notice netifd: wan (13069): udhcpc: broadcasting discover

Wed Jan 11 08:34:34 2023 daemon.notice netifd: wan (13069): udhcpc: broadcasting discover

1 Answer

0 votes
by

Hello,

  

Thank you for reaching out!

It would be great if you can generate a full troubleshoot file by navigating to System → Administration → Troubleshoot. The file can be attached to your original post and will only be visible to Teltonika moderators.

However, the main issue seems to be that the device cannot receive an IPv6 address. Perhaps the RUT300 needs to be added from the ISP side? If you have your old device (if there was one), the MAC address can be overridden from the old router's WAN interface.

Otherwise, perhaps your ISP requires any special settings?

Does the ISP provide dual-stack services (IPv4 and IPv6)?

   

Awaiting your response!

Best regards,
DaumantasG

by
I've added the troubleshoot file.
by
Been in contact with ISP. WAN receives IP but does not take it. It requests IP again and again. Something to do with the configuration?
by
No particular settings received from ISP. IPv4 only.  Is this a problem?
by

Thank you for the information.

Could you try following this procedure to set one of the LAN ports as WAN and try connecting WAN to that port?

Did you configure anything on the router or is it on the default settings?

Could you try using a different Ethernet cable?

  

Awaiting your response.

Best regards,
DaumantasG

by

Also, if the steps above don't help, I'd like you to navigate to Services → Package Manager → Upload, then download the TCPdump package from here and upload it.

Then, navigate to System → Administration → Troubleshoot and enable the TCP dump option. Select interface eth1 and leave everything else on defaults.

Then restart the router, navigate to back to System → Administration → Troubleshoot and download the TCPdump file. It can also be attached to the original post.

  

Best regards,
DaumantasG

by
It was the cable! It didn't imagine it could be the cause. It is fixed-mounted and has not been subject to any movements for months. The LEDs indicated it was working. It seemed more probable that the fault was to be found in the router. I am really sorry for taking your time!  Thank you very much for your kind assistance!

Carl
by
Not a problem!

Sometimes issues like this take the most time to figure out.

  

Let us know is any further issues arise!

Best regards,

DaumantasG