On Mon, 1 Oct 2018, Dave Taht wrote:
On Mon, Oct 1, 2018 at 8:58 AM Dave Taht wrote:
Here you go! Going to go look at the firewall rules in a sec
I changed the rules to allow 547 and 546, no difference. I even
flushed the ipv6tables rules entirely,
and I'm running without that for a
On Mon, Oct 1, 2018 at 10:13 AM Michael Richardson wrote:
>
>
> Dave Taht wrote:
> > hmm... bad udp checksum???
>
> With some capture mechanisms, tcpdump gets bogus values because the hardware
> did the checksums. I wouldn't imagine that we have hardware checksum offload
> on openwrt
Dave Taht wrote:
> hmm... bad udp checksum???
With some capture mechanisms, tcpdump gets bogus values because the hardware
did the checksums. I wouldn't imagine that we have hardware checksum offload
on openwrt devices, but could be.
Or it's a real issue.
> :/tmp# 09:12:17.404257 IP6
On Mon, Oct 1, 2018 at 9:29 AM Anderson, Charles R wrote:
>
> Is udp checksum offload enabled? If so, tcpdump/wireshark won't see
> the actual checksum and assume it is bad.
I imagine it is theoretically offloaded. I DO have an 18.06.1 arm box
now up that IS
getting dhcpv6-pd from comcast
Is udp checksum offload enabled? If so, tcpdump/wireshark won't see
the actual checksum and assume it is bad.
On Mon, Oct 01, 2018 at 09:12:57AM -0700, Dave Taht wrote:
> hmm... bad udp checksum???
>
> :/tmp# 09:12:17.404257 IP6 (flowlabel 0xdfff4, hlim 1, next-header UDP
> (17) payload length:
hmm... bad udp checksum???
:/tmp# 09:12:17.404257 IP6 (flowlabel 0xdfff4, hlim 1, next-header UDP
(17) payload length: 159) fe80::20d:b9ff:fe43:a06c.546 >
ff02::1:2.547: [bad udp cksum 0x58f4 -> 0xc4a1!]
On Mon, Oct 1, 2018 at 9:12 AM Dave Taht wrote:
>
> On Mon, Oct 1, 2018 at 8:58 AM Dave Taht
On Mon, Oct 1, 2018 at 8:58 AM Dave Taht wrote:
>
> Here you go! Going to go look at the firewall rules in a sec
I changed the rules to allow 547 and 546, no difference. I even
flushed the ipv6tables rules entirely,
and I'm running without that for a while. I can certainly imagine
comcast's
Here you go! Going to go look at the firewall rules in a sec
On Mon, Oct 1, 2018 at 8:45 AM Mikael Abrahamsson wrote:
>
> On Mon, 1 Oct 2018, Dave Taht wrote:
>
> > Sigh. Once upon a time I used to test this stuff on comcast. So I
> > finally got around to deploying
> > a new 18.06 gateway
On Mon, 1 Oct 2018, Dave Taht wrote:
Sigh. Once upon a time I used to test this stuff on comcast. So I
finally got around to deploying
a new 18.06 gateway and ipv6 is busted with comcast.
Can you please email me output from "tcpdump -n -vvv -i port 546 or
port 547 or icmp6" as your WAN is