Explore >> Select a destination
|
You are here 
|
vincent.bernat.ch | ||
| | | | |
blog.oddbit.com
|
|
| | | | | Last week, Oskar Stenberg asked on Unix & Linux if it were possible to configure connectivity between two networks, both using the same address range, without involving network namespaces. That is, given this high level view of the network... ...can we set things up so that hosts on the "inner" network can communicate with hosts on the "outer" network using the range 192.168.3.0/24, and similarly for communication in the other direction? | |
| | | | |
juniperlabs.wordpress.com
|
|
| | | | | Introduction Historically, MPLS and L3VPN have been the domain of carriers. More recently, I've seen many more enterprises deploying self-managed MPLS solutions, sometimes over vanilla L2 connectivity from carriers, other times, using a carrier VPLS service as an underlay within the core. For this lab, I didn't want a trivial setup, but still wanted to... | |
| | | | |
www.jamieweb.net
|
|
| | | | | Installing and configuring the Quagga network routing software suite and establishing a BGP peering session to exchange routing information. | |
| | | | |
debianaddict.com
|
|
| | | [AI summary] This article explains how to configure a Debian-based Linux system as a router using iptables, bind9, and dhcpd for network management and services. | ||
