Re: When is a switch not a switch?
On Thu, 22 Oct 2020 at 13:47, D'Arcy Cain wrote: > > Here is what the interfaces look like: > > eth0: flags=8943 metric 0 > mtu 1500 > options=80088 > ether 14:02:ec:31:60:d0 > media: Ethernet autoselect (1000baseT ) > status: active > nd6 options=29 > public: flags=8843 metric 0 mtu > 1500 > ether 02:9d:b2:b8:78:00 > inet 98.158.139.65 netmask 0xffe0 broadcast 98.158.139.95 > 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: eth0 flags=143 > ifmaxaddr 0 port 1 priority 128 path cost 55 > groups: bridge > nd6 options=9 > tap0: flags=8843 metric 0 mtu 1500 > description: vmnet-BASE-0-public > options=8 > ether 00:bd:5f:56:f8:00 > groups: tap vm-port > media: Ethernet autoselect > status: active > nd6 options=29 > Opened by PID 3679 > tap0 is not a member of public so has no way to get to eth0 or public. I'd avoid creating the 'public' bridge and let vm-bhyve create it. Something like: vm switch create public vm switch add public eth0 Then for the guest: vm add -d network -s public If you have IPv4/v6 addresses on eth0, you will be able to ping those from the guest. Cheers, Jason. In the VM I set the IP to 71 on the same network. Here is what that looks > like: > > vtnet0: flags=8943 metric > 0 > mtu 1500 > options=80028 > ether 22:22:22:22:22:00 > inet 98.158.139.71 netmask 0xffe0 broadcast 98.158.139.95 > media: Ethernet 10Gbase-T > status: active > nd6 options=29 > > Everything looks correct but I can't even ping between the host and the VM. ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: When is a switch not a switch?
On 10/20/20 7:52 AM, Patrick M. Hausen wrote:
What you need to configure depends on your hardware.
I made a table for the various interfaces we use at our place:
em: -rxcsum -txcsum -lro -vlanmtu -vlanhwcsum -vlanhwfilter
-vlanhwtag up
igb:-rxcsum -rxcsum6 -txcsum -txcsum6 -tso -vlanhwtag -vlanhwtso up
I have bge(4) cards. This seems to be the correct one for me.
It still doesn't work. Here is the relevant lines from my rc.conf. I may
as well use the actual values. This is verbatim.
ifconfig_eth0="-rxcsum -rxcsum6 -txcsum -txcsum6 -tso -vlanhwtag
-vlanhwtso up"
cloned_interfaces="bridge0 bridge1"
ifconfig_bridge0_name="public"
ifconfig_public="addm eth0 up"
ifconfig_public_alias0="inet 0x629e8b${me}/27"
ifconfig_public_alias0_ipv6="inet6 2605:2600:1001::${me}/64"
defaultrouter="98.158.139.94"
ipv6_defaultrouter=2605:2600:1001::1
Note that "me" is set to the hex value of the last octet, 65 in this case.
Here is what the interfaces look like:
eth0: flags=8943 metric 0
mtu 1500
options=80088
ether 14:02:ec:31:60:d0
media: Ethernet autoselect (1000baseT )
status: active
nd6 options=29
public: flags=8843 metric 0 mtu 1500
ether 02:9d:b2:b8:78:00
inet 98.158.139.65 netmask 0xffe0 broadcast 98.158.139.95
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: eth0 flags=143
ifmaxaddr 0 port 1 priority 128 path cost 55
groups: bridge
nd6 options=9
tap0: flags=8843 metric 0 mtu 1500
description: vmnet-BASE-0-public
options=8
ether 00:bd:5f:56:f8:00
groups: tap vm-port
media: Ethernet autoselect
status: active
nd6 options=29
Opened by PID 3679
In the VM I set the IP to 71 on the same network. Here is what that looks like:
vtnet0: flags=8943 metric 0
mtu 1500
options=80028
ether 22:22:22:22:22:00
inet 98.158.139.71 netmask 0xffe0 broadcast 98.158.139.95
media: Ethernet 10Gbase-T
status: active
nd6 options=29
Everything looks correct but I can't even ping between the host and the VM.
--
D'Arcy J.M. Cain | Democracy is three wolves
http://www.druid.net/darcy/| and a sheep voting on
+1 416 788 2246 (DoD#0082)(eNTP) | what's for dinner.
IM: da...@vybenetworks.com, VoIP: sip:da...@druid.net
Disclaimer: By sending an email to ANY of my addresses you
are agreeing that:
1. I am by definition, "the intended recipient".
2. All information in the email is mine to do with as I see
fit and make such financial profit, political mileage, or
good joke as it lends itself to. In particular, I may quote
it where I please.
3. I may take the contents as representing the views of
your company if I so wish.
4. This overrides any disclaimer or statement of
confidentiality that may be included or implied in
your message.
OpenPGP_signature
Description: OpenPGP digital signature
Re: When is a switch not a switch?
D'Arcy Cain wrote this message on Tue, Oct 20, 2020 at 05:28 -0400: > On 10/20/20 4:36 AM, Patrick M. Hausen wrote: > > It's officially documented here: > > https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-bridging.html > > I did see that. Does that mean that I don't even need to create switches at > all? > > > "If the bridge host needs an IP address, set it on the bridge interface, > > not on the member interfaces." > > But I don't necessarily need an IP on the bridge itself, right? I can't say w/o more info in exactly how your system is setup... If you could provide more concrete information about what interfaces you are using, and what IPs are configured on what interfaces (or VMs), that'd be helpful. -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." signature.asc Description: PGP signature
