wrote: […], any recommendations for a replacement? […]
Apologies for the late reply. I just searched for a generic power supply with the same specifications.
↧
Re: ERL Power supplies failing
↧
Re: ERL Power supplies failing
Ubiquiti hasn't done anything about this issue that I know of. I even shipped 2 power supplies to Taiwan or somewhere in Asia for them to look at but I have never heard anything back from them. We are still currently using the ERL for installs, but we no longer use the power supply that comes with the ERL. We just use one we found on Amazon for $5.
Its disappointing that they never acknowledged the issue or did anything to fix it.
We are probably going to move to the ER10x once we are out of our current stock of ERLs. The 10x comes with a totally different power supply.
Its disappointing that they never acknowledged the issue or did anything to fix it.
We are probably going to move to the ER10x once we are out of our current stock of ERLs. The 10x comes with a totally different power supply.
↧
↧
Re: ERL Power supplies failing
Kinda crappy they won't acknowledge it. What have you had success with on Amazon? I want to overdo it, like maybe a 2a supply
↧
Re: Unusual network configuration for an ER-X for campus network
I am not sure I understand your need for the eth3 equipment to have a campus network IP. IP addresses are a tool to help segment a large network and acheive proper routing between subnets. If you want to route between eth0 and eth3 they should have different subnets (hence I don't see how it can work when the eth3 equipment has a campus network IP without bridging).
From my (limited) knowledge I think your options are:
A. Accept the consequences of eth3 having a different subnet (unless it is bridged or switched together with eth1 and eth2, it should have a subnet different from these ports subnet and not 192.168.1.x like you wrote).
B. bridge eth0 and eth3. As you know the ER-X has a builtin switch, so if you do move the eth2 PC to the external switch connected to eth1 you should be able to free the builtin switch and use it to connect eth0 and eth3 without the performance penalty. If you do decide to bridge these ports (as opposed to using the hardware switch), I beleive that traffic coming from the other ports (i.e. eth1) will also suffer the performance hit because it would now need to go through this bridge.
I don't beleive either bridging or switching eth0 and eth3 together limits things like port forwarding etc., your "WAN" interface simply becomes either the bridge or switch interface. Obviously this might require some tweaking of the configuration relative to the defaults the setup wizard defines.
↧
Re: ERL Power supplies failing
https://www.amazon.com/Chanzon-Switching-100-240V-Transformer-Security/dp/B07G12LXDF/ref=pd_rhf_ee_s_rp_c_1_7/146-8978895-5158542?_encoding=UTF8&pd_rd_i=B07G12LXDF&pd_rd_r=93857327-dd82-42b6-b2f2-2e4139d0ca75&pd_rd_w=IHotm&pd_rd_wg=We2lO&pf_rd_p=4f7ba04e-e8f6-4ecc-9fa2-76eede5d0d3d&pf_rd_r=S75EJ13HC66YW6KTX35R&psc=1&refRID=S75EJ13HC66YW6KTX35R
Have only just started using them in the last 6 months, so don't know how they will hold up with time, but it can't be any worse than the OEM ones.
Have only just started using them in the last 6 months, so don't know how they will hold up with time, but it can't be any worse than the OEM ones.
↧
↧
ER8-Pro High CPU even with offload
$ show ubnt offload IP offload module : loaded IPv4 forwarding: enabled vlan : enabled pppoe : disabled gre : disabled IPv6 forwarding: enabled vlan : disabled pppoe : disabled IPSec offload module: loaded Traffic Analysis : export : disabled dpi : disabled
$ show version Version: v1.9.1 Build ID: 4939098 Build on: 12/14/16 07:33 Copyright: 2012-2016 Ubiquiti Networks, Inc. HW model: EdgeRouter Pro 8-Port
Uptime: 23:01:47 up 764 days, 4 min, 1 user, load average: 5.62, 5.46, 5.45
In light of the ongoing issues with 1.10 and 2.0 and offloading, I don't want to upgrade, but for the last couple of weeks I've seen 100% CPU on the router and packet loss to hosts behind the router. As you can see, the load average is high too.
I've tcpdumped the traffic and it's legitimate, but I have had an increase in traffic (100mbps, so nothing crazy).
The load seems to be in the soft IRQs, which is consistent with traffic not being offloaded, from what I can see:
root 3 0.7 0.0 0 0 ? R 2017 8530:53 \_ [ksoftirqd/0] root 5 0.0 0.0 0 0 ? S< 2017 0:00 \_ [kworker/0:0H] root 7 0.0 0.0 0 0 ? S 2017 4:02 \_ [migration/0] root 8 0.0 0.0 0 0 ? S 2017 0:00 \_ [rcu_bh] root 9 0.2 0.0 0 0 ? R 2017 2877:19 \_ [rcu_sched] root 10 0.0 0.0 0 0 ? S 2017 53:43 \_ [watchdog/0] root 11 0.0 0.0 0 0 ? S 2017 48:23 \_ [watchdog/1] root 12 0.0 0.0 0 0 ? S 2017 4:09 \_ [migration/1] root 13 0.5 0.0 0 0 ? R 2017 6019:59 \_ [ksoftirqd/1]
What am I missing? I've seen a couple of people saying you need to restart to truly enable hw offloading, but this isn't reflected in the documentation
↧
WOL magic packets not working with Edgerouter ER-X combined EdgeSwitch 10X
Hi,
I would appreciate any help regarding how to configure and ER-X combined a EdgeSwitch 10X to send magic packets to power on a device connected in the EdgeSwitch from another device connected to it as well. I am not able this works.
This is the configuration aprox.:
--- ERX --- EdgeSwitch 10X ---> Device A to be poweon (IP: x.y.40.20 - VLAN 3)
\ ---> Device as WOL server (IP: x.y.40.25 - VLAN 3)
I want to send a magic packet from the WOL server to the Device A to be powered on. Both shares the same subnet and VLAN, but both are connected to the EdgeSwitch 10X. In this one, the VLAN is created and assigned to each ports, so they can talk.
The EdgeSwitch is connected to one port of the EdgeRouter ERX, so the packets goes to the same eth port of the ERX.
I had created a switch0.3 virtual interface with VLAN 3 and the IP x.y.40.1. And in the switch0 main device checked the VLAN aware and configured the ethernet port the EdgeSwitch is connected in as vid = 3.
I am able to ping from each device to the other, Device A to router or to WOL server and viceverse.
However when I try to send a magic packet from the WOL server to the Device A, it does not reach the Device A. Maybe there is something in the ERX that is blocking the magic packet so I cant power on the Device A.
I am surfing for EdgeRouter WOL examples configuration but something I am not configuring well.
For last, somebody told me that my routher could need to have a option called "Directed broadcast" to enable transferring the magic packets from one side to other. I am not sure of this and if EdgeOS implements.
Could you please help me to clarify my concepts?
Thank so much
EDIT: I found this page https://community.ubnt.com/t5/EdgeRouter/WOL-inside-LAN-not-possible-with-Ubiquiti-EdgeRouter-POE/td-p/1683026 says there is WoL Wizards (GUI plugins) for EdgeOS in the beta forum
https://community.ubnt.com/t5/EdgeRouter-Beta/List-of-community-contributed-feature-wizards/m-p/1524500#U1524500
I am not able to enter because I do not have sufficient privilages. However I did not find the option to enter that beta forum via my account settings. Any help to give a try this WoL Wizards? Thanks
↧
ER-X vlan - unable to ping out to the wan in 1 vlan, but the rest work
My setup is modem, ER-X, Cisco 2960S, vlans 100, 200, 300, 110.
I am able to get WAN access and ping out on vlans 100,110, 200, but not 300. I know I'm missing something ridiculous and simple.
Config is below.
firewall {
all-ping enable
broadcast-ping disable
group {
network-group Guest_to_LAN {
description ""
network 10.10.110.0/24
}
network-group Mgmt_in {
description ""
network 10.10.3.0/24
}
network-group Servers_in {
description ""
network 10.10.2.0/24
}
network-group Users {
description ""
network 10.10.1.0/24
}
}
ipv6-receive-redirects disable
ipv6-src-route disable
ip-src-route disable
log-martians enable
name Users {
default-action accept
description ""
}
name WAN_IN {
default-action drop
description "WAN to internal"
rule 10 {
action accept
description "Allow established/related"
state {
established enable
related enable
}
}
rule 20 {
action drop
description "Drop invalid state"
state {
invalid enable
}
}
}
name WAN_LOCAL {
default-action drop
description "WAN to router"
rule 10 {
action accept
description "Allow established/related"
state {
established enable
related enable
}
}
rule 20 {
action drop
description "Drop invalid state"
state {
invalid enable
}
}
rule 21 {
action accept
description "Allow Ping"
destination {
group {
address-group ADDRv4_eth0
}
}
log disable
protocol icmp
}
}
name mgmt {
default-action accept
description ""
}
name outside {
default-action accept
description ""
}
receive-redirects disable
send-redirects enable
source-validation disable
syn-cookies enable
}
interfaces {
ethernet eth0 {
address dhcp
description Outside
duplex auto
speed auto
}
ethernet eth1 {
description Local
duplex auto
speed auto
}
ethernet eth2 {
description Local
duplex auto
speed auto
vif 100 {
address 10.10.1.1/24
description Users
mtu 1500
}
vif 110 {
address 10.10.110.1/24
description Guest_wifi
mtu 1500
}
vif 200 {
address 10.10.2.1/24
description Servers
mtu 1500
}
vif 300 {
address 10.10.3.1/24
description Mgmt
firewall {
in {
name mgmt
}
}
mtu 1500
}
}
ethernet eth3 {
description Local
duplex auto
speed auto
}
ethernet eth4 {
address dhcp
description Internet
duplex auto
firewall {
in {
name WAN_IN
}
local {
name WAN_LOCAL
}
}
speed auto
}
loopback lo {
}
switch switch0 {
address dhcp
description Local
switch-port {
interface eth1 {
}
interface eth3 {
}
}
}
}
port-forward {
auto-firewall enable
hairpin-nat enable
lan-interface eth2.100
lan-interface eth2.110
lan-interface eth2.200
lan-interface eth2.300
wan-interface eth0
}
protocols {
static {
}
}
service {
dhcp-server {
shared-network-name Guest_Wifi {
subnet 10.10.110.0/24 {
default-router 10.10.110.1
dns-server 1.1.1.1
dns-server 8.8.8.8
start 10.10.110.21 {
stop 10.10.110.30
}
}
}
shared-network-name Home_Wifi {
subnet 10.10.1.0/24 {
default-router 10.10.1.1
dns-server 10.10.1.1
start 10.10.1.21 {
stop 10.10.1.75
}
}
}
shared-network-name mgmt {
subnet 10.10.3.0/24 {
default-router 1.1.1.1
dns-server 1.1.1.1
start 10.10.3.21 {
stop 10.10.3.25
}
static-mapping WAP {
ip-address 10.10.3.21
mac-address fc:ec:da:a3:47:c0
}
static-mapping tucker03 {
ip-address 10.10.3.23
mac-address 00:25:90:7e:b7:e3
}
unifi-controller 10.10.2.21
}
}
shared-network-name servers {
subnet 10.10.2.0/24 {
default-router 10.10.2.1
dns-server 1.1.1.1
start 10.10.2.21 {
stop 10.10.2.90
}
}
}
}
dns {
forwarding {
cache-size 150
listen-on eth2.200
listen-on eth2.100
listen-on eth2.110
listen-on eth2.300
listen-on eth2
}
}
gui {
https-port 443
}
nat {
rule 5010 {
description "masquerade for WAN"
log disable
outbound-interface eth0
protocol all
type masquerade
}
rule 5011 {
description "masq for mgmt"
log disable
outbound-interface eth2.300
protocol all
source {
address 10.10.3.0/24
}
type masquerade
}
}
ssh {
port 22
protocol-version v2
}
unms {
disable
}
}
system {
host-name ubnt
login {
user ******* {
authentication {
encrypted-password ****************
}
level admin
}
}
name-server 1.1.1.1
name-server 8.8.8.8
ntp {
server 0.ubnt.pool.ntp.org {
}
server 1.ubnt.pool.ntp.org {
}
server 2.ubnt.pool.ntp.org {
}
server 3.ubnt.pool.ntp.org {
}
}
syslog {
global {
facility all {
level notice
}
facility protocols {
level debug
}
}
}
time-zone America/Chicago
traffic-analysis {
dpi disable
export enable
}
}Cisco config is:
interface GigabitEthernet1/0/48 description Trunk to Router switchport trunk allowed vlan 100,110,200,300 switchport mode trunk description Mgmt ip address 10.10.3.2 255.255.255.0 no ip redirects
↧
Re: EdgeMAX EdgeRouter software version v2.0.1 has been released!
Hi Emil,
You should not need to reinstall an older version, the previous version should still be installed and you need to set the older image to the default image (via the cli) and reboot.
Regards
↧
↧
Re: UBIQUITI ER-X-SFP Edgerouter - Google Wifi - Bell Fibe
Those numbers didnt work for me... I did mess around a lot with DNS though and MTU and settled on 1492/1500 and I seem to be getting about 900/900 now on some test servers. Some are 600/600ish. It seems to just depend who you use to test. I think they are all skewed though as sometimes it said I was at 150 before and my upload speed was like 200 kb/s garbage. So always test with FTP as well to be sure of upstream. Ookla bell server test gives me 650/150 but Torix speedtest gives me a solid 900/900. Telus gives me 500/750, Rogers gives me 750/10 Yes... only 10 lol Oookla speednet.net is 900/800
So I think there is a lot of garbage bell routing going on...
I am not sure exactly what got it working but it IS possible no matter what people say. But it took days of messing around. Basically the fiber going into the router and I have my google wifi double natted but whatever i need port forwarded I put into the router and forward, otherwise the wifi goes into a switch.
Good luck
↧
Re: ER-X vlan - unable to ping out to the wan in 1 vlan, but the rest work
Typo:
shared-network-name mgmt {
subnet 10.10.3.0/24 {
default-router 1.1.1.1
↧
RMA shipping labels?
Hi, I submitted an RMA yesterday for an ER-X that intermittently just quits routing any traffic... the RMA was approved, but I can't tell if I'm waiting for a shipping label or if I'm shipping it out myself. What is the SOP for these RMAs? I am in the US.
↧
How to Limit bandwith range of IP
I can easily do this in TPlink I hope there is a way to do it as well in ER-X
I want to limit IP range 192.168.1.2-192.168.1.10 to 5mb upload and download how can i do it here in edge router please help thanks.
↧
↧
router pidof[18188]: can't get program name from /proc/18187/stat, should I be worried?
What does the below error log message mean and is it cause for concern?
router pidof[18188]: can't get program name from /proc/18187/stat
EdgeRouter X, new as of Jan 2019, so maybe not so new now. Running 1.10.9. PPPoE DSL connection and a simple home network with one VLAN. I have one static public IP address. My LAN network uses a private network range. I run the L2TP VPN server built into the EdgeRouter X with a 32 character prefix and 18 character user password. I just saw this in my log today. Up-time a little over 2 months, 3 weeks. Research seems to indicate nothing. Hardly any Google results. My best guess based on Google is that it's harmless. On the other hand, someone was concerned about hardware failure.
Appreciate any knowledge on this.
Thanks, Spiderj.
Here's the full log.
May 29 01:07:19 router kernel: ESW: Link Status Changed - Port2 Link UP May 29 01:06:54 router kernel: ESW: Link Status Changed - Port2 Link Down May 29 00:58:59 router kernel: ESW: Link Status Changed - Port2 Link UP May 29 00:58:31 router kernel: ESW: Link Status Changed - Port2 Link Down May 25 23:09:18 router pidof[18188]: can't get program name from /proc/18187/stat May 24 13:32:47 router pppd[9356]: Modem hangup May 24 13:32:47 router pppd[9356]: Connection terminated: no multilink. May 24 13:32:44 router pppd[9356]: Overriding mru 1500 to mtu value 1460 May 24 13:32:44 router pppd[9356]: Overriding mtu 1500 to 1460 May 24 11:14:15 router pppd[9356]: remote IP address PRIVATE IP ADDRESS
↧
Re: SNMP v3 keys saved in plain text
Hi
Thank you for bringing up this issue. We will look into it.
-Ben
↧
Re: ER-12 not routing between interfaces 0-7 (removed from switch)
All,
Got everything working. Problem was the netplan config file. For others that have a vlan truck into their server, and want only mngt vlan on the host and only data vlan on the containers, then the format is:
network:
version: 2
renderer: networkd
ethernets:
lan:
match:
macaddress: 00:e0:4c:68:99:fd
set-name: lan
dhcp4: no
vlans:
vmngt.100:
id: 100
link: lan
vdata.110:
id: 110
link: lan
bridges:
brmngt:
interfaces: [ vmngt.100 ]
dhcp4: no
addresses: [ 192.168.100.2/24 ]
gateway4: 192.168.100.254
nameservers:
addresses: [ 192.168.110.20 ]
search: [ rosses.net ]
brdata:
interfaces: [ vdata.110 ]
dhcp4: no
nameservers:
addresses: [ 192.168.110.20 ]
search: [ rosses.net ]
↧
Re: ER-12 not routing between interfaces 0-7 (removed from switch)
All,
Got everything working. Problem was the netplan config file. For others that have a vlan truck into their server, and want only mngt vlan on the host and only data vlan on the containers, then the format is:
network:
version: 2
renderer: networkd
ethernets:
lan:
match:
macaddress: 00:e0:4c:68:99:fd
set-name: lan
dhcp4: no
vlans:
vmngt.100:
id: 100
link: lan
vdata.110:
id: 110
link: lan
bridges:
brmngt:
interfaces: [ vmngt.100 ]
dhcp4: no
addresses: [ 192.168.100.2/24 ]
gateway4: 192.168.100.254
nameservers:
addresses: [ 192.168.110.20 ]
search: [ rosses.net ]
brdata:
interfaces: [ vdata.110 ]
dhcp4: no
nameservers:
addresses: [ 192.168.110.20 ]
search: [ rosses.net ]
↧
↧
Re: RMA shipping labels?
Ship yourself
↧
Re: VLANs on backhaul & LAN
I don't think you understand how routing works, you have switching on your brain. You wasting address right now. You only need to use vlans where your actually splitting up the traffic, the rest of the time it should just be routed. Your over complicating it. K.I.S.S.
↧
Re: How to Limit bandwith range of IP
That seems like an easy task. But isn't
You could build upon this:
https://help.ubnt.com/hc/en-us/articles/220716608-EdgeRouter-Quality-of-Service-QoS-Advanced-Queue
https://community.ubnt.com/t5/EdgeRouter/EdgeMAX-Advanced-queue-CLI-examples/td-p/1515779
Create seperate classes for those 9 IPs , and all others, and assign different speeds to those classes.
Note this puts all traffic through QoS handling, disables offload, and will limit other traffic too. So it can only be used on modest WAN link speeds. Around 50....100Mb/s max
↧