Conversation

Notices

1. Embed this notice
   Ryan Castellucci (they/them) :nonbinary_flag: (ryanc@infosec.exchange)'s status on Saturday, 25-Apr-2026 18:24:10 JST Ryan Castellucci (they/them) :nonbinary_flag:

   For posterity:

   root@prosser:~# uptime;ifconfig wan0
   08:49:42 up 146 days, 14:17, 3 users, load average: 0.45, 0.90, 1.07
   wan0: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1500
   inet 10.0.0.1 netmask 255.255.255.255 destination 10.0.0.2
   inet6 2001:db8::1 prefixlen 64 scopeid 0x0<global>
   inet6 fe80::1 prefixlen 128 scopeid 0x20<link>
   ppp txqueuelen 3 (Point-to-Point Protocol)
   RX packets 79998878431 bytes 117340968771628 (106.7 TiB)
   RX errors 0 dropped 766290 overruns 0 frame 0
   TX packets 22331621651 bytes 2331014472182 (2.1 TiB)
   TX errors 0 dropped 571640 overruns 0 carrier 0 collisions 0
   
   • Embed this notice
     Ryan Castellucci (they/them) :nonbinary_flag: (ryanc@infosec.exchange)'s status on Sunday, 26-Apr-2026 04:54:49 JST Ryan Castellucci (they/them) :nonbinary_flag:

     in reply to

     • Jeroen Massar

     @jeroen I am running a patched pppd that does not tear down the interface if the link drops, and I've unplugged the ONTs a couple of times, but that's unrelated to why I wasn't able to resolve domains through dnsmasq.

   • Embed this notice
     Jeroen Massar (jeroen@secluded.ch)'s status on Sunday, 26-Apr-2026 04:54:51 JST Jeroen Massar

     in reply to

     @ryanc dropped packets are not useful indeed, interesting to see that over an active ppp link ; tcpdump would have shown that certain packets did not get answers if one noticed those missing, but yeah drop counters is always important to check too. Did you restart the session or do you have an idea why things got dropped?
     (and I am assuming that you anonimized the IPv4 & IPv6 address, which is a good thing, as using example space is not typically the right thing)

   • Embed this notice
     Paul_IPv6 (paul_ipv6@infosec.exchange)'s status on Sunday, 26-Apr-2026 05:27:01 JST Paul_IPv6

     in reply to

     @ryanc

     when i was at a large ISP in the DNS team, we used to get called into outage meetings and the first assumption everyone always made was that any problem must be DNS until we'd proved otherwise.

     turns out that pretty much all the time, get packets to pass reliably was the problem, which broke everything including DNS.

     we had patches and stickers made with "!L3 == !DNS".