From: Jerry Van Baren <gerald.vanbaren@smiths-aerospace.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] PATCH: Force TFTP to use a fixed UDP port
Date: Thu, 6 Jan 2005 16:55:42 -0500 [thread overview]
Message-ID: <41DDB3DE.4010403@smiths-aerospace.com> (raw)
Hi Wolfgang,
Attached is a patch to allow the user to set an environment variable
"tftpourport" to force TFTP to use that value for "TftpOurPort" (our UDP
port). As discussed yesterday on this list, this is helpful for
"punching through" a firewall such as is installed with Windows XP SP2.
Making it an environment variable is cute but an overkill. If there is
an outcry over the level of overkill, I would be willing to make the
UDP port a simple #define of a compile time constant, in which case it
would actually save a few bytes of ROM over the pseudo-random algorithm :-).
Thanks,
gvb
CHANGELOG:
* Patch by Jerry Van Baren 05 Jan 2005
- Make the u-boot TFTP source port be configurable using the
environment variable "tftpourport":
* If set, use that port as the u-boot source port
* If not set, use the current method of using a pseudo random port
- The additional code can be totally removed by setting the
#define TFTP_PORT_FROM_ENV (in the net/tftp.c file) to zero.
- The purpose behind this change is that our customer will
modify their TFTP server so that it blindly starts the
TFTP transfer using the pre-configured target IP address
and UDP port. This will have the effect of "punching through"
the (Windows XP) firewall, allowing the remainder of the TFTP
transfer to proceed normally.
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: 050105.patch
Url: http://lists.denx.de/pipermail/u-boot/attachments/20050106/44ee598e/attachment.txt
next reply other threads:[~2005-01-06 21:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-06 21:55 Jerry Van Baren [this message]
2005-01-06 23:31 ` [U-Boot-Users] PATCH: Force TFTP to use a fixed UDP port Wolfgang Denk
2005-01-06 23:48 ` Tolunay Orkun
2005-01-07 13:23 ` Jerry Van Baren
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=41DDB3DE.4010403@smiths-aerospace.com \
--to=gerald.vanbaren@smiths-aerospace.com \
--cc=u-boot@lists.denx.de \
/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