Reply
New Member
Posts: 32
Registered: ‎03-29-2016
Kudos: 2

Re: EdgeMAX EdgeRouter software version v2.0.0 has been released!

I have set up the ER X according to this guide as layer 2 switch.

 

New Member
Posts: 27
Registered: ‎02-18-2016
Kudos: 12

Re: EdgeMAX EdgeRouter software version v2.0.0 has been released!


@krl wrote:

I have set up the ER X according to this guide as layer 2 switch.

 


Look at step 5 under manual... you have to have an IP address to access/manage the ER X over IP.

New Member
Posts: 27
Registered: ‎02-18-2016
Kudos: 12

Re: EdgeMAX EdgeRouter software version v2.0.0 has been released!


@krl wrote:

I have set up the ER X according to this guide as layer 2 switch.

 


switch switch0 {
        address dhcp  <--If you don't have DHCP server you'll need to change this to the management IP you want

SuperUser
Posts: 16,617
Registered: ‎02-03-2013
Kudos: 9087
Solutions: 598
Contributions: 2

Re: EdgeMAX EdgeRouter software version v2.0.0 has been released!


@krl wrote:
@krl
> My ER-X in switch mode with Vlans was no longer accessible via GUI or SSH after the update to Edge OS 2.0.
Please post your interface configuration so I will reproduce it on my lab router
Spoiler
interfaces {
    ethernet eth0 {
        description "Switch Port"
        duplex auto
        speed auto
    }
    ethernet eth1 {
        description "Switch Port"
        duplex auto
        speed auto
    }
    ethernet eth2 {
        description "Switch Port"
        duplex auto
        speed auto
    }
    ethernet eth3 {
        description "Switch Port"
        duplex auto
        speed auto
    }
    ethernet eth4 {
        description "Switch Port"
        duplex auto
        poe {
            output off
        }
        speed auto
    }
    switch switch0 {
        address dhcp
        mtu 1500
        switch-port {
            interface eth0 {
                vlan {
                    vid 10
                    vid 20
                }
            }
            interface eth1 {
            }
            interface eth2 {
            }
            interface eth3 {
                vlan {
                    pvid 10
                }
            }
            interface eth4 {
                vlan {
                    vid 10
                    vid 20
                }
            }
            vlan-aware enable
        }
    }
}
service {
    gui {
        http-port 80
        https-port 443
        older-ciphers enable
    }
    ssh {
        port 22
        protocol-version v2
    }
    unms {
        connection wss://192.168.1.4:443*********************
+allowUntrustedCertificate
        disable
    }
}
system {
    conntrack {
        expect-table-size 4096
        hash-size 4096
        table-size 32768
        tcp {
            half-open-connections 512
            loose enable
            max-retrans 3
        }
    }
    host-name ubnt
    login {
        user ****** {
            authentication {
                encrypted-password ************
            }
            level admin
        }
    }
    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 UTC
}


/* Warning: Do not remove the following line. */
/* === vyatta-config-version: "config-management@1:conntrack@1:cron@1:dhcp-relay@1:dhcp-server@4:firewall@5:ipsec@5:nat@3:qos@1:quagga@2:suspend@1:system@4:ubnt-pptp@1:ubnt-udapi-server@1:ubnt-unms@1:ubnt-util@1:vrrp@1:webgui@1:webproxy@1:zone-policy@1" === */
/* Release version: v1.10.8.5142457.181120.1809 */

 

@krl And anyone else trying to set it up as a switch with vlans. After adding the vlan and IP to the switch. You currently have to reboot the router before the vlan is actually added. This is a work around until this is fixed in a future release.  After rebooting it will work fine. If you loose access just power cycle and everything will work.

ubiquiti certified trainer :: ubwa | uewa
New Member
Posts: 28
Registered: ‎09-05-2014
Kudos: 5
Solutions: 1

Re: EdgeMAX EdgeRouter software version v2.0.0 has been released!


@UBNT-afomins wrote: 

@jdrom
> ERX-SFP ... woke up this morning to have one of my G3 cameras showing as disconnected, it's plugged into eth2 with PoE enabled
> Decided to reboot the ERX just now and that fixed it

  1. Was the LED light no camera blinking?
  2. If it will ever happen again then please show output of "show interfaces ethernet poe" and "dmesg|grep link"

Happened again today but I rolled back to 1.10.8 before I checked these forums. I'll see if it still happens on 1.10.8 and go from there. 

New Member
Posts: 32
Registered: ‎03-29-2016
Kudos: 2

Re: EdgeMAX EdgeRouter software version v2.0.0 has been released!

Ok, but i have a second ER X as router an DHCP server, is it better to use the manual ip? Can this be the mistake why the ER X was not reachable after the update to EdgeOS 2.0?

 

Screenshot_2019-01-09 - ubnt.png

New Member
Posts: 33
Registered: ‎08-03-2017
Kudos: 7
Solutions: 3

Re: EdgeMAX EdgeRouter software version v2.0.0 has been released!

[ Edited ]

Since beta3, and also with this release, I suddenly suffer from this kernelmessage when my manually binded, route-based, VTI-tunnel is brought down:

 

   kernel:unregister_netdevice: waiting for vti0 to become free. Usage count = xxx

 

I have (since many 1.10.x and also 2.0.0.beta1 releases) a custom ipsec.conf in my config-folder, that references 'leftupdown=/config/ipsec_updown.sh' which in turns calls a shell-command that manually brings up or down the VTI tunnel.

 

Spoiler
#!/bin/bash

# set charon.install_virtual_ip = no to prevent the daemon from also installing the VIP

set -o nounset
set -o errexit

VTI_IF="vti0"

case "${PLUTO_VERB}" in
up-client)
ip tunnel add vti0 local "${PLUTO_ME}" remote "${PLUTO_PEER}" mode vti \
okey "${PLUTO_MARK_OUT%%/*}" ikey "${PLUTO_MARK_IN%%/*}"
/sbin/sysctl net.ipv4.conf.vti0.disable_policy=1
ip link set vti0 up
ip addr add "${PLUTO_MY_SOURCEIP}" dev vti0
ip route add "${PLUTO_PEER_CLIENT}" dev vti0
;;
down-client)
ip tunnel del vti0
;;
esac

Source (expand the 'example')

 

@UBNT-afomins; did something change in beta 2 or 3 (i couldn't test 2 because of the vlan-problem in it) that the kernel-message is now suddently a problem?  I'm able to test any manual changes/checks, so please let me know if i can be of further assistance.

New Member
Posts: 13
Registered: ‎03-18-2018
Kudos: 1

Re: EdgeMAX EdgeRouter software version v2.0.0 has been released!

Thank you for above config, I was able to fix my lighttp configuration.

 

Sigi

New Member
Posts: 17
Registered: ‎03-09-2018
Kudos: 1

Re: EdgeMAX EdgeRouter software version v2.0.0 has been released!


@gyrfalcon wrote:
Spoiler


@Harman20 wrote:

My password is now invalid after the update. To be fair, it was a several hundred character password with high ANSI characters.



To be honest, it would make me somewhat happy if your router got bricked from doing that...


Ow, my feelings Man Sad

Emerging Member
Posts: 59
Registered: ‎11-12-2016
Kudos: 17
Solutions: 8

Re: EdgeMAX EdgeRouter software version v2.0.0 has been released!

Curious timing...   Icon Razz

 

EdgeMax Survey.png

Emerging Member
Posts: 61
Registered: ‎10-07-2013
Kudos: 19
Solutions: 2

Re: EdgeMAX EdgeRouter software version v2.0.0 has been released!

Updated my ER-X to 2.0.0 via ssh.  Then, before rebooting, disabled hwnat and saved the config.  The ER-X then hung on the reboot command -- still responded to pings, but no gui, no ssh, no PPPoE internet traffic.  A power-cycle brought everything back, but the router hung again after about 4 hours, this time not even responding to pings.  I had been running the 2.0.0 betas with no problems.  I'm going to try to downgrade to 1.10.8.

Veteran Member
Posts: 7,602
Registered: ‎03-24-2016
Kudos: 1977
Solutions: 871

Re: EdgeMAX EdgeRouter software version v2.0.0 has been released!

@gharris999 wrote:

Updated my ER-X to 2.0.0 via ssh.  
Then, before rebooting, disabled hwnat and saved the config

I doubt that order of operation makes sense.  During the firmware install, a copy of running config is made into the new firmware version.  Any config changes thereafter on 1.x won't alter 2.x configuration

 

Established Member
Posts: 781
Registered: ‎01-29-2014
Kudos: 315
Solutions: 35

Re: EdgeMAX EdgeRouter software version v2.0.0 has been released!

Iagree

changes to config after starting the image upgrade process does not work.

Emerging Member
Posts: 77
Registered: ‎09-30-2014
Kudos: 5
Solutions: 2

Re: EdgeMAX EdgeRouter software version v2.0.0 has been released!

[ Edited ]

Updated ER-4 via ssh from v2-beta3 to v2.0.0 release - everything is in order. However i do no have any fancy configuration (some vlans, ipv6 and ...thats it)

Boot time - abt. 2 min 35 as per unms reporting.

 

L.E.

same annoying snmpd error: error on subcontainer 'ia_addr' insert (-1)

Jan 10 09:13:57 gw snmpd[4620]: pcilib: Cannot find any working access method.
Jan 10 09:13:57 gw snmpd[4620]: pcilib: pci_init failed
Jan 10 09:13:58 gw snmpd[4620]: notificationEvent OID: linkUp
Jan 10 09:13:58 gw snmpd[4620]: /etc/snmp/snmpd.conf: line 22: Error: unknown notification OID
Jan 10 09:13:58 gw snmpd[4620]: notificationEvent OID: linkDown
Jan 10 09:13:58 gw snmpd[4620]: /etc/snmp/snmpd.conf: line 23: Error: unknown notification OID
Jan 10 09:13:58 gw snmpd[4620]: /etc/snmp/snmpd.conf: line 24: Warning: Unknown token: monitor.
Jan 10 09:13:58 gw snmpd[4620]: /etc/snmp/snmpd.conf: line 25: Warning: Unknown token: monitor.
Jan 10 09:13:58 gw snmpd[4620]: net-snmp: 2 error(s) in config file(s)

Attached also last logs.

Spoiler
Jan 10 09:13:01 gw systemd[1]: var-log.mount: Directory /var/log to mount over is not empty, mounting anyway.
Jan 10 09:13:01 gw systemd-udevd[147]: Could not generate persistent MAC address for loop3: No such file or directory
Jan 10 09:13:01 gw systemd-udevd[145]: Could not generate persistent MAC address for npi0: No such file or directory
Jan 10 09:13:01 gw systemd-udevd[142]: Could not generate persistent MAC address for loop2: No such file or directory
Jan 10 09:13:01 gw systemd-udevd[154]: Could not generate persistent MAC address for loop0: No such file or directory
Jan 10 09:13:01 gw systemd-udevd[153]: Could not generate persistent MAC address for loop1: No such file or directory
Jan 10 09:13:01 gw systemd-udevd[152]: Could not generate persistent MAC address for npi1: No such file or directory
Jan 10 09:13:01 gw systemd-udevd[143]: Could not generate persistent MAC address for npi2: No such file or directory
Jan 10 09:13:01 gw systemd-udevd[149]: Could not generate persistent MAC address for npi3: No such file or directory
Jan 10 09:13:01 gw netplugd: Starting network plug daemon: netplugd.
Jan 10 09:13:01 gw liblogging-stdlog:  [origin software="rsyslogd" swVersion="8.24.0" x-pid="234" x-info="http://www.rsyslog.com"] start
Jan 10 09:13:01 gw kernel: Linux version 4.9.79-UBNT (ubnt@81e6d5e60acc) (gcc version 4.7.0 (Cavium Inc. Version: SDK_BUILD build 54) ) #1 SMP Fri Jan 4 07:05:51 UTC 2019
Jan 10 09:13:01 gw kernel: CVMSEG size: 3 cache lines (384 bytes)
Jan 10 09:13:01 gw kernel: Checking for the multiply/shift bug... 
Jan 10 09:13:01 gw kernel: no.
Jan 10 09:13:01 gw kernel: Checking for the daddiu bug... 
Jan 10 09:13:01 gw kernel: no.
Jan 10 09:13:01 gw kernel: Primary instruction cache 78kB, virtually tagged, 39 way, 16 sets, linesize 128 bytes.
Jan 10 09:13:01 gw kernel: Primary data cache 32kB, 32-way, 8 sets, linesize 128 bytes.
Jan 10 09:13:01 gw kernel: Secondary unified cache 512kB, 4-way, 1024 sets, linesize 128 bytes.
Jan 10 09:13:01 gw kernel: Secondary unified cache 512kB, 4-way, 1024 sets, linesize 128 bytes.
Jan 10 09:13:01 gw kernel: Kernel command line:  root=/dev/mmcblk0p2 rootdelay=10 rw rootsqimg=squashfs.img rootsqwdir=w mtdparts=spi32766.0:1024k(boot0),3072k(boot1),64k(eeprom) console=ttyS0,115200 rootwait rootflags=data=journal
Jan 10 09:13:01 gw kernel: Checking for the daddi bug... 
Jan 10 09:13:01 gw kernel: no.
Jan 10 09:13:01 gw kernel: SCSI subsystem initialized
Jan 10 09:13:01 gw kernel: /proc/octeon_perf: Octeon performance counter interface loaded
Jan 10 09:13:01 gw kernel: random: fast init done
Jan 10 09:13:01 gw kernel: 3 cmdlinepart partitions found on MTD device spi32766.0
Jan 10 09:13:01 gw kernel: Creating 3 MTD partitions on "spi32766.0":
Jan 10 09:13:01 gw kernel: 0x000000000000-0x000000100000 : "boot0"
Jan 10 09:13:01 gw kernel: 0x000000100000-0x000000400000 : "boot1"
Jan 10 09:13:01 gw kernel: 0x000000400000-0x000000410000 : "eeprom"
Jan 10 09:13:01 gw kernel: octeon-ethernet 2.0
Jan 10 09:13:01 gw kernel: Node 0 Interface 0 has 4 ports (QSGMII)
Jan 10 09:13:01 gw kernel: Node 0 Interface 1 has 4 ports (QSGMII)
Jan 10 09:13:01 gw kernel: Node 0 Interface 2 has 4 ports (NPI)
Jan 10 09:13:01 gw kernel: Node 0 Interface 3 has 4 ports (LOOP)
Jan 10 09:13:01 gw kernel: Node 0 Interface 4 has 1 ports (AGL)
Jan 10 09:13:01 gw kernel: dwc3 1680000000000.xhci: Configuration mismatch. dr_mode forced to host
Jan 10 09:13:01 gw kernel: dwc3 1690000000000.xhci: Configuration mismatch. dr_mode forced to host
Jan 10 09:13:01 gw kernel: OF: fdt:not creating '/sys/firmware/fdt': CRC check failed
Jan 10 09:13:01 gw kernel: EXT4-fs: Warning: mounting with data=journal disables delayed allocation and O_DIRECT support!
Jan 10 09:13:01 gw kernel: This architecture does not have kernel memory protection.
Jan 10 09:13:01 gw kernel: ubnt_platform: loading out-of-tree module taints kernel.
Jan 10 09:13:01 gw kernel: ubnt_platform: module license 'Proprietary' taints kernel.
Jan 10 09:13:01 gw kernel: Disabling lock debugging due to kernel taint
Jan 10 09:13:01 gw kernel: random: crng init done
Jan 10 09:13:03 gw kernel: eth0: Link down
Jan 10 09:13:03 gw kernel: eth1: Link down
Jan 10 09:13:04 gw kernel: eth2: Link down
Jan 10 09:13:04 gw kernel: eth3: Link down
Jan 10 09:13:05 gw kernel: eth3: 1000 Mbps Full duplex, port 0
Jan 10 09:13:06 gw kernel: eth0: 1000 Mbps Full duplex, port 1
Jan 10 09:13:08 gw ssh-recovery[746]: starting...
Jan 10 09:13:08 gw ssh-recovery[746]: if=(all) port=(60257) terminate-timeout=(60)
Jan 10 09:13:09 gw ssh-recovery[746]: enabling link on interfaces...
Jan 10 09:13:09 gw ssh-recovery[746]: eth0 :: mac=(78:8a:20:XX:XX:XX)
Jan 10 09:13:09 gw ssh-recovery[746]: eth1 :: mac=(78:8a:20:XX:XX:XX)
Jan 10 09:13:09 gw ssh-recovery[746]: eth2 :: mac=(78:8a:20:XX:XX:XX)
Jan 10 09:13:09 gw ssh-recovery[746]: eth3 :: mac=(78:8a:20:XX:XX:XX)
Jan 10 09:13:10 gw NSM[854]:  NSM-6: Initializing memdbg: ptr=0x56839e44 history-size=1024 memdbg-size=143552
Jan 10 09:13:11 gw kernel: 3.
Jan 10 09:13:11 gw kernel: 5.
Jan 10 09:13:11 gw kernel: 58.
Jan 10 09:13:11 gw kernel: 
Jan 10 09:13:11 gw NSM[863]:  NSM-6: 1000 MB
Jan 10 09:13:11 gw NSM[863]:  NSM-6: 1000 MB
Jan 10 09:13:11 gw NSM[863]:  NSM-6: 10 MB
Jan 10 09:13:11 gw NSM[863]:  NSM-6: 10 MB
Jan 10 09:13:11 gw NSM[863]:  NSM-6: ioctl(1) returned illegal value(0). Setting bandwidth to 0
Jan 10 09:13:11 gw NSM[863]: message repeated 7 times: [  NSM-6: ioctl(1) returned illegal value(0). Setting bandwidth to 0]
Jan 10 09:13:11 gw ssh-recovery[746]: service started :: pid=(857)
Jan 10 09:13:16 gw IMI[853]:  IMI-6: imi_server_send_config called (PM 1)
Jan 10 09:13:17 gw RIB[984]:  RIB-6: Initializing memdbg: ptr=0x55d9cd50 history-size=1024 memdbg-size=143552
Jan 10 09:13:17 gw IMI[853]:  IMI-6: imi_server_send_config called (PM 42)
Jan 10 09:13:17 gw RIB[985]:  RIB-6: RIBd (1.2.0) starts
Jan 10 09:13:17 gw IMI[853]:  IMI-6: imi_server_send_config called (PM 42)
Jan 10 09:13:19 gw rl-system.init: Checking/creating SSH host keys.
Jan 10 09:13:21 gw liblogging-stdlog:  [origin software="rsyslogd" swVersion="8.24.0" x-pid="234" x-info="http://www.rsyslog.com"] exiting on signal 15.
Jan 10 09:13:21 gw liblogging-stdlog:  [origin software="rsyslogd" swVersion="8.24.0" x-pid="1133" x-info="http://www.rsyslog.com"] start
Jan 10 09:13:22 gw liblogging-stdlog:  [origin software="rsyslogd" swVersion="8.24.0" x-pid="1133" x-info="http://www.rsyslog.com"] exiting on signal 15.
Jan 10 09:13:23 gw liblogging-stdlog:  [origin software="rsyslogd" swVersion="8.24.0" x-pid="1250" x-info="http://www.rsyslog.com"] start
Jan 10 09:13:38 gw NSM[863]:  NSM-6: 1000 MB
Jan 10 09:13:39 gw NSM[863]:  NSM-6: 1000 MB
Jan 10 09:13:39 gw NSM[863]:  NSM-6: 1000 MB
Jan 10 09:13:44 gw pppd[3788]: pppd 2.4.7 started by root, uid 0
Jan 10 09:13:44 gw liblogging-stdlog:  [origin software="rsyslogd" swVersion="8.24.0" x-pid="1250" x-info="http://www.rsyslog.com"] exiting on signal 15.
Jan 10 09:13:44 gw liblogging-stdlog:  [origin software="rsyslogd" swVersion="8.24.0" x-pid="3815" x-info="http://www.rsyslog.com"] start
Jan 10 09:13:45 gw liblogging-stdlog:  [origin software="rsyslogd" swVersion="8.24.0" x-pid="3815" x-info="http://www.rsyslog.com"] exiting on signal 15.
Jan 10 09:13:45 gw pppd[3788]: Connected to 00:25:90:e2:11:a9 via interface eth0
Jan 10 09:13:45 gw liblogging-stdlog:  [origin software="rsyslogd" swVersion="8.24.0" x-pid="3841" x-info="http://www.rsyslog.com"] start
Jan 10 09:13:45 gw pppd[3788]: Connect: pppoe0 <--> eth0
Jan 10 09:13:45 gw systemd-udevd[3836]: link_config: could not get ethtool features for ppp0
Jan 10 09:13:45 gw systemd-udevd[3836]: Could not set offload features of ppp0: No such device
Jan 10 09:13:45 gw liblogging-stdlog:  [origin software="rsyslogd" swVersion="8.24.0" x-pid="3841" x-info="http://www.rsyslog.com"] exiting on signal 15.
Jan 10 09:13:45 gw liblogging-stdlog:  [origin software="rsyslogd" swVersion="8.24.0" x-pid="3891" x-info="http://www.rsyslog.com"] start
Jan 10 09:13:48 gw ntpd[3964]: restrict 0.0.0.0: KOD does nothing without LIMITED.
Jan 10 09:13:48 gw ntpd[3964]: restrict ::: KOD does nothing without LIMITED.
Jan 10 09:13:50 gw ntpd[4255]: restrict 0.0.0.0: KOD does nothing without LIMITED.
Jan 10 09:13:50 gw ntpd[4255]: restrict ::: KOD does nothing without LIMITED.
Jan 10 09:13:51 gw avahi-daemon[4303]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
Jan 10 09:13:54 gw dhcpd: WARNING: Host declarations are global.  They are not limited to the scope you declared them in.
Jan 10 09:13:57 gw snmpd[4620]: pcilib: Cannot find any working access method.
Jan 10 09:13:57 gw snmpd[4620]: pcilib: pci_init failed
Jan 10 09:13:58 gw snmpd[4620]: notificationEvent OID: linkUp
Jan 10 09:13:58 gw snmpd[4620]: /etc/snmp/snmpd.conf: line 22: Error: unknown notification OID
Jan 10 09:13:58 gw snmpd[4620]: notificationEvent OID: linkDown
Jan 10 09:13:58 gw snmpd[4620]: /etc/snmp/snmpd.conf: line 23: Error: unknown notification OID
Jan 10 09:13:58 gw snmpd[4620]: /etc/snmp/snmpd.conf: line 24: Warning: Unknown token: monitor.
Jan 10 09:13:58 gw snmpd[4620]: /etc/snmp/snmpd.conf: line 25: Warning: Unknown token: monitor.
Jan 10 09:13:58 gw snmpd[4620]: net-snmp: 2 error(s) in config file(s)
Jan 10 09:14:44 gw miniupnpd[4741]: could not open lease file: /var/log/upnp.leases
Jan 10 09:14:47 gw kernel: Changing the IPv4 forwarding cache table size from 8192 to 32768
Jan 10 09:14:47 gw kernel: Changing the IPv6 forwarding cache table size from 8192 to 65536
Jan 10 09:14:50 gw ntpd[4255]: bind(34) AF_INET6 2a02:2f0d:XX:XX:XX:XX:XX:XX#123 flags 0x11 failed: Cannot assign requested address
Jan 10 09:14:50 gw ntpd[4255]: unable to create socket on eth3 (15) for 2a02:2f0d:XX:XX:XX:XX:XX:XX#123
Member
Posts: 109
Registered: ‎08-09-2013
Kudos: 60
Solutions: 2

Re: EdgeMAX EdgeRouter software version v2.0.0 has been released!

[ Edited ]

Upgraded one of my two ERLs yesterday. Did not come up after reboot.

After conencting serial cable, the only message I got back was:

You are in emergency mode. After logging in, type "journalctl -x Cannot open access to console, the root account is locked.

Rebooted once more, saw some corrupt sectors warning(USB storage has been changed once before on this deveice). But it booted to login, with some other services failing, unfortunately login did not work(said wrong user og pass). After a second reboot, everything worked fine.

 

Having another ERL with pretty much same config(standby router), and will monitor the upgrade a bit more closely on that.

Member
Posts: 142
Registered: ‎09-03-2016
Kudos: 6
Solutions: 2

Re: EdgeMAX EdgeRouter software version v2.0.0 has been released!

[ Edited ]

Updated ER4 from 1.10.8 to 2.0.0 via HTTP from the ER4 CLI with no issues.

New Member
Posts: 41
Registered: ‎11-04-2018
Solutions: 1

Re: EdgeMAX EdgeRouter software version v2.0.0 has been released!

Updated ER-4 from 1.10.8 to 2.0.0 via web interface with no problem. Working constantly now from update time...

 

 

er4_200.png
New Member
Posts: 14
Registered: ‎10-15-2016

Re: EdgeMAX EdgeRouter software version v2.0.0 has been released!

Upgraded ER-4 via Web GUI and it went fine (quicker than other upgrades) and all the existing functionality is working.  

Emerging Member
Posts: 71
Registered: ‎03-26-2017
Kudos: 8
Solutions: 2

Re: EdgeMAX EdgeRouter software version v2.0.0 has been released!

Update a couple of ER-4 / ER-6p

 

Generally it went pretty good, couple problems with IPv6.

 

One site lost all IPv6 connectivity to the local clients, I suspect because of radvd started after dhcp6c obtained a prefix for the local interfaces

$ ps aux | grep dhcp
root      5978  0.0  0.3   4904  3764 ?        Ss   07:58   0:00 /usr/sbin/dhcpd3 -pf /var/run/dhcpd.pid -cf /opt/vyatta/etc/dhcpd.conf -lf /var/run/dhcpd.leases
root      6447  0.0  0.0   2176   360 ?        Ss   07:58   0:00 /usr/sbin/dhcp6c -c /var/run/dhcp6c-eth0-pd.conf -p /var/run/dhcp6c-eth0-pd.pid -df eth0
root      7199  0.0  0.1   4012  1152 ?        Ss   07:59   0:00 /usr/sbin/dhcpd3 -6 -pf /var/run/dhcpdv6.pid -cf /opt/vyatta/etc/dhcpdv6.conf -lf /var/run/dhcpdv6.leases
$ ps aux | grep radv
root      6363  0.0  0.0   2600   128 ?        Ss   07:58   0:00 /usr/sbin/radvd --logmethod stderr_clean
root      6364  0.0  0.0   2600   128 ?        S    07:58   0:00 /usr/sbin/radvd --logmethod stderr_clean

You can see how radv PID is less than dhcp6c PID. UBNT needs to restart radvd in dhcp6c script after lease is obtained or if there is a change in the leased address.

 

Solution was pretty easy

sudo systemctl restart radvd

After that all local clients regained IPv6 connectivity immediately.

 

Second site with a local DHCPv6-PD server did not experience such problem, I assume because of the timing (local server assigned prefix rapidly).

 

Second problem is not new - dhcpv6 server on the EdgeRouter did not start after reboot, I reported it here previously, but it did not get any attention.

 

Fix is as usual:

restart dhcpv6 server

 

Bonus after the upgrade - my OpenVPN now connects with TLS1.2 and AES-256-GCM to the ER.

Emerging Member
Posts: 88
Registered: ‎09-26-2014
Kudos: 7
Solutions: 2

Re: EdgeMAX EdgeRouter software version v2.0.0 has been released!

Reply