Re: [vbox-dev] VirtualBox blocks 127/8 (loopback) subnets for intnet

George, sorry to say but even if your guests run fine with older versions of VirtualBox that still doesn't mean that your set up is "valid". Like Max said, the 127 network is reserved, period. To be honest, I don't know what changed in the meantime. Perhaps it's a simple setting -- I don't know.

Re: [vbox-dev] VirtualBox blocks 127/8 (loopback) subnets for intnet

>The MAC address of the interfaces have not changed. Some applications do use multiple virtual MAC addresses (like GNS3 - Graphical Network Simulator). So maybe yours is affected. On Tue, Dec 1, 2015 at 5:15 PM, wrote: > Hi Alexey, > > The MAC address of the interfaces have not changed. > It

Re: [vbox-dev] VirtualBox blocks 127/8 (loopback) subnets for intnet

Hi Alexey, The MAC address of the interfaces have not changed. It looks like there is some filtering in VirtualBox in the receive path to filter 127.x.x.x IP address before it reaches the Ethernet device emulation in VM. Best Regards George -Original Message- From: Alexey Eromenko [

Re: [vbox-dev] VirtualBox blocks 127/8 (loopback) subnets for intnet

Hi Maxime, Thanks a lot for the response. This is quite an old software which has been using this series of IP address (like 127.2.x.x and 127.3.x.x) for VM to VM communication. Unfortunately the software has a lot of dependency on this and same software code is shared between many products. So

Re: [vbox-dev] VirtualBox blocks 127/8 (loopback) subnets for intnet

Hi, >The original spec actually says 172.16.0.0/12 or 192.168.0.0/16. See >RFC1918, Private IP addresses. >But yes, most users use 172.16.0.0/16 and 192.168.0.0/24. you are completely right, it is just that if you use /12 and /16 you can't have different networks :) but yes, you are right! go

Re: [vbox-dev] VirtualBox blocks 127/8 (loopback) subnets for intnet

One major difference between old VirtualBox and new one is at the MAC level filtering at layer 2. To achieve network similar to VirtualBox 2.x, you need: VM->Settings->Network->Adapter [X]->Advanced->Promisc. Mode = "Allow All". If your application used to work with VBox 2.x, it will work with v5

Re: [vbox-dev] VirtualBox blocks 127/8 (loopback) subnets for intnet

On Tue, Dec 1, 2015 at 3:14 PM, Gianfranco Costamagna wrote: > Hi, > > >>Use 10.0.0.0/8 if you need such a big subnet, else go with >> 172.16.0.0/12 or 192.168.0.0/16 > > > mmm I guess it is 172.16.0.0/16 and 192.168.0.0/24 ;) > The original spec actually says 172.16.0.0/12 or 192.168.0.0/16. S

Re: [vbox-dev] VirtualBox blocks 127/8 (loopback) subnets for intnet

Hi, >Use 10.0.0.0/8 if you need such a big subnet, else go with > 172.16.0.0/12 or 192.168.0.0/16 mmm I guess it is 172.16.0.0/16 and 192.168.0.0/24 ;) cheers, G. On 01/12/15 13:43, george.va...@wipro.com wrote: Hi, We are having our test topology running multiple VMs on a server. The g

Re: [vbox-dev] VirtualBox blocks 127/8 (loopback) subnets for intnet

Hi George, If you mean IPs like 127.x.x.x, they are dedicated to localhost communications by the TCP/IP standard and described as such in RFC 990 : The class A network number 127 is assigned the "loopback" function, that is, a datagram sent by a hi

[vbox-dev] VirtualBox blocks 127/8 (loopback) subnets for intnet

Hi, We are having our test topology running multiple VMs on a server. The guest VMs are linux based and the host is based on RHEL 6.4. The eth interface of VMs are interconnected via 'intnet' NIC settings. The VMs are using 127/8 IP addresses to communicate with each other. We are currently usin