RUT240 - WAN isn't getting DHCP

Hi,

I’m plugging WAN coming from another router on a Teltonika RUT240. The WAN light immediately begins to blink. After a few seconds, the light turns off and nothing happen. WAN shows disconnected.

I get DHCP in my Laptop without any problem.

The RUT240 firmware is 7.04.05. I was in 7.05.4 before… since it’s was not working and all other RUT240 on other project work well I’ve downgraded, but the issue is still there.

Here’s a copy of the system log:
Mon Dec 4 18:43:33 2023 kern.info kernel: [ 669.316608] eth1: link up (10Mbps/Half duplex)
Mon Dec 4 18:43:33 2023 kern.info kernel: [ 669.320861] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
Mon Dec 4 18:43:33 2023 daemon.notice netifd: Network device ‘eth1’ link is up
Mon Dec 4 18:43:33 2023 daemon.notice netifd: Interface ‘wan’ has link connectivity
Mon Dec 4 18:43:33 2023 daemon.notice netifd: Interface ‘wan’ is setting up now
Mon Dec 4 18:43:33 2023 daemon.notice netifd: Interface ‘wan6’ has link connectivity
Mon Dec 4 18:43:33 2023 daemon.notice netifd: Interface ‘wan6’ is setting up now
Mon Dec 4 18:43:33 2023 kern.notice Port link state of port WAN changed to UP
Mon Dec 4 18:43:33 2023 kern.notice Port speed for port WAN changed to 10 baseT
Mon Dec 4 18:43:33 2023 daemon.err odhcp6c[10968]: Failed to send RS (Address not available)
Mon Dec 4 18:43:33 2023 daemon.notice odhcp6c[10968]: (re)starting transaction on eth1
Mon Dec 4 18:43:33 2023 daemon.info odhcp6c[10968]: Interface eth1 sending router solicitation message
Mon Dec 4 18:43:33 2023 daemon.notice netifd: wan (10969): udhcpc: started, v1.34.1
Mon Dec 4 18:43:34 2023 kern.info kernel: [ 670.339283] eth1: link down
Mon Dec 4 18:43:34 2023 daemon.notice netifd: Network device ‘eth1’ link is down
Mon Dec 4 18:43:34 2023 daemon.notice netifd: Interface ‘wan’ has link connectivity loss
Mon Dec 4 18:43:34 2023 daemon.notice netifd: Interface ‘wan6’ has link connectivity loss
Mon Dec 4 18:43:34 2023 daemon.notice netifd: wan (10969): Command failed: Permission denied
Mon Dec 4 18:43:34 2023 daemon.notice netifd: wan (10969): udhcpc: broadcasting discover
Mon Dec 4 18:43:34 2023 daemon.notice netifd: wan6 (10968): Command failed: Permission denied
Mon Dec 4 18:43:34 2023 daemon.notice odhcp6c[10968]: Starting SOLICIT transaction (timeout 4294967295s, max rc 0)
Mon Dec 4 18:43:34 2023 daemon.notice odhcp6c[10968]: carrier => 0 event on
Mon Dec 4 18:43:34 2023 daemon.notice odhcp6c[10968]: (re)starting transaction on eth1
Mon Dec 4 18:43:34 2023 daemon.info odhcp6c[10968]: Interface eth1 sending router solicitation message
Mon Dec 4 18:43:34 2023 daemon.notice netifd: wan (10969): udhcpc: received SIGTERM
Mon Dec 4 18:43:34 2023 daemon.notice netifd: Interface ‘wan’ is now down
Mon Dec 4 18:43:34 2023 kern.notice Port link state of port WAN changed to DOWN
Mon Dec 4 18:43:34 2023 daemon.notice odhcp6c[10968]: Starting SOLICIT transaction (timeout 4294967295s, max rc 0)
Mon Dec 4 18:43:34 2023 daemon.notice netifd: Interface ‘wan6’ is now down
Mon Dec 4 18:43:37 2023 user.warn mwan3-hotplug[10993]: hotplug called on wan before mwan3 has been set up
Mon Dec 4 18:43:40 2023 user.warn mwan3-hotplug[11156]: hotplug called on wan6 before mwan3 has been set up
Mon Dec 4 18:43:47 2023 kern.info kernel: [ 683.684611] eth1: link up (10Mbps/Half duplex)
Mon Dec 4 18:43:47 2023 daemon.notice netifd: Network device ‘eth1’ link is up
Mon Dec 4 18:43:47 2023 daemon.notice netifd: Interface ‘wan’ has link connectivity
Mon Dec 4 18:43:47 2023 daemon.notice netifd: Interface ‘wan’ is setting up now
Mon Dec 4 18:43:47 2023 daemon.notice netifd: Interface ‘wan6’ has link connectivity
Mon Dec 4 18:43:47 2023 daemon.notice netifd: Interface ‘wan6’ is setting up now
Mon Dec 4 18:43:47 2023 daemon.notice odhcp6c[11290]: (re)starting transaction on eth1
Mon Dec 4 18:43:47 2023 daemon.info odhcp6c[11290]: Interface eth1 sending router solicitation message
Mon Dec 4 18:43:47 2023 daemon.notice netifd: wan (11292): udhcpc: started, v1.34.1
Mon Dec 4 18:43:47 2023 kern.notice Port link state of port WAN changed to UP
Mon Dec 4 18:43:47 2023 kern.notice Port speed for port WAN changed to 10 baseT
Mon Dec 4 18:43:48 2023 daemon.notice odhcp6c[11290]: Starting SOLICIT transaction (timeout 4294967295s, max rc 0)
Mon Dec 4 18:43:48 2023 daemon.notice netifd: wan (11292): udhcpc: broadcasting discover
Mon Dec 4 18:43:48 2023 kern.info kernel: [ 684.725202] eth1: link down
Mon Dec 4 18:43:48 2023 daemon.notice odhcp6c[11290]: carrier => 0 event on
Mon Dec 4 18:43:48 2023 daemon.notice odhcp6c[11290]: (re)starting transaction on eth1
Mon Dec 4 18:43:48 2023 daemon.info odhcp6c[11290]: Interface eth1 sending router solicitation message
Mon Dec 4 18:43:48 2023 daemon.notice netifd: Network device ‘eth1’ link is down
Mon Dec 4 18:43:48 2023 daemon.notice netifd: Interface ‘wan’ has link connectivity loss
Mon Dec 4 18:43:48 2023 daemon.notice netifd: Interface ‘wan6’ has link connectivity loss
Mon Dec 4 18:43:48 2023 daemon.notice netifd: wan (11292): udhcpc: received SIGTERM
Mon Dec 4 18:43:48 2023 daemon.notice netifd: Interface ‘wan’ is now down
Mon Dec 4 18:43:49 2023 kern.notice Port link state of port WAN changed to DOWN
Mon Dec 4 18:43:49 2023 daemon.notice odhcp6c[11290]: Starting SOLICIT transaction (timeout 4294967295s, max rc 0)
Mon Dec 4 18:43:49 2023 daemon.notice netifd: Interface ‘wan6’ is now down
Mon Dec 4 18:43:52 2023 user.warn mwan3-hotplug[11313]: hotplug called on wan before mwan3 has been set up.

Hi,
found a solution yet?

10 Mbps is an “emergency mode”, it onle gets active if

  • a device is in sleep mode with wake-on-lan enabled
  • you have a (really old) LAN cable with just four wires (pins 1,2,3,6)
  • you have a cable that’s defective
  • if the port of the device is not auto-negotiating correctly
  • etc

First I’d check the cable/use a different one.

Regards,
Timelapse Admin

Hello,

Thanks for reaching us.

I can see that there is a stability issue on the connection, so kindly note the following notes:

1- Verify that the cable is not damaged (Try a new cable)
2- Perform a clean factory reset both devices to start a clean configuration
3- Double-check the WAN configuration in the RUT240 interface, make sure it is configured to obtain an IP address via DHCP.
4- Verify as well that there are no conflicting configurations, such as duplicate IP addresses.
5- I would advice to re upgrade the firmware to the latest one 7.05.4
6- try connecting to the WAN port in different RUT240 device to make sure that issue is not from the current device

Hope it helps.

Thanks

Hi,

Cable is working fine with my laptop. There’s no IP conflict, the RUT240 is the only device under the internet modem… As an OEM, we replicate the same configuration over and over… I know the configuration work on the 22 other devices already sold with our control panel. I got random trouble with all last 6 units purchased using the 7.05.4 firmware. It’s either the firmware or the device.

This RUT240 device gives me so much trouble… I’ve decided to just replace the unit. Time is money… and I’ve lost so much time on these devices.

This topic was automatically closed after 15 days. New replies are no longer allowed.