From: Ralf Baechle <ralf@linux-mips.org>
To: Florian Lohoff <flo@rfc822.org>
Cc: linux-mips@linux-mips.org
Subject: Re: Tftp problems with ARC firmware
Date: Fri, 14 Oct 2005 12:10:58 +0100 [thread overview]
Message-ID: <20051014111058.GA2608@linux-mips.org> (raw)
In-Reply-To: <20051013220936.GA15668@paradigm.rfc822.org>
On Fri, Oct 14, 2005 at 12:09:36AM +0200, Florian Lohoff wrote:
> > echo 1 > /proc/sys/net/ipv4/ip_no_pmtu_disc
> > echo 4096 32767 > /proc/sys/net/ipv4/ip_local_port_range
> >
> > at a new version of tftp-hpa which solves the PMTU problem by disabling it
> > only for the tftp client and introduces a new -R begin:end option which
> > allows to limit the port number range. The changes are about to become
> > available in the tftp-hpa git repository at
> > http://www.kernel.org/pub/scm/network/tftp/tftp-hpa.git; see also
> > http://www.linux-mips.org/wiki/ARC#tftp-hpa. Please send test reports to
> > syslinux@zytor.com and linux-mips@linux-mips.org.
>
> I made a patch against tftpd-hpa for disabling path MTU discovery - Its
> in the Debian BTS:
>
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=316616
>
> It should already be merged upstream. User "-F" to disable PMTUd.
Never made it to HPA - HPA wrote the patches for these two bugs himself
yesterday when I mentioned the problem to him. His patches are different
in the he disables PMTU discovery entirely - it's not useful for TFTP.
And your patch doesn't work around the other firmware bug which requires
restricting the port range. We had to get rid of the currently recommended
workaround - it seriously restricts the IP stack; cripples is probably
the right expression for busy servers.
Patch rotting in the Debian bugtracking system seems to become a classic ;-)
Ralf
next prev parent reply other threads:[~2005-10-14 11:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-13 19:32 Tftp problems with ARC firmware Ralf Baechle
2005-10-13 22:09 ` Florian Lohoff
2005-10-14 11:10 ` Ralf Baechle [this message]
2006-02-18 15:55 ` Stephen P. Becker
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=20051014111058.GA2608@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=flo@rfc822.org \
--cc=linux-mips@linux-mips.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.