<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Networking on Drown in Codes</title><link>https://blog.swineson.me/en/category/networking/</link><description>Recent content in Networking on Drown in Codes</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><copyright>Jamesits</copyright><lastBuildDate>Sat, 19 Jun 2021 02:44:23 +0000</lastBuildDate><atom:link href="https://blog.swineson.me/en/category/networking/index.xml" rel="self" type="application/rss+xml"/><item><title>Mellanox ConnectX-3 Firmware Flashing and Configuration for Both Ethernet and InfiniBand in 2021</title><link>https://blog.swineson.me/en/mellanox-connectx-3-firmware-flashing-and-configuration-for-both-ethernet-and-infiniband-in-2021/</link><pubDate>Sat, 19 Jun 2021 02:44:23 +0000</pubDate><guid>https://blog.swineson.me/en/mellanox-connectx-3-firmware-flashing-and-configuration-for-both-ethernet-and-infiniband-in-2021/</guid><description>Introduction Although old, Mellanox ConnectX-3 has been a good card with decent performance and a good price on second-hand markets. This makes it the straightforward choice for a high-performance home or lab network. (If you intend to run InfiniBand on ESXi 7.0 or higher, go for CX4 or higher.) Sometimes you would find a card with a strange firmware or one not compatible with your existent gear. Luckily you can change the port configuration on all CX3 cards with a simple firmware flash.</description></item><item><title>Juniper SRX as a DHCPv6 PD Client on a PPPoE Interface</title><link>https://blog.swineson.me/en/juniper-srx-as-a-dhcpv6-pd-client-on-a-pppoe-interface/</link><pubDate>Thu, 18 Feb 2021 06:52:52 +0000</pubDate><guid>https://blog.swineson.me/en/juniper-srx-as-a-dhcpv6-pd-client-on-a-pppoe-interface/</guid><description>&lt;p>Recently my ISP fixed the compatibility issues between their Huawei BRAS and my Junos router. After some digging, I managed to get some IPv6 address allocation for all my client devices. Here&amp;rsquo;s how I achieved it.&lt;/p></description></item><item><title>DHCP Server on Juniper SRX</title><link>https://blog.swineson.me/en/dhcp-server-on-juniper-srx/</link><pubDate>Fri, 12 Feb 2021 15:28:52 +0000</pubDate><guid>https://blog.swineson.me/en/dhcp-server-on-juniper-srx/</guid><description>This article provides everything you need to setup a local DHCP server on a SRX security device.
JDHCPD vs DHCPD JDHCPD provides more functionalities than DHCPD, so it is recommended to use JDHCPD on new setups. (Feature comparison)
DHCP and uRPF If you have uRPF and DHCP setup on the same interface, by default all DHCP traffic will be dropped. To make DHCP work, you need to set up an exemption:</description></item><item><title>Access Services on the Router from VRF on RouterOS 6</title><link>https://blog.swineson.me/en/access-services-on-the-router-from-vrf-on-routeros-6/</link><pubDate>Sat, 21 Nov 2020 12:08:02 +0000</pubDate><guid>https://blog.swineson.me/en/access-services-on-the-router-from-vrf-on-routeros-6/</guid><description>It is always a misconception that you can&amp;rsquo;t access services (management services like HTTP, WinBox or SNMP, and end-user services like SMB or DNS) from a VRF on RouterOS 6.x. In fact, you can, and here&amp;rsquo;s how you can achieve it.
The Theory No service (except ICMP echo, if you count it as a service) on RouterOS 6.x is VRF aware. That means, the service daemons do listen on all the IPs on all the VRFs, but when they send a reply packet, the packet is only routed using the main (global) routing table.</description></item><item><title>Access Services on the Router from VRF on RouterOS 6</title><link>https://blog.swineson.me/en/access-services-on-the-router-from-vrf-on-routeros-6/</link><pubDate>Sat, 21 Nov 2020 12:08:02 +0000</pubDate><guid>https://blog.swineson.me/en/access-services-on-the-router-from-vrf-on-routeros-6/</guid><description>It is always a misconception that you can&amp;rsquo;t access services (management services like HTTP, WinBox or SNMP, and end-user services like SMB or DNS) from a VRF on RouterOS 6.x. In fact, you can, and here&amp;rsquo;s how you can achieve it.
The Theory No service (except ICMP echo, if you count it as a service) on RouterOS 6.x is VRF aware. That means, the service daemons do listen on all the IPs on all the VRFs, but when they send a reply packet, the packet is only routed using the main (global) routing table.</description></item><item><title>What the Flow: Reverse Route Modes on Juniper SRX</title><link>https://blog.swineson.me/en/reverse-route-modes-on-juniper-srx/</link><pubDate>Sat, 24 Oct 2020 09:26:49 +0000</pubDate><guid>https://blog.swineson.me/en/reverse-route-modes-on-juniper-srx/</guid><description>A SRX is a &amp;ldquo;security device&amp;rdquo;, or as we call it conventionally, a firewall. Modern layer-3 firewalls route packets just like a router, but unlike a router, a firewall can organize packets into connections (flows) and run ACLs on the entire flow. This unique functionality is the fundamental building block of every &amp;ldquo;advanced&amp;rdquo; security feature offered by a firewall: dynamic NAT (PAT/NPT), zone-based firewall (ZBFW), ACLs for in or out connections only, L7 filtering, etc.</description></item><item><title>What the Flow: Reverse Route Modes on Juniper SRX</title><link>https://blog.swineson.me/en/what-the-flow-reverse-route-modes-on-juniper-srx/</link><pubDate>Sat, 24 Oct 2020 09:26:49 +0000</pubDate><guid>https://blog.swineson.me/en/what-the-flow-reverse-route-modes-on-juniper-srx/</guid><description>A SRX is a &amp;ldquo;security device&amp;rdquo;, or as we call it conventionally, a firewall. Modern layer-3 firewalls route packets just like a router, but unlike a router, a firewall can organize packets into connections (flows) and run ACLs on the entire flow. This unique functionality is the fundamental building block of every &amp;ldquo;advanced&amp;rdquo; security feature offered by a firewall: dynamic NAT (PAT/NPT), zone-based firewall (ZBFW), ACLs for in or out connections only, L7 filtering, etc.</description></item><item><title>Cisco Aironet 1800i: Hardware Detail</title><link>https://blog.swineson.me/en/cisco-aironet-1800i-hardware-details/</link><pubDate>Thu, 08 Oct 2020 08:04:49 +0000</pubDate><guid>https://blog.swineson.me/en/cisco-aironet-1800i-hardware-details/</guid><description>Cisco Aironet 1800i is a cute little device that is just a little smaller than my hand. They are light in weight, not very hot (not a good replacement of the old 3502i model if you also have a cat around your home) and require less power to operate. I recently got one 1800i in my room, so I&amp;rsquo;d like to write a little about this model since it is so different from the old PowerPC-based ones.</description></item><item><title>Multicast VXLAN for Routers</title><link>https://blog.swineson.me/en/multicast-vxlan-for-routers/</link><pubDate>Sat, 01 Aug 2020 09:21:48 +0000</pubDate><guid>https://blog.swineson.me/en/multicast-vxlan-for-routers/</guid><description>VXLAN has been around for a while, so how do router vendors support it? Well, let&amp;rsquo;s use a dead simple topology to test them out.
Our setup today:
All routers connected to the same dumb switch using IP range 169.254.0.0/24 Multicast signaling on address 239.0.0.1, No PIM VXLAN UDP port 4789 Network 10.0.0.0/24 on VNI 5000 (layer 3 termination / inter-VXLAN routing) Generic Linux Tested version: Debian 10, Linux kernel 4.</description></item><item><title>MOP: The Unknown "MAC Telnet" Protocol on Cisco Routers</title><link>https://blog.swineson.me/en/mop-the-unknown-mac-telnet-protocol-on-cisco-routers/</link><pubDate>Thu, 16 Jul 2020 15:30:17 +0000</pubDate><guid>https://blog.swineson.me/en/mop-the-unknown-mac-telnet-protocol-on-cisco-routers/</guid><description>When I was replacing all my buggy little MikroTik RouterOS boxes and VMs with some new shiny (and also buggy) Cisco ISR1000s and CSR1000vs a few years ago, there were several things that I missed so much that existed on the former but not on the latter. One of them was the &amp;ldquo;MAC Winbox&amp;rdquo; and &amp;ldquo;MAC Telnet&amp;rdquo; capability with which you can plug your maintenance workstation into the router with an Ethernet cable, fire up a Winbox, and it will let you configure the router through a layer 2 connection.</description></item><item><title>Configure OpenVPN Server with RouterOS 6.x compatibility</title><link>https://blog.swineson.me/en/config-openvpn-server-with-routeros-compatibility/</link><pubDate>Sun, 21 Jun 2020 12:18:46 +0000</pubDate><guid>https://blog.swineson.me/en/config-openvpn-server-with-routeros-compatibility/</guid><description>RouterOS has nothing to do with security, so this article will focus on usability rather than security. All configurations related to security will be marked as optional.
First of all, let&amp;rsquo;s review all the limitations we have on the OpenVPN client on RouterOS 6.x:
Supported protocol: TCP (TLS mode) only, no UDP, no static key Supported ciphers: none BF-CBC AES-128-CBC AES-192-CBC AES-256-CBC Supported digest algorithms: none MD5 SHA1 Supported authentication methods: username, password and optional client certificate Does not support MPLS even if running in TAP mode Server Configuration We use Debian 10 as an example here.</description></item><item><title>Use Linux as an MPLS Router</title><link>https://blog.swineson.me/en/use-linux-as-an-mpls-router/</link><pubDate>Wed, 18 Mar 2020 02:11:09 +0000</pubDate><guid>https://blog.swineson.me/en/use-linux-as-an-mpls-router/</guid><description>Two things happened in 2017:
FRRouting came into existence, which mainlined the Quagga ldpd patch Cumulus contributed its VRF implementation to mainline Linux Linux finally got native, working MPLS (L3VPN) and VRF support. 3 years later, a thorough documentation of MPLS configuration on Linux is still largely missing. Recently, after digging into all kinds of codes and documentation, I had a standard MPLS core network up and running in my lab.</description></item></channel></rss>