[Bug 227963] panic on shutdown - if_delmulti_ifma : Fatal trap 9: general protection fault while in kernel mode

2019-02-15 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227963

Andriy Voskoboinyk  changed:

   What|Removed |Added

 CC||a...@freebsd.org

--- Comment #1 from Andriy Voskoboinyk  ---
Seems to be handled in bug #233535; is it still reproducible on recent CURRENT?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


[Bug 234073] ixl: SR-IOV causes "Malicious Driver Detection event" when not all VFs are in passthrough mode

2019-02-15 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234073

--- Comment #12 from Eric Joyner  ---
(In reply to Finn from comment #11)
No, sorry. We haven't been able to pin down a root cause for the issue. We've
also had to do work on internal projects, so we haven't been able to spend much
time investigating this.

That said, we haven't forgotten about this issue; we do want to get this fixed.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


[Bug 235700] oce(4) driver causes fatal trap 12 on boot with emulex 10gbe nic

2019-02-15 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235700

Ryan Moeller  changed:

   What|Removed |Added

 CC||r...@freqlabs.com

--- Comment #1 from Ryan Moeller  ---
Created attachment 202047
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=202047=edit
Fix panic in OCE

I also experienced this issue, and came up with a patch that solved the panic.
That machine is currently in pieces waiting for a replacement motherboard, but
I think this was the change I applied.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


Re: bhyve, nat, lagg failover problems

2019-02-15 Thread Rodney W. Grimes
> On 2/15/19 5:28 PM, Johannes Lundberg wrote:
> > Hey!
> >
> > I have a setup like described here:
> > https://github.com/churchers/vm-bhyve/wiki/NAT-Configuration
> > Bhyve guests use static IP addresses and everything works fine (i.e.
> > guest can access host and internet).
> >
> > However, if I use lagg with failover for em0 and wlan0, and replace em0
> > with lagg0 in pf.conf the guests can not communicate with the host, or
> > internet. The failover works fine for the host. I'm sure there has to be
> > a way to get this to work...
> >
> > Is there anyone that can help?
> 
> Found the problem! The command
> 
> |# vm switch address public 192.168.8.1/24|
> 
> |fixed it. vm-bhyve's command 'vm's help did not list this option as
> available and therefor the confusion. It turns out the "vm" command's
> help was outdated, not the wiki. Now my bhyve guests also work properly
> during failover from ethernet to wifi :D I only setup the lagg in
> rc.conf and let vm-bhyve handle all settings regarding the bridge, as
> described in their wiki.
> |

Would you be willing to either put up a wiki article on this,
or work with Michael Dexter who would love to have this
well documented in the wiki as it is a frequently asked for
feature/setup.

I have added him to the cc, dex...@freebsd.org.

Thanks,
-- 
Rod Grimes rgri...@freebsd.org
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


Re: bhyve, nat, lagg failover problems

2019-02-15 Thread Johannes Lundberg


On 2/15/19 5:28 PM, Johannes Lundberg wrote:
> Hey!
>
> I have a setup like described here:
> https://github.com/churchers/vm-bhyve/wiki/NAT-Configuration
> Bhyve guests use static IP addresses and everything works fine (i.e.
> guest can access host and internet).
>
> However, if I use lagg with failover for em0 and wlan0, and replace em0
> with lagg0 in pf.conf the guests can not communicate with the host, or
> internet. The failover works fine for the host. I'm sure there has to be
> a way to get this to work...
>
> Is there anyone that can help?

Found the problem! The command

|# vm switch address public 192.168.8.1/24|

|fixed it. vm-bhyve's command 'vm's help did not list this option as
available and therefor the confusion. It turns out the "vm" command's
help was outdated, not the wiki. Now my bhyve guests also work properly
during failover from ethernet to wifi :D I only setup the lagg in
rc.conf and let vm-bhyve handle all settings regarding the bridge, as
described in their wiki.
|

>
> Cheers!
> /Johannes
>
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


[Bug 235699] Kernel panics when setting IP address if net.link.ether.inet.garp_rexmit_count=2

2019-02-15 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235699

Mark Linimon  changed:

   What|Removed |Added

   Assignee|b...@freebsd.org|n...@freebsd.org

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


[Bug 235700] oce(4) driver causes fatal trap 12 on boot with emulex 10gbe nic

2019-02-15 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235700

Mark Linimon  changed:

   What|Removed |Added

   Keywords||regression
   Assignee|b...@freebsd.org|n...@freebsd.org

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


bhyve, nat, lagg failover problems

2019-02-15 Thread Johannes Lundberg
Hey!

I have a setup like described here:
https://github.com/churchers/vm-bhyve/wiki/NAT-Configuration
Bhyve guests use static IP addresses and everything works fine (i.e.
guest can access host and internet).

However, if I use lagg with failover for em0 and wlan0, and replace em0
with lagg0 in pf.conf the guests can not communicate with the host, or
internet. The failover works fine for the host. I'm sure there has to be
a way to get this to work...

Is there anyone that can help?

Cheers!
/Johannes

___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


Point-to-point using GRE over IPv6 -> not possible with a single /128 address on the server?

2019-02-15 Thread Peter G.
Hi,

I've got issues establishing a point-to-point ipv6-over-ipv6 GRE link.

IPv4 which works as expected:
this end: 10.0.1.10
other end: 10.0.2.10
GW: 10.0.1.1
iface: em0

>ifconfig gre4 create
>ifconfig gre4 inet 10.0.1.10 10.0.2.10 netmask 0x tunnel
10.0.1.10 10.0.2.10 tunnelfib 2
>route add -host 10.0.1.1 -iface em0 -fib 2
>route add -host 10.0.2.10 10.0.1.1 -fib 2

Works. The tunnel is marked with FIB 2, and a point-to-point is
established. Can be used with IPSEC in transport or whatever.


Now, IPv6 is problematic. The server has allocated a single IPv6 address
with prefixlen 112. This could be the source of the issue.

Private addresses replicate the setup.

this end: fc01:e::100/112
other end fc02:e::200
GW: fc01:e::1

>ifconfig em0
#em0:
#   inet6 fc01:e::100 prefixlen 112

This works. Default GW is at fc01:e::1.

Now the GRE tunnel

>ifconfig gre6 create
>ifconfig gre6 inet6 fc01:e::100 fc:02:e::200 tunnelfib 6
#ifconfig: ioctl (SIOCAIFADDR): File exists

Why is this not possible? Isn't the logic behind it the same as with
IPv4? If not, why not?

Does this mean it is not possible to have a point-to-point using IPv6 on
a machine with only a single /128 address?

Found this as reference:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208173 but what he did
was on a much broader range.

Many thanks!

Peter
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


[Bug 235246] if_em init fails to allocate IRQ in 12.0-RELEASE

2019-02-15 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235246

Kubilay Kocak  changed:

   What|Removed |Added

  Flags||mfc-stable12+

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"