Odd, no-critical issue

All about the standard Meteobridge devices based on mobile routers from TP-Link, D-Link, ASUS

Moderator: Mattk

Post Reply
xannor
Junior Boarder
Junior Boarder
Posts: 27
Joined: Sat Aug 03, 2019 4:20 am

Odd, no-critical issue

Post by xannor »

I was working with my network setup today and removed the fixed ip from my dhcp server (I have the meteobridge working by name just fine.) When I did this the gw1000 went back to its default name of ESP_{MAC tail} instead of what I had previously called it. If used that name in the meteobridge it would say it could not resolve the device, but it reported it was trying to resolve ESP {MAC tail}, with no "_" in the messages log. I could ssh into the meteobridge and ping the device properly so it was resolvable. I just added an alias to my dns setup for the meanitme point to the old name and everything is fine, just thoguht it was odd that is could not resolve and did not show the underscore in the messages log. The underscore did show on the weatherstations page.

As I said this is non critical since I can work around it, but I thought I should bring it to your attention.
User avatar
galfert
Platinum Boarder
Platinum Boarder
Posts: 326
Joined: Sun Jun 24, 2018 10:31 pm
Location: Orlando, FL

Re: Odd, no-critical issue

Post by galfert »

Underscore in a host name is not a good practice.

https://en.m.wikipedia.org/wiki/Hostname#Syntax

I realize you can't change the default hostname. So perhaps rather than getting Meteobridge to accept the underscore, instead Ecowitt should change the hostname to not use the underscore.
Meteobridge RPI | GW1000
Post Reply