Date: Mon, 27 Oct 2008 20:16:35 -0300 From: "Marc G. Fournier" <freebsd@hub.org> To: "Marc G. Fournier" <freebsd@hub.org>, freebsd-net@freebsd.org Subject: Re: tap+bridge -> ethernet with an alias ... Message-ID: <7962F22A78B7483E6667733E@ganymede.hub.org> In-Reply-To: <C6A3C687D9CDFDD6E90CB132@ganymede.hub.org> References: <C6A3C687D9CDFDD6E90CB132@ganymede.hub.org>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 As an appendum, I have the following kernel modules loaded: 4 1 0xffffffffaf49c000 5066 if_bridge.ko 5 1 0xffffffffaf483000 35c5 bridgestp.ko 6 1 0xffffffffaf493000 2506 if_tap.ko same as on my desktop ... - --On Monday, October 27, 2008 19:46:02 -0300 "Marc G. Fournier" <freebsd@hub.org> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > On my desktop here, I have a qemu-img of Win XP that is using bridging to > connect to the Internet ... everything works great, even have remote desktop > working so that I can login from another windows box into the VM ... and very > responsive ... > > ... but this is on a private network where the ethernet doesn't have any > aliases attached to it ... > > I've tried uploading the image (after changing the IP) to one of my servers > with a public interface on it, but now can't seem to get networking working > ... > > my ifconfig -a looks like: > > bge0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu > 1500 > options=98<VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM> > ether 00:14:c2:3f:2e:86 > inet xxx.xxx.xxx.xxx netmask 0xffffff00 broadcast xxx.xxx.xxx.255 > inet 192.168.1.1 netmask 0xffffff00 broadcast 192.168.1.255 > inet xxx.xxx.xxx.xxx netmask 0xffffffff broadcast xxx.xxx.xxx.xxx > media: Ethernet 100baseTX <full-duplex> > status: active > bge1: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500 > options=9b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM> > ether 00:14:c2:3f:2e:85 > media: Ethernet autoselect (none) > status: no carrier > lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384 > inet 127.0.0.1 netmask 0xff000000 > bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 > ether ce:44:c7:1b:47:40 > id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 > maxage 20 holdcnt 6 proto rstp maxaddr 100 timeout 1200 > root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0 > member: bge0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP> > ifmaxaddr 0 port 1 priority 128 path cost 200000 > member: tap0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP> > ifmaxaddr 0 port 5 priority 128 path cost 2000000 > tap0: flags=8942<BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu > 1500 ether 00:bd:96:ae:67:00 > > the 192.168.1.x is used for 'internal routing' ... > > when I startup qemu, I use: > > qemu winxp.img -net nic -net tap -vnc :1 > > and I can connect via VNC, but the IP assigned to the image isn't pingable, > like it is on my desktop ... > > Is there something with 'pre-aliased' interfaces that can't be used with a > bridge/tap device? Or have I just missed something? > > > - -- > Marc G. Fournier Hub.Org Hosting Solutions S.A. (http://www.hub.org) > Email . scrappy@hub.org MSN . scrappy@hub.org > Yahoo . yscrappy Skype: hub.org ICQ . 7615664 > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.9 (FreeBSD) > > iEYEARECAAYFAkkGRKoACgkQ4QvfyHIvDvM2MQCaAoa8mt9L+80o+IQiooQ0QjDA > X08An1/mJwduTU0uH7sDlRFPp06Bs2cN > =2c6c > -----END PGP SIGNATURE----- > > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" - -- Marc G. Fournier Hub.Org Hosting Solutions S.A. (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkkGS9MACgkQ4QvfyHIvDvOmOwCeJy6mKN0SOwqEhuwTa0u457/0 wwgAn1sxRa2L3MyVaAF/2WMhFm5hDh5X =DYcR -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7962F22A78B7483E6667733E>