Eudimorphodon
Veteran Member
Man, this is sure getting sour over a thing that‘s barely even a cosmetic problem. What application is this actually causing a problem with?
Isn't that exactly what you did with the OP in this thread? "that kind of assumes your DHCP and DNS are working correctly. Your router isn't quite there"
In the thread where we discussed this on vogons you were already angling toward that conclusion with me.
It isn't, at least not for me. My only interest in reporting the bug was to help improve the product. Mike and I may not be soul sisters but he makes a tool that is exceedingly valuable to the community writ large. Trace attachedMan, this is sure getting sour over a thing that‘s barely even a cosmetic problem. What application is this actually causing a problem with?
It's not purely cosmetic. The issue would be very real if you actually need to use the host name on your network, because the DHCP client purges the hostname directive from the configuration file after the first DHCP request. Therefore your requested host name will only be honoured by the router the very first time you run the DHCP client. Every execution thereafter (I assume most users put DHCP in their AUTOEXEC.BAT) will result in the client requesting the default host name of DOSRULES.barely even a cosmetic problem
It's not purely cosmetic. The issue would be very real if you actually need to use the host name on your network, because the DHCP client purges the hostname directive from the configuration file after the first DHCP request. Therefore your requested host name will only be honoured by the router the very first time you run the DHCP client. Every execution thereafter (I assume most users put DHCP in their AUTOEXEC.BAT) will result in the client requesting the default host name of DOSRULES.
Looks about the same. Can you give me the specific Netgear model?
Did the older versions of mTCP wipe out the "hostname" if it didn't get a response or is that new behavior just for this version? If it's the latter would an acceptable workaround for now to be just use the DHCP binary from an older distribution?
Host Name: TURBO10 Device Type: -- IP Address: 192.168.1.125 MAC Address: 00:00:4d:11:68:51 Device Status: Online Port Type: ETH Port ID: LAN1 Online Duration: 0 hour 0 minute IP Acquisition Mode: DHCP Remaining Lease Time: 28570(s)
Thanks, tested on a different DOS computer. (I am rotating them, so none of them rests forever). This one is Turbo XT 10MHz
I got this:
Warning: Your DHCP server may not have honored your hostname request.
Requested hostname: "TURBO10", Assigned hostname: ""
Hostname was not wiped out form tcp.cfg.
Huawei router says this: