Tag Info

Hot answers tagged

3

It means that you are using the same IP range on both interfaces, or overlapping IP ranges. For example: Interface IP Address Subnet Mask eth0 192.168.2.10 255.255.255.240 eth1 192.168.2.2 255.255.255.252 It causes an overlapping because, according to the subnet mask: eth0 is in the range 192.168.2.0 - 192.168.2.15 ...


2

Bonding is not suited for such configuration. It is meant to be used on the same subnet. You probably could use ECMP (Equal Cost MultiPath) routing to achieve what you want. Some ECMP tutorial Your tutorial suggest creating a VPN through each of the WANs and bonding those VPNs. That is possible as well, though I'd say it's kind of ugly. To do that, you ...


2

from http://manpages.ubuntu.com/manpages/utopic/en/man8/ifenslave.8.html # modprobe bonding # ifconfig bond0 192.168.0.1 netmask 255.255.0.0 # ifenslave bond0 eth0 eth1 however, you have to be sure the same bonding protocol is also set on remote equipment. There are seven modes for bonding configuration. These affect which non failed interface will ...


1

This seems to come up in various bugtrackers from time to time: Debian #46049, Debian #711001, RH #133683. But none of these seem to be implemented. To recap: the Name Service Switch reads /etc/nsswitch.conf where to look for e.g. services information: $ strace -f -e open,stat getent services > /dev/null [...] open("/lib/x86_64-linux-gnu/libc.so.6", ...


1

The problem is that you're telling your machine that both interfaces should be handling traffic to the rest of the world. You see this in the last two lines of your routing table. If I've understood you correctly, it's the interface that gets its information from DHCP that's connected to the internet, and the other one is only connected to 192.168.56.0/24. ...


1

The ? (10.2.0.200) at <incomplete> on eth0 entry is a normal behavior when the machine cannot be reached (is the machine powered on?) If the destination machine has something in the IPTables, for example, it's blocking the ICMPv4 request, you will see a complete entry in the arp table because the traffic was discarted but it has reached to the host. ...


1

No, there is not a way to do that. That would break the very concept behind separation of network namespaces. There is one and only one way to "escape" that separation, and it's veth interfaces. In a little bit more detail, it wouldn't just be a matter of somehow "sharing" a loopback interface between network namespaces. Each network namespace is logically ...


1

My /etc/dhcp/dhclient.conf file uses the following configuration, notice the supercede line # Configuration file for /sbin/dhclient, which is included in Debian's # dhcp3-client package. # # This is a sample configuration file for dhclient. See dhclient.conf's # man page for more information about the syntax of this file # and a more comprehensive ...


1

First off, I usually create a second sshd process with its own configuration file. (sshd -f /etc/ssh/sshd-2222.conf for instance) or by overriding the configuration on the command-line (sshd -p 2222 -o PasswordAuthentication=no,AllowRoot=no). This way they share the same keys, etc, but you can override any of the parameters. Any ideas why this happen? ...


1

You could rent some cheap VPS servers that are positioned around the world and run traceroute yourself from those servers back to your website. AWS allows you rent per minute. Another option would be to search for "traceroute online" there are a large number of websites that allow you to run a traceroute from a remote server. Examples: ...


1

Try this on when launching qemu -redir tcp:2222::22 $ ssh -p 2222 localhost The tcp:2222::22 flag in the qemu launch command maps the 2222 port of the host machine to port 22 (the default ssh port) on the virtual machine. Then, simply sshing to the 2222 port on your localhost (the host machine) will redirect any traffic into the ssh 22 port in the ...



Only top voted, non community-wiki answers of a minimum length are eligible