FOR TIPS, gUIDES & TUTORIALS

subscribe to our Youtube

GO TO YOUTUBE

14455 questions

17168 answers

28195 comments

0 members

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.
0 votes
361 views 0 comments
by anonymous

Hello,

dnsmasq works normally then breaks completely if something is changed on the mobile interface:

Feb  1 13:39:41 lgrrutx.lg dnsmasq[5102]: 97515 fd69:267b:e6f6::1cd4:79ea:4fcc:e458/24590 reply lapresse.cloud.optable.co is 34.120.235.16
Feb  1 13:39:44 lgrrutx.lg netifd: mob1s1a1_4 (1204): udhcpc: sending renew to 10.228.194.2
Feb  1 13:39:44 lgrrutx.lg mwan3track[633]: Check (ping) failed for target "8.8.8.8" on interface mob1s1a1 (wwan0)
Feb  1 13:39:45 lgrrutx.lg mwan3[23848]: Execute ifdown event on interface mob1s1a1 (wwan0)
Feb  1 13:39:46 lgrrutx.lg dnsmasq[5102]: 97516 fd69:267b:e6f6::1cd4:79ea:4fcc:e458/6447 query[A] fsm.lapresse.ca from fd69:267b:e6f6::1cd4:79ea:4fcc:e458
Feb  1 13:39:46 lgrrutx.lg dnsmasq[5102]: 97516 fd69:267b:e6f6::1cd4:79ea:4fcc:e458/6447 config error is REFUSED
Feb  1 13:39:46 lgrrutx.lg dnsmasq[5102]: 97517 192.168.8.211/41925 query[A] fsm.lapresse.ca from 192.168.8.211
Feb  1 13:39:46 lgrrutx.lg dnsmasq[5102]: 97517 192.168.8.211/41925 config error is REFUSED
Feb  1 13:39:46 lgrrutx.lg dnsmasq[5102]: read /etc/hosts - 7 addresses
Feb  1 13:39:46 lgrrutx.lg dnsmasq[5102]: read /tmp/hosts/odhcpd - 1 addresses
Feb  1 13:39:46 lgrrutx.lg dnsmasq[5102]: read /tmp/hosts/dhcp.cfg01411c - 2 addresses
Feb  1 13:39:46 lgrrutx.lg dnsmasq-dhcp[5102]: read /etc/ethers - 0 addresses
Feb  1 13:39:47 lgrrutx.lg mwan3track[633]: Detect ifdown event on interface mob1s1a1 (wwan0)
Feb  1 13:39:47 lgrrutx.lg dnsmasq[5102]: 97522 192.168.8.194/32778 query[A] p2p-foreign5.myfoscam.com from 192.168.8.194
Feb  1 13:39:47 lgrrutx.lg dnsmasq[5102]: 97522 192.168.8.194/32778 config error is REFUSED

The mobile interface still works, the device at the other end of the wireguard tunnel is still reachable.

This time the failure occurred after changing the data limit on SIM1, switching SIMs either manually or automatically on data limit generates the same behavior.

Stopping and restarting dnsmasq doesn't cures the problem, reboot does and I have found that executing "/etc/init.d/mwan3 restart" is enough to get rid of the REFUSED answers.

I have the lsof outputs of the two dnsmasq processes -- before and after the errors occur -- nothing significant.

Any idea ?

Regards,

1 Answer

0 votes
by anonymous
Hi,

Could you send me your troubleshoot file and reproducing steps for this issue via private message?

EB.