Hot answers tagged linux-networking
You forgot the scope identifier, which is required to identify which link the link-local address you specified refers to. If the address you want is reachable through the eth1 interface, then you specify it: ping6 fe80::a00:27ff:fe77:9e77%eth1
If your switch supports it, I would use 802.1ad link aggregation for providing failover. With this feature, you bond the two interfaces together, and you can set one as active and one as passive interface. Your IP address would reside on the bonding interface, so there would be no IP address changes if one NIC fails.
Linux is designed to respond to ARP requests on any interface. It is assumed that the host owns the IP address and not the particular interface. What you are seeing is called ARP Flux. You can change this behavior using sysctrl arp_ignore - INTEGER Define different modes for sending replies in response to received ARP requests that resolve local ...
OK, this question is asked over and over again over the Internet and most of the time there is a (semi-) incorrect answer that you cannot do what was described in the original post. Let me clarify it once and for all :) The short answer is L2TP (and PPTP for that matter) do not have facilities to do route pushes inside the protocol, but it can be achieved ...
If you run ss or netstat the values Recv-Q and Send-Q produce this output. I.E $ ss -nt State Recv-Q Send-Q Local Address:Port Peer Address:Port ESTAB 203 0 192.168.1.2:36122 198.xxx.xxx.xxx:80 CLOSE-WAIT 1 0 192.168.1.2:43870 140.xxx.xxx.xxx:80 I have added a simple ...
If you want traffic from a network behind router 10.177.0.1 to go out through a different route (to server specifically), set the route up in 10.177.0.1 pointing to server. This would direct all outgoing traffic that passes through 10.177.0.1 through server, and I am not sure that is what you want.
Is it possible to have the INCOMING and OUTGOING be the same Ethernet card(just eth0)? Yes: the simplest way to acheive this (there are other approaches but they get very messy) is to configure the card with aliases and different subnets. Why is there no "Routing Decision" after the OUTPUT chain Because it's not necessary and that would ...
Only top voted, non community-wiki answers of a minimum length are eligible