You are here

GL.Inet AR-150

27 posts / 0 new
Last post
kc0ode
GL.Inet AR-150

Last night I upgraded my AR-150 to firmware 1307 from, I believe, firmware 1234. Now for the life of me, I can not get it to pull a WAN IP. I can connect to it just fine from the LAN side, but not when connected my main router that supplies the WAN IP. It worked until I did the upgrade. I would revert it back to the previous (working firmware), but can't find the copy that I originally downloaded. Thoughts/suggestions? A link to previous firmware?

N7JYS
Nightly build 1326-c0bac78

As of 02/12/20 nightly build 1326-c0bac78 , i am not able to get a tunnel client activated with the proper credentials on my newest Gl-Inet AR-150.
 My first AR-150 is running 1101-ad0aaf-gl-150 with no issues. Running the newest nightly build will not allow me to downgrade to and older version or a factory .bin file. 
Eric

AE6XE
AE6XE's picture
Be sure to install today's

Be sure to install today's nightly build, which fixed an issue with tunnel compatibility with prior releases.

need a support data file, link at bottom of admin page to look over.  Otherwise, little hope of discovering what the issue is.

joe AE6XE

N7JYS
Data File

Joe, What kind of data file are you looking for  and how to obtain this file. I'll help any way i can. 

Eric

AE6XE
AE6XE's picture
See support Data section here
N7JYS
Tunnel Client

Joe, one thing I did discovered is the tunnel client is active only when the mesh rf mode is selected. If I unselect this mode and select the part 15 lan wireless mode, I can no longer get an active tunnel client. This is only happing on my newest GL AR-150 with the lastest nightly build. 


Eric

AE6XE
AE6XE's picture
This is the expected behavior
This is the expected behavior if the WAN is not accessible directly on the AR150.   With mesh RF on, the auto routing will find an internet gateway across the mesh network and still make a tunnel connection over the internet.  This is not something anyone should do by design, loading RF links up with tunnel traffic.   All tunnels should be on devices with direct access to the internet.   
N7JYS
Reply to #7

Yes it would be pointless to be running a tunnel when your are close enough to be connected via mesh rf.
I like the AR-150 because I can use is as a part 15 gateway while pluged into internet,  running a tunnel to have access to all other mesh networks.
It didnt make since to have the tunnel client work while the mesh network is being selected and not the lan part 15 device. Something in the logic when switching between modes got left out preventing the tunnel for working. However with that said, My first AR150  running  1101-ad0caaf, can run a active tunnel client no mater which mode is slected.  Maybe this is what was being changed in the update but they got the logic backards. Just my 2 cents.

Eric

nc8q
nc8q's picture
GL.Inet AR-150

kc0ode: "I can not get it to pull a WAN IP"

This will be a 'deal breaker' or me.
I operate remote often, using a tunnel to my home station.
Losing WAN access while so would be a huge loss.
I operate my home station remotely using my AR-150; WSJTX-FT8.
Would this be impacted with the loss of WAN?

I was thrilled with the NBs through 1234. Now I am afraid to try 1326.

ae6xe 2/14/2020: "Be sure to install today's nightly build, which fixed an issue with tunnel compatibility with prior releases."

I was expecting to see a NB =>1327 dated 2/15 or later. I still find 1326 dated 2/12 in the NB pages.
?

Chuck

AE6XE
AE6XE's picture
Chuck,  1326 has the fix for

Chuck,  1326 has the fix for tunnel compatibility, it is good to go.   I need a support data file to find what is wrong with the configuration settings (when the WAN is not getting an IP address).  

Joe AE6XE

nc8q
nc8q's picture
GL-iNet-AR150 and NB 1326 and WAN and tunnel.

Disabled tunnel, keeping settings, upgraded to 1326, reloaded tunnel apk, enabled tunnel.
WAN working. Tunnel working.
:-)
No need to upload support data file.

Joe: Thanks.

Chuck

kc0ode
Through some techno wizardry

Through some techno wizardry (and finding a friend who also has an AR150 and had saved his copies of the previous builds), I was able to revert my AR150 to firmware 1190. I fully set it up and tested it (WAN IP address obtained), as well as downloaded the support data files. I then upgraded it to the new nightly build, 1336, and once again, it would not obtain an IP address for the WAN. The unit was not moved during upgrade, so nothing should have changed during the upgrade. 

Mesh RF is disabled, wireless LAN is enabled. WAN port plugged into router, LAN port plugged into a spare computer (for setup purposes). I can connect to the Wireless LAN as well.

I have both support files, do I upload them to this thread, or somewhere else?

 

AE6XE
AE6XE's picture
upload the support files on

upload the support files on this thread.

Joe

kc0ode
Support files

Support files

Support File Attachments: 
AE6XE
AE6XE's picture
Yes, definitely something has

Yes, definitely something has not been setup correctly for the WAN interface.   Are you able to upload back here the file /etc/board.json from 1339?    Something didn't get created on first boot correctly in this file.  (been meaning to include in the support data...)

Joe

kc0ode
You'll have to change the

You'll have to change the name and delete the .TGZ

Support File Attachments: 
AE6XE
AE6XE's picture
I found the root cause. 

I found the root cause.  Looks like someone upstream with OpenWrt accidently removed a definition.   I'll see if I can get a fix into tonight's build.

Thanks for persisting though to help find these issues.   We're in a period of time to ensure we all have confidence in the nightly build to do a release.  We just added a notch of confidence :) . 

Joe AE6XE

kc0ode
Thank You!

You're welcome and thank you for seeing about getting a fix in to tonight's build. It's been a pleasure working with you.

Seth

AE6XE
AE6XE's picture
Seth,  can you please try

Seth,  can you please try this image to confirm it works.  Capture a support dump and upload regardless.

https://drive.google.com/file/d/1vAfIGBgZwyHCZCpgIW7GbFHibSLMnZ9O/view?u...

Chuck NC8Q, if this worked for you, it was likely because you had a port connected to your switch.  It had a default setting and one port had all the vlans defined, the 2nd port was not configured.

Joe AE6XE

nc8q
nc8q's picture
likely because you had a port connected to your switch

Hi, Joe:

 Thanks.

 This is my typical remote tunnel 22 miles from home:
A GL-AR150 to local WiFi router connected to cable modem.
I tunnel home to a Nano loco M2 configured as an Access Point.
The only switch here at the remote location is the WiFi router.
The Nano loco M2 at home is DtD'ed to a GS-108Ev2 ( 1 WAN, 3 NODE, 4 LAN).

 I am attaching a then and now data_download in case it is of some value to you.



 

AE6XE
AE6XE's picture
Chuck,  the config is setup

Chuck,  the config is setup using the 5GHz wifi client to get access to the internet.  Going to hard cable, would not work. 

Joe AE6XE

N7JYS
Tunnel Server

Joe just downloaded and installed your file https://drive.google.com/file/d/1vAfIGBgZwyHCZCpgIW7GbFHibSLMnZ9O/view?u...
The only thing i see wrong was it would not allow me to install a tunnel server. Keeps giving me an error.


Eric

Support File Attachments: 
kc0ode
It appears that everything is

It appears that everything is working as my node is pulling a WAN IP again.

As for the tunneling not working, I'm guessing that's because the tunneling software version doesn't match the firmware version.

kc0ode
Here's my support file

Here's my support file

Support File Attachments: 
AE6XE
AE6XE's picture
The tunnel packages won't

The tunnel packages won't install.   it is trying to pull from the current nightly build, and signatures don't match.   Check for a new image tomorrow.

Joe AE6XE

kc0ode
IT WORKS

Joe,

Thank you for the help! My AR150 is work and the tunnel is connecting again!

Seth

N7JYS
It LIVES!!

Thanks you JOE!

NB-1347 is a big success! All is working on the AR-150.

Eric

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer