Re: [Accel-ppp-users] discarding message with invalid tid 0
Status: Beta
Brought to you by:
xebd
Menu
▾
▴
Re: [Accel-ppp-users] discarding message with invalid tid 0
|
From: Alarig Le L. <al...@sw...> - 2018-10-14 20:19:01
|
On ven. 12 oct. 17:21:01 2018, Guillaume Nault wrote:
> There are a few places where the bug might come from. Either the host
> doesn't tell the driver that checksum isn't fully computed, or the
> driver advertises checksum offload capabilities without actually
> implementing it.
> If you use virtualisation, the virtual NIC might advertise offload
> support and rely on the physical NIC driver to actually perform the
> computation. If the physical NIC doesn't offer this feature, the
> virtual NIC should provide software fallback.
> I suppose there is a bug somewhere in this chain.
>
> So I imagine something changed in your setup wrt. checksum offload,
> either on the LNS or the hypervisor.
The checksums seem to be enabled on both LNS:
judicael-adsl ~ # ethtool -k eth0 | grep tx-checksum
tx-checksumming: on
tx-checksum-ipv4: off [fixed]
tx-checksum-ip-generic: on
tx-checksum-ipv6: off [fixed]
tx-checksum-fcoe-crc: off [fixed]
tx-checksum-sctp: off [fixed]
lns02 ~ # ethtool -k eth2 | grep tx-checksum
tx-checksumming: on
tx-checksum-ipv4: off [fixed]
tx-checksum-ip-generic: on
tx-checksum-ipv6: off [fixed]
tx-checksum-fcoe-crc: off [fixed]
tx-checksum-sctp: off [fixed]
But, as soon as I re-enable checksumming on the BGP router, I see the
same kind of messages in the logs.
root@bgp-adsl:~ # ifconfig vtnet2 rxcsum txcsum tso lro
lns02 ~ # tail -F /var/log/daemon.log
[…]
Oct 14 22:00:42 lns02 accel-pppd: l2tp tunnel 347-46302 (78.41.184.80:1701): retransmission #1
Oct 14 22:00:42 lns02 accel-pppd: l2tp tunnel 347-46302 (78.41.184.80:1701): retransmit (timeout) [L2TP tid=46302 sid=0 <Message-Type Hello>]
Oct 14 22:00:44 lns02 accel-pppd: l2tp tunnel 347-46302 (78.41.184.80:1701): retransmission #2
Oct 14 22:00:44 lns02 accel-pppd: l2tp tunnel 347-46302 (78.41.184.80:1701): retransmit (timeout) [L2TP tid=46302 sid=0 <Message-Type Hello>]
Oct 14 22:00:48 lns02 accel-pppd: l2tp tunnel 347-46302 (78.41.184.80:1701): retransmission #3
Oct 14 22:00:48 lns02 accel-pppd: l2tp tunnel 347-46302 (78.41.184.80:1701): retransmit (timeout) [L2TP tid=46302 sid=0 <Message-Type Hello>]
Oct 14 22:00:56 lns02 accel-pppd: l2tp tunnel 347-46302 (78.41.184.80:1701): retransmission #4
Oct 14 22:00:56 lns02 accel-pppd: l2tp tunnel 347-46302 (78.41.184.80:1701): retransmit (timeout) [L2TP tid=46302 sid=0 <Message-Type Hello>]
Oct 14 22:01:12 lns02 accel-pppd: l2tp tunnel 347-46302 (78.41.184.80:1701): retransmission #5
Oct 14 22:01:12 lns02 accel-pppd: l2tp tunnel 347-46302 (78.41.184.80:1701): retransmit (timeout) [L2TP tid=46302 sid=0 <Message-Type Hello>]
Oct 14 22:01:28 lns02 accel-pppd: l2tp tunnel 347-46302 (78.41.184.80:1701): no acknowledgement from peer after 5 retransmissions, deleting tunnel
Oct 14 22:01:28 lns02 accel-pppd: l2tp tunnel 347-46302 (78.41.184.80:1701): deleting tunnel
Oct 14 22:01:28 lns02 accel-pppd: l2tp session 347-46302, 61625-32197: deleting session
Oct 14 22:01:28 lns02 accel-pppd: l2tp session 347-46302, 61625-32197: deleting data channel
Oct 14 22:01:28 lns02 accel-pppd: l2tp session 347-46302, 45186-40850: deleting session
Oct 14 22:01:28 lns02 accel-pppd: l2tp session 347-46302, 45186-40850: deleting data channel
Oct 14 22:01:28 lns02 accel-pppd: ppp0:qu...@gr...: send [RADIUS(1) Accounting-Request id=1 <User-Name "qu...@gr..."> <NAS-Identifier "accel-ppp"> <NAS-IP-Address 89.234.186.205> <NAS-Port 0> <NAS-Port-Id "ppp0"> <NAS-Port-Type Virtual> <Service-Type Framed-User> <Framed-Protocol PPP> <Calling-Station-Id "78.41.184.80"> <Called-Station-Id "89.234.186.12"> <Acct-Status-Type Stop> <Acct-Authentic RADIUS> <Acct-Session-Id "0dbb447ec6fa5cbf"> <Acct-Session-Time 73568> <Acct-Input-Octets 365708680> <Acct-Output-Octets 1036838156> <Acct-Input-Packets 2436312> <Acct-Output-Packets 4425180> <Acct-Input-Gigawords 0> <Acct-Output-Gigawords 1> <Framed-IP-Address 89.234.186.38> <Framed-Interface-Id 0:0:0:2> <Framed-IPv6-Prefix 2a00:5884:1100:3::/64> <Acct-Terminate-Cause NAS-Request>]
Oct 14 22:01:28 lns02 accel-pppd: ppp0:qu...@gr...: pppd_compat: ip-down started (pid 19050)
Oct 14 22:01:28 lns02 accel-pppd: ppp1:un...@gr...: send [RADIUS(1) Accounting-Request id=1 <User-Name "un...@gr..."> <NAS-Identifier "accel-ppp"> <NAS-IP-Address 89.234.186.205> <NAS-Port 1> <NAS-Port-Id "ppp1"> <NAS-Port-Type Virtual> <Service-Type Framed-User> <Framed-Protocol PPP> <Calling-Station-Id "78.41.184.80"> <Called-Station-Id "89.234.186.12"> <Acct-Status-Type Stop> <Acct-Authentic RADIUS> <Acct-Session-Id "0dbb447ec6fa4c93"> <Acct-Session-Time 153647> <Acct-Input-Octets 391223201> <Acct-Output-Octets 3536240375> <Acct-Input-Packets 4975569> <Acct-Output-Packets 6891147> <Acct-Input-Gigawords 0> <Acct-Output-Gigawords 1> <Framed-IP-Address 89.234.186.39> <Framed-Interface-Id 6:6b84:6:6b7d> <Framed-IPv6-Prefix 2a00:5884:1100:7::/64> <Acct-Terminate-Cause NAS-Request>]
Oct 14 22:01:28 lns02 accel-pppd: ppp1:un...@gr...: pppd_compat: ip-down started (pid 19051)
Oct 14 22:01:28 lns02 accel-pppd: ppp0:qu...@gr...: pppd_compat: ip-down finished (0)
Oct 14 22:01:28 lns02 accel-pppd: ppp0:: session destroyed
Oct 14 22:01:28 lns02 accel-pppd: l2tp session 347-46302, 45186-40850: session destroyed
Oct 14 22:01:28 lns02 accel-pppd: ppp1:un...@gr...: pppd_compat: ip-down finished (0)
Oct 14 22:01:28 lns02 accel-pppd: ppp1:: session destroyed
Oct 14 22:01:28 lns02 accel-pppd: l2tp session 347-46302, 61625-32197: session destroyed
Oct 14 22:01:28 lns02 accel-pppd: l2tp tunnel 347-46302 (78.41.184.80:1701): tunnel destroyed
Oct 14 22:01:28 lns02 bird: KRT: Received route 2a00:5884:1107::/48 with strange next-hop fe80::6:6b84:6:6b7d
Oct 14 22:01:28 lns02 accel-pppd: recv [RADIUS(1) Accounting-Response id=1]
Oct 14 22:01:28 lns02 accel-pppd: recv [RADIUS(1) Accounting-Response id=1]
Oct 14 22:01:41 lns02 accel-pppd: l2tp: discarding unexpected message from 78.41.184.80: invalid tid 347
Oct 14 22:01:42 lns02 accel-pppd: l2tp: discarding unexpected message from 78.41.184.80: invalid tid 347
So, the two ADSL lines on this LNS at this moment went down, and the
same kind of message appears (unless the tunnel number was already
negotiated)
The two hypervisors have the same kind of network cards
01:00.0 Ethernet controller: Broadcom Limited NetXtreme II BCM5709 Gigabit Ethernet (rev 20)
or
02:00.0 Ethernet controller: Broadcom Limited NetXtreme II BCM5716 Gigabit Ethernet (rev 20)
So for me, the problem is on the checksums, but is located on the FreeBSD IP stack (again…).
What I still don’t understand, is why xl2tpd isn’t affected, but I
think it’s not the right place to discuss about it ;)
Cheers,
--
Alarig
|
