Bug 173672 - emulators/virtualbox-ose: VirtualBox and bridge problem.
Summary: emulators/virtualbox-ose: VirtualBox and bridge problem.
Status: Closed Feedback Timeout
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: Tobias Kortkamp
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-11-16 23:50 UTC by Adrian Huryn
Modified: 2019-01-27 08:28 UTC (History)
5 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Adrian Huryn 2012-11-16 23:50:00 UTC 
Software :
virtualbox-ose-4.1.22 A general-purpose full virtualizer for x86 hardware
virtualbox-ose-kmod-4.1.22 VirtualBox kernel module for FreeBSD

Host : FreeBSD 9.1-PRE AMD64
Guest : Windows XP SP2 32Bit

When i try to use bridging with my wlan0 or em0 in VirtualBox my guest netcard can assign address. Setting static addresses dont resolv that problem. I see, that packages send increase but recived packages are all the time 0.

I try to set Promiscuous mode to : Allow ALL / Allow VMs, without luck.

How-To-Repeat: Try to use bridging in VirtualMachine
Comment 1 Adrian Huryn 2012-11-19 12:57:57 UTC 
Sorry, why that link don't work ?

Best regards, Adrian.

W dniu 2012-11-17 00:50, FreeBSD-gnats-submit@FreeBSD.org napisaÅ(a):
> Thank you very much for your problem report.
> It has the internal identification `misc/173672'.
> The individual assigned to look at your
> report is: freebsd-bugs.
>
> You can access the state of your problem report at any time
> via this link:
>
> http://www.freebsd.org/cgi/query-pr.cgi?pr=173672
>
>>Category:       misc
>>Responsible:    freebsd-bugs
>>Synopsis:       VirtualBox and bridge problem.
>>Arrival-Date:   Fri Nov 16 23:50:00 UTC 2012

-- 
Pozdrawiam, Huryn Adrian.
Comment 2 Eitan Adler freebsd_committer freebsd_triage 2012-11-19 13:47:33 UTC 
On 19 November 2012 07:57, Huryn Adrian <ahuryn@i-pi.pl> wrote:
> Sorry, why that link don't work ?

That gnats web interface is a bit behind.   The bug report made it through.

-- 
Eitan Adler
Comment 3 Adrian Huryn 2012-11-27 21:36:25 UTC 
Hello, i can't find that report? Link don't work.

Regards.

W dniu 2012-11-19 14:47, Eitan Adler napisaÅ(a):
> On 19 November 2012 07:57, Huryn Adrian <ahuryn@i-pi.pl> wrote:
>> Sorry, why that link don't work ?
>
> That gnats web interface is a bit behind.   The bug report made it 
> through.

-- 
Pozdrawiam, Huryn Adrian.
Comment 4 Ed Maste freebsd_committer freebsd_triage 2012-12-11 22:14:55 UTC 
Responsible Changed
From-To: freebsd-bugs->vbox

Assign to VirtualBox alias
Comment 5 Andriy Gapon freebsd_committer freebsd_triage 2012-12-13 22:39:01 UTC 
Could you please provide output of 'ngctl list' command?
I think that your problem might be related to this issue:
http://thread.gmane.org/gmane.os.freebsd.devel.net/37802/focus=37807
-- 
Andriy Gapon
Comment 6 Adrian Huryn 2012-12-14 09:01:39 UTC 
W dniu 2012-12-13 23:39, Andriy Gapon napisaÅ(a):
> Could you please provide output of 'ngctl list' command?
> I think that your problem might be related to this issue:
> http://thread.gmane.org/gmane.os.freebsd.devel.net/37802/focus=37807
[cr4sh@x300 ~]$ sudo ngctl list
There are 11 total nodes:
   Name: em0             Type: ether           ID: 00000001   Num hooks: 
0
   Name: btsock_hci_raw  Type: btsock_hci_raw  ID: 00000004   Num hooks: 
1
   Name: btsock_l2c_raw  Type: btsock_l2c_raw  ID: 00000005   Num hooks: 
1
   Name: btsock_l2c      Type: btsock_l2c      ID: 00000006   Num hooks: 
1
   Name: btsock_sco      Type: btsock_sco      ID: 00000007   Num hooks: 
0
   Name: ubt0            Type: ubt             ID: 0000006f   Num hooks: 
1
   Name: wlan0           Type: ether           ID: 00000070   Num hooks: 
0
   Name: ubt0hci         Type: hci             ID: 00000072   Num hooks: 
3
   Name: ubt0l2cap       Type: l2cap           ID: 00000076   Num hooks: 
3
   Name: ngctl35728      Type: socket          ID: 0000007c   Num hooks: 
0
   Name: vboxnet0        Type: ether           ID: 0000003f   Num hooks: 
0

Regards.
Comment 7 Andriy Gapon freebsd_committer freebsd_triage 2012-12-14 16:57:30 UTC 
on 14/12/2012 11:01 ahuryn@i-pi.pl said the following:
> W dniu 2012-12-13 23:39, Andriy Gapon napisaÅ(a):
>> Could you please provide output of 'ngctl list' command?
>> I think that your problem might be related to this issue:
>> http://thread.gmane.org/gmane.os.freebsd.devel.net/37802/focus=37807
> [cr4sh@x300 ~]$ sudo ngctl list
> There are 11 total nodes:
>   Name: em0             Type: ether           ID: 00000001   Num hooks: 0
>   Name: btsock_hci_raw  Type: btsock_hci_raw  ID: 00000004   Num hooks: 1
>   Name: btsock_l2c_raw  Type: btsock_l2c_raw  ID: 00000005   Num hooks: 1
>   Name: btsock_l2c      Type: btsock_l2c      ID: 00000006   Num hooks: 1
>   Name: btsock_sco      Type: btsock_sco      ID: 00000007   Num hooks: 0
>   Name: ubt0            Type: ubt             ID: 0000006f   Num hooks: 1
>   Name: wlan0           Type: ether           ID: 00000070   Num hooks: 0
>   Name: ubt0hci         Type: hci             ID: 00000072   Num hooks: 3
>   Name: ubt0l2cap       Type: l2cap           ID: 00000076   Num hooks: 3
>   Name: ngctl35728      Type: socket          ID: 0000007c   Num hooks: 0
>   Name: vboxnet0        Type: ether           ID: 0000003f   Num hooks: 0

Were you running a VM when capturing the above output?
I expected to see "Type: vboxnetflt" in the output.

Which instructions do you follow for configuring bridge mode?
Have you enabled vboxnet* drivers?

-- 
Andriy Gapon
Comment 8 Adrian Huryn 2012-12-15 20:28:18 UTC 
Hello.
YOu have right ;) i forget to run VBox.
[cr4sh@x300 ~]$ sudo ngctl list
There are 12 total nodes:
   Name: em0             Type: ether           ID: 00000001   Num hooks: 
0
   Name: wlan0           Type: ether           ID: 00000002   Num hooks: 
2
   Name: ubt0            Type: ubt             ID: 00000003   Num hooks: 
1
   Name: btsock_hci_raw  Type: btsock_hci_raw  ID: 00000004   Num hooks: 
1
   Name: btsock_l2c_raw  Type: btsock_l2c_raw  ID: 00000005   Num hooks: 
1
   Name: btsock_l2c      Type: btsock_l2c      ID: 00000006   Num hooks: 
1
   Name: btsock_sco      Type: btsock_sco      ID: 00000007   Num hooks: 
0
   Name: ubt0hci         Type: hci             ID: 00000009   Num hooks: 
3
   Name: ubt0l2cap       Type: l2cap           ID: 0000000d   Num hooks: 
3
   Name: vboxnet0        Type: ether           ID: 00000013   Num hooks: 
0
   Name: vboxnetflt_wlan0 Type: vboxnetflt      ID: 00000014   Num 
hooks: 2
   Name: ngctl39612      Type: socket          ID: 00000015   Num hooks: 
0

[cr4sh@x300 ~]$ cat /etc/rc.conf | grep vb
vboxnet_enable="YES"

I configure in Virtualbox bridge with promiscuous mode : allow ALL.

And that settings previously worked.


W dniu 2012-12-14 17:57, Andriy Gapon napisaÅ(a):
> on 14/12/2012 11:01 ahuryn@i-pi.pl said the following:
>> W dniu 2012-12-13 23:39, Andriy Gapon napisaÅ(a):
>>> Could you please provide output of 'ngctl list' command?
>>> I think that your problem might be related to this issue:
>>> 
>>> http://thread.gmane.org/gmane.os.freebsd.devel.net/37802/focus=37807
>> [cr4sh@x300 ~]$ sudo ngctl list
>> There are 11 total nodes:
>>   Name: em0             Type: ether           ID: 00000001   Num 
>> hooks: 0
>>   Name: btsock_hci_raw  Type: btsock_hci_raw  ID: 00000004   Num 
>> hooks: 1
>>   Name: btsock_l2c_raw  Type: btsock_l2c_raw  ID: 00000005   Num 
>> hooks: 1
>>   Name: btsock_l2c      Type: btsock_l2c      ID: 00000006   Num 
>> hooks: 1
>>   Name: btsock_sco      Type: btsock_sco      ID: 00000007   Num 
>> hooks: 0
>>   Name: ubt0            Type: ubt             ID: 0000006f   Num 
>> hooks: 1
>>   Name: wlan0           Type: ether           ID: 00000070   Num 
>> hooks: 0
>>   Name: ubt0hci         Type: hci             ID: 00000072   Num 
>> hooks: 3
>>   Name: ubt0l2cap       Type: l2cap           ID: 00000076   Num 
>> hooks: 3
>>   Name: ngctl35728      Type: socket          ID: 0000007c   Num 
>> hooks: 0
>>   Name: vboxnet0        Type: ether           ID: 0000003f   Num 
>> hooks: 0
>
> Were you running a VM when capturing the above output?
> I expected to see "Type: vboxnetflt" in the output.
>
> Which instructions do you follow for configuring bridge mode?
> Have you enabled vboxnet* drivers?

-- 
Pozdrawiam, Huryn Adrian.
Comment 9 Andriy Gapon freebsd_committer freebsd_triage 2012-12-16 08:21:57 UTC 
on 15/12/2012 22:28 Huryn Adrian said the following:
> Hello.
> YOu have right ;) i forget to run VBox.
> [cr4sh@x300 ~]$ sudo ngctl list
> There are 12 total nodes:
>   Name: em0             Type: ether           ID: 00000001   Num hooks: 0
>   Name: wlan0           Type: ether           ID: 00000002   Num hooks: 2
[snip]
>   Name: vboxnetflt_wlan0 Type: vboxnetflt      ID: 00000014   Num hooks: 2
>   Name: ngctl39612      Type: socket          ID: 00000015   Num hooks: 0
> 
> [cr4sh@x300 ~]$ cat /etc/rc.conf | grep vb
> vboxnet_enable="YES"

Hmm, looks like netgraph level connections are correctly established between
wlan0 and vboxnetflt_wlan0.  So I am out of ideas, sorry.

-- 
Andriy Gapon
Comment 10 Carlo Strub freebsd_committer freebsd_triage 2014-09-11 19:52:44 UTC 
Is this PR still relevant? Back to pool.
Comment 11 Ivan Klymenko 2014-11-02 17:33:25 UTC 
(In reply to Carlo Strub from comment #10)
> Is this PR still relevant? Back to pool.

Yes, I still have a problem in the virtual machine does not "see" the master host, if the network card is configured as a bridge and a master host system has any other bridge.

uname -a
FreeBSD nonamehost.local 10.1-PRERELEASE FreeBSD 10.1-PRERELEASE #0 r273931: Sat Nov  1 17:08:45 EET 2014     ivan@nonamehost.local:/media/da0s1/obj/usr/src/sys/mk10  amd64

virtualbox-ose-4.3.18          General-purpose full virtualizer for x86 hardware
virtualbox-ose-kmod-4.3.18     VirtualBox kernel module for FreeBSD

# ifconfig 
ath0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 2290
        ether xx:xx:xx:xx:xx:xx
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        media: IEEE 802.11 Wireless Ethernet autoselect (autoselect <hostap>)
        status: no carrier
re0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=82099<RXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE>
        ether xx:xx:xx:xx:xx:xx
        inet 192.168.0.238 netmask 0xffffff00 broadcast 192.168.0.255 
        nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
        media: Ethernet autoselect <flowcontrol> (100baseTX <full-duplex,flowcontrol,rxpause,txpause>)
        status: active
pflog0: flags=141<UP,RUNNING,PROMISC> metric 0 mtu 33160
pfsync0: flags=0<> metric 0 mtu 1500
        syncpeer: 0.0.0.0 maxupd: 128 defer: off
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
        options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
        inet6 ::1 prefixlen 128 
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5 
        inet 127.0.0.1 netmask 0xff000000 
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        ether 02:ac:22:d8:fe:00
        inet 192.168.1.1 netmask 0xffffff00 broadcast 192.168.1.255 
        nd6 options=9<PERFORMNUD,IFDISABLED>
        id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
        maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
        root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
        member: re0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
                ifmaxaddr 0 port 2 priority 128 path cost 200000
        member: wlan0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
                ifmaxaddr 0 port 7 priority 128 path cost 66666
wlan0: flags=8902<BROADCAST,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
        ether xx:xx:xx:xx:xx:xx
        nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
        media: IEEE 802.11 Wireless Ethernet autoselect mode 11g <hostap>
        status: no carrier
        ssid xxxxxwlan channel 11 (2462 MHz 11g)
        regdomain 96 indoor ecm authmode AUTO privacy OFF deftxkey 2
        txpower 20 scanvalid 60 protmode CTS wme burst dtimperiod 1 -dfs
Comment 12 Mark Linimon freebsd_committer freebsd_triage 2014-11-23 08:12:43 UTC 
Back to maintainer.
Comment 13 214748mv 2014-12-09 20:22:26 UTC 
This bug affects me too.
# uname -a
FreeBSD zippi 10.1-BETA3 FreeBSD 10.1-BETA3 #0 r272167: Fri Sep 26 11:11:24 UTC 2014     root@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC  amd64

# pkg info virtualbox-ose | head
virtualbox-ose-4.3.12_2
Name           : virtualbox-ose
Version        : 4.3.12_2
Installed on   : Fri Oct  3 14:41:11 CEST 2014
Origin         : emulators/virtualbox-ose
Architecture   : freebsd:10:x86:64
Prefix         : /usr/local
Categories     : emulators
Licenses       : GPLv2
Maintainer     : vbox@FreeBSD.org
Comment 14 Walter Schwarzenfeld 2018-01-12 03:39:02 UTC 
Three years gone without reply. Is this still a problem on recent FreeBSD-versions? Or can this PR closed?
Comment 15 Tobias Kortkamp freebsd_committer freebsd_triage 2019-01-27 08:28:40 UTC 
Closing one year after comment #14.