You are here

Issue with Nightly Build Firmware

9 posts / 0 new
Last post
AC2OG
AC2OG's picture
Issue with Nightly Build Firmware

Hello,
to connect with the aredn tunnel server I have been requested to install a Nightly Build Firmware.
After some days of using the nightly Built Release "aredn-1601-d06bbaa-ath79-ubnt_bullet-m-sysupgrade.bin" I report the following problems:
A). I can’t connect to my node with http://localnode:8080 but only with the IP address. When I try to connect with "localnode:8080" I get this error message:
"not possible to find the IP address of the local node server. DNS_PROBE_FINISHED_NXDOMAIN.".
B).In the section: <Port Forwarding, DHCP, and services/Current DHCP leases>  there is the message: “There are no active leases” even if the services are connected and the new ones are not displayed.
 After some hours and several re-boot or power off/on the problem is solved.
Shall I come back to the previous firmware version: 3.20.3.0
If so, am I going to lose the link with your tunnel server?
 
Thanks for suggestions.

AE6XE
AE6XE's picture
AC2OG,   

AC2OG,   

can you provide a picture of the forest of your setup?   To have a tunnel client on a Bullet would necessitate that you also have a an 802.1Q switch configured?   There are no other reports of these symptoms, consequently this suggests there is something local going on.    If your laptop is not obtaining an IP address or obtaining the DNS settings from the mesh node, as the error suggests, have you pulled the cat5 cable for 15 seconds and then plugged back in, does this resolve the issue if it occurs again?  

Joe AE6XE

AC2OG
AC2OG's picture
Nightly Build firmware.

Hello Joe,
I have a smart switch configured with VLANs with a  WAN port to the main router configured for my ISP provider.
Please pay attention to the fact that my bullet, with the previous firmware version 3.20.3.0, was working well. The problem raised when I uploaded the Nightly Build Version and it happens when I reboot the node. As I reported in my post, the issue is resolved after 2 or 3 power cycles. 
 

AE6XE
AE6XE's picture
The preference is to use the

The preference is to use the nightly build image to have the same OLSR settings as the tunnel server -- specifically that the  OLSR "mode Ethernet" setting is applied to tunnel interfaces.   You could roll back to 3.20.3.0 and manually apply this setting or use the nightly build image with the workaround reboots to get use.

I don't have a bullet available for the moment to try to reproduce, but maybe others in the community are able, and can help to isolate a root cause.   I'll need further data when the condition exists to find a root cause:   support data download, client network and DNS settings.  tcpdump packet captured when the device tried to acquire an IP address and DNS settings, etc.

Joe AE6XE

AC2OG
AC2OG's picture
Nightly Build Firmware

Hi Joe,

during a recent reboot the issue condition happened again. I downloaded the supportdata that I uploaded.

Support File Attachments: 
AE6XE
AE6XE's picture
I don't see any red flags in

I don't see any red flags in this data.  Let's turn attention to the client side.     Windows?  Linux?    Please try the link http://localnode.local.mesh:8080 .  If windows, it is possible for there to be policies or domain search path settings that will require a FQDN, short names will fail (I have a laptop in this boat).   Please attach back these settings, assuming windows "ipconfig /all" 

Joe AE6XE

AC2OG
AC2OG's picture
Nightly Build firmware.

The client is a laptop Lenovo Edge E530c running Windows 7 pro. Next time it will happen I'll try with the link you have suggested.
By the way please see attached info of my network
Thanks Joe.

AE6XE
AE6XE's picture
On a side issue... I know

On a side issue... I know that windows 7 is a beloved and known operating system and you're not the only one still using on the mesh network.   

Unfortunately, Microsoft stopped supporting this OS in Jan 2020.    Windows 7 devices are becoming virus honey pots over time, as they fall father out of date with new vulnerabilities found every day.    This increases risk of infection and turning into a platform to attack the networks it is connected and propagate the infection.   It is best to stay current with all OS/application patches and Anti-virus updates.

Joe AE6XE

AC2OG
AC2OG's picture
Thanks, Joe, I'll do it.

Thanks, Joe, I'll do it.

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer