This question will probably come across as very novice, but utlimately I'm trying to determine if a managed switch is required for how I'm trying to setup my basic home network. I am setting an up an ERLite 3 with my WAN coming into eth0, an unmanaged switch into eth1 and an AP AC Pro direct into eth2 (this is the part I'm unsure if I can actually do). I also have a UniFi Controller on the network managing the single AP, and it is able to manage it fine.

My question is whether a managed switch is required between the AP and ERLite to properly handle VLAN traffic between the router and AP. I have two SSIDs setup on the AP, each setup with their own VLAN. However, when I attempt to connect a device to either SSID, they fail to pull an IP. I have a DHCP server setup for each subnet and two VLANs on the eth2 port in the same subnet (on the ERLite).

I can provide a config as needed, but I figured I would ask to make sure if it's possible to directly hook the AP up to the ERLite, run two SSIDs with their own VLAN and them be able to get an IP for their appropriate VLAN / subnet from the router.

Hello all.

I have a fiber connection that authenticates via PPPoE with CenturyLink. I got the IPv4 portion of it working without issue.I would like to natively use v6 from my ISP rather than going through a tunnel broker like Hurricane Electric.

From what I have been reading, CenturyLInk uses IPv6 6RD rather than DHCPv6. I have seen some scattered documentation for getting an EdgeRouter to work on this, but I am still very new to Ubiquiti and relatively new to IPv6 in general. 

So I figured I would reach out to the community to just even find a starting point regarding this.

Thanks!

Hi all, I'm wearing my network admin hat today and I'm new to the Edge Router XFP

I got everything working great just using the wizards but now I've got one last piece of the puzzle

I need to be able to connect to an appliance with a static IP of 192.168.40.20 at port 4390 from the internet.

I set up a port forwarding rule and a rule to allow ping. 

Before testing from the internet I wanted to be sure I could connect to it from the LAN so I tried to ping it.

I got "Request Timed Out"

The appliance would reply on the old Linksys router but for some reason I can't ping it on this Edge Router.

I can ping the devices that are on the DHCP scope 192.168.2.20 - 30

Do I need to set up a DHCP scope with the static IP in it?

I'm wondering if I have missed something. The switch0 is set as 192.168.2.1/24

Thanks for any help. 

Hi all!

Juste got my new EdgeRouter 6P but i have some trubble with it. Ive set the router up with wizard WAN+2LAN2. After setup i get acess to internet thru port 1 and 2 but not on 3 and 4. Need these ports for 2 devices connected with ethernet. Anyone who can assist?

Thanks in advance.

/Dron

I've tried my best now i dont know what i missed in this config. 

i have 2 WAN, combining network from 2 different switch. 

I can ping to server at 192.168.2.59 and vlan gateway at 192.168.2.18 from IP range 99.x. However, server unable to ping my gateway at 99.x. anything that i missed in routing?

I tot 

I searched extensively so if I missed this somewhere, please forgive me if this is redundant. I searched the release notes and I haven't found the answer.

As of 1.10, the Vlan tab seems to be gone from the Interface Configuration UI for switch0. I'm not seeing an obvious replacement. I had it configured with several vlans and they are still operational. I looked in the config tree and they are listed in switch>switch0>switch-port>interface>ethX>vlan. Is this becoming a config-tree/cli only configuration option? or

I'm a newbie to configuring firewalls in Ubiquiti. Before commiting, it would give me great peace mind if someone could review my work. It would be greatly appreciated. I don't want to mess this up

I set up zones and followed the instructions from this page Ubiquiti EdgeRouter Lite Setup Part 2: Firewall Setup

The boot file is attached.

Brand new EdgeRouter. just upedated to v1.9.7.  Ran the WAN-2LAN2 wizzard.  I wanT to add eth5 to the LAN as a switch port.  Is ther a way to do this with the GUI?

New ER-X user, and I want to replace my old home router and RaspPi-based VPN solution (Softether) with it. I have the ER-X configured and installed, running 1.9.7, and have configured L2TP/IPSEC. I can open a VPN connection remotely and access my LAN, But I have a piece of radio equipment that uses broadcast packets for discovery, and this doesn't seem to work with the ER-X. It works fine with Softether, but that's on a Raspberry Pi using a single Ethernet port. I am not well versed in the ways of VPN, but I suspect this has something to do with the hardware architecture of the Edgerouter.

1. Is it possible to configured L2TP/IPSEC VPN on the ER-X to pass broadcast packets?

2. If not, is there any ER-X-based VPN solution that will do this?

Thanks for any help.

Regards,

Doug

I have a very old access point in my closet and there is no power there, but i need to get the line out to another structure in the back yard. The access point is already on a 100ft cable and it's powered via poe. I thought it would be so simple, I put a router in the closet and life goes on, but when I got the stuff organized, i realized I can't power a router because there is no outlet. So, I bought this edge X switch and I thought it does what I need it to. Power on with the cable from the old AP LR and pass it through enabling me to use that access point at 100ft and then I can put an additional wire into the ER X and put another 100 ft to the back yard structure. Is this possible? I received my ERX and it doesn't seem to do what I expect. I plug it into the poe from the AP, and it powers, but then it's not accessible. My main router is on 192.168.1.1, but I tried connecting directy into this with my wireless off at that address, and I even set my computer to 162.192.1.x and no luck. I tried 2 computers too... I can not access the router interface. I do not understand why this is happening, or why I can't find a phone number to call. What a downer. I am surrounded by cables and routers and nothing does anything.

Hello guys!
I've trying to find if this device has a ping watchdog feature but it seems i can't find one. Anyone can confirm if this has no feature for a watchdog?
Since this devices are installed high up in towers on remote location, i think these should have it. Its a must have feature!
Im experiencing disconnection issues with this and everytime it happens we have to travel 60km away just to reboot it...

https://help.ubnt.com/hc/en-us/articles/205231700-EdgeRouter-Destination-NAT

Following this guide to open port 443 on an internal server to select external IPs (work office, client office, and other locations where I sit away from home). Followed everything correctly on the stats page the counter for my WAN_IN https rule stays at 0. DNAT counter goes up though. 

Using an ERX on 1.10.0

Hi all,

I'm hoping someone here either has knowledge of setting up a bonded DSL connection (like with AAISP) or at least knows whether it's possible and how I'd go about doing so when the time comes.

I read that the EdgeRouter (mine being a Pro 8) supports ECMP which AAISP mention. Would it work for this kind of setup on this router, specifically being two DSL lines bonded both using the same public IP allocation (/29 for example)? My interest is in potentially near doubling the speed of my connection both downstream and upstream.

Hopefully the above makes sense, let me know .

Hello,

i'm configured 4 Vlan and 1 Guest Vlan, so  i want that Guest Vlan go straght to internet without any access to otherr Vlan.

I'm configured Firewall Ruleset and assign it to Switch0 / Accept, then rule for drop any traffic between Switch0.3 (vlan3 Guest)and

Switch0.5 (vlan5 Clients) for testing.... but nothing work...

I'm tested every possibility.. Switch0, 0.1, 0.3, Eth1, Eth2 it does not work.

Please Help. /Screenshot add.

Tander

PS

i was used search... but nothing found for solve this problem.

Hi all, I'm purchasing everything for my new home. I am going to be running an edgerouter x and want to have a separate vlan for my security cameras. My question is, do I need to use a managed switch for the vlan to work? I already have unmanaged gig switches, so don't want to buy an expensive managed if I don't have to. Thanks!

Hi,

New to UBNT and followed the documentation for advanced queues:

https://help.ubnt.com/hc/en-us/articles/220716608-EdgeRouter-Advanced-queue-CLI-examples

Whereafter I added new leafs and made sure it matched my LAN subnet (10.1.2.0/24):

show traffic-control output:

 advanced-queue {
     branch {
         queue 100 {
             bandwidth 12mbit
             description Upload
             parent 1
         }
         queue 200 {
             bandwidth 110mbit
             description Download
             parent 1
         }
     }
     filters {
         match 100 {
             attach-to 1
             description "WAN upload"
             ip {
                 source {
                     address 10.1.2.0/24
                 }
             }
             target 100
         }
         match 101 {
             application {
                 category File-Transfer
             }
             attach-to 100
             description "Low priority server traffic - File transfer"
             ip {
                 destination {
                     address 10.1.2.50/24
                 }
             }
             target 104
         }
         match 102 {
             application {
                 category Web
             }
             attach-to 100
             description "Low priority server traffic - Web"
             ip {
                 destination {
                     address 10.1.2.50/24
                 }
             }
             target 101
         }
         match 103 {
             application {
                 category P2P
             }
             attach-to 100
             description P2P
             target 102
         }
         match 104 {
             attach-to 100
             description Usenet
             ip {
                 source {
                     port 119,563
                 }
             }
             target 103
         }
         match 105 {
             attach-to 100
             description Plex
             ip {
                 source {
                     port 32400
                 }
             }
             target 105
         }
         match 106 {
             application {
                 category Web
             }
             attach-to 100
             description HTTP
             target 101
         }
         match 107 {
             application {
                 category Remote-Access-Terminals
             }
             attach-to 100
             description "Remote access terminals"
             target 107
         }
         match 108 {
             application {
                 category Streaming-Media
             }
             attach-to 100
             description "Streaming services"
             target 107
         }
         match 109 {
             application {
                 category Security-Update
             }
             attach-to 100
             description "Windows update"
             target 104
         }
         match 110 {
             attach-to 100
             description "Telnet / SSH"
             ip {
                 source {
                     port 21-22
                 }
             }
             target 108
         }
         match 111 {
             attach-to 100
             description DNS
             ip {
                 source {
                     port 53
                 }
             }
             target 101
         }
         match 112 {
             application {
                 category Games
             }
             attach-to 100
             description Games
             target 108
         }
         match 113 {
             attach-to 100
             description "Apple TV"
             ip {
                 destination {
                     address 10.1.2.52/24
                 }
             }
             target 107
         }
         match 114 {
             attach-to 100
             description "Torrent - PR"
             ip {
                 source {
                     port 9998-9999
                 }
             }
             target 101
         }
         match 115 {
             attach-to 100
             description "Torrent - automation"
             ip {
                 source {
                     port 19898-19899
                 }
             }
             target 101
         }
         match 200 {
             attach-to 1
             description "WAN download"
             ip {
                 destination {
                     address 10.1.2.0/24
                 }
             }
             target 200
         }
         match 201 {
             application {
                 category File-Transfer
             }
             attach-to 200
             description "Low priority server traffic - File transfer"
             ip {
                 source {
                     address 10.1.2.50/24
                 }
             }
             target 204
         }
         match 202 {
             application {
                 category Web
             }
             attach-to 200
             description "Low priority server traffic - Web"
             ip {
                 source {
                     address 10.1.2.50/24
                 }
             }
             target 204
         }
         match 203 {
             application {
                 category P2P
             }
             attach-to 200
             description P2P
             target 202
         }
         match 204 {
             attach-to 200
             description Usenet
             ip {
                 destination {
                     port 119,563
                 }
             }
             target 203
         }
         match 205 {
             attach-to 200
             description Plex
             ip {
                 destination {
                     port 32400
                 }
             }
             target 205
         }
         match 206 {
             application {
                 category Web
             }
             attach-to 200
             description HTTP
             target 206
         }
         match 207 {
             application {
                 category Remote-Access-Terminals
             }
             attach-to 200
             description "Remote access terminals"
             target 207
         }
         match 208 {
             application {
                 category Streaming-Media
             }
             attach-to 200
             description "Streaming services"
             target 207
         }
         match 209 {
             application {
                 category Security-Update
             }
             attach-to 200
             description "Windows update"
             target 204
         }
         match 210 {
             attach-to 200
             description "Telnet / SSH"
             ip {
                 destination {
                     port 21-22
                 }
             }
             target 208
         }
         match 211 {
             attach-to 200
             description DNS
             ip {
                 destination {
                     port 53
                 }
             }
             target 208
         }
         match 212 {
             application {
                 category Games
             }
             attach-to 200
             description Gaming
             target 208
         }
         match 213 {
             attach-to 200
             description AppleTv
             ip {
                 source {
                     address 10.1.2.52/24
                 }
             }
             target 207
         }
         match 214 {
             attach-to 200
             description "Torrent - PR"
             ip {
                 destination {
                     port 9998-9999
                 }
             }
             target 202
         }
         match 215 {
             attach-to 200
             description "Torrent - automation"
             ip {
                 destination {
                     port 19898-19899
                 }
             }
             target 201
         }
     }
     leaf {
         queue 101 {
             bandwidth 10mbit
             ceiling 12mbit
             description "Unmatched traffic"
             parent 100
             priority 3
             queue-type FQCODEL_UP
         }
         queue 102 {
             bandwidth 8mbit
             description "Bulk / P2P traffic"
             parent 100
             priority 0
             queue-type FQCODEL_UP
         }
         queue 103 {
             bandwidth 8mbit
             description Usenet
             parent 100
             priority 2
             queue-type FQCODEL_UP
         }
         queue 104 {
             bandwidth 8mbit
             ceiling 10mbit
             description "Low priority server traffic"
             parent 100
             priority 3
             queue-type FQCODEL_UP
         }
         queue 105 {
             bandwidth 12mbit
             description "Streaming servers (Plex)"
             parent 100
             priority 6
             queue-type FQCODEL_UP
         }
         queue 106 {
             bandwidth 10mbit
             ceiling 12mbit
             description HTTP
             parent 100
             priority 4
             queue-type FQCODEL_UP
         }
         queue 107 {
             bandwidth 12mbit
             description "Priority traffic"
             parent 100
             priority 6
             queue-type FQCODEL_UP
         }
         queue 108 {
             bandwidth 12mbit
             description "Low latency traffic"
             parent 100
             priority 7
             queue-type FQCODEL_UP
         }
         queue 201 {
             bandwidth 100mbit
             ceiling 110mbit
             description "Unmatched traffic"
             parent 200
             priority 3
             queue-type FQCODEL_DOWN
         }
         queue 202 {
             bandwidth 100mbit
             description "Bulk / P2P traffic"
             parent 200
             priority 0
             queue-type FQCODEL_DOWN
         }
         queue 203 {
             bandwidth 100mbit
             description Usenet
             parent 200
             priority 2
             queue-type FQCODEL_DOWN
         }
         queue 204 {
             bandwidth 100mbit
             description "Low priority server traffic"
             parent 200
             priority 3
             queue-type FQCODEL_DOWN
         }
         queue 205 {
             bandwidth 110mbit
             description "Streaming servers (Plex)"
             parent 200
             priority 6
             queue-type FQCODEL_DOWN
         }
         queue 206 {
             bandwidth 110mbit
             description HTTP
             parent 200
             priority 5
             queue-type FQCODEL_DOWN
         }
         queue 207 {
             bandwidth 110mbit
             description "Priority traffic"
             parent 200
             priority 6
             queue-type FQCODEL_DOWN
         }
         queue 208 {
             bandwidth 110mbit
             description "Low latency traffic"
             parent 200
             priority 7
             queue-type FQCODEL_DOWN
         }
     }
     queue-type {
         fq-codel FQCODEL_DOWN {
             ecn disable
         }
         fq-codel FQCODEL_UP {
             ecn disable
         }
     }
     root {
         queue 1 {
             attach-to global
             bandwidth 132mbit
         }
     }
 }

Now the problem is that nothing seems to get into those queues, tried to set a limit of 10mbit at the download branch or leaves and line still maxed out at 120mbit.

This on a ER-6P with latest firmware (1.10) with ETH0 as WAN and ETH1-5 bridged into LAN, any idea what I'm doing wrong here?

Hi,

I cant get port forwarding working.  I'm trying to set it up so I can access my Synology NAS.

I've attached my config for your reference.

Thanks,

Hi everyone. 

New here so i need some answers to a config i need, but please, explanations to be for a dummy, I’m a noob at this. 

I’m currently in need to load balance two wan connections comming into my home, one is an adsl pppoe connection, and another is a link comming in via a WISP, running through a Edgerouter X. 

Now i’ve been able to load balance these two, but i need some fine tuning. 

ADSL is a 20down/1up connections

WISP is a 15down/10up connection

my idea is to combine the two incomming connections as one big 35down trunk, but then route all outgoing traffic over the WISP 10up connection. 

How do i configure this, would be nice that is anyone one of the two fail, all traffic goes over the other. But this is not a priority. 

thanks in advanced. 

Hi everyone. 

New here so i need some answers to a config i need, but please, explanations to be for a dummy, I’m a noob at this. 

I’m currently in need to load balance two wan connections comming into my home, one is an adsl pppoe connection, and another is a link comming in via a WISP, running through a Edgerouter X. 

Now i’ve been able to load balance these two, but i need some fine tuning. 

ADSL is a 20down/1up connections

WISP is a 15down/10up connection

my idea is to combine the two incomming connections as one big 35down trunk, but then route all outgoing traffic over the WISP 10up connection. 

How do i configure this, would be nice that is anyone one of the two fail, all traffic goes over the other. But this is not a priority. 

thanks in advanced.