<div dir="ltr"><div>Hi Geert,</div><div><br></div><div>> It lacks the "why". I'll try to explain what I mean / miss</div><div><br></div><div>Thanks for your response. Lists like this have lots of functions, at the very least it's a method of seeing if anyone else has the same problem - it seems not at this point.</div><div><br></div><div>I think you're saying that it's not surprising that dnsmasq is not reading from the socket because the send queue is also full.</div><div><br></div><div>Taking random samples from netstat shows the receive socket is being serviced but packets are not being sent.</div><div><br></div><div>udp 191616 213376 <a href="http://192.168.1.1:53" target="_blank">192.168.1.1:53</a> 0.0.0.0:* <br>udp 188672 213376 <a href="http://192.168.1.1:53" target="_blank">192.168.1.1:53</a> 0.0.0.0:* <br>udp 185728 213376 <a href="http://192.168.1.1:53" target="_blank">192.168.1.1:53</a> 0.0.0.0:* <br>udp 185728 213376 <a href="http://192.168.1.1:53" target="_blank">192.168.1.1:53</a> 0.0.0.0:* <br>udp 185728 213376 <a href="http://192.168.1.1:53" target="_blank">192.168.1.1:53</a> 0.0.0.0:* <br>udp 182784 213376 <a href="http://192.168.1.1:53" target="_blank">192.168.1.1:53</a> 0.0.0.0:* <br>udp 182784 213376 <a href="http://192.168.1.1:53" target="_blank">192.168.1.1:53</a> 0.0.0.0:* <br>udp 182784 213376 <a href="http://192.168.1.1:53" target="_blank">192.168.1.1:53</a> 0.0.0.0:* <br>udp 179840 213376 <a href="http://192.168.1.1:53" target="_blank">192.168.1.1:53</a> 0.0.0.0:* <br>udp 179840 213376 <a href="http://192.168.1.1:53" target="_blank">192.168.1.1:53</a> 0.0.0.0:* <br>udp 175872 213376 <a href="http://192.168.1.1:53" target="_blank">192.168.1.1:53</a> 0.0.0.0:* <br>udp 175872 213376 <a href="http://192.168.1.1:53" target="_blank">192.168.1.1:53</a> 0.0.0.0:* <br>udp 175872 213376 <a href="http://192.168.1.1:53" target="_blank">192.168.1.1:53</a> 0.0.0.0:* </div><div><br></div><div>I managed to get to the device before syslog wrapped and I'm seeing these messages every second. Looks like the transmit socket is returning EAGAIN.</div><div><br></div><div>Mon Apr 25 14:55:17 2022 daemon.err dnsmasq[6268]: failed to send packet: Resource temporarily unavailable<br></div>Mon Apr 25 14:55:18 2022 daemon.err dnsmasq[6268]: failed to send packet: Resource temporarily unavailable<br>Mon Apr 25 14:55:19 2022 daemon.err dnsmasq[6268]: failed to send packet: Resource temporarily unavailable<br>Mon Apr 25 14:55:20 2022 daemon.err dnsmasq[6268]: failed to send packet: Resource temporarily unavailable<br>Mon Apr 25 14:55:21 2022 daemon.err dnsmasq[6268]: failed to send packet: Resource temporarily unavailable<br>Mon Apr 25 14:55:22 2022 daemon.err dnsmasq[6268]: failed to send packet: Resource temporarily unavailable<br><div><br></div><div>I'm going to experiment with removing bind-dynamic and see if that gives more information.</div><div><br></div><div>Thanks,<br>Tom</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, Apr 24, 2022 at 3:40 AM Geert Stappers via Dnsmasq-discuss <<a href="mailto:dnsmasq-discuss@lists.thekelleys.org.uk" target="_blank">dnsmasq-discuss@lists.thekelleys.org.uk</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Wed, Apr 20, 2022 at 07:38:52AM -0700, Tom Keddie via Dnsmasq-discuss wrote:<br>
> Hi All,<br>
> <br>
> We've been trying to track down some connectivity issues on unreleased<br>
> firmware for some of the openwrt based routers we sell<br>
<br>
Welcome to this mailinglist.<br>
<br>
<br>
> and have narrowed it to a dns issue.<br>
<br>
I do read that as a _possible_ DNS issue. ;-)<br>
<br>
<br>
> We're seeing dnsmasq 2.86 stop reading from one of its sockets after a<br>
> variable period of time with many (~45) clients. We also saw this problem<br>
> with dnsmasq 2.85 but on the single socket it opens.<br>
> <br>
> Upstream dns still works as does resolution on 127.0.0.1 but resolution on<br>
> the bridged lan interface, 192.168.1.1, is backed up and not responding.<br>
> <br>
> We do see some topology change events on the bridge but the interface has<br>
> been up since first boot and still responds to ping.<br>
> <br>
> Any suggestions are welcome.<br>
<br>
I do read that as <br>
"You have my awareness that I aim for win-win"<br>
<br>
<br>
> I did go through the pending commits for 2.87<br>
> but didn't see anything relevant. <br>
> I've included everything that I think might be useful here.<br>
<br>
It lacks the "why". I'll try to explain what I mean / miss<br>
<br>
<br>
> Thanks,<br>
> Tom Keddie<br>
> <br>
> root:~# netstat -anu<br>
<br>
I see the `netstat -anu`, but I don't see why this command<br>
and neither why this command as first.<br>
<br>
> Active Internet connections (servers and established)<br>
> Proto Recv-Q Send-Q Local Address Foreign Address State<br>
> udp 0 0 <a href="http://127.0.0.1:50032" rel="noreferrer" target="_blank">127.0.0.1:50032</a> 0.0.0.0:*<br>
> udp 0 0 <a href="http://127.0.0.1:38000" rel="noreferrer" target="_blank">127.0.0.1:38000</a> 0.0.0.0:*<br>
> udp 0 0 <a href="http://127.0.0.1:48000" rel="noreferrer" target="_blank">127.0.0.1:48000</a> 0.0.0.0:*<br>
> udp 0 0 <a href="http://127.0.0.1:37000" rel="noreferrer" target="_blank">127.0.0.1:37000</a> 0.0.0.0:*<br>
> udp 0 0 <a href="http://127.0.0.1:58000" rel="noreferrer" target="_blank">127.0.0.1:58000</a> 0.0.0.0:*<br>
> udp 0 0 <a href="http://0.0.0.0:51376" rel="noreferrer" target="_blank">0.0.0.0:51376</a> 0.0.0.0:*<br>
> udp 0 0 <a href="http://127.0.0.1:58032" rel="noreferrer" target="_blank">127.0.0.1:58032</a> 0.0.0.0:*<br>
> udp 0 0 <a href="http://127.0.0.1:46000" rel="noreferrer" target="_blank">127.0.0.1:46000</a> 0.0.0.0:*<br>
> udp 0 0 <a href="http://127.0.0.1:45000" rel="noreferrer" target="_blank">127.0.0.1:45000</a> 0.0.0.0:*<br>
> udp 0 0 <a href="http://127.0.0.1:44000" rel="noreferrer" target="_blank">127.0.0.1:44000</a> 0.0.0.0:*<br>
> udp 0 0 <a href="http://127.0.0.1:45032" rel="noreferrer" target="_blank">127.0.0.1:45032</a> 0.0.0.0:*<br>
> udp 0 0 <a href="http://127.0.0.1:43000" rel="noreferrer" target="_blank">127.0.0.1:43000</a> 0.0.0.0:*<br>
> udp 0 0 <a href="http://127.0.0.1:44032" rel="noreferrer" target="_blank">127.0.0.1:44032</a> 0.0.0.0:*<br>
> udp 0 0 <a href="http://127.0.0.1:42000" rel="noreferrer" target="_blank">127.0.0.1:42000</a> 0.0.0.0:*<br>
> udp 0 0 <a href="http://127.0.0.1:52000" rel="noreferrer" target="_blank">127.0.0.1:52000</a> 0.0.0.0:*<br>
> udp 0 0 <a href="http://127.0.0.1:42032" rel="noreferrer" target="_blank">127.0.0.1:42032</a> 0.0.0.0:*<br>
> udp 0 0 <a href="http://71.192.91.235:53" rel="noreferrer" target="_blank">71.192.91.235:53</a> 0.0.0.0:*<br>
> udp 0 0 <a href="http://127.0.0.1:53" rel="noreferrer" target="_blank">127.0.0.1:53</a> 0.0.0.0:*<br>
> udp 183552 213248 <a href="http://192.168.1.1:53" rel="noreferrer" target="_blank">192.168.1.1:53</a> 0.0.0.0:*<br>
> udp 0 0 <a href="http://127.0.0.1:51000" rel="noreferrer" target="_blank">127.0.0.1:51000</a> 0.0.0.0:*<br>
> udp 0 0 <a href="http://127.0.0.1:52032" rel="noreferrer" target="_blank">127.0.0.1:52032</a> 0.0.0.0:*<br>
> udp 0 0 <a href="http://0.0.0.0:67" rel="noreferrer" target="_blank">0.0.0.0:67</a> 0.0.0.0:*<br>
> udp 0 0 <a href="http://127.0.0.1:50000" rel="noreferrer" target="_blank">127.0.0.1:50000</a> 0.0.0.0:*<br>
> <br>
> <br>
> root:~# nslookup <a href="http://minim.co" rel="noreferrer" target="_blank">minim.co</a> 75.75.75.75<br>
<br>
Showing that 75.75.75.75 is working as DNS<br>
(75.75.75.75 is configured as upstream DNS)<br>
<br>
> Server: 75.75.75.75<br>
> Address: <a href="http://75.75.75.75:53" rel="noreferrer" target="_blank">75.75.75.75:53</a><br>
> <br>
> Non-authoritative answer:<br>
> Name: <a href="http://minim.co" rel="noreferrer" target="_blank">minim.co</a><br>
> Address: 18.215.222.49<br>
> <br>
> Non-authoritative answer:<br>
> <br>
> root:~# nslookup <a href="http://minim.co" rel="noreferrer" target="_blank">minim.co</a> 75.75.76.76<br>
<br>
Showing that 75.75.76.76 is working as DNS<br>
(75.75.76.76 is configured as upstream DNS)<br>
<br>
<br>
> Server: 75.75.76.76<br>
> Address: <a href="http://75.75.76.76:53" rel="noreferrer" target="_blank">75.75.76.76:53</a><br>
> <br>
> Non-authoritative answer:<br>
> <br>
> Non-authoritative answer:<br>
> Name: <a href="http://minim.co" rel="noreferrer" target="_blank">minim.co</a><br>
> Address: 18.215.222.49<br>
> <br>
> root:~# nslookup <a href="http://minim.co" rel="noreferrer" target="_blank">minim.co</a> 127.0.0.1<br>
<br>
Showing that 127.0.0.1 is working as DNS<br>
<br>
<br>
> Server: 127.0.0.1<br>
> Address: <a href="http://127.0.0.1:53" rel="noreferrer" target="_blank">127.0.0.1:53</a><br>
> <br>
> Non-authoritative answer:<br>
> Name: <a href="http://minim.co" rel="noreferrer" target="_blank">minim.co</a><br>
> Address: 18.215.222.49<br>
> <br>
> Non-authoritative answer:<br>
> <br>
> root:~# nslookup <a href="http://minim.co" rel="noreferrer" target="_blank">minim.co</a> 192.168.1.1<br>
<br>
The non-working DNS<br>
<br>
> ;; connection timed out; no servers could be reached<br>
> <br>
> root:~# ps w | grep dns<br>
<br>
Probably: dnsmasq is running and the configuration file it is using.<br>
<br>
<br>
> 6268 dnsmasq 2260 S /usr/sbin/dnsmasq -C /var/etc/dnsmasq.conf.cfg01411c -k -x /var/run/dnsmasq/dnsmasq.cfg01411c.pid<br>
> root:~# cat /var/etc/dnsmasq.conf.cfg01411c<br>
<br>
Show content of configuration file<br>
<br>
<br>
> # auto-generated config file from /etc/config/dhcp<br>
> conf-file=/etc/dnsmasq.conf<br>
> dhcp-authoritative<br>
> domain-needed<br>
> localise-queries<br>
> read-ethers<br>
> enable-ubus=dnsmasq<br>
> expand-hosts<br>
> bind-dynamic<br>
> local-service<br>
> edns-packet-max=1232<br>
> domain=lan<br>
> local=/lan/<br>
> addn-hosts=/tmp/hosts<br>
> dhcp-leasefile=/tmp/dhcp.leases<br>
> resolv-file=/tmp/resolv.conf.d/resolv.conf.auto<br>
> stop-dns-rebind<br>
> rebind-localhost-ok<br>
> dhcp-broadcast=tag:needs-broadcast<br>
> conf-dir=/tmp/dnsmasq.d<br>
> user=dnsmasq<br>
> group=dnsmasq<br>
> dhcp-host=00:0a:cd:32:6e:e9,192.168.1.193,Multisensor-Database<br>
> dhcp-ignore-names=tag:dhcp_bogus_hostname<br>
> conf-file=/usr/share/dnsmasq/dhcpbogushostname.conf<br>
> bogus-priv<br>
> conf-file=/usr/share/dnsmasq/rfc6761.conf<br>
> dhcp-range=set:lan,192.168.1.10,192.168.1.254,255.255.255.0,24h<br>
> <br>
> root:~# cat /tmp/resolv.conf.d/resolv.conf.auto<br>
<br>
Showing "/etc/resolv.conf"<br>
<br>
> # Interface wan<br>
> nameserver 75.75.75.75<br>
> nameserver 75.75.76.76<br>
> search <a href="http://hsd1.ma.comcast.net" rel="noreferrer" target="_blank">hsd1.ma.comcast.net</a>.<br>
> root:~# cat /tmp/dhcp.leases<br>
<br>
Might be to back the "many (~45) clients" statement<br>
<br>
<br>
> 1650547228 16:27:11:bd:95:42 192.168.1.208 OnePlus-Nord-N200-5G 01:16:27:11:bd:95:42<br>
> 1650510491 48:98:ca:9b:e3:cc 192.168.1.157 KNOK 01:48:98:ca:9b:e3:cc<br>
> 1650541991 12:0d:6e:11:0e:f1 192.168.1.222 Dennis-s-S21-Ultra 01:12:0d:6e:11:0e:f1<br>
> 1650535710 72:20:71:2f:c8:2f 192.168.1.123 * 01:72:20:71:2f:c8:2f<br>
> 1650533880 26:26:22:df:cb:e3 192.168.1.236 Galaxy-S10 01:26:26:22:df:cb:e3<br>
> 1650535136 00:0a:cd:32:6e:e9 192.168.1.193 Multisensor-Database 01:00:0a:cd:32:6e:e9<br>
> 1650491917 80:c1:6e:f3:f7:4c 192.168.1.182 * 01:80:c1:6e:f3:f7:4c<br>
> 1650534737 a4:83:e7:5a:49:33 192.168.1.99 ZoomDev 01:a4:83:e7:5a:49:33<br>
> 1650534463 6c:94:f8:a1:b4:fb 192.168.1.174 Denniss-iPad 01:6c:94:f8:a1:b4:fb<br>
> 1650548813 0c:cb:85:f7:e5:81 192.168.1.62 MH7601 *<br>
> 1650490643 0c:cb:85:f7:e5:80 192.168.1.61 * *<br>
> 1650548775 0c:cb:85:f7:e5:7d 192.168.1.58 * *<br>
> 1650537688 08:5b:d6:81:99:99 192.168.1.155 DESKTOP-QPFCJMS 01:08:5b:d6:81:99:99<br>
> 1650546045 0a:35:2a:f3:bb:6a 192.168.1.161 Pixel-3-XL 01:0a:35:2a:f3:bb:6a<br>
> 1650534279 48:98:ca:2a:5c:d0 192.168.1.206 CORI 01:48:98:ca:2a:5c:d0<br>
> 1650532675 4c:66:41:63:a3:ce 192.168.1.212 Galaxy-S7 01:4c:66:41:63:a3:ce<br>
> 1650532683 00:b5:d0:fc:cd:b5 192.168.1.16 Galaxy-Tab-A-2016 01:00:b5:d0:fc:cd:b5<br>
> 1650544456 00:51:ed:3b:53:b2 192.168.1.243 LGwebOSTV 01:00:51:ed:3b:53:b2<br>
> 1650547147 40:06:a0:a7:dc:a4 192.168.1.41 4006A0A7DCA4-mysimplelink *<br>
> 1650545297 34:20:03:ed:e2:e3 192.168.1.190 * *<br>
> 1650546997 5c:f3:70:26:7b:3f 192.168.1.30 DESKTOP-R3VI2U2 01:5c:f3:70:26:7b:3f<br>
> 1650490270 0c:cb:85:f7:e5:7c 192.168.1.57 * *<br>
> 1650546786 34:97:f6:b6:9b:01 192.168.1.127 DESKTOP-MVQ4Q7J 01:34:97:f6:b6:9b:01<br>
> 1650548017 5c:f3:70:26:7b:67 192.168.1.70 DESKTOP-59AGI93 01:5c:f3:70:26:7b:67<br>
> 1650546628 28:b2:bd:1a:03:06 192.168.1.186 kaplan-laptop 01:28:b2:bd:1a:03:06<br>
> 1650545301 34:20:03:ed:d1:40 192.168.1.84 * *<br>
> 1650546024 38:f9:d3:5e:02:e1 192.168.1.165 * 01:38:f9:d3:5e:02:e1<br>
> 1650546052 8c:85:90:4f:35:12 192.168.1.185 DVTs-MBP 01:8c:85:90:4f:35:12<br>
> 1650545303 34:20:03:ed:f1:6f 192.168.1.139 * *<br>
> 1650547347 60:dd:8e:d3:d1:6e 192.168.1.211 DVT-Test 01:60:dd:8e:d3:d1:6e<br>
> 1650545313 34:20:03:ed:d4:f1 192.168.1.78 * *<br>
> 1650545301 34:20:03:ed:ea:22 192.168.1.244 * *<br>
> 1650533137 48:43:dd:6b:86:50 192.168.1.221 * *<br>
> 1650533886 dc:f5:05:13:2f:51 192.168.1.184 P12100384 01:dc:f5:05:13:2f:51<br>
> 1650545293 34:20:03:ed:8d:7a 192.168.1.125 * *<br>
> 1650533065 b0:fc:0d:7a:80:b2 192.168.1.67 amazon-533fd135f 01:b0:fc:0d:7a:80:b2<br>
> 1650533016 d0:c5:d3:65:17:47 192.168.1.60 C72926881 01:d0:c5:d3:65:17:47<br>
> 1650510564 b4:e6:2d:03:b5:32 192.168.1.130 Etekcity-Outlet *<br>
> 1650546031 d4:25:8b:94:c3:de 192.168.1.251 * 01:d4:25:8b:94:c3:de<br>
> 1650545211 48:98:ca:f9:3a:d2 192.168.1.252 C58804806 01:48:98:ca:f9:3a:d2<br>
> 1650546123 b8:31:b5:ba:64:c9 192.168.1.18 XBOXONE 01:b8:31:b5:ba:64:c9<br>
> 1650534777 48:98:ca:f4:c2:bf 192.168.1.232 C58213759 01:48:98:ca:f4:c2:bf<br>
> 1650533023 bc:d7:d4:32:0f:ea 192.168.1.89 RokuUltra *<br>
> 1650541196 60:f8:1d:ab:eb:40 192.168.1.249 build-001 01:60:f8:1d:ab:eb:40<br>
> 1650550011 3c:06:30:3b:74:04 192.168.1.54 MacBook-Pro 01:3c:06:30:3b:74:04<br>
> root:~# ip addr<br>
<br>
Yes, but why?<br>
<br>
What are you trying to tell?? As in: What do you expect us to see???<br>
<br>
<br>
> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue qlen 1000<br>
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00<br>
> inet <a href="http://127.0.0.1/8" rel="noreferrer" target="_blank">127.0.0.1/8</a> scope host lo<br>
> valid_lft forever preferred_lft forever<br>
> 2: dummy0: <BROADCAST,NOARP> mtu 1500 qdisc noop qlen 1000<br>
> link/ether 22:ca:00:55:d9:ee brd ff:ff:ff:ff:ff:ff<br>
> 3: ifb0: <BROADCAST,NOARP> mtu 1500 qdisc noop qlen 32<br>
> link/ether ba:84:9c:1e:ec:ac brd ff:ff:ff:ff:ff:ff<br>
> 4: ifb1: <BROADCAST,NOARP> mtu 1500 qdisc noop qlen 32<br>
> link/ether 8e:9e:7d:ee:3a:6c brd ff:ff:ff:ff:ff:ff<br>
> 5: gre0@NONE: <NOARP> mtu 1476 qdisc noop qlen 1000<br>
> link/gre 0.0.0.0 brd 0.0.0.0<br>
> 6: gretap0@NONE: <BROADCAST,MULTICAST> mtu 1476 qdisc noop qlen 1000<br>
> link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff<br>
> 7: erspan0@NONE: <BROADCAST,MULTICAST> mtu 1464 qdisc noop qlen 1000<br>
> link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff<br>
> 8: sit0@NONE: <NOARP> mtu 1480 qdisc noop qlen 1000<br>
> link/sit 0.0.0.0 brd 0.0.0.0<br>
> 9: ip6gre0@NONE: <NOARP> mtu 1448 qdisc noop qlen 1000<br>
> link/[823] 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00 brd 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00<br>
> 10: archer: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue<br>
> link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff<br>
> 11: bcmsw: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000<br>
> link/ether 0c:cb:85:f7:e5:a8 brd ff:ff:ff:ff:ff:ff<br>
> 12: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000<br>
> link/ether 0c:cb:85:f7:e5:a9 brd ff:ff:ff:ff:ff:ff<br>
> inet <a href="http://71.192.91.235/22" rel="noreferrer" target="_blank">71.192.91.235/22</a> brd 71.192.91.255 scope global eth0<br>
> valid_lft forever preferred_lft forever<br>
> 13: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master br-lan qlen 1000<br>
> link/ether 0c:cb:85:f7:e5:a8 brd ff:ff:ff:ff:ff:ff<br>
> 14: wl0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master br-lan qlen 1000<br>
> link/ether 0c:cb:85:f7:e5:ab brd ff:ff:ff:ff:ff:ff<br>
> 15: wl1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master br-lan qlen 1000<br>
> link/ether 0c:cb:85:f7:e5:aa brd ff:ff:ff:ff:ff:ff<br>
> 18: br-lan: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue qlen 1000<br>
> link/ether 0c:cb:85:f7:e5:a8 brd ff:ff:ff:ff:ff:ff<br>
> inet <a href="http://192.168.1.1/24" rel="noreferrer" target="_blank">192.168.1.1/24</a> brd 192.168.1.255 scope global br-lan<br>
> valid_lft forever preferred_lft forever<br>
> 19: wl1.1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master br-lan qlen 1000<br>
> link/ether 72:cb:85:f7:e5:ab brd ff:ff:ff:ff:ff:ff<br>
> 29: wds1.1.1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast<br>
> master br-lan qlen 1000<br>
> link/ether 72:cb:85:f7:e5:ab brd ff:ff:ff:ff:ff:ff<br>
> 30: wds1.1.2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master br-lan qlen 1000<br>
> link/ether 72:cb:85:f7:e5:ab brd ff:ff:ff:ff:ff:ff<br>
> root:~# brctl show<br>
<br>
Why?<br>
<br>
<br>
> bridge name bridge id STP enabled interfaces<br>
> br-lan 7000.0ccb85f7e5a8 yes eth1<br>
> wds1.1.1<br>
> wds1.1.2<br>
> wl0<br>
> wl1<br>
> wl1.1<br>
> root:~# dmesg | grep br-lan<br>
<br>
Why?<br>
<br>
<br>
> [ 2257.008455] br-lan: port 1(eth1) entered blocking state<br>
> [ 2257.013706] br-lan: port 1(eth1) entered listening state<br>
> [ 2259.046965] br-lan: port 1(eth1) entered learning state<br>
> [ 2261.094953] br-lan: port 1(eth1) entered forwarding state<br>
> [ 2261.100376] br-lan: topology change detected, propagating<br>
> [ 2271.342450] br-lan: port 1(eth1) entered disabled state<br>
> [ 2279.536780] br-lan: port 1(eth1) entered blocking state<br>
> [ 2279.542056] br-lan: port 1(eth1) entered listening state<br>
> [ 2281.574810] br-lan: port 1(eth1) entered learning state<br>
> [ 2283.622807] br-lan: port 1(eth1) entered forwarding state<br>
> [ 2283.628240] br-lan: topology change detected, propagating<br>
> [ 4835.714957] br-lan: received packet on wl1 with own address as source address (addr:0c:cb:85:f7:e5:aa, vlan:0)<br>
> [ 6689.781276] br-lan: received packet on wl0 with own address as source address (addr:0c:cb:85:f7:e5:ab, vlan:0)<br>
> [10165.333204] br-lan: received packet on wl0 with own address as source address (addr:0c:cb:85:f7:e5:ab, vlan:0)<br>
> [20921.866775] br-lan: port 5(wds1.1.1) entered disabled state<br>
> [20921.883309] br-lan: port 5(wds1.1.1) entered disabled state<br>
> [20922.512373] br-lan: received packet on wl1 with own address as source address (addr:0c:cb:85:f7:e5:aa, vlan:0)<br>
> [20923.718768] br-lan: port 5(wds1.1.1) entered blocking state<br>
> [20923.725229] br-lan: port 5(wds1.1.1) entered disabled state<br>
> [20923.737857] br-lan: port 5(wds1.1.1) entered blocking state<br>
> [20923.743492] br-lan: port 5(wds1.1.1) entered listening state<br>
> [20925.766397] br-lan: port 5(wds1.1.1) entered learning state<br>
> [20927.814380] br-lan: port 5(wds1.1.1) entered forwarding state<br>
> [20927.820154] br-lan: topology change detected, propagating<br>
> [20930.280812] br-lan: port 5(wds1.1.1) received tcn bpdu<br>
> [20930.285982] br-lan: topology change detected, propagating<br>
> [20948.714635] br-lan: received packet on wl0 with own address as source address (addr:0c:cb:85:f7:e5:ab, vlan:0)<br>
> [26002.362865] br-lan: received packet on wl1 with own address as source address (addr:0c:cb:85:f7:e5:aa, vlan:0)<br>
> [26003.804245] br-lan: port 6(wds1.1.2) entered disabled state<br>
> [26003.821039] br-lan: port 6(wds1.1.2) entered disabled state<br>
> [26005.660527] br-lan: port 6(wds1.1.2) entered blocking state<br>
> [26005.667707] br-lan: port 6(wds1.1.2) entered disabled state<br>
> [26005.680231] br-lan: port 6(wds1.1.2) entered blocking state<br>
> [26005.685845] br-lan: port 6(wds1.1.2) entered listening state<br>
> [26007.703587] br-lan: port 6(wds1.1.2) entered learning state<br>
> [26009.751572] br-lan: port 6(wds1.1.2) entered forwarding state<br>
> [26009.757342] br-lan: topology change detected, propagating<br>
> [26010.603790] br-lan: port 6(wds1.1.2) received tcn bpdu<br>
> [26010.608954] br-lan: topology change detected, propagating<br>
> [26903.288550] br-lan: received packet on wl1 with own address as source address (addr:0c:cb:85:f7:e5:aa, vlan:0)<br>
> [29308.403115] br-lan: received packet on wl0 with own address as source address (addr:0c:cb:85:f7:e5:ab, vlan:0)<br>
> [44074.437481] br-lan: port 5(wds1.1.1) entered disabled state<br>
> [44074.453464] br-lan: port 5(wds1.1.1) entered disabled state<br>
> [44075.721563] br-lan: port 5(wds1.1.1) entered blocking state<br>
> [44075.727494] br-lan: port 5(wds1.1.1) entered disabled state<br>
> [44075.740713] br-lan: port 5(wds1.1.1) entered blocking state<br>
> [44075.746331] br-lan: port 5(wds1.1.1) entered listening state<br>
> [44077.811280] br-lan: port 5(wds1.1.1) entered learning state<br>
> [44079.859259] br-lan: port 5(wds1.1.1) entered forwarding state<br>
> [44079.865029] br-lan: topology change detected, propagating<br>
> [44082.572293] br-lan: port 5(wds1.1.1) received tcn bpdu<br>
> [44082.577454] br-lan: topology change detected, propagating<br>
> [44221.999541] br-lan: port 6(wds1.1.2) entered disabled state<br>
> [44222.022059] br-lan: port 6(wds1.1.2) entered disabled state<br>
> [44223.231419] br-lan: port 6(wds1.1.2) entered blocking state<br>
> [44223.237146] br-lan: port 6(wds1.1.2) entered disabled state<br>
> [44223.249414] br-lan: port 6(wds1.1.2) entered blocking state<br>
> [44223.255030] br-lan: port 6(wds1.1.2) entered listening state<br>
> [44225.265897] br-lan: port 6(wds1.1.2) entered learning state<br>
> [44227.313875] br-lan: port 6(wds1.1.2) entered forwarding state<br>
> [44227.319647] br-lan: topology change detected, propagating<br>
> [44228.227914] br-lan: port 6(wds1.1.2) received tcn bpdu<br>
> [44228.233077] br-lan: topology change detected, propagating<br>
> [44228.625036] br-lan: received packet on wl0 with own address as source address (addr:0c:cb:85:f7:e5:ab, vlan:0)<br>
> [55550.135997] br-lan: received packet on wl1 with own address as source address (addr:0c:cb:85:f7:e5:aa, vlan:0)<br>
> [56437.513600] br-lan: received packet on wl0 with own address as source address (addr:0c:cb:85:f7:e5:ab, vlan:0)<br>
> [56900.600612] br-lan: received packet on wl0 with own address as source address (addr:0c:cb:85:f7:e5:ab, vlan:0)<br>
> [57338.311331] br-lan: received packet on wl0 with own address as source address (addr:0c:cb:85:f7:e5:ab, vlan:0)<br>
> [57399.986991] br-lan: received packet on wl1 with own address as source address (addr:0c:cb:85:f7:e5:aa, vlan:0)<br>
> [57545.345542] br-lan: received packet on wl0 with own address as source address (addr:0c:cb:85:f7:e5:ab, vlan:0)<br>
> [58224.520851] br-lan: received packet on wl0 with own address as source address (addr:0c:cb:85:f7:e5:ab, vlan:0)<br>
> [61335.029068] br-lan: received packet on wl1 with own address as source address (addr:0c:cb:85:f7:e5:aa, vlan:0)<br>
> root:~# ping 192.168.1.1<br>
<br>
ping --count 5 192.168.1.1 # to show interface still responds to ping.<br>
<br>
<br>
> PING 192.168.1.1 (192.168.1.1): 56 data bytes<br>
> 64 bytes from <a href="http://192.168.1.1" rel="noreferrer" target="_blank">192.168.1.1</a>: seq=0 ttl=64 time=0.181 ms<br>
> ^C<br>
> --- 192.168.1.1 ping statistics ---<br>
> 1 packets transmitted, 1 packets received, 0% packet loss<br>
> round-trip min/avg/max = 0.181/0.181/0.181 ms<br>
<br>
<br>
<br>
Advice for digging deeper:<br>
<br>
watch 'netstat -anu | grep <a href="http://192.168.1.1:53" rel="noreferrer" target="_blank">192.168.1.1:53</a>'<br>
<br>
--log-queries=extra<br>
<br>
<br>
<br>
Groeten<br>
Geert Stappers<br>
-- <br>
Silence is hard to parse<br>
<br>
_______________________________________________<br>
Dnsmasq-discuss mailing list<br>
<a href="mailto:Dnsmasq-discuss@lists.thekelleys.org.uk" target="_blank">Dnsmasq-discuss@lists.thekelleys.org.uk</a><br>
<a href="https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss" rel="noreferrer" target="_blank">https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss</a><br>
</blockquote></div>