Search
268 results for “ghostinthenet”
-
Taking a break from the day to day for an awesome event in Toronto. #NetEng https://tornog.ca/events/tornog-1/
-
Taking a break from the day to day for an awesome event in Toronto. #NetEng https://tornog.ca/events/tornog-1/
-
Taking a break from the day to day for an awesome event in Toronto. #NetEng https://tornog.ca/events/tornog-1/
-
Taking a break from the day to day for an awesome event in Toronto. #NetEng https://tornog.ca/events/tornog-1/
-
Taking a break from the day to day for an awesome event in Toronto. #NetEng https://tornog.ca/events/tornog-1/
-
-
-
-
-
-
I’m wondering if @mikrotik has thought of adding “access point” on the back of these? Maybe taking the joke a little too far? https://merch.mikrotik.com/products/groove-boxer-briefs #WiFi #NetEng #Merch
-
I’m wondering if @mikrotik has thought of adding “access point” on the back of these? Maybe taking the joke a little too far? https://merch.mikrotik.com/products/groove-boxer-briefs #WiFi #NetEng #Merch
-
I’m wondering if @mikrotik has thought of adding “access point” on the back of these? Maybe taking the joke a little too far? https://merch.mikrotik.com/products/groove-boxer-briefs #WiFi #NetEng #Merch
-
I’m wondering if @mikrotik has thought of adding “access point” on the back of these? Maybe taking the joke a little too far? https://merch.mikrotik.com/products/groove-boxer-briefs #WiFi #NetEng #Merch
-
I’m wondering if @mikrotik has thought of adding “access point” on the back of these? Maybe taking the joke a little too far? https://merch.mikrotik.com/products/groove-boxer-briefs #WiFi #NetEng #Merch
-
For anyone interested in my “Scalable and Secure Self-Serve RouterOS Remote Management” presentation at the MikroTik Professionals Conference in Prague, the slide deck, #Docker, and #ContainerLab files can be found here. https://github.com/ghostinthenet/l2vpnLab #MTPC #NetEng
-
For anyone interested in my “Scalable and Secure Self-Serve RouterOS Remote Management” presentation at the MikroTik Professionals Conference in Prague, the slide deck, #Docker, and #ContainerLab files can be found here. https://github.com/ghostinthenet/l2vpnLab #MTPC #NetEng
-
For anyone interested in my “Scalable and Secure Self-Serve RouterOS Remote Management” presentation at the MikroTik Professionals Conference in Prague, the slide deck, #Docker, and #ContainerLab files can be found here. https://github.com/ghostinthenet/l2vpnLab #MTPC #NetEng
-
For anyone interested in my “Scalable and Secure Self-Serve RouterOS Remote Management” presentation at the MikroTik Professionals Conference in Prague, the slide deck, #Docker, and #ContainerLab files can be found here. https://github.com/ghostinthenet/l2vpnLab #MTPC #NetEng
-
For anyone interested in my “Scalable and Secure Self-Serve RouterOS Remote Management” presentation at the MikroTik Professionals Conference in Prague, the slide deck, #Docker, and #ContainerLab files can be found here. https://github.com/ghostinthenet/l2vpnLab #MTPC #NetEng
-
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.