Your ifconfig -a picture shows your eth0 interface with a 10.x.x.x address.
As 10.x.x.x is non-routeable you must be running in a Virtual Machine environment like virtualbox or kvm or vmware?
What is the IP address of the HOST machine that that VM is running in?
Am 11.06.2014 23:39, schrieb brian mullan:
As 10.x.x.x is non-routeable you must be running in a Virtual Machine environment like virtualbox or kvm or vmware?
*ahem*.
10.x.x.x is routable. Like 192.168.x.x and 172.16.x.x etc.
Those ranges are reserved for private use, i.e. behind a NAT, so they're not unique and don't show up on the public internet - but they're perfectly routeable within your own, local IP-based network setup.
In fact, most of the machines I sell have a local network in the 192.168.x.z routing to another local network in the 172.16.a.b range and to another one in the 192.168.y.z range (where y != x).
Works perfectly well.
-Stefan
Stefan
By not-routable... I did mean not route-able over the Internet... of course you could do it for a private local lan environment.
It might be a sw problem but it could be a topology/implementation issue... Were the machines VMs, were they LXC containers, was x2goserver in a IaaS cloud somewhere, was it just a PC/laptop on a private network. Were these different machines in different networks and do they get rebooted and assigned new IP addresses?
sorry for the confusion... just wanted to ask the questions.
brian
On Wed, Jun 11, 2014 at 5:44 PM, Stefan Baur <newsgroups.mail2@stefanbaur.de
wrote:
Am 11.06.2014 23:39, schrieb brian mullan:
As 10.x.x.x is non-routeable you must be running in a Virtual Machine environment like virtualbox or kvm or vmware?
*ahem*.
10.x.x.x is routable. Like 192.168.x.x and 172.16.x.x etc.
Those ranges are reserved for private use, i.e. behind a NAT, so they're not unique and don't show up on the public internet - but they're perfectly routeable within your own, local IP-based network setup.
In fact, most of the machines I sell have a local network in the 192.168.x.z routing to another local network in the 172.16.a.b range and to another one in the 192.168.y.z range (where y != x).
Works perfectly well.
-Stefan
x2go-user mailing list x2go-user@lists.x2go.org http://lists.x2go.org/listinfo/x2go-user
-
brian mullan -
Stefan Baur