Follow-up Comment #8, bug #43396 (project grub):
Andrei, yes 10.13.13.254 is the relay and 10.22.11.1 is the DHCP server
itself. I've captured 'dhcp.pcap' on the DHCP server itself, the other capture
was made using a host on a mirrored port.
The 'rogue address' is indeed the relay, and AFAICT GRUB shouldn't even try to
talk to it - as I understand it, the gateway field giaddr (RFC 2131 describes
it as 'Relay agent IP address') is used so that the DHCP server can know which
network to use (which makes sense, how else can the server know which range to
use?)
It seems to me that the confusion is that in BOOTP, giaddr indeed was a
gateway IP address (at least, my quick scan of RFC 951 leads me to conclude
that). For DHCP, it is used for relaying and options are used to provide the
routers, as Vladimir also states.
I'd propose that a fix is to ignore giaddr in the DHCP case, as it is
meaningless to the client - yet, in the BOOTP case, traffic still shouldn't go
to the default gateway, but the client cannot know this because the network
mask isn't known...
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?43396>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-grub mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-grub
