#therearedays — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #therearedays, aggregated by home.social.
-
I just spent an hour #Labbing an #L2TPv3 pseudowire native fragmentation (#PWE3) problem. Turns out the platform doesn’t •do• native fragmentation, but it took forever for me to figure this out because my oversized #IPv6 pings were making it across the wire. This shouldn’t happen without native fragmentation.
Two coffees later it dawned on me that I was pinging from the device that was anchoring the pseudowire, so IPv6 was fragmenting at the source. A packet capture showed the fragmentation headers •and• the missing MRRU attribute in the L2TPv3 pseudowire setup. I should have started there.
-
I just spent an hour #Labbing an #L2TPv3 pseudowire native fragmentation (#PWE3) problem. Turns out the platform doesn’t •do• native fragmentation, but it took forever for me to figure this out because my oversized #IPv6 pings were making it across the wire. This shouldn’t happen without native fragmentation.
Two coffees later it dawned on me that I was pinging from the device that was anchoring the pseudowire, so IPv6 was fragmenting at the source. A packet capture showed the fragmentation headers •and• the missing MRRU attribute in the L2TPv3 pseudowire setup. I should have started there.
-
I just spent an hour #Labbing an #L2TPv3 pseudowire native fragmentation (#PWE3) problem. Turns out the platform doesn’t •do• native fragmentation, but it took forever for me to figure this out because my oversized #IPv6 pings were making it across the wire. This shouldn’t happen without native fragmentation.
Two coffees later it dawned on me that I was pinging from the device that was anchoring the pseudowire, so IPv6 was fragmenting at the source. A packet capture showed the fragmentation headers •and• the missing MRRU attribute in the L2TPv3 pseudowire setup. I should have started there.
-
I just spent an hour #Labbing an #L2TPv3 pseudowire native fragmentation (#PWE3) problem. Turns out the platform doesn’t •do• native fragmentation, but it took forever for me to figure this out because my oversized #IPv6 pings were making it across the wire. This shouldn’t happen without native fragmentation.
Two coffees later it dawned on me that I was pinging from the device that was anchoring the pseudowire, so IPv6 was fragmenting at the source. A packet capture showed the fragmentation headers •and• the missing MRRU attribute in the L2TPv3 pseudowire setup. I should have started there.
-
I just spent an hour #Labbing an #L2TPv3 pseudowire native fragmentation (#PWE3) problem. Turns out the platform doesn’t •do• native fragmentation, but it took forever for me to figure this out because my oversized #IPv6 pings were making it across the wire. This shouldn’t happen without native fragmentation.
Two coffees later it dawned on me that I was pinging from the device that was anchoring the pseudowire, so IPv6 was fragmenting at the source. A packet capture showed the fragmentation headers •and• the missing MRRU attribute in the L2TPv3 pseudowire setup. I should have started there.
-
After two weeks of off-and-on banging my head against this multicast routing lab, I finally found the problem. The default TTL for •all• multicast packets on Linux is… 1. Of course, I overlooked all of the simple stuff in my troubleshooting, as one does. #NetEng #Multicast #Troubleshooting #LessonLearned #ThereAreDays #Sigh