u-boot.git/net/bootp.c, branch v2016.05

bootp: Prevent u-boot from using others responses.

2016-03-27T13:12:21+00:00

In rare circumstances two dhcp clients may generate the same
bootp ID. If this happens it is vital that the client also checks
the hw address in the received response to prevent IP address conflicts.

Signed-off-by: Anton Persson

net: bootp: Add environment variable for timeout period

2016-02-26T19:37:38+00:00

There is currently one config option (CONFIG_NET_RETRY_COUNT) that
is available to tune the retries of the network stack.
Unfortunately, it is global to all protocols, and the value is
interpreted differently in all of them.

Add a new environment variable that directly sets the retry period for
BOOTP timeouts. If this new value is not set, the period is still derived
from the default number of retries, or from CONFIG_NET_RETRY_COUNT if
defined. When both the new variable is set and CONFIG_NET_RETRY_COUNT
is defined, the variable has precedence.

Signed-off-by: Alexandre Messier

net: Add bootfile in DHCP Request

2016-01-28T23:19:43+00:00

Add the bootfile name in the DHCP Request packet, in addition
to it already being sent in the DHCP Discover.

This is needed by some DHCP servers so that the bootfile name is
properly returned by the server to the client in the DHCP Ack, as
expected by U-Boot.

Signed-off-by: Alexandre Messier

net: bootp: Ignore packets whose yiaddr is 0

2016-01-28T18:22:23+00:00

When doing `dhcp`, there is a bad dhcp server in my network
which always reply dhcp request with yiaddr 0, which cause
uboot can not successfully get ipaddr from the good dhcp server.
But the Linux PC can get the ip address even if there is a bad
dhcp server. This patch is to fix that even if there is a bad
dhcp server, uboot can still get ipaddr and tftp work ok.

The way is to ignore the packets from the bad dhcp server by filtering
out the yiaddr whose value is 0.

Signed-off-by: Peng Fan 
Cc: Joe Hershberger 
Reviewed-by: Wolfgang Denk 
Acked-by: Joe Hershberger

net: parse DHCP options from overloaded file/sname fields

2015-10-29T19:05:45+00:00

If Option 52 in the vendor option field signals overloading
of the file and/or sname fields, these field may contain
additional options. Formatting of file/sname contained options
is the same as in the vendor options field, but without the
leading magic.

Signed-off-by: Stefan Brüns 
Acked-by: Joe Hershberger

net: Do not overwrite options found in overloaded 'file' field

2015-10-29T19:05:45+00:00

If 'file' is overloaded, it is wrong to get or put the bootfile name
from it/to it.

Signed-off-by: Stefan Brüns 
Acked-by: Joe Hershberger

net: cancel timeout handler after DHCPACK

2015-10-28T19:58:13+00:00

Timeout handler should be stopped after reception of DHCPACK. If "autoload"
is not set, the handler is immediately replaced by the TFTP handler,
otherwise it may trigger before the next boot stage begins.

Signed-off-by: Stefan Brüns 
Acked-by: Joe Hershberger

net: Fix parsing of Bootp/DHCP option 0 (Pad)

2015-10-28T19:56:20+00:00

Pad has no len byte, so the normal parsing code fails.

Signed-off-by: Stefan Brüns 
Acked-by: Joe Hershberger

net: send RFC1542 compliant value for bootp requests

2015-10-28T19:55:47+00:00

RFC1542, 3.2:
"The 'secs' field of a BOOTREQUEST message SHOULD represent the
elapsed time, in seconds, since the client sent its first BOOTREQUEST
message.  Note that this implies that the 'secs' field of the first
BOOTREQUEST message SHOULD be set to zero."

Signed-off-by: Stefan Brüns 
Acked-by: Joe Hershberger

net: reject Bootp/DHCP packets with bad OP value

2015-10-28T19:54:19+00:00

Rename check_packet to check_reply_packet to make its function more
obvious.
The check for DHCP_* values is completely off, as it should
compare against DHCP option 53 (Message Type). Only valid value for
any Bootp/DHCP reply is BOOTREPLY.

Signed-off-by: Stefan Brüns 
Acked-by: Joe Hershberger