Re: bhyve tapN additions
On 10/22/14, 10:09 PM, John wrote: Hi all, I couldn't see the following answered clearly in the literature, so I'll ask it here. When a freeBSD host is running a [anything] guest, a tap interface needs to be created. Let's say I've done all this: # ifconfig tap0 create # sysctl net.link.tap.up_on_open=1 net.link.tap.up_on_open: 0 -> 1 # ifconfig bridge0 create # ifconfig bridge0 addm igb0 addm tap0 # ifconfig bridge0 up I want to add another tap, I don't want to restart the host. If I do # ifconfig bridge0 addm tap1 then configure another vm to use tap1, can I expect it to work? Or, If I want 2 vns with 2 taps, do I need to do this: # ifconfig bridge0 create # ifconfig bridge0 addm igb0 addm tap0 addm tap1 # ifconfig bridge0 up The reason I ask, is because I'm expecting a freebsd vm to work on tap1, and it's not. thanks, I do this on 10-stable.. it works for me.. ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: bhyve tapN additions
On 10/22/14 2:54 PM, Peter Grehan wrote: Hi Allan, The tap device can also be created automatically by bhyve, make sure you specify a different tap device for each instance of bhyve. That may require some devd scripting to get it to be added to a bridge group. We're looking at having the bridge interface have a cloneable tap-style interface so this step can be avoided i.e. point bhyve at a /dev/bridgeN device, and it will automatically become a part of that bridge. Peter, that would be super helpful. Thank you! -Alfred ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: bhyve tapN additions
Hi Allan, The tap device can also be created automatically by bhyve, make sure you specify a different tap device for each instance of bhyve. That may require some devd scripting to get it to be added to a bridge group. We're looking at having the bridge interface have a cloneable tap-style interface so this step can be avoided i.e. point bhyve at a /dev/bridgeN device, and it will automatically become a part of that bridge. later, Peter. ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: bhyve tapN additions
On 2014-10-22 10:16, John wrote: > On Wed, Oct 22, 2014 at 10:12:32AM -0400, Manas wrote: >> I think you have to do >> >> ifconfig tap1 create >> >> Before the addm > > argh! I need a drink... > > Thanks for that, very quick. Sorry for the noise! > The tap device can also be created automatically by bhyve, make sure you specify a different tap device for each instance of bhyve. -- Allan Jude signature.asc Description: OpenPGP digital signature
Re: bhyve tapN additions
On Wed, Oct 22, 2014 at 10:12:32AM -0400, Manas wrote: > I think you have to do > > ifconfig tap1 create > > Before the addm argh! I need a drink... Thanks for that, very quick. Sorry for the noise! -- John ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: bhyve tapN additions
I think you have to do ifconfig tap1 create Before the addm Manas On BlackBerry Original Message From: John Sent: Wednesday, October 22, 2014 10:09 AM To: freebsd-virtualization@freebsd.org Reply To: freebsd-li...@freebsd.org Subject: bhyve tapN additions Hi all, I couldn't see the following answered clearly in the literature, so I'll ask it here. When a freeBSD host is running a [anything] guest, a tap interface needs to be created. Let's say I've done all this: # ifconfig tap0 create # sysctl net.link.tap.up_on_open=1 net.link.tap.up_on_open: 0 -> 1 # ifconfig bridge0 create # ifconfig bridge0 addm igb0 addm tap0 # ifconfig bridge0 up I want to add another tap, I don't want to restart the host. If I do # ifconfig bridge0 addm tap1 then configure another vm to use tap1, can I expect it to work? Or, If I want 2 vns with 2 taps, do I need to do this: # ifconfig bridge0 create # ifconfig bridge0 addm igb0 addm tap0 addm tap1 # ifconfig bridge0 up The reason I ask, is because I'm expecting a freebsd vm to work on tap1, and it's not. thanks, -- John ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org" ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
bhyve tapN additions
Hi all, I couldn't see the following answered clearly in the literature, so I'll ask it here. When a freeBSD host is running a [anything] guest, a tap interface needs to be created. Let's say I've done all this: # ifconfig tap0 create # sysctl net.link.tap.up_on_open=1 net.link.tap.up_on_open: 0 -> 1 # ifconfig bridge0 create # ifconfig bridge0 addm igb0 addm tap0 # ifconfig bridge0 up I want to add another tap, I don't want to restart the host. If I do # ifconfig bridge0 addm tap1 then configure another vm to use tap1, can I expect it to work? Or, If I want 2 vns with 2 taps, do I need to do this: # ifconfig bridge0 create # ifconfig bridge0 addm igb0 addm tap0 addm tap1 # ifconfig bridge0 up The reason I ask, is because I'm expecting a freebsd vm to work on tap1, and it's not. thanks, -- John ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
