Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Maciej Soltysiak <maciej@soltysiak.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] ping icmp ttl exceeded
Date: Mon, 4 Feb 2013 08:37:41 -0800	[thread overview]
Message-ID: <CAA93jw4X5RSTM4hVC5cNh8h0zsjpk=i1ou9FQTayP+dd5aK54w@mail.gmail.com> (raw)
In-Reply-To: <CAMZR1YDvoSh15hN0Y72P_gs3aVGS8xh=_UcYguCiD+jr16TNLQ@mail.gmail.com>

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

On Mon, Feb 4, 2013 at 6:17 AM, Maciej Soltysiak <maciej@soltysiak.com>wrote:

> On Mon, Feb 4, 2013 at 8:41 AM, Dave Taht <dave.taht@gmail.com> wrote:
>
>> Heh. I turned out I'd left mtr running in another window...
>
> Yeah, exactly. Decreasing TTLs suggest traceroute tools :-)
>

Well in this case I've still been chasing the crc bug I'd encountered and
some problems with the double nat I'm still dealing with. I'd got pdsh up
and had been issuing commands like

pdsh -a -l root 'fping -C 2 -q 8.8.8.8'

(which -a finds all routers in /etc/genders, and simultaneously as possible
executes the ping command)

So I thought maybe I'd done an infinite ping or there was a real routing
problem for the 5 minutes after I'd written that email.

This btw, is so far as I know, is now the worlds most complex, meshed, and
nfq_codeled wifi/ethernet network. snmp is up too, but I struggle to get
useful information out of minstrel and codel's drop stats as yet. I think
adding better kernel support for the latter would be nice (some sort of
netlink message containing the dropped packet and why)

The longest path through it:

http://pastebin.com/kWAXJS6d

(pdsh is also very useful for things like 'opkg update; opkg install
something',
when a network gets this large and complex)

I can certainly see why being able to specify a route was very important in
the early protocol design of the imps and ip, and am kind of sorry it
proved problematic in terms of security.



>
> As Ketan noted, it's best to decode what's in the ICMP TTL exceeded
> payload to see what packet triggered this.
>
> traceroute uses ICMP ECHO REQUEST
> tracepath uses UDP
> tcptraceroute uses TCP SYN (this tools is actually usefull to check if
> your packets go different routes depending on the port they're going to,
> e.g. detecting a transparent proxy which shows up for port 80, but not for
> others)
>
> There are other tools which could be used to do the same with different
> types of packets, say, crafting a fake ICMP ECHO REPLY to see how good at
> being stateful are the firewalls on the path.
>
> Regards,
> Maciej
>
>



-- 
Dave Täht

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

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

      reply	other threads:[~2013-02-04 16:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-04  7:10 Dave Taht
2013-02-04  7:33 ` Ketan Kulkarni
2013-02-04  7:34   ` Ketan Kulkarni
2013-02-04  7:41     ` Dave Taht
2013-02-04 14:17       ` Maciej Soltysiak
2013-02-04 16:37         ` Dave Taht [this message]

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='CAA93jw4X5RSTM4hVC5cNh8h0zsjpk=i1ou9FQTayP+dd5aK54w@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=maciej@soltysiak.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