How to enable Lan port on GL-AR300M?

wacnstac · 2019-07-23T02:35:33.058Z

I have a screen that looks quite similar to the first one that you displayed, but I have no Network->Switch on my menu.

limbot · 2019-07-23T02:55:41.687Z

You need to get to the luci interface.

On firmware 3.x it’s Settings-Advanced but don’t know how on 2.x (can’t find doco). Try going to 192.168.8.1/cgi-bin/luci which may bring you to the luci screen. Just login with root and your normal password (sorry never used firmware 2. 0)

limbot · 2019-07-23T03:07:24.804Z

What happens if you click advanced settings top right?

x921×698 63.6 KB

(or as per the screen shot press the reset button for 10 seconds and hard reset so you can eliminate the config )

wacnstac · 2019-07-23T03:09:38.794Z

I’m into the Luci settings but I have no Network->Switch on my menu.

image1080×1920 300 KB

limbot · 2019-07-23T03:20:48.618Z

Ok could be the older version or a difference on the AR300m. Sorry but my initial recommendation still holds. Either reset on current firmware or upgrade and reset.

This will eliminate the config as the issue and point potentially to a hardware fault.

wacnstac · 2019-07-23T03:25:58.405Z

Just what exactly would you have me try once I reset the currently settings?

jeffsf · 2019-07-23T03:46:25.899Z

OK, thanks for the great illustration. I’ll look up the Mobley as I’m not familiar with how its providing IP connectivity over USB yet.

Configuration of the TP-Link device looks “right” and the GL-AR300M is probably right, depending on how the Mobley connects – just looks to be a question of getting the Mobley and its routing straightened out.

Edit:

The Mobley looks to be a ZTE-made, OBD-plug device that gets power over a USB adapter, or is it providing packet connectivity over USB?

Would you post the relevant sections of your /etc/config/network (or PM them, if you’re not comfortable posting them)?

limbot · 2019-07-23T03:47:53.114Z

Sadly, it’s a process of elimination to work out the issue:

Updating the firmware to the latest, not only gives you all the new functionality in the 3.x but also eliminates the old firmware as an issue
Resetting the device eliminates a configuration issue in the AR300m causing the problem

Once you’ve upgraded and reset do the initial setup of the AR300m ( Language and password)
Plug in your modem and setup the tethering
Plug a device into the LAN port and see if you’ve got internetz
Connect to the WiFi and see if you’ve got internetz

If you haven’t on the LAN then there’s a high certainty that there’s a fault with the LAN port assuming cable and device are fine and also the Mobley are not an issue.

I’m basically just going through the steps I’d go through to diagnose .

Hopefully between that and Jeffsf’s suggestions

@jeffsf given how the mobley is normally powered via a car I’d assume it’s maybe 12V normally . Possible that the USB to Mobley adapter is drawing too much power for the ar300m to handle (assuming this is what @wacnstac is using) and stuffing the LAN port signalling?
" * May not be compatible with low output (mA) USB power sources like some smaller power banks or USB chargers"

wacnstac · 2019-07-23T13:05:23.275Z

The Mobley gets its power from an ODB II adapter not the USB (I am definitely providing it 12volts seperate from USB). It provides the connectivity over USB to the AR300M.

What device do you want the /etc/config/network stuff from and what is relevant? I hope if is from the AR300M as I don’t know if I can get that from the Mobley.

jeffsf · 2019-07-23T16:57:20.391Z

Yes, from the GL-AR300M – how the interface to the Mobley is defined, especially the driver, protocols, and addressing involved.

My current thought is that you’ll need to have the GL-AR300M’s WAN be a client of the Mobley’s DHCP and use NAT, as I think I read that there is a five-device limit on the Mobley.

wacnstac · 2019-07-23T18:49:54.328Z

There is definitely a 5 device limit on the number of wireless devices that you can hang off the Mobley but what I don’t know is if this extends to the Mobley’s DHCP handing out IP addresses.

I will get you the /etc/config/network from the AR300M, but don’t know how much more information I can get you on the Mobley.

jeffsf · 2019-07-23T18:54:07.497Z

In the mean time, consider setting up the WAN interface as DHCP with however you’re connecting to the Mobly. Since it’s handing out on 192.168.1.1/24 and the GL-AR300M is handing out on 192.168.8.1/24, there shouldn’t be a conflict. “Double NAT” isn’t great, but if your looking for general Internet access, it should work well enough for you. (Likely no way to get rid of double NAT without being subject to the five-device limit.)

wacnstac · 2019-07-23T19:16:38.607Z

Jeffsf, I’m not sure if I understand what you mean with “setting up the WAN interface as DHCP”. The connection to the Mobly is done through a USB port between the Mobly and the AR300M and is governed by the settings under Internet_Settings->3/4G on the AR300M.

jeffsf · 2019-07-23T20:33:57.717Z

wacnstac:

what you mean with “setting up the WAN interface as DHCP”.

That is the information I’m looking for from /etc/network/config – how it appears there. Basically I think you need to configure the connection to the Mobly so that it becomes your upstream connectivity, including the firewall rules (with NAT) that would normally be on the “WAN” interface/zone.

wacnstac · 2019-07-23T23:38:20.380Z

Ok, need a little more help. I was able to SSH into the AR300M, but when I get to /etc/config it won’t allow be do cd network. I get an error “cd: can’t cd to network”. What do I have to do?

It seems I don’t have permissions to view that directory. Don’t know how to login as su.

jeffsf · 2019-07-24T00:42:19.569Z

/etc/config/network is a file. cat /etc/config/network or less /etc/config/network so you can copy and then paste into a post using the preformatted button </>

wacnstac · 2019-07-24T00:57:50.165Z

/etc/config# less network

config interface ‘loopback’

option ifname ‘lo’

option proto ‘static’

option ipaddr ‘127.0.0.1’

option netmask ‘255.0.0.0’

config globals ‘globals’

option ula_prefix ‘fdc4:6cf5:7afc::/48’

config interface ‘lan’

option ifname ‘eth1’

option force_link ‘1’

option type ‘bridge’

option proto ‘static’

option netmask ‘255.255.255.0’

option ip6assign ‘60’

option hostname ‘GL-AR300M-7b9’

option ipaddr ‘192.168.8.1’

config interface ‘wan’

option ifname ‘eth0’

option hostname ‘GL-AR300M-7b9’

network

On another note. I took the ar300m as is and disconnected from Mobley. Hooked wan into a lan port on my main home router, then hooked a laptop up to the lan port of the ar300m and still couldn’t get anything out of it but my main home router does Id the ar300 as a client. Could be that I need to turn off dhcp on the ar300…

wacnstac · 2019-07-25T14:34:30.567Z

@jeffsf do you need any more information?

jeffsf · 2019-07-25T15:41:19.777Z

That only looks like the first few lines of the file. (Also, the preformat button, </> makes code/output a lot easier to read.)

wacnstac · 2019-07-28T19:14:58.976Z

@jeffsf, sorry was on vacation. Hopefully this is everything you need out of that file. @limbot, I may try the firmware upgrade as well depending on how far I get today.

root@OutInTheSticks:/etc/config# cat network

config interface 'loopback'
  option ifname 'lo'
  option proto 'static'
  option ipaddr '127.0.0.1'
  option netmask '255.0.0.0'

config globals 'globals'
  option ula_prefix 'fdc4:6cf5:7afc::/48'

config interface 'lan'
  option ifname 'eth1'
  option force_link '1'
  option type 'bridge'
  option proto 'static'
  option netmask '255.255.255.0'
  option ip6assign '60'
  option hostname 'GL-AR300M-7b9'
  option ipaddr '192.168.8.1'

config interface 'wan'
  option ifname 'eth0'
  option hostname 'GL-AR300M-7b9'
  option metric '10'
  option peerdns '0'
  option proto 'static'
  option ipaddr '192.168.1.42'
  option netmask '255.255.255.0'
  option gateway '192.168.1.1'
  option dns '8.8.8.8'

config interface 'wan6'
  option ifname 'eth0'
  option proto 'dhcpv6'

config interface 'wwan'
  option proto 'dhcp'
  option metric '20'
  option peerdns '0'
  option dns '8.8.8.8 8.8.4.4'

config interface 'modem'
  option proto '3g'
  option ifname '3g-modem'
  option device '/dev/ttyUSB2'
  option country 'country73'
  option sp 'isp0'
  option service 'umts'
  option dialnum '*99#'
  option apn 'broadband'
  option metric '40'
  option peerdns '0'
  option dns '8.8.8.8 8.8.4.4'