Reply
Established Member
Posts: 969
Registered: ‎02-12-2013
Kudos: 247
Solutions: 89

Re: EdgeMAX EdgeRouter software version v1.10.8 has been released!

Hi @Berkutta
Do you have enough system to try to re-install the firmware again?
https://help.ubnt.com/hc/en-us/articles/205146110-EdgeRouter-Upgrading-EdgeOS-Firmware#3
Otherwise you might try resetting to factory defaults:
https://help.ubnt.com/hc/en-us/articles/205202620-EdgeRouter-Reset-to-Factory-Defaults
Ubiquiti Employee
Posts: 1,229
Registered: ‎07-20-2015
Kudos: 1446
Solutions: 81

Re: EdgeMAX EdgeRouter software version v1.10.8 has been released!

@mousehunt
> df: /run/netns/zebosfib0: Permission denied
> df: /run/netns/zebosfib1: Permission denied
> Anything to worry about?
You should not worry about that, just run `show system storage` or `sudo df -h` to get rid of "Permission denied" errors

 

@kshrwood02
> ER8 stuck in a boot loop after update from 1.10.1 to 1.10.8
I provided recovery instructions in linked thread

 

@Berkutta
> upgrading a ER-PoE from 1.10.6 to 1.10.8
> After the first reboot to apply the update the Webinterface was just showing 'Render error: TypeError: 'undefined' is not an object (evaluating 'this.model.get')'
> Then I made a reboot through SSH. After this reboot the device wasn't working anymore
> A look via Console Cable showed that at least half of my interfaces were missing and also other configurations weren't there anymore.

  1. Does factory reset help?
  2. Can you login ER via console? If you can then please show output of "show tech-support" CLI command
Emerging Member
Posts: 77
Registered: ‎09-30-2014
Kudos: 5
Solutions: 2

Re: EdgeMAX EdgeRouter software version v1.10.8 has been released!

Some issues after upgrading from 10.7 to 10.8 (ER-4):

Dec  2 14:16:04 gw kernel: ------------[ cut here ]------------
Dec  2 14:16:04 gw kernel: WARNING: at mm/slab_common.c:394 kmalloc_slab+0xcc/0xe0()
Dec  2 14:16:04 gw kernel: Modules linked in: nf_conntrack_netlink pppoe pppox ppp_generic slhc 8021q garp stp llc ipt_MASQUERADE xt_nat nf_conntrack_ipv6 nf_defrag_ipv6 xt_mac xt_time xt_comment xt_set xt_conntrack xt_TCPMSS xt_tcpudp ip6table_mangle ip6table_filter ip6table_raw ip6_tables iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 iptable_mangle xt_CT iptable_raw nf_nat_pptp nf_conntrack_pptp nf_conntrack_proto_gre nf_nat_h323 nf_conntrack_h323 nf_nat_sip nf_conntrack_sip nf_nat_proto_gre nf_nat_tftp nf_nat_ftp nf_nat nf_conntrack_tftp nf_conntrack_ftp nf_conntrack iptable_filter ip_tables x_tables ip_set_hash_net ip_set nfnetlink cvm_ipsec_kame(O) ipv6 imq cavium_ip_offload(PO) ubnt_nf_app(PO) tdts(PO) octeon_rng rng_core ubnt_platform(PO)
Dec  2 14:16:04 gw kernel: CPU: 0 PID: 17360 Comm: cat Tainted: P           O 3.10.107-UBNT #1
Dec  2 14:16:04 gw kernel: Stack : 00000000000000d3 0000000030009ce1 0000000000402100 0000000000000007
Dec  2 14:16:04 gw kernel: 	  0000000000000000 0000000000000000 ffffffff80ef0000 00000000000000d3
Dec  2 14:16:04 gw kernel: 	  ffffffff80ee65d8 ffffffff80da0000 00000000000000d3 3130372d55424e54
Dec  2 14:16:04 gw kernel: 	  0000000000000003 ffffffff80eea348 ffffffff80ef0000 0000000000000000
Dec  2 14:16:04 gw kernel: 	  0000000000000000 0000000000000009 ffffffff808f7b24 000000000000018a
Dec  2 14:16:04 gw kernel: 	  ffffffff80ccb000 000000007f8a1b18 8000000038df3e00 80000000499db538
Dec  2 14:16:04 gw kernel: 	  0000000000000003 0000000000000001 0000000077a88490 0f0000000133e907
Dec  2 14:16:04 gw kernel: 	  8000000038df0000 8000000038df3b20 0000000002000000 ffffffff8087d460
Dec  2 14:16:04 gw kernel: 	  800000004c2cf3e0 ffffffff80cc1c98 0000000000000000 00000000000043d0
Dec  2 14:16:04 gw kernel: 	  0000000000000000 ffffffff8085f674 0000000000000000 0000000000000000
Dec  2 14:16:04 gw kernel: 	  ...
Dec  2 14:16:04 gw kernel: Call Trace:
Dec  2 14:16:04 gw kernel: [<ffffffff8085f674>] show_stack+0x6c/0xf8
Dec  2 14:16:04 gw kernel: [<ffffffff8087d460>] warn_slowpath_common+0x78/0xa8
Dec  2 14:16:04 gw kernel: [<ffffffff808f7b24>] kmalloc_slab+0xcc/0xe0
Dec  2 14:16:04 gw kernel: 
Dec  2 14:16:04 gw kernel: ---[ end trace 2256c173adaf38e7 ]---
Dec 11 15:05:29 gw kernel: skbuff: Gotcha2 8000000040853000 8000000040853142 -4
Dec 11 15:05:29 gw kernel: CPU: 3 PID: 0 Comm: swapper/3 Tainted: P        W  O 3.10.107-UBNT #1
Dec 11 15:05:29 gw kernel: Stack : 00000000000000ec 0000000014009ce1 0000000010200040 0000000000000007
Dec 11 15:05:29 gw kernel: 	  0000000000000000 0000000000000000 ffffffff80ef0000 00000000000000ec
Dec 11 15:05:29 gw kernel: 	  ffffffff80ee65d8 ffffffff80da0000 00000000000000ec 302e3130372d5542
Dec 11 15:05:29 gw kernel: 	  0000000000000005 ffffffff80eeaba0 ffffffff80ef0000 0000000000000000
Dec 11 15:05:29 gw kernel: 	  800000004d40c500 fffffffffffffffc 800000004cbf9000 8000000040853142
Dec 11 15:05:29 gw kernel: 	  000000000000015a ffffffff80d313f8 0000000000000001 800000004cbf9000
Dec 11 15:05:29 gw kernel: 	  0000000000000005 0000000000000001 800000004c267e10 800000004c267e10
Dec 11 15:05:29 gw kernel: 	  800000004c264000 800000004c267880 8000000049c14c80 ffffffff80b4c44c
Dec 11 15:05:29 gw kernel: 	  800000004c25aa10 ffffffff80cc1c98 0000000000000003 0000000000000000
Dec 11 15:05:29 gw kernel: 	  0000000000000000 ffffffff8085f674 0000000000000000 0000000000000000
Dec 11 15:05:29 gw kernel: 	  ...
Dec 11 15:05:29 gw kernel: Call Trace:
Dec 11 15:05:29 gw kernel: [<ffffffff8085f674>] show_stack+0x6c/0xf8
Dec 11 15:05:29 gw kernel: [<ffffffff80b4c44c>] skb_push+0xa4/0xb0
Dec 11 15:05:29 gw kernel: [<ffffffff80bfecc8>] packet_rcv+0xe0/0x470
Dec 11 15:05:29 gw kernel: [<ffffffff80b56af4>] __netif_receive_skb_core+0x59c/0x8a8
Dec 11 15:05:29 gw kernel: [<ffffffff80b5a9cc>] process_backlog+0xbc/0x1b8
Dec 11 15:05:29 gw kernel: [<ffffffff80b5b360>] net_rx_action+0x220/0x2b0
Dec 11 15:05:29 gw kernel: [<ffffffff80885048>] __do_softirq+0x1d0/0x218
Dec 11 15:05:29 gw kernel: [<ffffffff80885158>] do_softirq+0x68/0x70
Dec 11 15:05:29 gw kernel: [<ffffffff808857b8>] irq_exit+0x68/0x78
Dec 11 15:05:29 gw kernel: [<ffffffff8080697c>] plat_irq_dispatch+0x4c/0xe0
Dec 11 15:05:29 gw kernel: [<ffffffff8085ae34>] handle_int+0x114/0x11c
Dec 11 15:05:29 gw kernel: 
Dec 11 15:05:29 gw kernel: skbuff: Gotcha2 8000000040853000 8000000040853142 -4
Dec 11 15:05:29 gw kernel: CPU: 3 PID: 0 Comm: swapper/3 Tainted: P        W  O 3.10.107-UBNT #1
Dec 11 15:05:29 gw kernel: Stack : 00000000000000fc 0000000014009ce1 0000000010200040 ffffffff80d9c520
Dec 11 15:05:29 gw kernel: 	  0000000000000000 0000000000000000 ffffffff80ef0000 00000000000000fc
Dec 11 15:05:29 gw kernel: 	  ffffffff80ee65d8 ffffffff80da0000 00000000000000fc 302e3130372d5542
Dec 11 15:05:29 gw kernel: 	  0000000000000005 ffffffff80eeb218 ffffffff80ef0000 0000000000000000
Dec 11 15:05:29 gw kernel: 	  800000004d40c500 fffffffffffffffc 800000004cbf9000 8000000040853142
Dec 11 15:05:29 gw kernel: 	  000000000000015a 0000000000000800 0000000000000000 800000004cbf9000
Dec 11 15:05:29 gw kernel: 	  0000000000000005 0000000000000001 0000000000000000 ffffffff80ee0000
Dec 11 15:05:29 gw kernel: 	  800000004c264000 800000004c267880 0000000000000000 ffffffff80b4c44c
Dec 11 15:05:29 gw kernel: 	  800000004c25aa10 ffffffff80cc1c98 0000000000000003 0000000000000000
Dec 11 15:05:29 gw kernel: 	  0000000000000000 ffffffff8085f674 0000000000000000 0000000000000000
Dec 11 15:05:29 gw kernel: 	  ...
Dec 11 15:05:29 gw kernel: Call Trace:
Dec 11 15:05:29 gw kernel: [<ffffffff8085f674>] show_stack+0x6c/0xf8
Dec 11 15:05:29 gw kernel: [<ffffffff80b4c44c>] skb_push+0xa4/0xb0
Dec 11 15:05:29 gw kernel: [<ffffffff80bfecc8>] packet_rcv+0xe0/0x470
Dec 11 15:05:29 gw kernel: [<ffffffff80b569c4>] __netif_receive_skb_core+0x46c/0x8a8
Dec 11 15:05:29 gw kernel: [<ffffffff80b5a9cc>] process_backlog+0xbc/0x1b8
Dec 11 15:05:29 gw kernel: [<ffffffff80b5b360>] net_rx_action+0x220/0x2b0
Dec 11 15:05:29 gw kernel: [<ffffffff80885048>] __do_softirq+0x1d0/0x218
Dec 11 15:05:29 gw kernel: [<ffffffff80885158>] do_softirq+0x68/0x70
Dec 11 15:05:29 gw kernel: [<ffffffff808857b8>] irq_exit+0x68/0x78
Dec 11 15:05:29 gw kernel: [<ffffffff8080697c>] plat_irq_dispatch+0x4c/0xe0
Dec 11 15:05:29 gw kernel: [<ffffffff8085ae34>] handle_int+0x114/0x11c
Dec 11 15:05:29 gw kernel: 
Dec 11 15:05:29 gw kernel: skbuff: Gotcha2 8000000036122000 8000000036122142 -4
Dec 11 15:05:29 gw kernel: CPU: 3 PID: 0 Comm: swapper/3 Tainted: P        W  O 3.10.107-UBNT #1
Dec 11 15:05:29 gw kernel: Stack : 000000000000010c 0000000014009ce1 0000000010200040 ffffffff80d9c520
Dec 11 15:05:29 gw kernel: 	  0000000000000000 0000000000000000 ffffffff80ef0000 000000000000010c
Dec 11 15:05:29 gw kernel: 	  ffffffff80ee65d8 ffffffff80da0000 000000000000010c 302e3130372d5542
Dec 11 15:05:29 gw kernel: 	  0000000000000005 ffffffff80eeb890 ffffffff80ef0000 0000000000000000
Dec 11 15:05:29 gw kernel: 	  8000000041a73580 fffffffffffffffc 800000004cbf9000 8000000036122142
Dec 11 15:05:29 gw kernel: 	  000000000000015a ffffffff80d313f8 0000000000000001 800000004cbf9000
Dec 11 15:05:29 gw kernel: 	  0000000000000005 0000000000000001 0000000000000000 ffffffff80ee0000
Dec 11 15:05:29 gw kernel: 	  800000004c264000 800000004c267880 8000000049c14c80 ffffffff80b4c44c
Dec 11 15:05:29 gw kernel: 	  800000004c25aa10 ffffffff80cc1c98 0000000000000003 0000000000000000
Dec 11 15:05:29 gw kernel: 	  0000000000000000 ffffffff8085f674 0000000000000000 0000000000000000
Dec 11 15:05:29 gw kernel: 	  ...
Dec 11 15:05:29 gw kernel: Call Trace:
Dec 11 15:05:29 gw kernel: [<ffffffff8085f674>] show_stack+0x6c/0xf8
Dec 11 15:05:29 gw kernel: [<ffffffff80b4c44c>] skb_push+0xa4/0xb0
Dec 11 15:05:29 gw kernel: [<ffffffff80bfecc8>] packet_rcv+0xe0/0x470
Dec 11 15:05:29 gw kernel: [<ffffffff80b56af4>] __netif_receive_skb_core+0x59c/0x8a8
Dec 11 15:05:29 gw kernel: [<ffffffff80b5a9cc>] process_backlog+0xbc/0x1b8
Dec 11 15:05:29 gw kernel: [<ffffffff80b5b360>] net_rx_action+0x220/0x2b0
Dec 11 15:05:29 gw kernel: [<ffffffff80885048>] __do_softirq+0x1d0/0x218
Dec 11 15:05:29 gw kernel: [<ffffffff80885158>] do_softirq+0x68/0x70
Dec 11 15:05:29 gw kernel: [<ffffffff808857b8>] irq_exit+0x68/0x78
Dec 11 15:05:29 gw kernel: [<ffffffff8080697c>] plat_irq_dispatch+0x4c/0xe0
Dec 11 15:05:29 gw kernel: [<ffffffff8085ae34>] handle_int+0x114/0x11c
Dec 11 15:05:29 gw kernel: 
Dec 11 15:05:29 gw kernel: skbuff: Gotcha2 8000000036122000 8000000036122142 -4
Dec 11 15:05:29 gw kernel: CPU: 3 PID: 0 Comm: swapper/3 Tainted: P        W  O 3.10.107-UBNT #1
Dec 11 15:05:29 gw kernel: Stack : 000000000000011c 0000000014009ce1 0000000010200040 0000000000000007
Dec 11 15:05:29 gw kernel: 	  0000000000000000 0000000000000000 ffffffff80ef0000 000000000000011c
Dec 11 15:05:29 gw kernel: 	  ffffffff80ee65d8 ffffffff80da0000 000000000000011c 302e3130372d5542
Dec 11 15:05:29 gw kernel: 	  0000000000000005 ffffffff80eebf08 ffffffff80ef0000 0000000000000000
Dec 11 15:05:29 gw kernel: 	  8000000041a73580 fffffffffffffffc 800000004cbf9000 8000000036122142
Dec 11 15:05:29 gw kernel: 	  000000000000015a 0000000000000800 0000000000000000 800000004cbf9000
Dec 11 15:05:29 gw kernel: 	  0000000000000005 0000000000000001 0000000000000000 ffffffff80ef6a08
Dec 11 15:05:29 gw kernel: 	  800000004c264000 800000004c267880 0000000000000000 ffffffff80b4c44c
Dec 11 15:05:29 gw kernel: 	  800000004c25aa10 ffffffff80cc1c98 0000000000000003 0000000000000000
Dec 11 15:05:29 gw kernel: 	  0000000000000000 ffffffff8085f674 0000000000000000 0000000000000000
Dec 11 15:05:29 gw kernel: 	  ...
Dec 11 15:05:29 gw kernel: Call Trace:
Dec 11 15:05:29 gw kernel: [<ffffffff8085f674>] show_stack+0x6c/0xf8
Dec 11 15:05:29 gw kernel: [<ffffffff80b4c44c>] skb_push+0xa4/0xb0
Dec 11 15:05:29 gw kernel: [<ffffffff80bfecc8>] packet_rcv+0xe0/0x470
Dec 11 15:05:29 gw kernel: [<ffffffff80b569c4>] __netif_receive_skb_core+0x46c/0x8a8
Dec 11 15:05:29 gw kernel: [<ffffffff80b5a9cc>] process_backlog+0xbc/0x1b8
Dec 11 15:05:29 gw kernel: [<ffffffff80b5b360>] net_rx_action+0x220/0x2b0
Dec 11 15:05:29 gw kernel: [<ffffffff80885048>] __do_softirq+0x1d0/0x218
Dec 11 15:05:29 gw kernel: [<ffffffff80885158>] do_softirq+0x68/0x70
Dec 11 15:05:29 gw kernel: [<ffffffff808857b8>] irq_exit+0x68/0x78
Dec 11 15:05:29 gw kernel: [<ffffffff8080697c>] plat_irq_dispatch+0x4c/0xe0
Dec 11 15:05:29 gw kernel: [<ffffffff8085ae34>] handle_int+0x114/0x11c
Dec 11 15:05:29 gw kernel: 
Dec 11 15:05:32 gw kernel: skbuff: Gotcha2 8000000036164000 8000000036164142 -4
Dec 11 15:05:32 gw kernel: CPU: 3 PID: 0 Comm: swapper/3 Tainted: P        W  O 3.10.107-UBNT #1
Dec 11 15:05:32 gw kernel: Stack : 000000000000012c 0000000014009ce1 0000000010200040 0000000000000007
Dec 11 15:05:32 gw kernel: 	  0000000000000000 0000000000000000 ffffffff80ef0000 000000000000012c
Dec 11 15:05:32 gw kernel: 	  ffffffff80ee65d8 ffffffff80da0000 000000000000012c 302e3130372d5542
Dec 11 15:05:32 gw kernel: 	  0000000000000005 ffffffff80eec580 ffffffff80ef0000 0000000000000000
Dec 11 15:05:32 gw kernel: 	  80000000394b7380 fffffffffffffffc 800000004cbf9000 8000000036164142
Dec 11 15:05:32 gw kernel: 	  000000000000015a ffffffff80d313f8 0000000000000001 800000004cbf9000
Dec 11 15:05:32 gw kernel: 	  0000000000000005 0000000000000001 800000004c267e10 800000004c267e10
Dec 11 15:05:32 gw kernel: 	  800000004c264000 800000004c267880 8000000049c14c80 ffffffff80b4c44c
Dec 11 15:05:32 gw kernel: 	  800000004c25aa10 ffffffff80cc1c98 0000000000000003 0000000000000000
Dec 11 15:05:32 gw kernel: 	  0000000000000000 ffffffff8085f674 0000000000000000 0000000000000000
Dec 11 15:05:32 gw kernel: 	  ...
Dec 11 15:05:32 gw kernel: Call Trace:
Dec 11 15:05:32 gw kernel: [<ffffffff8085f674>] show_stack+0x6c/0xf8
Dec 11 15:05:32 gw kernel: [<ffffffff80b4c44c>] skb_push+0xa4/0xb0
Dec 11 15:05:32 gw kernel: [<ffffffff80bfecc8>] packet_rcv+0xe0/0x470
Dec 11 15:05:32 gw kernel: [<ffffffff80b56af4>] __netif_receive_skb_core+0x59c/0x8a8
Dec 11 15:05:32 gw kernel: [<ffffffff80b5a9cc>] process_backlog+0xbc/0x1b8
Dec 11 15:05:32 gw kernel: [<ffffffff80b5b360>] net_rx_action+0x220/0x2b0
Dec 11 15:05:32 gw kernel: [<ffffffff80885048>] __do_softirq+0x1d0/0x218
Dec 11 15:05:32 gw kernel: [<ffffffff80885158>] do_softirq+0x68/0x70
Dec 11 15:05:32 gw kernel: [<ffffffff808857b8>] irq_exit+0x68/0x78
Dec 11 15:05:32 gw kernel: [<ffffffff8080697c>] plat_irq_dispatch+0x4c/0xe0
Dec 11 15:05:32 gw kernel: [<ffffffff8085ae34>] handle_int+0x114/0x11c
Dec 11 15:05:32 gw kernel: 
Dec 11 15:05:32 gw kernel: skbuff: Gotcha2 8000000036164000 8000000036164142 -4
Dec 11 15:05:32 gw kernel: CPU: 3 PID: 0 Comm: swapper/3 Tainted: P        W  O 3.10.107-UBNT #1
Dec 11 15:05:32 gw kernel: Stack : 000000000000013c 0000000014009ce1 0000000010200040 ffffffff80d9c520
Dec 11 15:05:32 gw kernel: 	  0000000000000000 0000000000000000 ffffffff80ef0000 000000000000013c
Dec 11 15:05:32 gw kernel: 	  ffffffff80ee65d8 ffffffff80da0000 000000000000013c 302e3130372d5542
Dec 11 15:05:32 gw kernel: 	  0000000000000005 ffffffff80eecbf8 ffffffff80ef0000 0000000000000000
Dec 11 15:05:32 gw kernel: 	  80000000394b7380 fffffffffffffffc 800000004cbf9000 8000000036164142
Dec 11 15:05:32 gw kernel: 	  000000000000015a 0000000000000800 0000000000000000 800000004cbf9000
Dec 11 15:05:32 gw kernel: 	  0000000000000005 0000000000000001 0000000000000000 ffffffff80ee0000
Dec 11 15:05:32 gw kernel: 	  800000004c264000 800000004c267880 0000000000000000 ffffffff80b4c44c
Dec 11 15:05:32 gw kernel: 	  800000004c25aa10 ffffffff80cc1c98 0000000000000003 0000000000000000
Dec 11 15:05:32 gw kernel: 	  0000000000000000 ffffffff8085f674 0000000000000000 0000000000000000
Dec 11 15:05:32 gw kernel: 	  ...
Dec 11 15:05:32 gw kernel: Call Trace:
Dec 11 15:05:32 gw kernel: [<ffffffff8085f674>] show_stack+0x6c/0xf8
Dec 11 15:05:32 gw kernel: [<ffffffff80b4c44c>] skb_push+0xa4/0xb0
Dec 11 15:05:32 gw kernel: [<ffffffff80bfecc8>] packet_rcv+0xe0/0x470
Dec 11 15:05:32 gw kernel: [<ffffffff80b569c4>] __netif_receive_skb_core+0x46c/0x8a8
Dec 11 15:05:32 gw kernel: [<ffffffff80b5a9cc>] process_backlog+0xbc/0x1b8
Dec 11 15:05:32 gw kernel: [<ffffffff80b5b360>] net_rx_action+0x220/0x2b0
Dec 11 15:05:32 gw kernel: [<ffffffff80885048>] __do_softirq+0x1d0/0x218
Dec 11 15:05:32 gw kernel: [<ffffffff80885158>] do_softirq+0x68/0x70
Dec 11 15:05:32 gw kernel: [<ffffffff808857b8>] irq_exit+0x68/0x78
Dec 11 15:05:32 gw kernel: [<ffffffff8080697c>] plat_irq_dispatch+0x4c/0xe0
Dec 11 15:05:32 gw kernel: [<ffffffff8085ae34>] handle_int+0x114/0x11c
Dec 11 15:05:32 gw kernel: 
Dec 11 17:20:10 gw dhcpd: Abandoning IP address 10.0.20.122: pinged before offer
Dec 11 19:46:52 gw kernel: skbuff: Gotcha2 80000000417a1000 80000000417a1142 -4
Dec 11 19:46:52 gw kernel: CPU: 3 PID: 0 Comm: swapper/3 Tainted: P        W  O 3.10.107-UBNT #1
Dec 11 19:46:52 gw kernel: Stack : 000000000000014c 0000000014009ce1 0000000010200040 ffffffff80d9c520
Dec 11 19:46:52 gw kernel: 	  0000000000000000 0000000000000000 ffffffff80ef0000 000000000000014c
Dec 11 19:46:52 gw kernel: 	  ffffffff80ee65d8 ffffffff80da0000 000000000000014c 302e3130372d5542
Dec 11 19:46:52 gw kernel: 	  0000000000000005 ffffffff80eed270 ffffffff80ef0000 0000000000000000
Dec 11 19:46:52 gw kernel: 	  800000004c9d8780 fffffffffffffffc 800000004cbf9000 80000000417a1142
Dec 11 19:46:52 gw kernel: 	  000000000000015a ffffffff80d313f8 0000000000000001 800000004cbf9000
Dec 11 19:46:52 gw kernel: 	  0000000000000005 0000000000000001 0000000000000000 ffffffff80ee0000
Dec 11 19:46:52 gw kernel: 	  800000004c264000 800000004c267880 8000000049c14c80 ffffffff80b4c44c
Dec 11 19:46:52 gw kernel: 	  800000004c25aa10 ffffffff80cc1c98 0000000000000003 0000000000000000
Dec 11 19:46:52 gw kernel: 	  0000000000000000 ffffffff8085f674 0000000000000000 0000000000000000
Dec 11 19:46:52 gw kernel: 	  ...
Dec 11 19:46:52 gw kernel: Call Trace:
Dec 11 19:46:52 gw kernel: [<ffffffff8085f674>] show_stack+0x6c/0xf8
Dec 11 19:46:52 gw kernel: [<ffffffff80b4c44c>] skb_push+0xa4/0xb0
Dec 11 19:46:52 gw kernel: [<ffffffff80bfecc8>] packet_rcv+0xe0/0x470
Dec 11 19:46:52 gw kernel: [<ffffffff80b56af4>] __netif_receive_skb_core+0x59c/0x8a8
Dec 11 19:46:52 gw kernel: [<ffffffff80b5a9cc>] process_backlog+0xbc/0x1b8
Dec 11 19:46:52 gw kernel: [<ffffffff80b5b360>] net_rx_action+0x220/0x2b0
Dec 11 19:46:52 gw kernel: [<ffffffff80885048>] __do_softirq+0x1d0/0x218
Dec 11 19:46:52 gw kernel: [<ffffffff80885158>] do_softirq+0x68/0x70
Dec 11 19:46:52 gw kernel: [<ffffffff808857b8>] irq_exit+0x68/0x78
Dec 11 19:46:52 gw kernel: [<ffffffff8080697c>] plat_irq_dispatch+0x4c/0xe0
Dec 11 19:46:52 gw kernel: [<ffffffff8085ae34>] handle_int+0x114/0x11c
Dec 11 19:46:52 gw kernel: 
Dec 11 19:46:52 gw kernel: skbuff: Gotcha2 80000000417a1000 80000000417a1142 -4
Dec 11 19:46:52 gw kernel: CPU: 3 PID: 0 Comm: swapper/3 Tainted: P        W  O 3.10.107-UBNT #1
Dec 11 19:46:52 gw kernel: Stack : 000000000000015c 0000000014009ce1 0000000010200040 0000000000000007
Dec 11 19:46:52 gw kernel: 	  0000000000000000 0000000000000000 ffffffff80ef0000 000000000000015c
Dec 11 19:46:52 gw kernel: 	  ffffffff80ee65d8 ffffffff80da0000 000000000000015c 302e3130372d5542
Dec 11 19:46:52 gw kernel: 	  0000000000000005 ffffffff80eed8e8 ffffffff80ef0000 0000000000000000
Dec 11 19:46:52 gw kernel: 	  800000004c9d8780 fffffffffffffffc 800000004cbf9000 80000000417a1142
Dec 11 19:46:52 gw kernel: 	  000000000000015a 0000000000000800 0000000000000000 800000004cbf9000
Dec 11 19:46:52 gw kernel: 	  0000000000000005 0000000000000001 0000000000000000 ffffffff80ee0000
Dec 11 19:46:52 gw kernel: 	  800000004c264000 800000004c267880 0000000000000000 ffffffff80b4c44c
Dec 11 19:46:52 gw kernel: 	  800000004c25aa10 ffffffff80cc1c98 0000000000000003 0000000000000000
Dec 11 19:46:52 gw kernel: 	  0000000000000000 ffffffff8085f674 0000000000000000 0000000000000000
Dec 11 19:46:52 gw kernel: 	  ...
Dec 11 19:46:52 gw kernel: Call Trace:
Dec 11 19:46:52 gw kernel: [<ffffffff8085f674>] show_stack+0x6c/0xf8
Dec 11 19:46:52 gw kernel: [<ffffffff80b4c44c>] skb_push+0xa4/0xb0
Dec 11 19:46:52 gw kernel: [<ffffffff80bfecc8>] packet_rcv+0xe0/0x470
Dec 11 19:46:52 gw kernel: [<ffffffff80b569c4>] __netif_receive_skb_core+0x46c/0x8a8
Dec 11 19:46:52 gw kernel: [<ffffffff80b5a9cc>] process_backlog+0xbc/0x1b8
Dec 11 19:46:52 gw kernel: [<ffffffff80b5b360>] net_rx_action+0x220/0x2b0
Dec 11 19:46:52 gw kernel: [<ffffffff80885048>] __do_softirq+0x1d0/0x218
Dec 11 19:46:52 gw kernel: [<ffffffff80885158>] do_softirq+0x68/0x70
Dec 11 19:46:52 gw kernel: [<ffffffff808857b8>] irq_exit+0x68/0x78
Dec 11 19:46:52 gw kernel: [<ffffffff8080697c>] plat_irq_dispatch+0x4c/0xe0
Dec 11 19:46:52 gw kernel: [<ffffffff8085ae34>] handle_int+0x114/0x11c
Dec 11 19:46:52 gw kernel: 
Dec 11 19:46:52 gw kernel: skbuff: Gotcha2 8000000041bf4000 8000000041bf4142 -4
Dec 11 19:46:52 gw kernel: CPU: 3 PID: 0 Comm: swapper/3 Tainted: P        W  O 3.10.107-UBNT #1
Dec 11 19:46:52 gw kernel: Stack : 000000000000016c 0000000014009ce1 0000000010200040 ffffffff80d9c520
Dec 11 19:46:52 gw kernel: 	  0000000000000000 0000000000000000 ffffffff80ef0000 000000000000016c
Dec 11 19:46:52 gw kernel: 	  ffffffff80ee65d8 ffffffff80da0000 000000000000016c 302e3130372d5542
Dec 11 19:46:52 gw kernel: 	  0000000000000005 ffffffff80eedf60 ffffffff80ef0000 0000000000000000
Dec 11 19:46:52 gw kernel: 	  800000004ca5a280 fffffffffffffffc 800000004cbf9000 8000000041bf4142
Dec 11 19:46:52 gw kernel: 	  000000000000015a ffffffff80d313f8 0000000000000001 800000004cbf9000
Dec 11 19:46:52 gw kernel: 	  0000000000000005 0000000000000001 0000000000000000 ffffffff80ee0000
Dec 11 19:46:52 gw kernel: 	  800000004c264000 800000004c267880 8000000049c14c80 ffffffff80b4c44c
Dec 11 19:46:52 gw kernel: 	  800000004c25aa10 ffffffff80cc1c98 0000000000000003 0000000000000000
Dec 11 19:46:52 gw kernel: 	  0000000000000000 ffffffff8085f674 0000000000000000 0000000000000000
Dec 11 19:46:52 gw kernel: 	  ...
Dec 11 19:46:52 gw kernel: Call Trace:
Dec 11 19:46:52 gw kernel: [<ffffffff8085f674>] show_stack+0x6c/0xf8
Dec 11 19:46:52 gw kernel: [<ffffffff80b4c44c>] skb_push+0xa4/0xb0
Dec 11 19:46:52 gw kernel: [<ffffffff80bfecc8>] packet_rcv+0xe0/0x470
Dec 11 19:46:52 gw kernel: [<ffffffff80b56af4>] __netif_receive_skb_core+0x59c/0x8a8
Dec 11 19:46:52 gw kernel: [<ffffffff80b5a9cc>] process_backlog+0xbc/0x1b8
Dec 11 19:46:52 gw kernel: [<ffffffff80b5b360>] net_rx_action+0x220/0x2b0
Dec 11 19:46:52 gw kernel: [<ffffffff80885048>] __do_softirq+0x1d0/0x218
Dec 11 19:46:52 gw kernel: [<ffffffff80885158>] do_softirq+0x68/0x70
Dec 11 19:46:52 gw kernel: [<ffffffff808857b8>] irq_exit+0x68/0x78
Dec 11 19:46:52 gw kernel: [<ffffffff8080697c>] plat_irq_dispatch+0x4c/0xe0
Dec 11 19:46:52 gw kernel: [<ffffffff8085ae34>] handle_int+0x114/0x11c
Dec 11 19:46:52 gw kernel: 
Dec 11 19:46:52 gw kernel: skbuff: Gotcha2 8000000041bf4000 8000000041bf4142 -4
Dec 11 19:46:52 gw kernel: CPU: 3 PID: 0 Comm: swapper/3 Tainted: P        W  O 3.10.107-UBNT #1
Dec 11 19:46:52 gw kernel: Stack : 000000000000017c 0000000014009ce1 0000000010200040 0000000000000007
Dec 11 19:46:52 gw kernel: 	  0000000000000000 0000000000000000 ffffffff80ef0000 000000000000017c
Dec 11 19:46:52 gw kernel: 	  ffffffff80ee65d8 ffffffff80da0000 000000000000017c 302e3130372d5542
Dec 11 19:46:52 gw kernel: 	  0000000000000005 ffffffff80eee5d8 ffffffff80ef0000 0000000000000000
Dec 11 19:46:52 gw kernel: 	  800000004ca5a280 fffffffffffffffc 800000004cbf9000 8000000041bf4142
Dec 11 19:46:52 gw kernel: 	  000000000000015a 0000000000000800 0000000000000000 800000004cbf9000
Dec 11 19:46:52 gw kernel: 	  0000000000000005 0000000000000001 0000000000000000 ffffffff80ee0000
Dec 11 19:46:52 gw kernel: 	  800000004c264000 800000004c267880 0000000000000000 ffffffff80b4c44c
Dec 11 19:46:52 gw kernel: 	  800000004c25aa10 ffffffff80cc1c98 0000000000000003 0000000000000000
Dec 11 19:46:52 gw kernel: 	  0000000000000000 ffffffff8085f674 0000000000000000 0000000000000000
Dec 11 19:46:52 gw kernel: 	  ...
Dec 11 19:46:52 gw kernel: Call Trace:
Dec 11 19:46:52 gw kernel: [<ffffffff8085f674>] show_stack+0x6c/0xf8
Dec 11 19:46:52 gw kernel: [<ffffffff80b4c44c>] skb_push+0xa4/0xb0
Dec 11 19:46:52 gw kernel: [<ffffffff80bfecc8>] packet_rcv+0xe0/0x470
Dec 11 19:46:52 gw kernel: [<ffffffff80b569c4>] __netif_receive_skb_core+0x46c/0x8a8
Dec 11 19:46:52 gw kernel: [<ffffffff80b5a9cc>] process_backlog+0xbc/0x1b8
Dec 11 19:46:52 gw kernel: [<ffffffff80b5b360>] net_rx_action+0x220/0x2b0
Dec 11 19:46:52 gw kernel: [<ffffffff80885048>] __do_softirq+0x1d0/0x218
Dec 11 19:46:52 gw kernel: [<ffffffff80885158>] do_softirq+0x68/0x70
Dec 11 19:46:52 gw kernel: [<ffffffff808857b8>] irq_exit+0x68/0x78
Dec 11 19:46:52 gw kernel: [<ffffffff8080697c>] plat_irq_dispatch+0x4c/0xe0
Dec 11 19:46:52 gw kernel: [<ffffffff8085ae34>] handle_int+0x114/0x11c
New Member
Posts: 6
Registered: ‎10-22-2017
Kudos: 1

Re: EdgeMAX EdgeRouter software version v1.10.8 has been released!

Working fine on ER-X after 1.10.7 -> 1.10.8 upgrade.  Did a

 

$ delete system image

 

before upgrade to free up space.

New Member
Posts: 18
Registered: ‎01-22-2015
Kudos: 8
Solutions: 2

Re: EdgeMAX EdgeRouter software version v1.10.8 has been released!

[ Edited ]

Just updated an ERX from 1.10.5 via CLI. Also updated bootloader and reinstalled wireguard. All is working. Thanks and keep up the great work!

Emerging Member
Posts: 49
Registered: ‎02-11-2018
Kudos: 1

Re: EdgeMAX EdgeRouter software version v1.10.8 has been released!

waterside , I identified what is broken several times. But , just for you, I guess you can fix this, right? :-) I'll repeat 1. link-detect doesn't work; 2. /32 network if vrrp in ospf config? really? 3. routes just disappears over ipsec+gre , randomly.
Emerging Member
Posts: 60
Registered: ‎07-15-2015
Kudos: 4
Solutions: 1

Re: EdgeMAX EdgeRouter software version v1.10.8 has been released!

[ Edited ]

Seems like static routes don't work anymore.

I've set:

# show protocols static route
 route 10.255.255.0/24 {
     next-hop 192.168.250.32 {
         description tinc
     }
 }
 route 192.168.57.0/24 {
     next-hop 192.168.250.32 {
         description remote.tinc
     }
 }

But if I do a "netstat -rn" the gateway isn't set to 192.168.250.32, but to my WAN gateway address.

 

Removing and re-setting the routes doesn't resolve the issue as the gateway is again set to my WAN gateway address.

 

For now switched back to 1.10.7 as I need the routes. With the same config, it works on 1.10.7.

EdgeRouter Lite - UniFi Switch 24 - UniFi Switch 16 POE-150W - 2x UniFi Switch 8 - UniFi AP-AC-Pro
Ubiquiti Employee
Posts: 1,229
Registered: ‎07-20-2015
Kudos: 1446
Solutions: 81

Re: EdgeMAX EdgeRouter software version v1.10.8 has been released!

@sles
> you have to fix ospf.
> I identified what is broken several times.

I must have missed those posts, could you please provide more details (or post link where those issue have been discussed).

 

> 1. link-detect doesn't work
> 2. /32 network if vrrp in ospf config
> 3. routes just disappears over ipsec+gre , randomly.
I need reproduction scenario + config so I can reproduce those issues on my lab router


@HomeServ
> Seems like static routes don't work anymore.
I made similar config with following commands:

set interfaces ethernet eth1 address 192.168.250.31/24
set protocols static route 10.255.255.0/24 next-hop 192.168.250.32 description tinc
set protocols static route 192.168.57.0/24 next-hop 192.168.250.32 description remote.tinc


... and routing table in routing daemon is correct:

$ show ip route|egrep "10.255.255|192.168.57|192.168.250"
S *> 10.255.255.0/24 [1/0] via 192.168.250.32, eth1
S *> 192.168.57.0/24 [1/0] via 192.168.250.32, eth1
C *> 192.168.250.0/24 is directly connected, eth1


... and forwarding table in kernel is also correct:

$ netstat -rn|egrep "10.255.255|192.168.57|192.168.250"
10.255.255.0 192.168.250.32 255.255.255.0 UG 0 0 0 eth1
192.168.57.0 192.168.250.32 255.255.255.0 UG 0 0 0 eth1
192.168.250.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1

> the gateway isn't set to 192.168.250.32, but to my WAN gateway address.

That would only be possible if 192.168.250.0/24 would be missing:

 

  1. Are you sure that interface towards "192.168.250.32" host is up and running (in my case it's eth1)? 
  2. Please post output of following shell commands:
    show ip route
    ip route
    show interfaces
    
Ubiquiti Employee
Posts: 1,229
Registered: ‎07-20-2015
Kudos: 1446
Solutions: 81

Re: EdgeMAX EdgeRouter software version v1.10.8 has been released!

@ogo
> Some issues after upgrading from 10.7 to 10.8 (ER-4):
1) Are you sure that you did not see those messages in v1.10.7?

 

> WARNING: at mm/slab_common.c:394 kmalloc_slab+0xcc/0xe0()
This error means that kernel/kernel-module is trying to allocate too much memory -> https://elixir.bootlin.com/linux/v3.10.108/source/mm/slab_common.c#L379

Unfortunately backrace is does not give any clue what caused this.

 

2) How often do you see this errors?
3) Does it cause system crash?

 

> skbuff: Gotcha2 8000000036164000 8000000036164142 -4
> Dec 11 15:05:32 gw kernel: [<ffffffff8085f674>] show_stack+0x6c/0xf8
> Dec 11 15:05:32 gw kernel: [<ffffffff80b4c44c>] skb_push+0xa4/0xb0
> Dec 11 15:05:32 gw kernel: [<ffffffff80bfecc8>] packet_rcv+0xe0/0x470
4) Can you install "v2.0.0-beta.2" that has newer kernel (v4.9 vs v3.10) and check if you still see those messages.

Emerging Member
Posts: 60
Registered: ‎07-15-2015
Kudos: 4
Solutions: 1

Re: EdgeMAX EdgeRouter software version v1.10.8 has been released!

@UBNT-afomins, I'm currently back to 1.10.7 so can't check the settings in 1.10.8.

I hope I can upgrade again next wednesday.

 

192.168.250.32 is available and does routes traffic to the subnets set as static route (1.10.7).

eth0 is my internal lan

eth1 is my ISP (with internet over VIF 34)

eth2 is a seperate network on VIF 3

 

Currently my output:

 

homeserv@ubnt:~$ show ip route
Codes: K - kernel, C - connected, S - static, R - RIP, B - BGP
       O - OSPF, IA - OSPF inter area
       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
       E1 - OSPF external type 1, E2 - OSPF external type 2
       > - selected route, * - FIB route, p - stale info

IP Route Table for VRF "default"
S    *> 0.0.0.0/0 [210/0] via 217.19.24.1, eth1.34
C    *> 0.0.0.0/26 is directly connected, vtun2
C       0.0.0.0/26 is directly connected, vtun1
S    *> 10.255.255.0/24 [1/0] via 192.168.250.32, eth0
C    *> 127.0.0.0/8 is directly connected, lo
C    *> 172.21.16.0/26 is directly connected, eth0.21
C    *> 172.21.16.64/26 is directly connected, eth0.21
C    *> 172.21.16.128/26 is directly connected, eth0.21
C    *> 172.21.16.192/26 is directly connected, eth0.21
C    *> 192.168.11.0/24 is directly connected, eth2.3
S    *> 192.168.57.0/24 [1/0] via 192.168.250.32, eth0
C    *> 192.168.216.0/24 is directly connected, eth0.216
C    *> 192.168.250.0/24 is directly connected, eth0
C    *> 192.168.251.0/26 is directly connected, vtun1
C    *> 192.168.251.64/26 is directly connected, vtun2
C    *> 217.19.24.0/22 is directly connected, eth1.34
homeserv@ubnt:~$ ip route
0.0.0.0/26 dev vtun2  proto kernel  scope link 
default via 217.19.24.1 dev eth1.34  proto zebra 
10.255.255.0/24 via 192.168.250.32 dev eth0  proto zebra 
172.21.16.0/26 dev eth0.21  proto kernel  scope link  src 172.21.16.1 
172.21.16.64/26 dev eth0.21  proto kernel  scope link  src 172.21.16.65 
172.21.16.128/26 dev eth0.21  proto kernel  scope link  src 172.21.16.129 
172.21.16.192/26 dev eth0.21  proto kernel  scope link  src 172.21.16.193 
192.168.11.0/24 dev eth2.3  proto kernel  scope link  src 192.168.11.253 
192.168.57.0/24 via 192.168.250.32 dev eth0  proto zebra 
192.168.216.0/24 dev eth0.216  proto kernel  scope link  src 192.168.216.1 
192.168.250.0/24 dev eth0  proto kernel  scope link  src 192.168.250.253 
192.168.251.0/26 dev vtun1  proto kernel  scope link  src 192.168.251.1 
192.168.251.64/26 dev vtun2  proto kernel  scope link  src 192.168.251.65 
217.19.24.0/22 dev eth1.34  proto kernel  scope link  src 217.19.24.42 
homeserv@ubnt:~$ show interfaces
Codes: S - State, L - Link, u - Up, D - Down, A - Admin Down
Interface    IP Address                        S/L  Description                 
---------    ----------                        ---  -----------                 
eth0         192.168.250.253/24                u/u  Cust: Homeserv [1Gbit] (HS) 
             2001:470:xxxx:xxx::253:1/64      
eth0.21      172.21.16.1/26                    u/u  HSTest [1Gbit] (HSTest)     
             172.21.16.65/26                  
             172.21.16.129/26                 
             172.21.16.193/26                 
eth0.216     192.168.216.1/24                  u/u  Dliv Guest network          
eth1         -                                 u/u  Tweak [1Gbit] (ISP)         
eth1.34      217.19.24.xx/22                   u/u  Tweak [1Gbit] (ISP Internet 
                                                    VLAN)                       
eth2         -                                 u/u  Cust: Bos [1Gbit] (BosLAN)  
eth2.3       192.168.11.253/24                 u/u  BosLAN [1Gbit] (BosVLAN)    
lo           127.0.0.1/8                       u/u                              
             ::1/128                          
tun0         2001:470:xxxx:xxx::2/64           u/u  HE.NET IPv6 Tunnel          
vtun1        192.168.251.1/26                  u/u  HomeServLAN                 
vtun2        192.168.251.65/26                 u/u  HomeServLAN-UDP             

homeserv@ubnt:~$ configure
[edit]
homeserv@ubnt# show protocols static route 
 route 10.255.255.0/24 {
     next-hop 192.168.250.32 {
         description tinc.homeserv
     }
 }
 route 192.168.57.0/24 {
     next-hop 192.168.250.32 {
         description remote.tinc.homeserv
     }
 }

 

 

EdgeRouter Lite - UniFi Switch 24 - UniFi Switch 16 POE-150W - 2x UniFi Switch 8 - UniFi AP-AC-Pro
Emerging Member
Posts: 49
Registered: ‎02-11-2018
Kudos: 1

Re: EdgeMAX EdgeRouter software version v1.10.8 has been released!

New Member
Posts: 3
Registered: ‎12-17-2018

Re: EdgeMAX EdgeRouter software version v1.10.8 has been released!

I purchased the Ubiquiti EdgeRouter 4 last Friday and set it up yesterday. The only issue that I had is when I updated the firmware to the latest version (1.10.8) I had the message that it was uploading and I gave up after around 15 minutes. I never got the update completed message so I clicked cancel and tried to update the firmware again which gave me an error. I rebooted followed by trying again to update the firmware which also resulted in an error. At some point I noticed that the firmware version was now shown as the later version.

 

How do I know for sure that the firmware was properly updated?  I think that the previous (out of the box) firmware version was 1.9.8 but I don't remember for sure.  I know that the out of the box firmware date was about a year ago.

 

When I turned on one of my desktop computers today I saw the Windows message that there was no internet access.  I waiting a couple of minutes and decided to log into the router.  Around the time that I logged into the router the no internet access cleared.  Why this lag time?  Is there something that I can do to reduce or eliminated this lag time?

The router seems to be working OK. My old router gave me a throughput of about 56 mbps. My ISP nominal bandwidth is 300 mbps. My cable modem nominal bandwidth is a little over 300 mbps. My throughput is now around 260 mbps which seems reasonable.

 

Thanks in Advance.

 

Emerging Member
Posts: 72
Registered: ‎10-16-2013
Kudos: 10
Solutions: 1

Re: EdgeMAX EdgeRouter software version v1.10.8 has been released!

@UBNT-afomins Would you mind to comment on why DHCP failover still is not implemented correctly? One would think that after several years this bug should be fixed by now.

https://community.ubnt.com/t5/EdgeRouter/dhcp-failover-configuration-on-ubnt-edgemax/m-p/1503648#M10...

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

Re: EdgeMAX EdgeRouter software version v1.10.8 has been released!

@UBNT-afomins

1) yes, i'm absolutely sure that those errors appeared after I updated from 10.7 to 10.8

2) only 2 times in the past 17 days

3) system doesn't crush, but there is an error output  for offload flows (not everytime, as i mentioned in this topic: https://community.ubnt.com/t5/EdgeRouter/show-ubnt-offload-flows-fails/td-p/2582613)

admin@gw:~$ show ubnt offload flows
cat: read error: Cannot allocate memory

4) i'll try new beta and report back.

Ubiquiti Employee
Posts: 1,229
Registered: ‎07-20-2015
Kudos: 1446
Solutions: 81

Re: EdgeMAX EdgeRouter software version v1.10.8 has been released!

@TheKid7
> I rebooted followed by trying again to update the firmware which also resulted in an error.
> At some point I noticed that the firmware version was now shown as the later version.
That's weird, there should be no errors when upgrading to same version. Please show output of following shell command - show system image

 

> How do I know for sure that the firmware was properly updated?
If you see that firmware version is "v1.10.8" then it means that upgrade was successful, otherwise router would not have booted.

 

@Ryan_Hardy
> Would you mind to comment on why DHCP failover still is not implemented correctly? 
I was not aware of this issue until now. I was able to reproduce and you may find my response in linked thread.

 

New Member
Posts: 3
Registered: ‎12-17-2018

Re: EdgeMAX EdgeRouter software version v1.10.8 has been released!

I downloaded WinSCP Portable but could not figure out how to use it properly to do the shell command.  What is the proper way to do the shell command?

 

Please show output of following shell command - show system image

 

Attached are a couple of screenshots.

Ubiquity Top of GUI.jpg

 

Ubiquity System.jpg

 

Senior Member
Posts: 3,234
Registered: ‎08-06-2015
Kudos: 1383
Solutions: 186

Re: EdgeMAX EdgeRouter software version v1.10.8 has been released!


@TheKid7 wrote:

I downloaded WinSCP Portable but could not figure out how to use it properly to do the shell command.  What is the proper way to do the shell command?

 

This KB article may be of some help:  EdgeRouter - How to Access the EdgeRouter.  

You can also reach the CLI via the GUI:  At the top right of the GUI after you login you'll see a button for 'CLI', just to the left of the button for 'Toolbox'.  Click that and you'll be provided a terminal window with a login prompt.

 

From the CLI that you obtain following the KB article above you would do:

user@er:~$ show system image
The system currently has the following image(s) installed:

v1.10.8.5142441.181120.1647    (running image) (default boot) 
v1.10.7.5127970.181001.1055    

 

New Member
Posts: 3
Registered: ‎12-17-2018

Re: EdgeMAX EdgeRouter software version v1.10.8 has been released!

Attached is the screenshot.  For future, how do I copy the text from CLI to Notepad.  I marked the text to be copied followed by right click copy, followed by paste into Notepad, but the copied text did not show up in Notepad.

 

Show System Image.jpg

New Member
Posts: 32
Registered: ‎09-17-2015
Kudos: 1
Solutions: 4

Re: EdgeMAX EdgeRouter software version v1.10.8 has been released!

[ Edited ]

Hi all,

Just to make sure the bootversion for ERPOE-5, correct right?

Bootversion: (002) for ERPOE3, ERLITE3 & ER-8-XG

boot-v.png

 

re-testing downgraded firmware v1.10.8 back to v1.10.7 and not show a new or old uboot version.

 

Thanks

Emerging Member
Posts: 60
Registered: ‎07-15-2015
Kudos: 4
Solutions: 1

Re: EdgeMAX EdgeRouter software version v1.10.8 has been released!

@UBNT-afomins, just upgraded again to 1.10.8 and now the static routes seems to be set to the correct gateway.

 

homeserv@ubnt:~$ show ip route
Codes: K - kernel, C - connected, S - static, R - RIP, B - BGP
       O - OSPF, IA - OSPF inter area
       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
       E1 - OSPF external type 1, E2 - OSPF external type 2
       > - selected route, * - FIB route, p - stale info

IP Route Table for VRF "default"
S    *> 0.0.0.0/0 [210/0] via 217.19.24.1, eth1.34
C    *> 0.0.0.0/26 is directly connected, vtun2
C       0.0.0.0/26 is directly connected, vtun1
S    *> 10.255.255.0/24 [1/0] via 192.168.250.32, eth0
C    *> 127.0.0.0/8 is directly connected, lo
C    *> 172.21.16.0/26 is directly connected, eth0.21
C    *> 172.21.16.64/26 is directly connected, eth0.21
C    *> 172.21.16.128/26 is directly connected, eth0.21
C    *> 172.21.16.192/26 is directly connected, eth0.21
C    *> 192.168.11.0/24 is directly connected, eth2.3
S    *> 192.168.57.0/24 [1/0] via 192.168.250.32, eth0
C    *> 192.168.216.0/24 is directly connected, eth0.216
C    *> 192.168.250.0/24 is directly connected, eth0
C    *> 192.168.251.0/26 is directly connected, vtun1
C    *> 192.168.251.64/26 is directly connected, vtun2
C    *> 217.19.24.0/22 is directly connected, eth1.34
homeserv@ubnt:~$ ip route
0.0.0.0/26 dev vtun2  proto kernel  scope link
default via 217.19.24.1 dev eth1.34  proto zebra
10.255.255.0/24 via 192.168.250.32 dev eth0  proto zebra
172.21.16.0/26 dev eth0.21  proto kernel  scope link  src 172.21.16.1
172.21.16.64/26 dev eth0.21  proto kernel  scope link  src 172.21.16.65
172.21.16.128/26 dev eth0.21  proto kernel  scope link  src 172.21.16.129
172.21.16.192/26 dev eth0.21  proto kernel  scope link  src 172.21.16.193
192.168.11.0/24 dev eth2.3  proto kernel  scope link  src 192.168.11.253
192.168.57.0/24 via 192.168.250.32 dev eth0  proto zebra
192.168.216.0/24 dev eth0.216  proto kernel  scope link  src 192.168.216.1
192.168.250.0/24 dev eth0  proto kernel  scope link  src 192.168.250.253
192.168.251.0/26 dev vtun1  proto kernel  scope link  src 192.168.251.1
192.168.251.64/26 dev vtun2  proto kernel  scope link  src 192.168.251.65
217.19.24.0/22 dev eth1.34  proto kernel  scope link  src 217.19.24.42
homeserv@ubnt:~$ show interfaces
Codes: S - State, L - Link, u - Up, D - Down, A - Admin Down
Interface    IP Address                        S/L  Description
---------    ----------                        ---  -----------
eth0         192.168.250.253/24                u/u  Cust: Homeserv [1Gbit] (HS)
             2001:470:xxxx:xxx::253:1/64
eth0.21      172.21.16.1/26                    u/u  HSTest [1Gbit] (HSTest)
             172.21.16.65/26
             172.21.16.129/26
             172.21.16.193/26
eth0.216     192.168.216.1/24                  u/u  Dliv Guest network
eth1         -                                 u/u  Tweak [1Gbit] (ISP)
eth1.34      217.19.24.xx/22                   u/u  Tweak [1Gbit] (ISP Internet
                                                    VLAN)
eth2         -                                 u/u  Cust: Bos [1Gbit] (BosLAN)
eth2.3       192.168.11.253/24                 u/u  BosLAN [1Gbit] (BosVLAN)
lo           127.0.0.1/8                       u/u
             ::1/128
tun0         2001:470:xxxx:xxx::2/64           u/u  HE.NET IPv6 Tunnel
vtun1        192.168.251.1/26                  u/u  HomeServLAN
vtun2        192.168.251.65/26                 u/u  HomeServLAN-UDP
EdgeRouter Lite - UniFi Switch 24 - UniFi Switch 16 POE-150W - 2x UniFi Switch 8 - UniFi AP-AC-Pro
Reply