-
Notifications
You must be signed in to change notification settings - Fork 181
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Debugging DHCP relay with netboot #71
Comments
Asked Huawei about it https://forum.huawei.com/enterprise/en/thread-464421-1-1.html This router bug ruins all my content plans about |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I've got a problem - Hiawei HG8245H router that doesn't forward DHCP packets. https://forums.whirlpool.net.au/archive/2281094 explains it well.
My network card doesn't event get IP from switch's DHCP server and I want to understand why. Is it because Huawei drops
DHCPDISCOVERY
with Option 60 set. Or is it because my network card expects something different. I would like to debug it withnetboot
utility.Even it
DHCP Relay
option in my switch does not work, there is still a menu with DHCP options and I'd like to try setting them as if the router supports PXE.Checking router.
DHCPDISCOVERY
request and check that standardDHCPDISCOVERY
reply is received (no option set)DHCPDISCOVERY+PXE
request and check what kind ofDHCPDISCOVERY
reply is returnedOptions 60
to router (no idea what the value should be) and repeatDHCPDISCOVERY
andDHCPDISCOVERY+PXE
to heck what kind ofDHCPDISCOVERY
reply is returned see if there is any difference from expected packets. For these tests it would be nice to automate what is expected.Checking client.
DHCPDISCOVERY+PXE
request and check the differences from standardDHCPDISCOVERY
reply - show if there any anomalies like options and show their numbers and values in hex and human readable formDHCPDISCOVERY+PXE
and send it againIt is just a start, and maybe I will be able to trick the router into booting it further.
The text was updated successfully, but these errors were encountered: