WIKIABOUT

FOR TIPS, gUIDES & TUTORIALS

subscribe to our Youtube

GO TO YOUTUBE

14455 questions

17168 answers

28195 comments

0 members

Most popular tags

rut955 rut240 rut950 rutx11 rms vpn to openvpn wifi not sms trb140 firmware connection - ipsec on rutx12 rutx09 modbus
We are migrating to our new platform at https://community.teltonika.lt. Moving forward, you can continue discussions on this new platform. This current platform will be temporarily maintained for reference purposes.

RUTX09 dnsmasq bug with single DNS entry

+1 vote
919 views 9 comments
by anonymous
Since one month my RUTX09 failed to receive an IP-address from the sunrise mobile network because there's a bug with dnsmasq.

I'm using the latest firmware EG06ELAR04A04M4G with RUTX_R_00.02.06.1.
 

Further details below...
by anonymous

Ok, the problem seems to be dnsmasq which handles wrong the received DNS entries.

On sunrise I only get a single DNS from the provider which results in a corrupted /tmp/dnsmasq.d/bridge file...

Sun May 30 12:20:15 2021 daemon.crit dnsmasq[10766]: bad IPv4 address at line 5 of /tmp/dnsmasq.d/bridge

Sun May 30 12:20:15 2021 daemon.crit dnsmasq[10766]: FAILED to start up

Sun May 30 12:20:15 2021 daemon.info procd: Instance dnsmasq::cfg01411c s in a crash loop 9 crashes, 0 seconds since last crash

/tmp/dnsmasq.d/bridge file:

dhcp-range=tag:mobbridge,*.*.*.*,static,255.255.255.128,1h

shared-network=br-lan,*.*.*.*

dhcp-host=11:11:11:11:11:11,set:mobbridge,*.*.*.*

dhcp-option=tag:mobbridge,br-lan,3,*.*.*.*

dhcp-option=tag:mobbridge,br-lan,6,*.*.*.*,

server=*.*.*.*

server=

by anonymous
Any changes to fix this ?
by anonymous
If I remove the leading comma in line 5 and delete the empty "server" entry, connection could successfully be established.
by anonymous
I have exactly this issue. From time to time dnsmasq will crash because of "bad IPv4 address at line 5 of /tmp/dnsmasq.d/bridge".

Inspecting the file shows an empty second DNS entry. I have captured a troubleshooting package when the modem is in the faulting state.

This is on an RUT 240 in passthrough mode.

2 Answers

0 votes
by anonymous
Hello,

Could you post your mobile configuration window and also correct config file entries? I will make sure to forward this information to our RnD team to investigate. Also, specify everything you can about this operator.

Regards.
by anonymous

(Mac address changed)

I tried custom DNS servers, but this makes no difference

I changed the /tmp/dnsmasq.d/bridge to the following

dhcp-range=tag:mobbridge,*.*.*.*,static,255.255.255.128,1h

shared-network=br-lan,*.*.*.*

dhcp-host=11:11:11:11:11:11,set:mobbridge,*.*.*.*

dhcp-option=tag:mobbridge,br-lan,3,*.*.*.*

dhcp-option=tag:mobbridge,br-lan,6,*.*.*.*

server=*.*.*.*

Here a snippet from the log

Sun May 30 12:20:14 2021 daemon.notice netifd: Interface 'mob1s1a1' is now up

Sun May 30 12:20:14 2021 daemon.notice netifd: Network device 'wwan0' link is up

Sun May 30 12:20:14 2021 daemon.notice netifd: mob1s1a1 (10380): [/dev/cdc-wdm0] Current settings retrieved:

Sun May 30 12:20:14 2021 daemon.notice netifd: mob1s1a1 (10380):            IP Family: IPv4

Sun May 30 12:20:14 2021 daemon.notice netifd: mob1s1a1 (10380):         IPv4 address: *.*.*.*

Sun May 30 12:20:14 2021 daemon.notice netifd: mob1s1a1 (10380):     IPv4 subnet mask: 255.255.255.128

Sun May 30 12:20:14 2021 daemon.notice netifd: mob1s1a1 (10380): IPv4 gateway address: *.*.*.*

Sun May 30 12:20:14 2021 daemon.notice netifd: mob1s1a1 (10380):     IPv4 primary DNS: *.*.*.*

Sun May 30 12:20:14 2021 daemon.notice netifd: mob1s1a1 (10380):                  MTU: 1460

Sun May 30 12:20:14 2021 daemon.notice netifd: mob1s1a1 (10380):              Domains: none

Sun May 30 12:20:14 2021 daemon.notice netifd: mob1s1a1 (10380): [/dev/cdc-wdm0] Client ID not released:

Sun May 30 12:20:14 2021 daemon.notice netifd: mob1s1a1 (10380): Service: 'wds'

Sun May 30 12:20:14 2021 daemon.notice netifd: mob1s1a1 (10380):    CID: '21'

Sun May 30 12:20:14 2021 kern.info kernel: [  202.907870] IPv6: ADDRCONF(NETDEV_UP): qmimux0: link is not ready

Sun May 30 12:20:14 2021 kern.info kernel: [  202.907985] IPv6: ADDRCONF(NETDEV_CHANGE): qmimux0: link becomes ready

Sun May 30 12:20:14 2021 daemon.notice netifd: Interface 'mob1s1a1_4' is enabled

Sun May 30 12:20:14 2021 daemon.notice netifd: Network device 'qmimux0' link is up

Sun May 30 12:20:14 2021 daemon.notice netifd: Interface 'mob1s1a1_4' has link connectivity

Sun May 30 12:20:14 2021 daemon.notice netifd: Interface 'mob1s1a1_4' is setting up now

Sun May 30 12:20:14 2021 daemon.notice netifd: Interface 'mob1s1a1_4' is now up

Sun May 30 12:20:15 2021 daemon.info dnsmasq[10197]: exiting on receipt of SIGTERM

Sun May 30 12:20:15 2021 daemon.crit dnsmasq[10766]: bad IPv4 address at line 5 of /tmp/dnsmasq.d/bridge

Sun May 30 12:20:15 2021 daemon.crit dnsmasq[10766]: FAILED to start up

Sun May 30 12:20:15 2021 daemon.info procd: Instance dnsmasq::cfg01411c s in a crash loop 9 crashes, 0 seconds since last crash

I have to make my changes in the /tmp/dnsmasq.d/bridge file before the "last try" of dnsmasq
by anonymous
The operator is the swiss company "Sunrise". Everything worked since the beginning (except the speed is very poor, but the signal strength is also very bad at the current location). But then about one month ago it suddenly stopped working. I can't remember if I applied the latest firmware update at that time... So maybe the problem was not present in RUTX_R_00.02.05. But it's definitely a bug in the handling of an empty DNS2 server, as the SIM works perfectly when inserted in a mobile phone.
by anonymous

As a workaround I just commented out the corresponding lines (responsible for dns2) in /lib/netifd/proto/connm.sh and /lib/netifd/proto/qmux.sh

My device is on a remote location and has to work after a reboot...

by anonymous
Hello,

Thank you very much for sharing your insight about this. I will share this information with our RnD team.
by anonymous
Any news on this?
0 votes
by anonymous

Still not fixed in RUTX_R_00.07.00