linux-kernel - Re: strange fragmented udp packets

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 3 Jan 2011 16:47:55 -0700
From:	Thomas Fjellstrom <thomas@...llstrom.ca>
To:	linux-kernel@...r.kernel.org
Cc:	linux-net@...r.kernel.org
Subject: Re: strange fragmented udp packets

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@...llstrom.ca
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/