may have to stick with beta 1 for now........

[davidee]

So before I start with my issue, the software is great and I will be buying it here this evening, great job guys!


I have a Macbook pro, and I downloaded Beta 2 this morning. I was playing with it and my net config is as follows (on the host)

en0: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
inet 192.168.1.183 netmask 0xffffff00 broadcast 192.168.1.255
ether 00:16:cb:87:32:21
media: 10baseT/UTP <half-duplex> status: inactive
supported media: autoselect 10baseT/UTP <half-duplex> 10baseT/UTP <full-duplex> 10baseT/UTP <full-duplex,hw-loopback> 10baseT/UTP <full-duplex,flow-control> 100baseTX <half-duplex> 100baseTX <full-duplex> 100baseTX <full-duplex,hw-loopback> 100baseTX <full-duplex,flow-control> 1000baseT <full-duplex> 1000baseT <full-duplex,hw-loopback> 1000baseT <full-duplex,flow-control> none
en1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet6 fe80::214:51ff:feee:10fc%en1 prefixlen 64 scopeid 0x5
inet 192.168.0.76 netmask 0xffffff00 broadcast 192.168.0.255
ether 00:14:51:ee:10:fc
media: autoselect status: active
supported media: autoselect

now I assigned the guest (now reffered to as VM's) ip's on the segment 192.168.1.x

so basically they would be able to talk back and forth from between each other and the host after I ifconfig'd en0 on the host UP

this was working in beta 1....

in beta 2 this will work but only if they are using the en1 interface. I will not be needing those boxes to talk out to the net, but when I do, I'lll change the bridge interface and ip on the VM (or I assume this is how it should work).

I never really had a problem on beta 1 of the VM's talking out to the internet, and now that beta 2 came out it seems I can only reliably create a private lan on en1 (which is not what I would want normally) also the checkbox if toggled while another VM is set to use en0 will crash all active VM's

any ideas? Did something change in the core networking setup, I basically need a private lan to and from the VM's and hosts.....then the ocassional I need to dl patches or whatever so let me place it on the internet segment (other than that i can always use the macbook to pull patches and sftp/scp them to the VM's (they are redhat enterprise 4 btw, and yes I made sure to turn off the firewall)

thanks much for any help

-ee

 

[davidee]

so this is sort of a bump.......

I have been reading all the other posts and find that others are having the same issue that I am having just worded differently. in the meantime there is always the possibiltiy of just having the vm's share en1 and give them ip's on my lan, but I will have to do more testing if this will work when the host is not connected to a network (plane/demo, etc). host to vm's and vm's to hosts a must external internet access from vm's a really nice to have but for all those other people doing local demo's like me, being able to design a proper test lan(s) is crucial.

still an awesome product
*/me gets wallet for purchase*

-ee