*** Official Ubiquiti Discussion Thread ***

Mine is in PPPoE mode but the issue is that to access the web interface to get at the stats the USG doesn't play nicely. I think it doesn't like an RFC1918 address on the WAN interface but as yet I haven't found a way to get things working as I want.
 
The Vigor 130 maintains the web UI on 192.168.2.1, so if you can add another address to your WAN interface of the USG and set it to NAT outside then you should be able to access the UI still. If you can set a default gateway on the LAN settings for the 130 then you won't need to NAT (I have a stack of 130s at work but can't check right now).

The above should be doable on the EdgeRouter, I don't know how many settings are exposed on the USG or whether you can send supplemental CLI commands as part of the config. If you can then I would add baby jumbos to the list as the 130 and EdgeRouter platforms definitely both support those.
 
Last edited:
Caged said:
If you can set a default gateway on the LAN settings for the 130
Click to expand...

Bingo. Why didn't I think of that?

You can't set a gateway through the web UI but you can set a static route through the telnet interface. So I've added a route to my address space via the USG and can now reach the Vigor 130 web interface from the LAN.

Next I need to work out how to set a static IP on the WAN interface on the USG without having to do it at the command line. The USG checks in with the controller periodically so about 5-10 minutes after setting the IP address in teh CLI it'll be removed.

The USG uses the same CLI structure as the ERL so I just need to to generate a config.gateway.json file and put it in the relevant place on the controller. I also need to check if the static route on the Vigor 130 is persistent or not so I'll reboot it later and see.
 
I have lost count of the number of times I set up routing to send packets one way and then completely forget that the replies have to get back somehow.
 
Well we had a power cut last night and after that 2 x UniFi AP-AC-Lite's and 4 ports (1-4) on my UniFi Switch 8 POE-150W seem to be toast :(

If I plug a laptop into ports 1-4 I get nothing, no link light.

If I plug the AP-AC-Lite's into a Ubiquiti POE injector the don't boot
 
It's a known issue with certain models, you can get all the kit replaced:

https://community.ubnt.com/t5/UniFi...with-UniFi-Switch-on-PoE/m-p/1592375#U1592375

the-evaluator said:
Bingo. Why didn't I think of that?

You can't set a gateway through the web UI but you can set a static route through the telnet interface. So I've added a route to my address space via the USG and can now reach the Vigor 130 web interface from the LAN.

Next I need to work out how to set a static IP on the WAN interface on the USG without having to do it at the command line. The USG checks in with the controller periodically so about 5-10 minutes after setting the IP address in teh CLI it'll be removed.

The USG uses the same CLI structure as the ERL so I just need to to generate a config.gateway.json file and put it in the relevant place on the controller. I also need to check if the static route on the Vigor 130 is persistent or not so I'll reboot it later and see.
Click to expand...

I have set my Vigor 130 up today on the WAN side of my EdgeRouter Lite. Added an IP in the 192.168.2.0/24 range to eth0, added a static route for 0.0.0.0 0.0.0.0 with the gateway of 192.168.2.2 to the Vigor 130, and I could ping from the LAN to the modem. What I can't do is hit the web UI - it just times out. I can run curl 192.168.2.1 on the ER-L and I get the HTML from the login page, so the web server is working.

Did you need to do anything else to get the web UI appearing inside your LAN? There are no firewall rules in place on the ER-L as far as I can tell.
 
Last edited:
Caged said:
I have set my Vigor 130 up today on the WAN side of my EdgeRouter Lite. Added an IP in the 192.168.2.0/24 range to eth0, added a static route for 0.0.0.0 0.0.0.0 with the gateway of 192.168.2.2 to the Vigor 130, and I could ping from the LAN to the modem. What I can't do is hit the web UI - it just times out. I can run curl 192.168.2.1 on the ER-L and I get the HTML from the login page, so the web server is working.

Did you need to do anything else to get the web UI appearing inside your LAN? There are no firewall rules in place on the ER-L as far as I can tell.
Click to expand...

The only thing I did differently was that I added a static on the Vigor 130 to just my LAN address space but I don't see why using 0.0.0.0 would make any difference especially as you can ping the modem from the LAN.
 
I had my RT-N66U talking to my 130 so I could access the 130 from my LAN address space. I can't remember what I did to get it to work, may boot it up and look but I think I added a static route, odd as the eth0 to 130 interface is directly connected so not sure how a static route would have helped.
 
the-evaluator said:
The static route is needed so that the 130 can route traffic to the LAN address space using eth0 as the next hop.
Click to expand...

That's implying a static route on the Vigor 130 and not the Edgerouter, I'm 90% sure the config I did was on the RT-N66U. Let me have a google, I'm sure I found a thread on it somewhere.

Edit, pretty sure this is what I followed and I have it set the same on the ER-L - perhaps it's firewall rules.

https://github.com/RMerl/asuswrt-merlin/wiki/Access-modem-Web-UI-on-WAN-port-(no-script)
 
the-evaluator said:
The only thing I did differently was that I added a static on the Vigor 130 to just my LAN address space but I don't see why using 0.0.0.0 would make any difference especially as you can ping the modem from the LAN.
Click to expand...

I'll try being more specific with the route, but yeah I'm confused as it pings fine.
 
Caged said:
I'll try being more specific with the route, but yeah I'm confused as it pings fine.
Click to expand...

That's my confusion as well. I don't think I have done anything different between the RT-N66U config and that on the ER-L which leads me to assume it's a firewall issue. But I haven't properly looked into it, I was out drinking most of the bank holiday weekend. :p
 
HEADRAT said:
Just had a response authorizing my RMAs, only problem is I have to RMA back to:

RMA Dept. (RM96477)
Ubiquiti Networks
2580 Orchard Parkway
San Jose, CA 95131
Click to expand...


Surely you should be able to deal with the shop you purchased from in the UK to arrange replacement as it's a manufacturing defect.
 
That's exactly what I'm doing now,I just didn't realize that RMA would be back Ubiquiti in the USA.

I guess I'm a little disappointed that they don't have a RMA handler in the UK. (well apart from the shop I purchased from in the UK) ;)
 
Last edited:
The RMA has been approved on the serial numbers you have given them so I see no reason why the reseller would have a problem with handling the return for you - they aren't going to lose out other than in terms of time and shipping, and see that as the cost of business.
 
You must log in or register to reply here.
Back
Top Bottom