Explore >> Select a destination
|
You are here 
|
juniperlabs.wordpress.com | ||
| | | | |
vincent.bernat.ch
|
|
| | | | | For ease of configuration, virtual guests are usually connected to a layer 2 network. However, hypervisors can be turned into layer 3 routers... | |
| | | | |
www.jamieweb.net
|
|
| | | | | Installing and configuring the Quagga network routing software suite and establishing a BGP peering session to exchange routing information. | |
| | | | |
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? | |
| | | | |
blog.preyneyv.dev
|
|
| | | It feels like every single web service wants to use OAuth to get user data, and for good reason too. The alternatives include requiring users to create access tokens manually (yikes) and asking users to input their usernames/passwords to impersonate them (giga yikes). At least with OAuth, users get to see a pretty screen with a big "Approve" button. | ||
