[Bug 277038] igc driver accesses hardware resources after they are released.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277038 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|n...@freebsd.org Keywords||IntelNetworking -- You are receiving this mail because: You are the assignee for the bug.
Re: how to troubleshoot "arpresolve: can't allocate llinfo for " errorr ?
> I get the following error "arpresolve: can't allocate llinfo for 1.1.245.192 > on vlan320" I can't explain. (IP edited). I only setup 1.1.245.192/31 between > this vlan which parent is a VF from a MLX5EN(4) card . > > I am using a generated mac address and distribute IPs over OSPF with bird. > > What could trigger this error? The doc says > > ``` > It "arpresolve: can't allocate llinfo for %d.%d.%d.%d" > The route for the referenced host points to a device upon which ARP is > required, but ARP was unable to allocate a routing table entry in which > to store the host's MAC address. > This usually points to a misconfigured routing table. Mis matched netmask on this network segment is a common cause of this issue. Check all your hosts that there netmask matches the /31 you show below. I could also be a bad netmask on a route entry, check your routing table to make sure it has a /31 route or a pair of /32 routes. > It can also occur if the kernel cannot allocate memory. > ``` > > But I am not sure what to check. Any hint is welcome :) > > The configuration for this vlan is locally: > > ``` > vlan320: flags=1008843 > metric 0 mtu > 1500options=1c680703 > ether 02:01:02:01:01:01 > inet 1.1245.193 netmask 0xfffe broadcast 255.255.255.255 not a valid address, so when tiy "obscured" this you also created invalid data. I think this was suppose to be 1.1.245.193 > inet6 fe80::1:2ff:fe01:101%vlan320 prefixlen 64 scopeid 0x9 > inet6 ::1:fe02::2 prefixlen 64 > groups: vlan > vlan: 320 vlanproto: 802.1q vlanpcp: 0 parent interface: mce1 > media: Ethernet 25GBase-SR > status: active > nd6 options=21 > > > > ``` > vlan320: flags=1008843 > metric 0 mtu 1500 > > options=1c680703 > ether 02:01:02:02:01:01 > inet 1.1.245.192 netmask 0xfffe broadcast 255.255.255.255 > inet6 fe80::1:2ff:fe02:101%vlan320 prefixlen 64 scopeid 0xa > groups: vlan > vlan: 320 vlanproto: 802.1q vlanpcp: 0 parent interface: mce1 > media: Ethernet 25GBase-SR > status: active > nd6 options=21 > ``` > on remote: > > ``` > > > Beno?t > > > -- Rod Grimes rgri...@freebsd.org
[Bug 277029] Invalid source address selection for IPv4
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277029 Mark Linimon changed: What|Removed |Added CC||ma...@freebsd.org Assignee|b...@freebsd.org|n...@freebsd.org -- You are receiving this mail because: You are the assignee for the bug.
[Bug 276890] Getting fq_codel correct on inbound shaping
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276890 --- Comment #2 from Dave Taht --- I got some packet captures from an opnsense user, who also on my behalf turned on and off LRO. One of the test runs was decidedly odd in that it missed the target for far, far too long, which could be just about anything, including a path change or a tcp bug. I will plot it later, and poke deeper into the packet captures. http://london.starlink.taht.net/freebsd/ecn/ The ecn on tests also showed a known issue with coping with slow start on short RTTs. -- You are receiving this mail because: You are the assignee for the bug.
Stop Newsletter
Stop Newsletter Cordialement, Marcos Lage
how to troubleshoot "arpresolve: can't allocate llinfo for " errorr ?
I get the following error "arpresolve: can't allocate llinfo for 1.1.245.192 on vlan320" I can't explain. (IP edited). I only setup 1.1.245.192/31 between this vlan which parent is a VF from a MLX5EN(4) card . I am using a generated mac address and distribute IPs over OSPF with bird. What could trigger this error? The doc says ``` It "arpresolve: can't allocate llinfo for %d.%d.%d.%d" The route for the referenced host points to a device upon which ARP is required, but ARP was unable to allocate a routing table entry in which to store the host's MAC address. This usually points to a misconfigured routing table. It can also occur if the kernel cannot allocate memory. ``` But I am not sure what to check. Any hint is welcome :) The configuration for this vlan is locally: ``` vlan320: flags=1008843 metric 0 mtu 1500options=1c680703 ether 02:01:02:01:01:01 inet 1.1245.193 netmask 0xfffe broadcast 255.255.255.255 inet6 fe80::1:2ff:fe01:101%vlan320 prefixlen 64 scopeid 0x9 inet6 ::1:fe02::2 prefixlen 64 groups: vlan vlan: 320 vlanproto: 802.1q vlanpcp: 0 parent interface: mce1 media: Ethernet 25GBase-SR status: active nd6 options=21 ``` vlan320: flags=1008843 metric 0 mtu 1500 options=1c680703 ether 02:01:02:02:01:01 inet 1.1.245.192 netmask 0xfffe broadcast 255.255.255.255 inet6 fe80::1:2ff:fe02:101%vlan320 prefixlen 64 scopeid 0xa groups: vlan vlan: 320 vlanproto: 802.1q vlanpcp: 0 parent interface: mce1 media: Ethernet 25GBase-SR status: active nd6 options=21 ``` on remote: ``` Benoît
