Hostname (standard PC-192-168-xxx-xxx)

blubb
Posts: 116
Joined: Mon Jun 22, 2015 5:35 am

Re: Hostname (standard PC-192-168-xxx-xxx)

Postby blubb » Wed Jul 01, 2015 5:51 pm

This is what we were afraid of. So the next question would be: Considering the market share of Windows based operating systems, do you plan to implement the protocol so that Windows users can access devices based on your hardware in a customer-friendly way, too?

ESP_Faye
Posts: 1646
Joined: Mon Oct 27, 2014 11:08 am

Re: Hostname (standard PC-192-168-xxx-xxx)

Postby ESP_Faye » Wed Jul 08, 2015 11:20 am

Hi,

We attach great importance to your suggestion.

It will be supported in next SDK.

Thanks for your interest in Espressif Systems and ESP8266 !

blubb
Posts: 116
Joined: Mon Jun 22, 2015 5:35 am

Re: Hostname (standard PC-192-168-xxx-xxx)

Postby blubb » Sun Jul 19, 2015 10:58 pm

Thanks. We're already looking forward to it! :)

blubb
Posts: 116
Joined: Mon Jun 22, 2015 5:35 am

Re: Hostname (standard PC-192-168-xxx-xxx)

Postby blubb » Wed Aug 12, 2015 8:33 pm

Hi, is the feature implemented in the new SDK 1.3.0? I could not find it in the change log.

ESP_Faye
Posts: 1646
Joined: Mon Oct 27, 2014 11:08 am

Re: Hostname (standard PC-192-168-xxx-xxx)

Postby ESP_Faye » Thu Aug 13, 2015 10:40 am

Hi,

Yes, have a try with the latest sdk_v1.3.0

If your problem is still unsolved, please feel free to let us know.

blubb
Posts: 116
Joined: Mon Jun 22, 2015 5:35 am

Re: Hostname (standard PC-192-168-xxx-xxx)

Postby blubb » Thu Aug 13, 2015 11:32 pm

Hmmm, no, the Windows 10 machine I'm currently sitting on cannot access the module by host name. Is there something I need to pay attention to? I'm setting the host name using wifi_station_set_hostname before wifi_station_dhcpc_start.

User avatar
kolban
Posts: 131
Joined: Tue Jun 16, 2015 1:09 pm
Location: Fort Worth, Texas, USA

Re: Hostname (standard PC-192-168-xxx-xxx)

Postby kolban » Fri Aug 14, 2015 1:58 am

What command are you issuing at the windows side to try and reach the ESP device by hostname? What is the full hostname address you are trying?

ESP_Faye
Posts: 1646
Joined: Mon Oct 27, 2014 11:08 am

Re: Hostname (standard PC-192-168-xxx-xxx)

Postby ESP_Faye » Fri Aug 14, 2015 4:18 pm

Hi,

So sorry for the inconvenience. I checked it with our engineer again, esp_iot_sdk_v1.3.0 did not add this optimization.

Here is a patch based on esp_iot_sdk_v1.3.0 to support this new feature.

Please replace it in folder "lib" and add definition below in espconn.h

Code: Select all

void espconn_nbns_init(void)


Call it after ESP8266 station connected to AP and got a IP address. For example,

Code: Select all

wifi_station_set_hostname("esp8266");
espconn_nbns_init();
Attachments
liblwip.a.zip
(102.74 KiB) Downloaded 385 times

blubb
Posts: 116
Joined: Mon Jun 22, 2015 5:35 am

Re: Hostname (standard PC-192-168-xxx-xxx)

Postby blubb » Fri Aug 14, 2015 6:17 pm

Hi Faye, thank you very much! I just tried it and, well, it *almost* works:

When I ping the ESP by host name, Windows tries to ping IP 168.0.135.0 which is not correct. The correct IP would be 192.168.0.135 in my case.
Looking at the IPs I think it was shifted by 1 byte accidentally! So this should be easy to fix if you look at your code.

blubb
Posts: 116
Joined: Mon Jun 22, 2015 5:35 am

Re: Hostname (standard PC-192-168-xxx-xxx)

Postby blubb » Sun Aug 16, 2015 10:00 pm

Could you also be a little more specific on when to call espconn_nbns_init() in our finished application?

- Do I need to call it every time ESP8266 got an IP?
- Do I need to call it every time I change the host name with wifi_station_set_hostname?
- Or is it enough calling it only once (in user_init() maybe)?

Who is online

Users browsing this forum: No registered users and 27 guests