Hot answers tagged networking
Your mixing things up a bit. Layer 2 switches and Layer 3 switches both function as network switches with the difference being that a Layer 3 switch has the capability of being able to perform routing functions. BUT, being managed doesn't imply Layer 3 capability. There are many, many Layer 2 managed switches that do nothing more than switch. That being ...
Yes, As Michal Sokolowski said :) The method would be to: create the guest-only-bridge (and have it "up" :) disable the IPv6 on that bridge interface (Something that's "default to create/setup a link local IP O_o ) attach the KVM guests' interfaces to that guest-only-bridge on the guests, have either one of them act as DHCP server and the rest as dhcp ...
Seems that you have "client-to-client" option turned on in you server openvpn config. You should just remove it cause openvpn doesn't route client-to-client traffic by default. Here is text from man-page of openvpn: client-to-client Because the OpenVPN server mode handles multiple clients through a single tun or tap interface, it is effectively a ...
One cheeky and simple way to do this is to use two switches rather than one. You could then uplink half of your devices to one switch and half on the other, and thereby double your total throughput. If you then require more outgoing throughput from a single server, you could bond the two interfaces with uplinks to both switches in your room. Just make sure ...
Did you restart the openvpn service on the server? You can see how to do this here. Check the section under "Controlling a running OpenVPN process". This is different depending on how it is running, but it describes two methods for windows. My irrelevant first suggestion is still below. sudo systemctl restart openvpn OR sudo service openvpn restart
sudo systemctl restart openvpn Using this command. Rolls Royce Chauffeur Hire in London
Try not to listen to eth0, it might be a better idea to listen on 0.0.0.0. listen on 0.0.0.0 port 587 tls-require pki mail.XXX.XX auth <creds> and so on.. Change the other line with eth0 accordingly. That has the advantage of being able to use 127.0.0.1 to send mails, and should also work, even if the network interface hasn't got any IPv4 or IPv6 ...
Switches aren't meant to do things like DHCP, port forwarding, NAT, PPPOE, DNS, Wifi, etc... like a home router does. they are designed to switch. Some have extra features, but that is the general idea. Unmanaged switches really only just switch with no other significant features and cannot be configured to do anything else. They have no management ...
A workaround this issue is connecting to the same VPN server on both machines involved in the terminal connection. It works for me.
Only top voted, non community-wiki answers of a minimum length are eligible