Re: bhyve and arp problem
Bezüglich Daniel Braniss's Nachricht vom 04.04.2018 15:08 (localtime): > > >> On 2 Apr 2018, at 19:19, Harry Schmalzbauer wrote: >> >> Bezüglich Rodney W. Grimes's Nachricht vom 02.04.2018 18:11 (localtime): Bez?glich Daniel Braniss's Nachricht vom 02.04.2018 16:58 (localtime): ? >> >> Are you trying to use the HOSTS ip address in the GUEST? > > the client is using the server?s /usr/local, which is mounted via nfs. I guess you have reasons to prefer nfs over nullfs. >>> >>> You can not nullfs mount from inside a bhyve guest the host file >>> system would be his reason. >> >> Doh, of course – I mind-mixed with jails… Almost all my FreeBSD >> "guests" on a bhyve(8) host are jails... Please simply ignore ;-) >> >> >> … your results... Else I can't explain what you see other than the above scenario. >>> >>> Is it still true that if you have a bridge hooked to an interface >>> you must move the IP assignement from the interace device to the >>> bridge? >> >> I have no idea, I haven't used if_bridge(4) for some years. Perferably >> I use vale(4) (if I don't need .11q) or ng_bridge(4) for bhyve(8) setups. >> >> -harry > > maybe this could be the cause: > on the server, every time a client is started iI see: > kernel: bridge0: error setting interface capabilities on mlxen0 Members added to the bridge will automatically get some (TX) offloadings disabled, which seems to fail in your case. man 4 if_bridge: The TOE, TSO, TXCSUM and TXCSUM6 capabilities on all interfaces added to the bridge are disabled if any of the interfaces doesn't support/enable them. The LRO capability is always disabled. All the capabilities are restored when the interface is removed from bridge. Changing capabilities in run time may cause NIC reinit and the link flap. I don't think the kernel-bridge0-logs are related to your ARP issue – txcsum offloading enabled on if_bridge(4) uplinks cause other errors (dropped packets – one layer up). -harry ___ 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: bhyve and arp problem
> On 2 Apr 2018, at 19:19, Harry Schmalzbauer wrote: > > Bezüglich Rodney W. Grimes's Nachricht vom 02.04.2018 18:11 (localtime): >>> Bez?glich Daniel Braniss's Nachricht vom 02.04.2018 16:58 (localtime): >>> >>> ? > > Are you trying to use the HOSTS ip address in the GUEST? the client is using the server?s /usr/local, which is mounted via nfs. >>> >>> I guess you have reasons to prefer nfs over nullfs. >> >> You can not nullfs mount from inside a bhyve guest the host file >> system would be his reason. > > Doh, of course – I mind-mixed with jails… Almost all my FreeBSD > "guests" on a bhyve(8) host are jails... Please simply ignore ;-) > > > … >>> your results... Else I can't explain what you see other than the above >>> scenario. >> >> Is it still true that if you have a bridge hooked to an interface >> you must move the IP assignement from the interace device to the >> bridge? > > I have no idea, I haven't used if_bridge(4) for some years. Perferably > I use vale(4) (if I don't need .11q) or ng_bridge(4) for bhyve(8) setups. > > -harry maybe this could be the cause: on the server, every time a client is started iI see: kernel: bridge0: error setting interface capabilities on mlxen0 and BTW, with the latest kernel, there is only one complaint about arp moving! danny ___ 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: bhyve and arp problem
Bezüglich Rodney W. Grimes's Nachricht vom 02.04.2018 18:11 (localtime): >> Bez?glich Daniel Braniss's Nachricht vom 02.04.2018 16:58 (localtime): >> >> ? Are you trying to use the HOSTS ip address in the GUEST? >>> >>> the client is using the server?s /usr/local, which is mounted via nfs. >> >> I guess you have reasons to prefer nfs over nullfs. > > You can not nullfs mount from inside a bhyve guest the host file > system would be his reason. Doh, of course – I mind-mixed with jails… Almost all my FreeBSD "guests" on a bhyve(8) host are jails... Please simply ignore ;-) … >> your results... Else I can't explain what you see other than the above >> scenario. > > Is it still true that if you have a bridge hooked to an interface > you must move the IP assignement from the interace device to the > bridge? I have no idea, I haven't used if_bridge(4) for some years. Perferably I use vale(4) (if I don't need .11q) or ng_bridge(4) for bhyve(8) setups. -harry ___ 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: bhyve and arp problem
> Bez?glich Daniel Braniss's Nachricht vom 02.04.2018 16:58 (localtime): > > ? > >> > >> Are you trying to use the HOSTS ip address in the GUEST? > > > > the client is using the server?s /usr/local, which is mounted via nfs. > > I guess you have reasons to prefer nfs over nullfs. You can not nullfs mount from inside a bhyve guest the host file system would be his reason. > > so I guess the answer is yes. > > I don't see how /usr/local is related to IP address assigning... Yes, this is not any part of this issue, I believe the RP misunderstood my question. > ? > > the guest has only vtnet0 and lo0 > > the ip of the client is obtained via dhcp > > on the server, there is a bridge, bridge0 and it bridges between the taps > > and the mxlen0 > > Hmm, do you assing an IP address to your if_tap(4) interfaces at your > bhyve-host? I missed that as a possible, yes, that would cause odd issues. > if_tap(4) is used for interconnecting bhyve(8)'s virtio-net "backend" > with the host's host-IP stack via the character device /dev/tapX. > The if_tap(4) interfaces on the host mustn't get the guest's (clients) > IP address! The address must be assigned to the if_vtnet(4) interface > _inside_ the guest (I call it the front-end of bhyve's virtio-net) ? > done usually in /etc/rc.conf ? no relation to /usr/local? > > But chances are good I misunderstood something, either your setup or > your results... Else I can't explain what you see other than the above > scenario. Is it still true that if you have a bridge hooked to an interface you must move the IP assignement from the interace device to the bridge? Ie in this case here the IP address of the most must be put on bridge0, and NOT on mlxen0. > -harry > -- Rod Grimes rgri...@freebsd.org ___ 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: bhyve and arp problem
> > On 2 Apr 2018, at 16:51, Rodney W. Grimes > > wrote: > > > >>> On 2 Apr 2018, at 15:33, Harry Schmalzbauer wrote: > >>> > >>> Bez?glich Daniel Braniss's Nachricht vom 30.03.2018 13:16 (localtime): > hi, > this is my first attempt at bhyve, and so far all seems ok, except > in my guest, the mac address of the hosting keeps flipping, ie, every 20 > minutes > i see a message : > ? arp: nnn (the hosting ip) moved from to > on both the host and guest I?m running a very resent -stable. > the is the mac of the host nic, while the is the tap0 > > i know this looks harmless, but it?s annoying > >>> > >>> You can calm it with > >>> 'sysctl net.link.ether.inet.log_arp_movements=0' > >>> > >>> There's also "net.link.ether.inet.log_arp_wrong_iface" and > >>> "net.inet.ip.check_interface" which influence related behaviour. > >>> > >>> You also posted (documentationized IP-addresses): > I think the problem starts with the host seeing the client/guest on 2 > interfaces, the nic (mlnxen0) and the tap(tap0) > on the host: > > arp -a > ... > bhv-00.cs.huji.ac.il (192.0.2.246) at xx.xx.xx.xx.xx on tap0 expires in > 1001 seconds [ethernet] > bhv-00.cs.huji.ac.il (192.0.2.246) at xx.xx.xx.xx.xx on mlxen0 expires > in 644 seconds [ethernet] > >>> > >> > >> the above 2 lines are on the host running bhyve (server?) and the MACs > >> belong to the client, and they are identical, > >> there is no complaints. > >> (BTW, did you change the ip?s?) > >> > >>> Initially, you reference two MAC-addresses with and . > >> this is on the client, where the MAC are different (it?s of the hosting > >> computer). > >> > >>> The recent post indicates non-different MAC-addresses. > >>> > >>> If and - resp. xx.xx.xx.xx.xx - are equal (but seen on > >>> different interfaces), this wouldn't get logged I think. > >>> But it was the only harmless case for straight forward setups. > >>> Even with STP/LACP/CARP/etc. in place, "arp: IP-address moved" always > >>> indicates a misconfiguration and I don't know any example where the two > >>> different MAC-Addresses for one IP-address were harmless. > >>> While using a single (locally administrated?) MAC address more than once > >>> sitewide _can_ make sense, having two interfaces on one host which both > >>> are on the same ethernet segment like the two interfaces with the same > >>> MAC address, looks like an unintended setup. > >>> > >>> So I strongly suggest to analyze your setup before altering the > >>> mentioned sysctl!!! > >>> > >> I do want to know if there are ip/mac issues, it usually happens when more > >> than one host has the same ip, > >> which is not the case here :-( > > > > Are you trying to use the HOSTS ip address in the GUEST? > > the client is using the server?s /usr/local, which is mounted via nfs. > so I guess the answer is yes. I didnt mean to access it, I meant did you assign the same IP to the GUEST that is assigned on the HOST. I suspect the answer here is no from other context. > > And how do you have an mlxen interface in a GUEST? > no > the guest has only vtnet0 and lo0 > the ip of the client is obtained via dhcp > on the server, there is a bridge, bridge0 and it bridges between the taps and > the mxlen0 Is 192.0.2.246 on the mlxen0 interface, or on the bridge0? I believe you need to move the ip from the interface to the bridge to have this work right. > > > Is this being done with PCI passthrough? > again, no. > > cheers, > danny -- Rod Grimes rgri...@freebsd.org ___ 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: bhyve and arp problem
Bezüglich Daniel Braniss's Nachricht vom 02.04.2018 16:58 (localtime): … >> >> Are you trying to use the HOSTS ip address in the GUEST? > > the client is using the server’s /usr/local, which is mounted via nfs. I guess you have reasons to prefer nfs over nullfs. > so I guess the answer is yes. I don't see how /usr/local is related to IP address assigning... … > the guest has only vtnet0 and lo0 > the ip of the client is obtained via dhcp > on the server, there is a bridge, bridge0 and it bridges between the taps and > the mxlen0 Hmm, do you assing an IP address to your if_tap(4) interfaces at your bhyve-host? if_tap(4) is used for interconnecting bhyve(8)'s virtio-net "backend" with the host's host-IP stack via the character device /dev/tapX. The if_tap(4) interfaces on the host mustn't get the guest's (clients) IP address! The address must be assigned to the if_vtnet(4) interface _inside_ the guest (I call it the front-end of bhyve's virtio-net) – done usually in /etc/rc.conf – no relation to /usr/local… But chances are good I misunderstood something, either your setup or your results... Else I can't explain what you see other than the above scenario. -harry ___ 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: bhyve and arp problem
> On 2 Apr 2018, at 16:51, Rodney W. Grimes > wrote: > >>> On 2 Apr 2018, at 15:33, Harry Schmalzbauer wrote: >>> >>> Bez?glich Daniel Braniss's Nachricht vom 30.03.2018 13:16 (localtime): hi, this is my first attempt at bhyve, and so far all seems ok, except in my guest, the mac address of the hosting keeps flipping, ie, every 20 minutes i see a message : ? arp: nnn (the hosting ip) moved from to on both the host and guest I?m running a very resent -stable. the is the mac of the host nic, while the is the tap0 i know this looks harmless, but it?s annoying >>> >>> You can calm it with >>> 'sysctl net.link.ether.inet.log_arp_movements=0' >>> >>> There's also "net.link.ether.inet.log_arp_wrong_iface" and >>> "net.inet.ip.check_interface" which influence related behaviour. >>> >>> You also posted (documentationized IP-addresses): I think the problem starts with the host seeing the client/guest on 2 interfaces, the nic (mlnxen0) and the tap(tap0) on the host: arp -a ... bhv-00.cs.huji.ac.il (192.0.2.246) at xx.xx.xx.xx.xx on tap0 expires in 1001 seconds [ethernet] bhv-00.cs.huji.ac.il (192.0.2.246) at xx.xx.xx.xx.xx on mlxen0 expires in 644 seconds [ethernet] >>> >> >> the above 2 lines are on the host running bhyve (server?) and the MACs >> belong to the client, and they are identical, >> there is no complaints. >> (BTW, did you change the ip?s?) >> >>> Initially, you reference two MAC-addresses with and . >> this is on the client, where the MAC are different (it?s of the hosting >> computer). >> >>> The recent post indicates non-different MAC-addresses. >>> >>> If and - resp. xx.xx.xx.xx.xx - are equal (but seen on >>> different interfaces), this wouldn't get logged I think. >>> But it was the only harmless case for straight forward setups. >>> Even with STP/LACP/CARP/etc. in place, "arp: IP-address moved" always >>> indicates a misconfiguration and I don't know any example where the two >>> different MAC-Addresses for one IP-address were harmless. >>> While using a single (locally administrated?) MAC address more than once >>> sitewide _can_ make sense, having two interfaces on one host which both >>> are on the same ethernet segment like the two interfaces with the same >>> MAC address, looks like an unintended setup. >>> >>> So I strongly suggest to analyze your setup before altering the >>> mentioned sysctl!!! >>> >> I do want to know if there are ip/mac issues, it usually happens when more >> than one host has the same ip, >> which is not the case here :-( > > Are you trying to use the HOSTS ip address in the GUEST? the client is using the server’s /usr/local, which is mounted via nfs. so I guess the answer is yes. > And how do you have an mlxen interface in a GUEST? no the guest has only vtnet0 and lo0 the ip of the client is obtained via dhcp on the server, there is a bridge, bridge0 and it bridges between the taps and the mxlen0 > Is this being done with PCI passthrough? again, no. cheers, danny > > > -- > Rod Grimes rgri...@freebsd.org ___ 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: bhyve and arp problem
> > On 2 Apr 2018, at 15:33, Harry Schmalzbauer wrote: > > > > Bez?glich Daniel Braniss's Nachricht vom 30.03.2018 13:16 (localtime): > >> hi, > >> this is my first attempt at bhyve, and so far all seems ok, except > >> in my guest, the mac address of the hosting keeps flipping, ie, every 20 > >> minutes > >> i see a message : > >>? arp: nnn (the hosting ip) moved from to > >> on both the host and guest I?m running a very resent -stable. > >> the is the mac of the host nic, while the is the tap0 > >> > >> i know this looks harmless, but it?s annoying > > > > You can calm it with > > 'sysctl net.link.ether.inet.log_arp_movements=0' > > > > There's also "net.link.ether.inet.log_arp_wrong_iface" and > > "net.inet.ip.check_interface" which influence related behaviour. > > > > You also posted (documentationized IP-addresses): > >> I think the problem starts with the host seeing the client/guest on 2 > >> interfaces, the nic (mlnxen0) and the tap(tap0) > >> on the host: > >> > >> arp -a > >> ... > >> bhv-00.cs.huji.ac.il (192.0.2.246) at xx.xx.xx.xx.xx on tap0 expires in > >> 1001 seconds [ethernet] > >> bhv-00.cs.huji.ac.il (192.0.2.246) at xx.xx.xx.xx.xx on mlxen0 expires in > >> 644 seconds [ethernet] > > > > the above 2 lines are on the host running bhyve (server?) and the MACs belong > to the client, and they are identical, > there is no complaints. > (BTW, did you change the ip?s?) > > > Initially, you reference two MAC-addresses with and . > this is on the client, where the MAC are different (it?s of the hosting > computer). > > > The recent post indicates non-different MAC-addresses. > > > > If and - resp. xx.xx.xx.xx.xx - are equal (but seen on > > different interfaces), this wouldn't get logged I think. > > But it was the only harmless case for straight forward setups. > > Even with STP/LACP/CARP/etc. in place, "arp: IP-address moved" always > > indicates a misconfiguration and I don't know any example where the two > > different MAC-Addresses for one IP-address were harmless. > > While using a single (locally administrated?) MAC address more than once > > sitewide _can_ make sense, having two interfaces on one host which both > > are on the same ethernet segment like the two interfaces with the same > > MAC address, looks like an unintended setup. > > > > So I strongly suggest to analyze your setup before altering the > > mentioned sysctl!!! > > > I do want to know if there are ip/mac issues, it usually happens when more > than one host has the same ip, > which is not the case here :-( Are you trying to use the HOSTS ip address in the GUEST? And how do you have an mlxen interface in a GUEST? Is this being done with PCI passthrough? -- Rod Grimes rgri...@freebsd.org ___ 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: bhyve and arp problem
> On 2 Apr 2018, at 15:33, Harry Schmalzbauer wrote: > > Bezüglich Daniel Braniss's Nachricht vom 30.03.2018 13:16 (localtime): >> hi, >> this is my first attempt at bhyve, and so far all seems ok, except >> in my guest, the mac address of the hosting keeps flipping, ie, every 20 >> minutes >> i see a message : >> … arp: nnn (the hosting ip) moved from to >> on both the host and guest I’m running a very resent -stable. >> the is the mac of the host nic, while the is the tap0 >> >> i know this looks harmless, but it’s annoying > > You can calm it with > 'sysctl net.link.ether.inet.log_arp_movements=0' > > There's also "net.link.ether.inet.log_arp_wrong_iface" and > "net.inet.ip.check_interface" which influence related behaviour. > > You also posted (documentationized IP-addresses): >> I think the problem starts with the host seeing the client/guest on 2 >> interfaces, the nic (mlnxen0) and the tap(tap0) >> on the host: >> >> arp -a >> ... >> bhv-00.cs.huji.ac.il (192.0.2.246) at xx.xx.xx.xx.xx on tap0 expires in 1001 >> seconds [ethernet] >> bhv-00.cs.huji.ac.il (192.0.2.246) at xx.xx.xx.xx.xx on mlxen0 expires in >> 644 seconds [ethernet] > the above 2 lines are on the host running bhyve (server?) and the MACs belong to the client, and they are identical, there is no complaints. (BTW, did you change the ip’s?) > Initially, you reference two MAC-addresses with and . this is on the client, where the MAC are different (it’s of the hosting computer). > The recent post indicates non-different MAC-addresses. > > If and - resp. xx.xx.xx.xx.xx - are equal (but seen on > different interfaces), this wouldn't get logged I think. > But it was the only harmless case for straight forward setups. > Even with STP/LACP/CARP/etc. in place, "arp: IP-address moved" always > indicates a misconfiguration and I don't know any example where the two > different MAC-Addresses for one IP-address were harmless. > While using a single (locally administrated?) MAC address more than once > sitewide _can_ make sense, having two interfaces on one host which both > are on the same ethernet segment like the two interfaces with the same > MAC address, looks like an unintended setup. > > So I strongly suggest to analyze your setup before altering the > mentioned sysctl!!! > I do want to know if there are ip/mac issues, it usually happens when more than one host has the same ip, which is not the case here :-( thanks, danny > -harry ___ 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: bhyve and arp problem
Bezüglich Daniel Braniss's Nachricht vom 30.03.2018 13:16 (localtime): > hi, > this is my first attempt at bhyve, and so far all seems ok, except > in my guest, the mac address of the hosting keeps flipping, ie, every 20 > minutes > i see a message : > … arp: nnn (the hosting ip) moved from to > on both the host and guest I’m running a very resent -stable. > the is the mac of the host nic, while the is the tap0 > > i know this looks harmless, but it’s annoying You can calm it with 'sysctl net.link.ether.inet.log_arp_movements=0' There's also "net.link.ether.inet.log_arp_wrong_iface" and "net.inet.ip.check_interface" which influence related behaviour. You also posted (documentationized IP-addresses): > I think the problem starts with the host seeing the client/guest on 2 > interfaces, the nic (mlnxen0) and the tap(tap0) > on the host: > > arp -a > ... > bhv-00.cs.huji.ac.il (192.0.2.246) at xx.xx.xx.xx.xx on tap0 expires in 1001 > seconds [ethernet] > bhv-00.cs.huji.ac.il (192.0.2.246) at xx.xx.xx.xx.xx on mlxen0 expires in 644 > seconds [ethernet] Initially, you reference two MAC-addresses with and . The recent post indicates non-different MAC-addresses. If and - resp. xx.xx.xx.xx.xx - are equal (but seen on different interfaces), this wouldn't get logged I think. But it was the only harmless case for straight forward setups. Even with STP/LACP/CARP/etc. in place, "arp: IP-address moved" always indicates a misconfiguration and I don't know any example where the two different MAC-Addresses for one IP-address were harmless. While using a single (locally administrated?) MAC address more than once sitewide _can_ make sense, having two interfaces on one host which both are on the same ethernet segment like the two interfaces with the same MAC address, looks like an unintended setup. So I strongly suggest to analyze your setup before altering the mentioned sysctl!!! -harry ___ 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: bhyve and arp problem
> On 30 Mar 2018, at 18:44, Allan Jude wrote: > > On 2018-03-30 07:16, Daniel Braniss wrote: >> hi, >> this is my first attempt at bhyve, and so far all seems ok, except >> in my guest, the mac address of the hosting keeps flipping, ie, every 20 >> minutes >> i see a message : >> … arp: nnn (the hosting ip) moved from to >> on both the host and guest I’m running a very resent -stable. >> the is the mac of the host nic, while the is the tap0 >> >> i know this looks harmless, but it’s annoying >> >> danny >> ___ >> 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" >> > > The MAC address is likely not changing. That sounds more like an IP > conflict. I think the problem starts with the host seeing the client/guest on 2 interfaces, the nic (mlnxen0) and the tap(tap0) on the host: arp -a ... bhv-00.cs.huji.ac.il (132.65.80.246) at xx.xx.xx.xx.xx on tap0 expires in 1001 seconds [ethernet] bhv-00.cs.huji.ac.il (132.65.80.246) at xx.xx.xx.xx.xx on mlxen0 expires in 644 seconds [ethernet] > > -- > Allan Jude > ___ > 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" ___ 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: bhyve and arp problem
On 2018-03-30 07:16, Daniel Braniss wrote: > hi, > this is my first attempt at bhyve, and so far all seems ok, except > in my guest, the mac address of the hosting keeps flipping, ie, every 20 > minutes > i see a message : > … arp: nnn (the hosting ip) moved from to > on both the host and guest I’m running a very resent -stable. > the is the mac of the host nic, while the is the tap0 > > i know this looks harmless, but it’s annoying > > danny > ___ > 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" > The MAC address is likely not changing. That sounds more like an IP conflict. -- Allan Jude ___ 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"
