Live data from Hacker News

Linux Networking Shallow Dive: WireGuard, Routing, TCP/IP and NAT

im.salty.fish

61–66 of 66 posts

Re: Linux Networking Shallow Dive: WireGuard, Routing, TCP/IP and NAT

#61
post #19

Earlier quoted context omitted.

Since WireGuard is Layer 3, what would is everyone's use case of doing Layer 2 on it? Or, what can it improve over existing solutions? I have tried to do the same for a bit while still learning networking, but ran into Layer 3 limitations.

People who require layer 2 require either a protocol which is neither TCP nor UDP or they need devices in the same broadcast domain

Can one do multicast over wireguard?

Re: Linux Networking Shallow Dive: WireGuard, Routing, TCP/IP and NAT

#62

Earlier quoted context omitted.

People who require layer 2 require either a protocol which is neither TCP nor UDP or they need devices in the same broadcast domain

Can one do multicast over wireguard?

Frustratingly enough, apparently not as I could never get it to work. It is pretty easy to set up a vxlan tunnel over wireguard if you absolutely need stuff like that though.

Re: Linux Networking Shallow Dive: WireGuard, Routing, TCP/IP and NAT

#63
post #48
post #24

Earlier quoted context omitted.

I experienced this back when I configured my home Linux boxes as a router, VPN server, firewall, media server, etc. Since I had the time, compiled all of the info I found on random blogs and sites and added them to the Ubuntu Community wiki. That was the 12.x days, when Ubuntu was in its prime and the distro to use. While these blogs were a great resource, I often found the commands outdated or applied to a different…

This is one reason Mikrotik products are so nice. At least, they have a pretty decent Web UI that you can use to configure stuff.

OpenSuse has Yast, which is simpler in my experience.

Re: Linux Networking Shallow Dive: WireGuard, Routing, TCP/IP and NAT

#64

We recently switched a bunch of stuff from OpenVPN to Wireguard. A number of the links were OpenVPN layer 2 tunnels to pass, of all things, Novell Netware running on IPX (the particular situation precludes switching to TCP/IP for those customers). Now, layer 2 tunneling is being performed using RFC 3378 EtherIP, and it's much more performant, not to mention easier to manage. Old and new systems are running OpenBSD.

If you have a write up of how you managed to get layer 2 working inside wireguard, I'd love to read it.

gretap.

But why run Wireguard+gretap when you could just run tap-mode OpenVPN?

Re: Linux Networking Shallow Dive: WireGuard, Routing, TCP/IP and NAT

#66

Earlier quoted context omitted.

Can one do multicast over wireguard?

Frustratingly enough, apparently not as I could never get it to work. It is pretty easy to set up a vxlan tunnel over wireguard if you absolutely need stuff like that though.

Oh hadn't thought about that, thanks. 'need' is a big word here but sometimes you can't change the client and server apps so, having support for the basic (although niche) features in the lower layers helps migrating smoothly.
Post reply on HN