The Wiert Corner – irregular stream of stuff

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

  • My work

  • My badges

  • Twitter Updates

    • G+ These are the command-line parameters I assembled to get close to “Ultra” compression from the 7-zip... 1 hour ago
    • Getting close to 7zip GUI “Ultra” compression from a batch file… 1 hour ago
    • RT @Nick_Craver: Nothing of what I planned to do today got done. Nothing. Nothing at all. But we kept the error count under 2.5 million beh… 8 hours ago
    • RT @kellabyte: I really don’t get the harsh criticism around Intel 3D XPoint. Yes they didn’t deliver persisted RAM. They did deliver 8x… 8 hours ago
    • G+ “Some managers just don’t recognize how profound the differences between their people are; others don’t... 9 hours ago
  • My Flickr Stream

  • Pages

  • All categories

  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 1,347 other followers

Buffalo WLAE-AG300N DHCP client is buggy and adds a NULL character to the host name.

Posted by jpluimers on 2016/05/13

Buffalo WLAE-AG300N is one of those buggy DHCP clients… Even running firmware Ver.1.85 (R1.05/B1.00)), it gets the length of the DHCP host name wrong so adds a bogus NULL byte to that name.

@Buffalo: please fix this.

The DHCP client options are of structure Type/Length/Value so a client is supposed to set the length of the hostname to exactly the number of characters.
However there exist buggy clients that either send a length of 1 more and a \00 at the end of the name, or send a fixed length and pad it with \00 as necessary.

Source: DHCP server: Odd active hostname behaviour: some views have null character at the end, some don’t. – MikroTik RouterOS

Fromt a packet capture:

Buffalo WLAE-AG300N gets the length of the DHCP name wrong and inserts an extra NULL character.

Buffalo WLAE-AG300N gets the length of the DHCP name wrong and inserts an extra NULL character.

This besides these devices also not automatically powering up when power goes out and comes back up

Mikrotik packet capture and viewing it in Wireshark

Anyway: getting and displaying the packet capture was quite easy:

  1. In Winbox (or from the console):
    1. Tools ->
    2. Packet Sniffer ->
    3.  General tab: set filename and file limit, then click Apply
    4. Filter tab: choose the interface, protocol (UDP) and port (67), then click Apply
    5. Click Start
    6. Wait for the DHCP refresh to happen
    7. Click Stop
  2. In Winbox (or from the console):
    1. Files -> Choose the captured file -> Download
  3. In your file manager, ensure the downloaded file gets the .pcap extension
  4. In Wireshark: load the .pcap file and inspect it



Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: