Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Robert Bradley <robert.bradley1@gmail.com>,
	Felix Fietkau <nbd@nbd.name>,
	 cerowrt-devel@lists.bufferbloat.net
Subject: [Cerowrt-devel] deployed some cero this weekend, chasing checksums
Date: Sun, 27 Jan 2013 23:41:37 -0800	[thread overview]
Message-ID: <CAA93jw7S0_3CW6WG=3Ztq4A3A3x2_7dvV6inN53crD9-wnNfOA@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1329 bytes --]

I have been debugging some weirdness for a while. You might want to do some
captures on the latest cero and look at checksums.

An unreasonably high number of checksum issues seem to be happening, but
there doesn't appear to be a whole lot of pattern to it, as yet.

I will simplify. I pinged locally and 8.8.8.8 and surfed the web, and a
symptom is that some other routers can't ping sometimes nor access much of
the internet beyond the gateway. They can always reach the gateway.

in the interim, the topology on this capture are

172.30.102.17 - laptop via ethernet to
172.20.102.1 - cerowrt 3.7.4-4 via ethernet to
172.20.6.1 - ubnt 3.3.8-26 via mesh to
172.20.142.11 - ubnt 3.7.4-4 via ethernet to
* 192.168.100.1 - cerowrt 3.7.2 capture point (yes, updating that)
10.0.10.1 - comcast box (yes, double nat, fixing that)

I took a capture on the se00 interface

tcpdump -i se00 -w/tmp/yurt.cap host 172.20.102.17

and stuck that capture there:

http://snapon.lab.bufferbloat.net/~d/yurt/yurt.cap

and then looked at it with wireshark with this filter

ip.checksum_bad == 1

and scratched my head at the error rate (about 1%) and the pattern (lack
thereof)

I will simplify in the mroning

-- 
Dave Täht

Fixing bufferbloat with cerowrt:
http://www.teklibre.com/cerowrt/subscribe.html

[-- Attachment #2: Type: text/html, Size: 1595 bytes --]

             reply	other threads:[~2013-01-28  7:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-28  7:41 Dave Taht [this message]
2013-01-28  7:52 ` Dave Taht
2013-01-28 13:43   ` Robert Bradley
2013-01-28 14:14     ` Dave Taht
2013-01-28 23:29     ` David Lang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAA93jw7S0_3CW6WG=3Ztq4A3A3x2_7dvV6inN53crD9-wnNfOA@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=nbd@nbd.name \
    --cc=robert.bradley1@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox