Date: Wed, 25 Apr 2018 21:37:27 +0000 From: Paul Esson <paul.esson@redstor.com> To: "Rodney W. Grimes" <freebsd-rwg@pdx.rh.cn85.dnsmgr.net> Cc: "freebsd-virtualization@freebsd.org" <freebsd-virtualization@freebsd.org> Subject: Re: bhyve networking Message-ID: <HE1PR0102MB2588F8CFD2E2C40CC6306A2B9E8F0@HE1PR0102MB2588.eurprd01.prod.exchangelabs.com> In-Reply-To: <201804252131.w3PLVTs3098068@pdx.rh.CN85.dnsmgr.net> References: <HE1PR0102MB2588F1B078AB3A5D89DD6D1A9E8F0@HE1PR0102MB2588.eurprd01.prod.exchangelabs.com>, <201804252131.w3PLVTs3098068@pdx.rh.CN85.dnsmgr.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Rod,
Apologies, predictive testing - for trimmed read trunked. I'll get some co=
mmand output when I get back online to system tomorrow.
Regards,
Paul Esson | Redstor Limited
t +44 (0)118 951 5235
m +44 (0)776 690 6514
e paul.esson@redstor.com
________________________________
From: Rodney W. Grimes <freebsd-rwg@pdx.rh.CN85.dnsmgr.net>
Sent: Wednesday, April 25, 2018 10:31:29 PM
To: Paul Esson
Cc: freebsd-virtualization@freebsd.org
Subject: Re: bhyve networking
> Hi Rod,
> Can you share a command line for that?
Its not just a single command, but you want these in /etc/rc.conf of the GU=
EST:
network_interfaces=3D"lo0"
cloned_interfaces=3D"vlan48"
ifconfig_lo0=3D" inet 127.0.0.1 netmask 0xff000000"
ifconfig_vtnet0=3D" up"
ifconfig_vlan48=3D" inet 192.168.48.38 netmask 0xffffff00 vlan 4=
8 vlandev vtnet0"
That may be your issue... is your vtnet0 "up" in the guest.
It would help a whole lot to share more of the info about
your system, from commands, not from "vm-bhyve" settings.
Like
ifconfig -a
on the host and the guest would be a starting point.
> I also tried presenting an access port from my switch on a specific VLAN =
- not trimmed.
Trimmed? You mean you set the switch port to untagged mode,
and had the switch tag/untag the packets to a specific vlan.
Be sure you also set the default incoming tag at the switch if you did this=
,
some switches do not follow the vlan setting.
> Would I still have to tag the interface on the guest in that scenario?
No. If I understand what I think you meant by trimmed.
> Regards,
>
>
> Paul Esson | Redstor Limited
> t +44 (0)118 951 5235
> m +44 (0)776 690 6514
> e paul.esson@redstor.com
>
> ________________________________
> From: Rodney W. Grimes <freebsd-rwg@pdx.rh.CN85.dnsmgr.net>
> Sent: Wednesday, April 25, 2018 9:33:57 PM
> To: Paul Esson
> Cc: Harry Schmalzbauer; freebsd-virtualization@freebsd.org
> Subject: Re: bhyve networking
>
> [ Charset windows-1252 unsupported, converting... ]
> > Hi Harry,
> > I?m simply using the ?vm? utility as in
> >
> > vm switch create public
> > vm switch add public igb1
> >
> > That must make underlying calls to if config or equivalent as the bridg=
e and tap interfaces are created automatically.
> >
> > The vm template file has these relevant parameters
> >
> > network0_type=3D?virtio-net?
> > network0_switch=3D?public?
> >
> > I?ve done nothing to the igb1 interface other than connect it to a phys=
ical switch on the appropriate VLAN.
>
> How have you configured your vtnet devices inside the guest? If your pas=
s a "trunked" ethernet device
> to a guest the guest is going to need to run vlan decapuslation. I do th=
is here, and it works fine.
>
> vtnet0: flags=3D8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metr=
ic 0 mtu 1500
> options=3D80028<VLAN_MTU,JUMBO_MTU,LINKSTATE>
> ether 58:9c:fc:0e:8b:ec
> nd6 options=3D29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
> media: Ethernet 10Gbase-T <full-duplex>
> status: active
> lo0: flags=3D8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
> options=3D600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
> inet 127.0.0.1 netmask 0xff000000
> inet6 ::1 prefixlen 128
> inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
> nd6 options=3D21<PERFORMNUD,AUTO_LINKLOCAL>
> groups: lo
> vlan48: flags=3D8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu=
1500
> ether 58:9c:fc:0e:8b:ec
> inet 192.168.48.38 netmask 0xffffff00 broadcast 192.168.48.255
> nd6 options=3D29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
> media: Ethernet 10Gbase-T <full-duplex>
> status: active
> vlan: 48 vlanpcp: 0 parent interface: vtnet0
> groups: vlan
>
> ...
> >
> > Bez?glich Paul Esson's Nachricht vom 25.04.2018 20:44 (localtime):
> > > Hi Folks,
> > >
> > > I'm struggling with networking when using vm-bhyve on FreeBSD 11.1-RE=
LEASE. I have two NICs and have configured the first (igb0) on a management=
network and want to use the second (igb1) for VMs. However, I can't get a=
ny VM to communicate through the virtual switch if I have igb1 added to it.=
If I take the NIC out of the switch and configure an ipv4 address on it I=
can reach other hosts on the relevant subnet so I believe the poet set-up =
is valid. If I replace igb1 in the switch with igb0, I can then configure =
VMs on my management network and they have network connectivity. Can I onl=
y use
> >
> > Hello,
> >
> > a example of the command you used was nice.
> > I guess you're using if_bridge(4) ? the example would clarify.
> > But there's ng_bridge(4) and vale(4) also, and others are using
> > OpenVSwitch...
> >
> > > an interface that has an IP address configured at the host level bef=
ore adding it to the switch? I've used other
> >
> > No.
> > But the interface has to be in promisc mode. And some offloading
> > functions must be disabled, but in case of if_bridge(4), it's done
> > automagically (and reverted if you remove the interface again).
> >
> > Hth,
> >
> > -harry
> > _______________________________________________
> > freebsd-virtualization@freebsd.org mailing list
> > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
> > To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe@fr=
eebsd.org"
> >
> >
>
> --
> Rod Grimes rgrimes@freebs=
d.org
> _______________________________________________
> freebsd-virtualization@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
> To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe@free=
bsd.org"
>
--
Rod Grimes rgrimes@freebsd.=
org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?HE1PR0102MB2588F8CFD2E2C40CC6306A2B9E8F0>