From: Thomas Fjellstrom <thomas@fjellstrom.ca>
To: linux-kernel@vger.kernel.org
Cc: linux-net@vger.kernel.org
Subject: Re: strange fragmented udp packets
Date: Mon, 3 Jan 2011 16:47:55 -0700 [thread overview]
Message-ID: <201101031647.56077.thomas@fjellstrom.ca> (raw)
In-Reply-To: <201012272354.44196.thomas@fjellstrom.ca>
On December 27, 2010, Thomas Fjellstrom wrote:
> I've been seeing a strange problem poke its head up since I switched from
> pfSense to a debian based shorewall firewall.
>
> I've been un able to connect to my VOIP provider due to some oddly
> fragmented UDP sip packets not ever reaching the application layer on the
> provider's side.
>
> I can't explain the packets getting fragmented (or I couldn't, see below).
> And only have a guess as to why my VOIP provider isn't seeing them, I've
> heard that some firewalls explicitly block fragmented UDP as its often
> used in DoS attacks, and for little else.
>
> Here's at least what tcpdump has to say..
>
> packet coming in:
> 23:38:26.136021 IP x.x.x.x.5060 > x.x.x.x.5060: SIP, length: 582
>
> packet going out:
> 23:38:18.136085 IP x.x.x.x.5060 > x.x.x.x.5060: SIP, length: 544
> 23:38:18.136169 IP x.x.x.x > x.x.x.x: udp
>
> ...
>
> After writing all that I've realized that the problem is the mtu on the nic
> attached to my cable modem, it was set to 576 for some odd reason. Changing
> the mtu to 1500 fixes my problem, but what is causing it to auto select an
> mtu of 576 anyhow? Could my modem be telling it that 576 is better for it?
Anyone have a hint? I've checked with my sip provider and they don't have
iptables set up, so nothing should be getting in the way of these packets. For
some reason they just aren't reaching the SIP server.
--
Thomas Fjellstrom
thomas@fjellstrom.ca
next prev parent reply other threads:[~2011-01-03 23:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-28 6:54 strange fragmented udp packets Thomas Fjellstrom
2011-01-03 23:47 ` Thomas Fjellstrom [this message]
2011-01-04 8:50 ` Alexander Clouter
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201101031647.56077.thomas@fjellstrom.ca \
--to=thomas@fjellstrom.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
/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