RUT X50 - Activate WAN port with I/O signal

[ELW]

Hello,

is there any possibility to activate the WAN port from the RUT X50 with an I/O signal?

Input/Output

Many thanks in advance.

Kind regards

Nicolai

[Daumantas]

Hello,

Indeed, this is possible and quite simple to configure:

• On your RUTX50, navigate to Services → Input/Output → I/O Juggler → Actions tab;

• Create two actions - one named up_wan, and another down_wan. Both should be of type Script;

• Here are the scripts for both rules: wan_change_state.zip (552 Bytes)

These are very simple scripts, that simply execute one command (ubus call to disable wan) and then log the port change in the system logs. No additional arguments are needed in the rule.

• Navigate to the General tab, and create two new rules for Input (3) pin - one will execute down_wan action upon Rising input pin,and another will execute up_wan upon Falling input pin. I’d also suggest increasing the interval, to avoid spamming the system logs with success messages.

• Finally, make sure the I/O Juggler, as well as both rules are enabled, and test the setup. Please use actual tests, as inverting the pin state in the WebUI will not trigger the created rules.

A few notes about the scripts:

• They execute commands to temporarily disable the WAN interface. This means that once the commands are executed, the WAN port will be disabled until the device is restarted, or the other script is ran to enable the port.

• If you have more than one physical device assigned to the WAN interface, they will also be disabled;

• Network → Interfaces → General, as well as port LEDs will still display this interface as “turned on”, but this is only visual. The interface itself will not be active.

Let me know if any more help is needed!

Best regards,

[ELW]

Hello Daumantas,

thank you very much for your kind reply.

I configured the RUT X50 as described in your message but it doesn´t work if I noticed correctly.

The WAN port is still up and traffic is running over this port even though the input 3 is down.

The I/O Juggler, as well as both rules are enabled (please take a look at the pictured attached).

I changed the trigger as followed:

rising: wan port up (up_wan)

falling: wan port down (down_wan)

trigger interval: 5 seconds

Many thanks in advance.

Kind regards
Nicolai

[ELW]

@Daumantas

make sure the I/O Juggler, as well as both rules are enabled

[ELW]

[ELW]

[ELW]

[ELW]

[ELW]

[Daumantas]

Hello,

The actios should be reversed - when the pin voltage is rising, the port should be turned off, and when the voltade is falling, the port should be turned on.
Let me know if this helps.

Best regards,

[ELW]

Hello,

I´ve changed the actions.

When the voltage is falling, the port turn on.

When the voltage is rising, the port is turned off.

Unfortunately it doesn´t work. WAN interface is still active even when the voltage is rising on input 3.

I´ve used the command interface (cmd → tracert www.google.com) and the complete network traffic is running through the WAN port.

IP: 192.168.0.1 → RUT X50 eg. RUT X11
192.168.1.1 → RUT 955 (connected to the WAN-Port from the RUT X50)

Kind regards

Nicolai

[Daumantas]

Hello,

Could you try logging into the device using SSH/CLI (username root, password is the same as the WebUI), and run these commands:

touch /etc/wan_down_script
touch /etc/wan_up_script
chmod +x /etc/wan_down_script
chmod +x /etc/wan_up_script
vi /etc/wan_down_script

When the VI editor opens up, press the i key, and paste the following script:

#!/bin/sh

ubus call network.interface.wan down #disable WAN interface
ubus call network.interface.wan6 down #disable WAN6 (IPv6) interface
logger "WAN port was turned off due to HIGH input signal"

exit 0

Press Esc key, then type :wq for Write and Quit.
Then edit the wan_up_script using the command vi /etc/wan_up_script. Paste the following script:

#!/bin/sh

ubus call network.interface.wan up #enable WAN interface
ubus call network.interface.wan6 up #enable WAN6 (IPv6) interface
logger "WAN port was turned on due to LOW input signal"

exit 0

Save and exit the script. In the WebUI, navigate to Services → Input/Output → I/O Juggler → Actions tab. Edit the previously created rules, and set the Specify path option to Specify a path. The path will be /etc/wan_down_script for the DOWN_WAN rule, and /etc/wan_up_script for UP_WAN rule.
Save the configuration and re-test if it’s working.

Best regards,

[ELW]

Hello,

thank you very much for your reply.

I´ve run the commands, but unfortunately the WAN-Port is not getting up again after signal from the I/O-Port is falling (low).

WAN port turn of due HIGH input signal but not turning on again due LOW input signal.

Kind regards

Nicolai

[Daumantas]

Hello,

Could you try replacing

ubus call network.interface.wan down #disable WAN interface
ubus call network.interface.wan6 down #disable WAN6 (IPv6) interface

with

uci set network.wan.disabled='1'
uci set network.wan6.disabled='1'
uci commit network
/etc/init.d/network restart

and

ubus call network.interface.wan up #enable WAN interface
ubus call network.interface.wan6 up #enable WAN6 (IPv6) interface

with

uci delete network.wan.disabled
uci delete network.wan6.disabled
uci commit network
/etc/init.d/network restart

These options will disable the WAN interface, so even a reboot will not bring it up. This should be kept in mind. Let me know if this helps.

Best regards,

[ELW]

Hello,

thank you very much for your effort.

I´ve used the following commands:

#!/bin/sh

uci set network.wan.disabled=‘1’
uci set network.wan6.disabled=‘1’
uci commit network
/etc/init.d/network restart
logger “WAN port was turned off due to HIGH input signal”

exit 0

---

#!/bin/sh

uci delete network.wan.disabled
uci delete network.wan6.disabled
uci commit network
/etc/init.d/network restart
logger “WAN port was turned on due to LOW input signal”

exit 0

Please take a look at the following logs.

WAN interface is shutting down if the input signal is “HIGH” but not starting again if the input signal is “LOW”.

Kind regards

Nicolai

[ELW]

[Daumantas]

Hello,

Apologies, missed that the network restart would be performed every 100 seconds, which is not very good for usability. I’d suggest reverting to the previous scripts.
From the previous logs, it seems like the WAN port does start working later. Could you check if the WAN interface receives an IP address?

Best regards,

[ELW]

Hello,

I´ve reset the router to factory settings and reverted to the following script:

touch /etc/wan_down_script
touch /etc/wan_up_script
chmod +x /etc/wan_down_script
chmod +x /etc/wan_up_script
vi /etc/wan_down_script

When the VI editor opens up, press the i key, and paste the following script:

#!/bin/sh

ubus call network.interface.wan down #disable WAN interface
ubus call network.interface.wan6 down #disable WAN6 (IPv6) interface
logger "WAN port was turned off due to HIGH input signal"

exit 0

Press Esc key, then type :wq for Write and Quit.
Then edit the wan_up_script using the command vi /etc/wan_up_script. Paste the following script:

#!/bin/sh

ubus call network.interface.wan up #enable WAN interface
ubus call network.interface.wan6 up #enable WAN6 (IPv6) interface
logger "WAN port was turned on due to LOW input signal"

exit 0

The WAN-interface is shutting down if the I/O-input receive a “High”-signal but not starting up again when a “LOW”-signal is applied to the pin.

Even if I pull the RJ45 plug from the WAN-Interface and plug it again, the interface is not starting up again.

The WAN-Interface receives an IP address (see picture below).

I also attached some extracts from the system log.

Thank you very much for your effort.

Kind regards
Nicolai

Mon Oct 9 08:46:36 2023 daemon.notice netifd: Interface ‘lan’ is enabled
Mon Oct 9 08:46:36 2023 daemon.notice netifd: Interface ‘lan’ is setting up now
Mon Oct 9 08:46:36 2023 daemon.notice netifd: Interface ‘lan’ is now up
Mon Oct 9 08:46:36 2023 daemon.notice netifd: Interface ‘loopback’ is enabled
Mon Oct 9 08:46:36 2023 daemon.notice netifd: Interface ‘loopback’ is setting up now
Mon Oct 9 08:46:36 2023 daemon.notice netifd: Interface ‘loopback’ is now up
Mon Oct 9 08:46:36 2023 daemon.notice netifd: Interface ‘wan’ is enabled
Mon Oct 9 08:46:36 2023 daemon.notice netifd: Interface ‘wan6’ is enabled
Mon Oct 9 08:46:36 2023 daemon.notice netifd: Network device ‘eth0’ link is up
Mon Oct 9 08:46:36 2023 kern.info kernel: [ 36.098172] ess_edma c080000.edma eth1: Link is Down
Mon Oct 9 08:46:36 2023 daemon.notice netifd: Network device ‘lo’ link is up
Mon Oct 9 08:46:36 2023 daemon.notice netifd: Interface ‘loopback’ has link connectivity
Mon Oct 9 08:46:36 2023 user.notice /bin/trigger_vuci_routes_reload: vuci reload_routes triggered
Mon Oct 9 08:46:37 2023 kern.info kernel: [ 37.033476] br-lan: port 1(eth0) entered blocking state
Mon Oct 9 08:46:37 2023 kern.info kernel: [ 37.033520] br-lan: port 1(eth0) entered forwarding state
Mon Oct 9 08:46:37 2023 kern.info kernel: [ 37.038029] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready
Mon Oct 9 08:46:37 2023 daemon.notice netifd: bridge ‘br-lan’ link is up
Mon Oct 9 08:46:37 2023 daemon.notice netifd: Interface ‘lan’ has link connectivity
Mon Oct 9 08:46:38 2023 kern.debug kernel: [ 37.298183] ath: EEPROM regdomain: 0x8348
Mon Oct 9 08:46:38 2023 kern.debug kernel: [ 37.298195] ath: EEPROM indicates we should expect a country code
Mon Oct 9 08:46:38 2023 kern.debug kernel: [ 37.298204] ath: doing EEPROM country->regdmn map search
Mon Oct 9 08:46:38 2023 kern.debug kernel: [ 37.298211] ath: country maps to regdmn code: 0x3a
Mon Oct 9 08:46:38 2023 kern.debug kernel: [ 37.298217] ath: Country alpha2 being used: US
Mon Oct 9 08:46:38 2023 kern.debug kernel: [ 37.298221] ath: Regpair used: 0x3a
Mon Oct 9 08:46:38 2023 kern.debug kernel: [ 37.298229] ath: regdomain 0x8348 dynamically updated by user
Mon Oct 9 08:46:38 2023 kern.debug kernel: [ 37.298259] ath: EEPROM regdomain: 0x8348
Mon Oct 9 08:46:38 2023 kern.debug kernel: [ 37.298263] ath: EEPROM indicates we should expect a country code
Mon Oct 9 08:46:38 2023 kern.debug kernel: [ 37.298270] ath: doing EEPROM country->regdmn map search
Mon Oct 9 08:46:38 2023 kern.debug kernel: [ 37.298276] ath: country maps to regdmn code: 0x3a
Mon Oct 9 08:46:38 2023 kern.debug kernel: [ 37.298280] ath: Country alpha2 being used: US
Mon Oct 9 08:46:38 2023 kern.debug kernel: [ 37.298284] ath: Regpair used: 0x3a
Mon Oct 9 08:46:38 2023 kern.debug kernel: [ 37.298289] ath: regdomain 0x8348 dynamically updated by user
Mon Oct 9 08:46:38 2023 daemon.notice procd: /etc/rc.d/S12simcard: Command failed: Not found
Mon Oct 9 08:46:38 2023 kern.info kernel: [ 38.175734] ess_edma c080000.edma eth1: Link is Up - 100Mbps/Full - flow control rx/tx
Mon Oct 9 08:46:38 2023 kern.info kernel: [ 38.175835] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
Mon Oct 9 08:46:38 2023 daemon.notice netifd: Network device ‘eth1’ link is up
Mon Oct 9 08:46:38 2023 daemon.notice netifd: Interface ‘wan’ has link connectivity
Mon Oct 9 08:46:38 2023 daemon.notice netifd: Interface ‘wan’ is setting up now
Mon Oct 9 08:46:38 2023 daemon.notice netifd: Interface ‘wan6’ has link connectivity
Mon Oct 9 08:46:38 2023 daemon.notice netifd: Interface ‘wan6’ is setting up now
Mon Oct 9 08:46:39 2023 daemon.notice netifd: wan (2519): udhcpc: started, v1.34.1
Mon Oct 9 08:46:39 2023 user.warn mwan3-hotplug[1808]: hotplug called on lan before mwan3 has been set up
Mon Oct 9 08:46:39 2023 daemon.err odhcp6c[2520]: Failed to send RS (Address not available)
Mon Oct 9 08:46:39 2023 daemon.notice odhcp6c[2520]: (re)starting transaction on eth1
Mon Oct 9 08:46:39 2023 daemon.info odhcp6c[2520]: Interface eth1 sending router solicitation message
Mon Oct 9 08:46:39 2023 daemon.notice netifd: wan (2519): udhcpc: broadcasting discover
Mon Oct 9 08:46:39 2023 daemon.notice netifd: wan (2519): udhcpc: broadcasting select for 192.168.1.229, server 192.168.1.1
Mon Oct 9 08:46:39 2023 daemon.notice netifd: wan (2519): udhcpc: lease of 192.168.1.229 obtained from 192.168.1.1, lease time 43200
Mon Oct 9 08:46:39 2023 daemon.notice hostapd: Configuration file: /var/run/hostapd-phy0.conf (phy wlan0) → new PHY
Mon Oct 9 08:46:39 2023 daemon.notice odhcp6c[2520]: Starting SOLICIT transaction (timeout 4294967295s, max rc 0)
Mon Oct 9 08:46:39 2023 daemon.err odhcp6c[2520]: Failed to send SOLICIT message to ff02::1:2 (Address not available)
Mon Oct 9 08:46:40 2023 daemon.err odhcp6c[2520]: Failed to send SOLICIT message to ff02::1:2 (Address not available)
Mon Oct 9 08:46:41 2023 daemon.notice netifd: Interface ‘wan’ is now up
Mon Oct 9 08:46:41 2023 daemon.info dnsmasq[1508]: reading /tmp/resolv.conf.d/resolv.conf.auto
Mon Oct 9 08:46:41 2023 daemon.info dnsmasq[1508]: using only locally-known addresses for domain test
Mon Oct 9 08:46:41 2023 daemon.info dnsmasq[1508]: using only locally-known addresses for domain onion
Mon Oct 9 08:46:41 2023 daemon.info dnsmasq[1508]: using only locally-known addresses for domain localhost
Mon Oct 9 08:46:41 2023 daemon.info dnsmasq[1508]: using only locally-known addresses for domain local
Mon Oct 9 08:46:41 2023 daemon.info dnsmasq[1508]: using only locally-known addresses for domain invalid
Mon Oct 9 08:46:41 2023 daemon.info dnsmasq[1508]: using only locally-known addresses for domain bind
Mon Oct 9 08:46:41 2023 daemon.info dnsmasq[1508]: using only locally-known addresses for domain lan
Mon Oct 9 08:46:41 2023 daemon.info dnsmasq[1508]: using nameserver 192.168.1.1#53
Mon Oct 9 08:46:41 2023 kern.info kernel: [ 40.499531] br-lan: port 2(wlan0) entered blocking state
Mon Oct 9 08:46:41 2023 kern.info kernel: [ 40.499568] br-lan: port 2(wlan0) entered disabled state
Mon Oct 9 08:46:41 2023 kern.info kernel: [ 40.504383] device wlan0 entered promiscuous mode
Mon Oct 9 08:46:41 2023 daemon.notice hostapd: wlan0: interface state UNINITIALIZED->COUNTRY_UPDATE
Mon Oct 9 08:46:41 2023 daemon.notice hostapd: ACS: Automatic channel selection started, this may take a bit
Mon Oct 9 08:46:41 2023 daemon.notice hostapd: wlan0: interface state COUNTRY_UPDATE->ACS
Mon Oct 9 08:46:41 2023 daemon.notice hostapd: wlan0: ACS-STARTED
Mon Oct 9 08:46:41 2023 daemon.notice hostapd: Configuration file: /var/run/hostapd-phy1.conf (phy wlan1) → new PHY
Mon Oct 9 08:46:41 2023 user.notice firewall: Reloading firewall due to ifup of lan (br-lan)
Mon Oct 9 08:46:41 2023 daemon.info dnsmasq[1508]: exiting on receipt of SIGTERM
Mon Oct 9 08:46:42 2023 daemon.err odhcp6c[2520]: Failed to send SOLICIT message to ff02::1:2 (Address not available)
Mon Oct 9 08:46:42 2023 kern.info kernel: [ 42.187264] br-lan: port 3(wlan1) entered blocking state
Mon Oct 9 08:46:42 2023 kern.info kernel: [ 42.187308] br-lan: port 3(wlan1) entered disabled state
Mon Oct 9 08:46:42 2023 kern.info kernel: [ 42.192073] device wlan1 entered promiscuous mode
Mon Oct 9 08:46:42 2023 kern.info kernel: [ 42.197255] br-lan: port 3(wlan1) entered blocking state
Mon Oct 9 08:46:42 2023 kern.info kernel: [ 42.201586] br-lan: port 3(wlan1) entered forwarding state
Mon Oct 9 08:46:42 2023 daemon.info dnsmasq[2772]: Connected to system UBus
Mon Oct 9 08:46:42 2023 daemon.info dnsmasq[2772]: started, version 2.85 cachesize 150
Mon Oct 9 08:46:42 2023 daemon.info dnsmasq[2772]: compile time options: IPv6 GNU-getopt no-DBus UBus no-i18n no-regex no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-auth no-cryptohash no-DNSSEC no-ID loop-detect inotify dumpfile
Mon Oct 9 08:46:42 2023 daemon.info dnsmasq[2772]: UBus support enabled: connected to system bus
Mon Oct 9 08:46:42 2023 daemon.info dnsmasq-dhcp[2772]: DHCP, IP range 192.168.0.150 – 192.168.0.200, lease time 12h
Mon Oct 9 08:46:42 2023 daemon.info dnsmasq[2772]: using only locally-known addresses for domain test
Mon Oct 9 08:46:42 2023 daemon.info dnsmasq[2772]: using only locally-known addresses for domain onion
Mon Oct 9 08:46:42 2023 kern.info kernel: [ 42.208620] br-lan: port 3(wlan1) entered disabled state
Mon Oct 9 08:46:42 2023 daemon.notice hostapd: wlan1: interface state UNINITIALIZED->COUNTRY_UPDATE
Mon Oct 9 08:46:42 2023 daemon.info dnsmasq[2772]: using only locally-known addresses for domain localhost
Mon Oct 9 08:46:42 2023 daemon.info dnsmasq[2772]: using only locally-known addresses for domain local
Mon Oct 9 08:46:42 2023 daemon.info dnsmasq[2772]: using only locally-known addresses for domain invalid
Mon Oct 9 08:46:42 2023 daemon.notice hostapd: wlan1: interface state COUNTRY_UPDATE->HT_SCAN
Mon Oct 9 08:46:42 2023 daemon.info dnsmasq[2772]: using only locally-known addresses for domain bind
Mon Oct 9 08:46:42 2023 daemon.info dnsmasq[2772]: using only locally-known addresses for domain lan
Mon Oct 9 08:46:42 2023 daemon.info dnsmasq[2772]: reading /tmp/resolv.conf.d/resolv.conf.auto
Mon Oct 9 08:46:42 2023 daemon.info dnsmasq[2772]: using only locally-known addresses for domain test
Mon Oct 9 08:46:42 2023 daemon.info dnsmasq[2772]: using only locally-known addresses for domain onion
Mon Oct 9 08:46:42 2023 daemon.info dnsmasq[2772]: using only locally-known addresses for domain localhost
Mon Oct 9 08:46:42 2023 daemon.info dnsmasq[2772]: using only locally-known addresses for domain local
Mon Oct 9 08:46:42 2023 daemon.info dnsmasq[2772]: using only locally-known addresses for domain invalid
Mon Oct 9 08:46:42 2023 daemon.info dnsmasq[2772]: using only locally-known addresses for domain bind
Mon Oct 9 08:46:42 2023 daemon.info dnsmasq[2772]: using only locally-known addresses for domain lan
Mon Oct 9 08:46:42 2023 daemon.info dnsmasq[2772]: using nameserver 192.168.1.1#53
Mon Oct 9 08:46:42 2023 daemon.info dnsmasq[2772]: read /etc/hosts - 4 addresses
Mon Oct 9 08:46:42 2023 daemon.info dnsmasq[2772]: read /tmp/hosts/dhcp.cfg01411c - 2 addresses
Mon Oct 9 08:46:42 2023 daemon.info dnsmasq-dhcp[2772]: read /etc/ethers - 0 addresses
Mon Oct 9 08:46:43 2023 daemon.notice netifd: Wireless device ‘radio0’ is now up
Mon Oct 9 08:46:43 2023 daemon.info dnsmasq[2772]: exiting on receipt of SIGTERM
Mon Oct 9 08:46:43 2023 daemon.info dnsmasq[3177]: Connected to system UBus
Mon Oct 9 08:46:43 2023 daemon.info dnsmasq[3177]: started, version 2.85 cachesize 150
Mon Oct 9 08:46:43 2023 daemon.info dnsmasq[3177]: compile time options: IPv6 GNU-getopt no-DBus UBus no-i18n no-regex no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-auth no-cryptohash no-DNSSEC no-ID loop-detect inotify dumpfile
Mon Oct 9 08:46:43 2023 daemon.info dnsmasq[3177]: UBus support enabled: connected to system bus
Mon Oct 9 08:46:43 2023 daemon.info dnsmasq-dhcp[3177]: DHCP, IP range 192.168.0.150 – 192.168.0.200, lease time 12h
Mon Oct 9 08:46:43 2023 daemon.info dnsmasq[3177]: using only locally-known addresses for domain test
Mon Oct 9 08:46:43 2023 daemon.info dnsmasq[3177]: using only locally-known addresses for domain onion
Mon Oct 9 08:46:43 2023 daemon.info dnsmasq[3177]: using only locally-known addresses for domain localhost
Mon Oct 9 08:46:43 2023 daemon.info dnsmasq[3177]: using only locally-known addresses for domain local
Mon Oct 9 08:46:43 2023 daemon.info dnsmasq[3177]: using only locally-known addresses for domain invalid
Mon Oct 9 08:46:43 2023 daemon.info dnsmasq[3177]: using only locally-known addresses for domain bind
Mon Oct 9 08:46:43 2023 daemon.info dnsmasq[3177]: using only locally-known addresses for domain lan
Mon Oct 9 08:46:43 2023 daemon.info dnsmasq[3177]: reading /tmp/resolv.conf.d/resolv.conf.auto
Mon Oct 9 08:46:43 2023 daemon.info dnsmasq[3177]: using only locally-known addresses for domain test
Mon Oct 9 08:46:43 2023 daemon.info dnsmasq[3177]: using only locally-known addresses for domain onion
Mon Oct 9 08:46:43 2023 daemon.info dnsmasq[3177]: using only locally-known addresses for domain localhost
Mon Oct 9 08:46:43 2023 daemon.info dnsmasq[3177]: using only locally-known addresses for domain local
Mon Oct 9 08:46:43 2023 daemon.info dnsmasq[3177]: using only locally-known addresses for domain invalid
Mon Oct 9 08:46:43 2023 daemon.info dnsmasq[3177]: using only locally-known addresses for domain bind
Mon Oct 9 08:46:43 2023 daemon.info dnsmasq[3177]: using only locally-known addresses for domain lan
Mon Oct 9 08:46:43 2023 daemon.info dnsmasq[3177]: using nameserver 192.168.1.1#53
Mon Oct 9 08:46:43 2023 daemon.info dnsmasq[3177]: read /etc/hosts - 4 addresses
Mon Oct 9 08:46:43 2023 daemon.info dnsmasq[3177]: read /tmp/hosts/dhcp.cfg01411c - 2 addresses
Mon Oct 9 08:46:43 2023 daemon.info dnsmasq-dhcp[3177]: read /etc/ethers - 0 addresses
Mon Oct 9 08:46:43 2023 daemon.info dnsmasq[3177]: read /etc/hosts - 4 addresses
Mon Oct 9 08:46:43 2023 daemon.info dnsmasq[3177]: read /tmp/hosts/dhcp.cfg01411c - 2 addresses
Mon Oct 9 08:46:43 2023 daemon.info dnsmasq-dhcp[3177]: read /etc/ethers - 0 addresses
Mon Oct 9 08:46:43 2023 kern.info kernel: [ 42.849441] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
Mon Oct 9 08:46:43 2023 kern.info kernel: [ 42.849773] br-lan: port 3(wlan1) entered blocking state
Mon Oct 9 08:46:43 2023 kern.info kernel: [ 42.854980] br-lan: port 3(wlan1) entered forwarding state
Mon Oct 9 08:46:43 2023 daemon.notice hostapd: wlan1: interface state HT_SCAN->ENABLED
Mon Oct 9 08:46:43 2023 daemon.notice hostapd: wlan1: AP-ENABLED
Mon Oct 9 08:46:43 2023 authpriv.warn dropbear[3289]: Failed loading /etc/dropbear/dropbear_rsa_host_key
Mon Oct 9 08:46:43 2023 authpriv.info dropbear[3289]: Not backgrounding
Mon Oct 9 08:46:44 2023 daemon.notice netifd: Wireless device ‘radio1’ is now up
Mon Oct 9 08:46:44 2023 daemon.notice netifd: Network device ‘wlan1’ link is up
Mon Oct 9 08:46:44 2023 user.warn mwan3-hotplug[3348]: hotplug called on loopback before mwan3 has been set up
Mon Oct 9 08:46:45 2023 user.notice mwan3-hotplug[3618]: Execute ifup event on interface wan (eth1)
Mon Oct 9 08:46:46 2023 daemon.info mobifd: [gsm.modem0] Initializing modem. Please wait.
Mon Oct 9 08:46:47 2023 user.notice mwan3track[3759]: Interface wan (eth1) is online
Mon Oct 9 08:46:47 2023 user.info kernel: [ 46.997030] kmodloader: loading kernel modules from /etc/modules-late.d/*
Mon Oct 9 08:46:47 2023 user.info kernel: [ 46.997596] kmodloader: done loading kernel modules from /etc/modules-late.d/*
Mon Oct 9 08:46:48 2023 user.notice mwan3-hotplug[4207]: Execute ifup event on interface wan (eth1)
Mon Oct 9 08:46:48 2023 kern.notice Port link state of port CPU/WiFi changed to UP
Mon Oct 9 08:46:48 2023 kern.notice Port speed for port CPU/WiFi changed to 1000 baseT
Mon Oct 9 08:46:48 2023 kern.notice Port link state of port WAN changed to UP
Mon Oct 9 08:46:48 2023 kern.notice Port speed for port WAN changed to 100 baseT
Mon Oct 9 08:46:48 2023 user.warn mwan3-hotplug[4207]: failed to add 192.168.0.0/24 dev br-lan proto static scope link metric 1 to table 1
Mon Oct 9 08:46:48 2023 user.warn mwan3-hotplug[4207]: failed to add 192.168.1.0/24 dev eth1 proto static scope link metric 2 to table 1
Mon Oct 9 08:46:48 2023 user.warn mwan3-hotplug[4207]: failed to add default via 192.168.1.1 dev eth1 proto static src 192.168.1.229 metric 2 to table 1
Mon Oct 9 08:46:49 2023 user.info mwan3track[3759]: Detect ifup event on interface wan (eth1)
Mon Oct 9 08:46:49 2023 user.info mwan3track[3759]: Check (ping) failed for target “1.1.1.1” on interface wan (eth1). Current score: 6
Mon Oct 9 08:46:49 2023 user.notice firewall: Reloading firewall due to ifup of wan (eth1)
Mon Oct 9 08:46:49 2023 daemon.notice hostapd: wlan0: ACS-COMPLETED freq=2412 channel=1
Mon Oct 9 08:46:50 2023 cron.err crond[4845]: crond (busybox 1.34.1) started, log level 5
Mon Oct 9 08:46:50 2023 kern.info kernel: [ 49.450629] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Mon Oct 9 08:46:50 2023 kern.info kernel: [ 49.451011] br-lan: port 2(wlan0) entered blocking state
Mon Oct 9 08:46:50 2023 kern.info kernel: [ 49.456151] br-lan: port 2(wlan0) entered forwarding state
Mon Oct 9 08:46:50 2023 daemon.notice netifd: Network device ‘wlan0’ link is up
Mon Oct 9 08:46:50 2023 daemon.notice hostapd: wlan0: interface state ACS->ENABLED
Mon Oct 9 08:46:50 2023 daemon.notice hostapd: wlan0: AP-ENABLED
Mon Oct 9 08:46:51 2023 user.info mwan3track[3759]: Check (ping) failed for target “8.8.8.8” on interface wan (eth1). Current score: 6
Mon Oct 9 08:46:51 2023 user.notice mwan3track[3759]: Interface wan (eth1) is disconnecting
Mon Oct 9 08:46:51 2023 cron.err crond[5264]: crond (busybox 1.34.1) started, log level 5
Mon Oct 9 08:46:51 2023 daemon.err insmod: module is already loaded - arc4
Mon Oct 9 08:46:51 2023 daemon.err insmod: module is already loaded - slhc
Mon Oct 9 08:46:51 2023 daemon.err insmod: module is already loaded - crc-ccitt
Mon Oct 9 08:46:51 2023 daemon.err insmod: module is already loaded - ppp_generic
Mon Oct 9 08:46:51 2023 daemon.err insmod: module is already loaded - ppp_async
Mon Oct 9 08:46:51 2023 daemon.err insmod: module is already loaded - ppp_mppe
Mon Oct 9 08:46:52 2023 user.notice mwan3track[3759]: Interface wan (eth1) is online
Mon Oct 9 08:46:52 2023 daemon.info mobifd: [gsm.modem0] Initializing modem. Please wait.
Mon Oct 9 08:46:55 2023 user.info mwan3track[3759]: Check (ping) failed for target “1.1.1.1” on interface wan (eth1). Current score: 5
Mon Oct 9 08:46:55 2023 daemon.info stunnel: No uci service section enabled or found!
Mon Oct 9 08:46:57 2023 user.info mwan3track[3759]: Check (ping) failed for target “8.8.8.8” on interface wan (eth1). Current score: 5
Mon Oct 9 08:46:57 2023 user.notice mwan3track[3759]: Interface wan (eth1) is disconnecting
Mon Oct 9 08:46:58 2023 cron.err crond[6742]: crond (busybox 1.34.1) started, log level 5
Mon Oct 9 08:46:58 2023 daemon.notice procd: /etc/rc.d/S96led: Command failed: Not found
Mon Oct 9 08:46:59 2023 daemon.info ledman[6983]: [set_eth_led_mode:36] error: Unable to set port led mode
Mon Oct 9 08:47:00 2023 daemon.info sim_switch[7357]: Starting sim_switch…
Mon Oct 9 08:47:00 2023 daemon.info sim_switch[7357]: Initializing uloop…
Mon Oct 9 08:47:00 2023 daemon.info sim_switch[7357]: Connecting to ubus…
Mon Oct 9 08:47:00 2023 daemon.info sim_switch[7357]: Reading configuration…
Mon Oct 9 08:47:00 2023 daemon.info sim_switch[7357]: Running…
Mon Oct 9 08:47:01 2023 daemon.info iojuggler: Starting up
Mon Oct 9 08:47:01 2023 daemon.err iojuggler: Set for subsription din1
Mon Oct 9 08:47:01 2023 daemon.err iojuggler: Set for subsription din1
Mon Oct 9 08:47:04 2023 user.info mwan3track[3759]: Check (ping) failed for target “1.1.1.1” on interface wan (eth1). Current score: 4
Mon Oct 9 08:47:04 2023 daemon.notice procd: /etc/rc.d/S99rut_fota: /etc/rc.common: line 25: arithmetic syntax error
Mon Oct 9 08:47:05 2023 daemon.info procd: - init complete -
Mon Oct 9 08:47:05 2023 daemon.info dfota[7553]: Searching for WAN…
Mon Oct 9 08:47:05 2023 daemon.info dfota[7553]: WAN found on interface: wan
Mon Oct 9 08:47:05 2023 daemon.info dfota[7553]: Preparing for gsm.modem0 update!
Mon Oct 9 08:47:05 2023 daemon.info dfota[7553]: Searching for updates…
Mon Oct 9 08:47:06 2023 user.info mwan3track[3759]: Check (ping) failed for target “8.8.8.8” on interface wan (eth1). Current score: 4
Mon Oct 9 08:47:06 2023 user.notice mwan3track[3759]: Interface wan (eth1) is offline
Mon Oct 9 08:47:06 2023 user.notice mwan3-hotplug[8969]: Execute disconnected event on interface wan (eth1)
Mon Oct 9 08:47:06 2023 kern.info WAN (wan) is down, no more backups to switch
Mon Oct 9 08:47:12 2023 daemon.info dfota[7553]: Connection error to FOTA server! ErrorCode: 169
Mon Oct 9 08:47:12 2023 daemon.info dfota[7553]: No update found!
Mon Oct 9 08:47:13 2023 cron.err crond[9400]: crond (busybox 1.34.1) started, log level 5
Mon Oct 9 08:47:13 2023 cron.err crond[9526]: crond (busybox 1.34.1) started, log level 5
Mon Oct 9 08:47:13 2023 daemon.info dfota[7553]: Update script done!
Mon Oct 9 08:47:47 2023 daemon.info hostapd: wlan0: STA 08:be:ac:13:ef:d4 IEEE 802.11: authenticated
Mon Oct 9 08:47:47 2023 daemon.info hostapd: wlan0: STA 08:be:ac:13:ef:d4 IEEE 802.11: associated (aid 1)
Mon Oct 9 08:47:47 2023 daemon.notice hostapd: wlan0: AP-STA-CONNECTED 08:be:ac:13:ef:d4
Mon Oct 9 08:47:47 2023 kern.notice RUT_F9A5_2G: WiFi client connected: 08:BE:AC:13:EF:D4
Mon Oct 9 08:47:47 2023 daemon.info hostapd: wlan0: STA 08:be:ac:13:ef:d4 RADIUS: starting accounting session 506AF223FF81F187
Mon Oct 9 08:47:47 2023 daemon.info hostapd: wlan0: STA 08:be:ac:13:ef:d4 WPA: pairwise key handshake completed (RSN)
Mon Oct 9 08:47:47 2023 daemon.info dnsmasq-dhcp[3177]: DHCPREQUEST(br-lan) 192.168.0.185 08:be:ac:13:ef:d4
Mon Oct 9 08:47:47 2023 daemon.warn dnsmasq-dhcp[3177]: Ignoring domain GSF-DOM.local for DHCP host name FEELW-03
Mon Oct 9 08:47:47 2023 daemon.info dnsmasq-dhcp[3177]: DHCPACK(br-lan) 192.168.0.185 08:be:ac:13:ef:d4 FEELW-03
Mon Oct 9 08:47:47 2023 kern.info Leased 192.168.0.185 IP address for client 08:be:ac:13:ef:d4 - FEELW-03 in WiFi
Mon Oct 9 08:47:56 2023 kern.notice Authentication was successful from HTTP 192.168.0.185
Mon Oct 9 08:47:56 2023 daemon.err uhttpd[3029]: vuci: accepted login for admin from 192.168.0.185
Mon Oct 9 08:48:16 2023 daemon.info iojuggler: executing action id=2
Mon Oct 9 08:48:16 2023 user.notice root: WAN port was turned off due to HIGH input signal
Mon Oct 9 08:48:16 2023 daemon.notice netifd: wan (2519): udhcpc: received SIGTERM
Mon Oct 9 08:48:16 2023 daemon.notice netifd: Interface ‘wan’ is now down
Mon Oct 9 08:48:16 2023 daemon.warn dnsmasq[3177]: no servers found in /tmp/resolv.conf.d/resolv.conf.auto, will retry
Mon Oct 9 08:48:16 2023 daemon.notice netifd: Interface ‘wan6’ is now down
Mon Oct 9 08:48:16 2023 kern.info kernel: [ 136.219306] ess_edma c080000.edma eth1: Link is Down
Mon Oct 9 08:48:16 2023 daemon.notice netifd: Interface ‘wan’ is disabled
Mon Oct 9 08:48:16 2023 daemon.notice netifd: Interface ‘wan6’ is disabled
Mon Oct 9 08:48:16 2023 daemon.notice netifd: Network device ‘eth1’ link is down
Mon Oct 9 08:48:16 2023 daemon.notice netifd: Interface ‘wan’ has link connectivity loss
Mon Oct 9 08:48:16 2023 daemon.notice netifd: Interface ‘wan6’ has link connectivity loss
Mon Oct 9 08:48:17 2023 daemon.info iojuggler: Input triggered too soon. Skipping
Mon Oct 9 08:48:17 2023 daemon.info iojuggler: Input triggered too soon. Skipping
Mon Oct 9 08:48:17 2023 user.notice mwan3-hotplug[9919]: Execute ifdown event on interface wan (unknown)
Mon Oct 9 08:48:17 2023 user.info mwan3track[3759]: Detect ifdown event on interface wan (eth1)
Mon Oct 9 08:48:17 2023 user.notice mwan3track[3759]: Interface wan (eth1) is offline
Mon Oct 9 08:48:17 2023 user.notice mwan3-hotplug[10088]: Execute disconnected event on interface wan (eth1)
Mon Oct 9 08:48:17 2023 daemon.info iojuggler: executing action id=2
Mon Oct 9 08:48:18 2023 user.notice root: WAN port was turned off due to HIGH input signal
Mon Oct 9 08:48:19 2023 user.notice mwan3-hotplug[10488]: mwan3 hotplug on wan6 not called because interface disabled
Mon Oct 9 08:48:30 2023 daemon.info sim_switch[7357]: [3-1] SIM switch in progress. Triggered by no_network rule
Mon Oct 9 08:48:30 2023 daemon.info mobifd: [gsm.modem0] Default SIM change initiated
Mon Oct 9 08:48:50 2023 kern.info kernel: Changing to SIM2: cellular network unavailable
Mon Oct 9 08:49:03 2023 daemon.info iojuggler: executing action id=1
Mon Oct 9 08:49:03 2023 daemon.info iojuggler: Input triggered too soon. Skipping
Mon Oct 9 08:49:03 2023 daemon.info iojuggler: Input triggered too soon. Skipping
Mon Oct 9 08:49:03 2023 daemon.info iojuggler: executing action id=1
Mon Oct 9 08:49:03 2023 daemon.info iojuggler: Input triggered too soon. Skipping
Mon Oct 9 08:49:03 2023 daemon.info iojuggler: Input triggered too soon. Skipping
Mon Oct 9 08:49:03 2023 daemon.info iojuggler: Input triggered too soon. Skipping
Mon Oct 9 08:49:03 2023 daemon.info iojuggler: Input triggered too soon. Skipping
Mon Oct 9 08:49:51 2023 daemon.info sim_switch[7357]: [3-1] SIM switch in progress. Triggered by no_network rule
Mon Oct 9 08:49:54 2023 daemon.info sim_switch[7357]: [3-1] SIM switch failed. ERR: Unable to retrieve valid simd response: Request timed out
Mon Oct 9 08:49:54 2023 daemon.info mobifd: [gsm.modem0] Default SIM change initiated
Mon Oct 9 08:49:56 2023 kern.notice Port link state of port WAN changed to DOWN
Mon Oct 9 08:50:05 2023 kern.notice Port link state of port WAN changed to UP
Mon Oct 9 08:50:05 2023 kern.notice Port speed for port WAN changed to 100 baseT

[ELW]

Hello Daumantas,

do you have any more suggestions?

Thanks

Kind regards