Qemu networking issue

[Per Hedeland]

"Trent Nelson" <tnelson at onresolve.com> wrote:
>
>I've tried the sysctl net.link.ether.bridge and ifconfig bridge0
>approaches mentioned in [1-4].  This initially involved having a tap0
>inet 0.0.0.0 broadcast 0.255.255.255 interface, and a bridge0 with
>em0,tap0 (and no assigned IP for the bridge), but when I tried to tell
>the Windows box to use IP 205.97.38.47 (after I've removed this aliased
>IP from em0), subnet 0xffffff00, gateway 216.203.62.29, the local
>connection properties dialog would hang with 'Acquiring address...' then
>eventually fail.  If I picked an IP address like 192.168.0.1, it would
>go through, but there wouldn't actually be any network connectivity
>between the host/guest.

Like others have in their replies, I would recommend the ifconfig method
- and as also mentioned, both bridge and tap interface must be
ifconfig'ed "up", but neither with an IP address. Your 0.0.0.0 on tap0
above may be OK, but no reason to put it there.

However, the config you're telling windows to use - "IP 205.97.38.47,
subnet 0xffffff00, gateway 216.203.62.29" - doesn't make sense: The
gateway must be in the local subnet, i.e. 205.97.38.xxx if you want to
use 205.97.38.47/0xffffff00. I'm not sure why you have addresses in two
different subnets on em0 to begin with, it's a bit "strange" - in any
case a host that "is" in only one of those subnets needs a gateway in
that subnet to reach the other (or anything else). Whether this problem
is actually the cause of the 'Acquiring address...' hang I don't know
though...

--Per Hedeland