- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Sticky This Topic
- Bookmark
- Subscribe
- Printer Friendly Page
EdgeMAX EdgeRouter software version v1.10.1 has been released!
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
a month ago
See release notes here -> https://community.ubnt.com/t5/EdgeMAX-Updates-Blog/EdgeMAX-EdgeRouter-software-release-v1-10-1/ba-p/...
Your feedback is highly appreciated
Re: EdgeMAX EdgeRouter software version v1.10.1 has been released!
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
a month ago
@UBNT-afomins Can this be pinned?
Re: EdgeMAX EdgeRouter software version v1.10.1 has been released!
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
a month ago
Seems to working fine with loadbalancing on eth and pppoe
Re: EdgeMAX EdgeRouter software version v1.10.1 has been released!
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
a month ago
Doesn't fix the gotcha2 errors I saw with 1.10 that aren't in the earlier releases. Within 2 hours of installing 1.10.1 I have 21 pages of:
Mar 21 16:20:29 ERL-Home kernel: skbuff: Gotcha2 800000041923d000 800000041923d142 -4
Mar 21 16:20:29 ERL-Home kernel: CPU: 0 PID: 0 Comm: swapper/0 Tainted: P O 3.10.107-UBNT #1
Mar 21 16:20:29 ERL-Home kernel: Stack : 00000000000000a3 0000000050008ce1 0000000000200000 0000000000000007
Mar 21 16:20:29 ERL-Home kernel: 0000000000000000 0000000000000000 ffffffffc0660000 00000000000000a3
Mar 21 16:20:29 ERL-Home kernel: ffffffffc064ec58 ffffffffc0520000 00000000000000a3 302e3130372d5542
Mar 21 16:20:29 ERL-Home kernel: 0000000000000005 ffffffffc0651998 ffffffffc0660000 0000000000000000
Mar 21 16:20:29 ERL-Home kernel: 800000041c5e9300 fffffffffffffffc 800000041caff000 800000041923d142
Mar 21 16:20:29 ERL-Home kernel: 0000000000000040 0000000000000000 0000000000000001 800000041caff000
Mar 21 16:20:29 ERL-Home kernel: 0000000000000005 0000000000000001 0000000000000000 0000000000000000
Mar 21 16:20:29 ERL-Home kernel: ffffffffc04dc000 ffffffffc04df790 0000000000000000 ffffffffc032423c
Mar 21 16:20:29 ERL-Home kernel: ffffffffc050ff60 ffffffffc0484d88 0000000000000000 0000000000000000
Mar 21 16:20:29 ERL-Home kernel: 0000000000000000 ffffffffc006f0a4 0000000000000000 0000000000000000
Mar 21 16:20:29 ERL-Home kernel: ...
Mar 21 16:20:29 ERL-Home kernel: Call Trace:
Mar 21 16:20:29 ERL-Home kernel: [<ffffffffc006f0a4>] show_stack+0x6c/0xf8
Mar 21 16:20:29 ERL-Home kernel: [<ffffffffc032423c>] skb_push+0xa4/0xb0
Mar 21 16:20:29 ERL-Home kernel: [<ffffffffc03d93a4>] packet_rcv+0xdc/0x4c0
Mar 21 16:20:29 ERL-Home kernel: [<ffffffffc032e7b0>] __netif_receive_skb_core+0x498/0x8c8
Mar 21 16:20:29 ERL-Home kernel: [<ffffffffc03329b8>] netif_receive_skb+0x28/0xa8
Mar 21 16:20:29 ERL-Home kernel: [<ffffffffc087fac8>] cvm_oct_napi_poll_38+0x4d0/0xa70 [octeon_ethernet]
Mar 21 16:20:29 ERL-Home kernel: [<ffffffffc0333230>] net_rx_action+0x228/0x2b8
Mar 21 16:20:29 ERL-Home kernel: [<ffffffffc0095294>] __do_softirq+0x1dc/0x228
Mar 21 16:20:29 ERL-Home kernel: [<ffffffffc00953b0>] do_softirq+0x68/0x70
Mar 21 16:20:29 ERL-Home kernel: [<ffffffffc0095a80>] irq_exit+0x70/0x80
Mar 21 16:20:29 ERL-Home kernel: [<ffffffffc00073a4>] plat_irq_dispatch+0x4c/0xd8
Mar 21 16:20:29 ERL-Home kernel: [<ffffffffc006a834>] handle_int+0x114/0x11c
Mar 21 16:20:29 ERL-Home kernel:
Re: EdgeMAX EdgeRouter software version v1.10.1 has been released!
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
a month ago
For the accounting data problem, seems that there is some problem now with the vlan aware disabled, the netflow are much smaller than the actual netflow. I am using the ER-X.
Re: EdgeMAX EdgeRouter software version v1.10.1 has been released!
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
a month ago
Upgrade was successful on an ER-X from 1.10.0 to 1.10.1
Re: EdgeMAX EdgeRouter software version v1.10.1 has been released!
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
a month ago
"https://www.ubnt.com/downloads/firmwares/edgemax/v1.10.x/ER-e100.v1.10.1.5067571.tar"
500 Internal Server Error
Download worked on 2nd try, - thx for new release:-)
Re: EdgeMAX EdgeRouter software version v1.10.1 has been released!
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
a month ago
https://support.google.com/chrome/answer/95647?co=GENIE.Platform%3DDesktop&hl=fr
https://support.mozilla.org/en-US/kb/delete-cookies-remove-info-websites-stored#w_delete-cookies-for...
Re: EdgeMAX EdgeRouter software version v1.10.1 has been released!
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
a month ago
I bought the ER X SFP because it support Load Balancing.
I've two WAN, one ADSL ( U/D are 0.56/4,34 Mbit/s ) and a 4G LTE
Some good result testing with both connexions (ADSL on Eth0, LTE on Eth1) :
http://www.speedtest.net/result/7163688129
http://www.speedtest.net/result/7163695332
Only with the LTE :
http://www.speedtest.net/result/7163698943
sometimes, my upload bandwith is very low (near 0.56 Mbit/s), I believe it use my ADSL and don't "switch" too the LTE one.
So it will be great to allow, in the future, spillover load balancing,
In my case I would like to use ADSL first and if this connexion is surcharged, use the LTE one which is data month limited.
Anyway it look like it work great, and maybe it work better letting the router switching.
Re: EdgeMAX EdgeRouter software version v1.10.1 has been released!
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
a month ago
Upgarde all went well on my Egderouter x.
I do wish there was a way to keep all the custom configurations though.
Re: EdgeMAX EdgeRouter software version v1.10.1 has been released!
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
a month ago
Hi,
I am experiancing problems after upgrading from 1.9.7-hf4 to 1.10.1 with address groups in my load balanced with failover setup.
eth0 -> ISP - Bahnhof
eth1 -> ISP - Comhem
eth2-4 -> Local LAN
192.168.21.0/24 is the local LAN.
I am using the exact same configuration for both firmware versions but with very different results, the address groups does not work in 1.10.1.
The setup
All IPs that are not defined in the below address groups are "Load balanced" between eth0 and eth1.
Address group "LB-Bahnhof clients" forced all definied IP´s out on eth0
Address group "LB-Comhem clients" forced all definied IP´s out on eth1
Have I made a "boo boo" earlier that did not show in 1.9.7-hf4 or have I discovered a bug?
Thanks for all you hard work! <3
Here is a traceroute from 192.168.21.12 (that should have been passed out on "bahnhof" and not "comhem":
pi@mini:~ $ ip address 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether b8:27:eb:c6:45:43 brd ff:ff:ff:ff:ff:ff inet 192.168.21.12/24 brd 192.168.21.255 scope global eth0 valid_lft forever preferred_lft forever inet 169.254.148.114/16 brd 169.254.255.255 scope global eth0 valid_lft forever preferred_lft forever inet6 fe80::c400:13e9:b96e:167d/64 scope link valid_lft forever preferred_lft forever pi@mini:~ $ traceroute ping.sunet.se traceroute to ping.sunet.se (192.36.125.18), 30 hops max, 60 byte packets 1 snubben.my.home.network.net (192.168.21.1) 0.652 ms 0.732 ms 0.922 ms 2 213.200.142.59 (213.200.142.59) 6.822 ms 8.781 ms 8.704 ms 3 ksk-bbr-2-be10-10.net.comhem.se (213.200.164.177) 9.121 ms 9.047 ms 9.698 ms 4 mtc-core-1-be124.net.comhem.se (213.200.163.21) 14.296 ms 14.193 ms 13.958 ms 5 mtc-peer-1-be1.net.comhem.se (213.200.162.36) 14.874 ms 14.807 ms 14.968 ms 6 ping.sunet.se (192.36.125.18) 14.900 ms 13.664 ms 15.331 ms pi@mini:~ $
Below is my full configuration:
admin@myrouter:~$ show configuration firewall { all-ping enable broadcast-ping disable group { address-group LB-Bahnhof-clients { address 192.168.21.2-192.168.21.13 address 192.168.21.70-192.168.21.99 address 192.168.21.252-192.168.21.254 address 192.168.21.20-192.168.21.29 description "Bahnhof clients only" } address-group LB-Comhem-clients { address 192.168.21.16-192.168.21.19 address 192.168.21.100-192.168.21.140 description "Comhem client only" } network-group PRIVATE_NETS { network 192.168.0.0/16 network 172.16.0.0/12 network 10.0.0.0/8 } } ipv6-receive-redirects disable ipv6-src-route disable ip-src-route disable log-martians disable modify balance { rule 10 { action modify description "do NOT load balance lan to lan" destination { group { network-group PRIVATE_NETS } } modify { table main } } rule 11 { action modify modify { lb-group LB-Comhem } source { group { address-group LB-Comhem-clients } } } rule 12 { action modify modify { lb-group LB-Bahnhof } source { group { address-group LB-Bahnhof-clients } } } rule 20 { action modify description "do NOT load balance destination public address" destination { group { address-group ADDRv4_eth0 } } modify { table main } } rule 30 { action modify description "do NOT load balance destination public address" destination { group { address-group ADDRv4_eth1 } } modify { table main } } rule 70 { action modify modify { lb-group G } } } 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 1 { action accept description "Allow established/related" state { established enable related enable } } rule 10 { action drop description "Drop invalid state" state { invalid enable } } } receive-redirects disable send-redirects enable source-validation disable syn-cookies enable } interfaces { ethernet eth0 { address dhcp description "Bahnhof WAN" dhcp-options { default-route update default-route-distance 210 name-server no-update } duplex auto firewall { in { modify balance name WAN_IN } local { name WAN_LOCAL } } poe { output off } speed auto } ethernet eth1 { address dhcp description "Comhem WAN" dhcp-options { default-route update default-route-distance 210 name-server no-update } duplex auto firewall { in { name WAN_IN } local { name WAN_LOCAL } } poe { output off } speed auto } ethernet eth2 { duplex auto poe { output off } speed auto } ethernet eth3 { duplex auto poe { output off } speed auto } ethernet eth4 { duplex auto poe { output 48v } speed auto } loopback lo { } switch switch0 { address 192.168.21.1/24 description Local firewall { in { modify balance } } mtu 1500 switch-port { interface eth2 { } interface eth3 { } interface eth4 { } vlan-aware disable } } } load-balance { group G { interface eth0 { route-test { initial-delay 60 interval 10 type { ping { target 192.36.125.18 } } } weight 50 } interface eth1 { route-test { initial-delay 60 interval 10 type { ping { target 192.36.125.18 } } } weight 50 } lb-local enable lb-local-metric-change disable sticky { dest-addr enable dest-port enable proto disable source-addr enable source-port disable } } group LB-Bahnhof { interface eth0 { } interface eth1 { failover-only } lb-local enable lb-local-metric-change disable } group LB-Comhem { interface eth0 { failover-only } interface eth1 { } lb-local enable lb-local-metric-change disable } } port-forward { auto-firewall enable hairpin-nat enable lan-interface switch0 rule 1 { description "box web 80" forward-to { address 192.168.21.12 port 80 } original-port 80 protocol tcp_udp } protocols { static { interface-route 192.168.22.0/24 { next-hop-interface eth1 { description "Till 4G routern" distance 1 } } } } service { dns { forwarding { cache-size 150 listen-on switch0 } } gui { http-port 80 https-port 443 older-ciphers enable } nat { rule 5000 { description "masquerade for WAN" outbound-interface eth0 type masquerade } rule 5002 { description "masquerade for WAN 2" outbound-interface eth1 type masquerade } } snmp { community public { authorization ro } contact tub location tubs } ssh { port 22 protocol-version v2 } } system { conntrack { expect-table-size 4096 hash-size 4096 table-size 32768 tcp { half-open-connections 512 loose enable max-retrans 3 } } domain-name my.home.network.net host-name myrouter login { user admin { authentication { encrypted-password **************** } level admin } } name-server 192.168.21.12 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 Europe/Stockholm }
Re: EdgeMAX EdgeRouter software version v1.10.1 has been released!
[ Edited ]- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
a month ago - last edited a month ago
Upgraded our test ER-Lite from 1.10.0
During the upgrade we lost the system name-server settings. Well they were still shown in the gui config but non-functional. On attempting to delete them in the gui and then reset them gave an error in the alerts that they were unable to be set. Setting them via the CLI worked a charm.
Otherwise all seems to be functioning as expected and loadbalancing/failover working well.
Re: EdgeMAX EdgeRouter software version v1.10.1 has been released!
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
a month ago
Upgraded 1 ER5-POE
Had issues with DHCP just dropping and routing stopping.
reboot sorts out but happened twice now.
investigating
Re: EdgeMAX EdgeRouter software version v1.10.1 has been released!
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
a month ago
Re: EdgeMAX EdgeRouter software version v1.10.1 has been released!
[ Edited ]- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
a month ago - last edited a month ago
@thy030
> For the accounting data problem, seems that there is some problem now with the vlan aware disabled, the netflow are much smaller than the actual netflow. I am using the ER-X.
- Is this regression in 1.10.1 or it was like this in previous release (1.10.0 and 1.9.7+hotfix.4)?
- Please post your configuration
- Please provide numbers showing how inaccurate is netflow?
- Does netflow show wrong numbers with low throughput (less than 1mbps)?
@leakim
> sometimes, my upload bandwith is very low (near 0.56 Mbit/s), I believe it use my ADSL and don't "switch" too the LTE one.
> So it will be great to allow, in the future, spillover load balancing,
Please show following data when LB is using ADSL instead of LTE:
- show configuration
- show load-balance status
- show load-balance watchdog
@briantetlow
> I do wish there was a way to keep all the custom configurations though.
What do you mean by "custom configurations"?
If you are talking about preserving manual changes files in "/etc" then we are not going to support that.
@1enginepilot
> Doesn't fix the gotcha2 errors I saw with 1.10 that aren't in the earlier releases. Within 2 hours of installing 1.10.1 I have 21 pages of:
Yeah, we did not address this issue yet.
@tubstr
> I am experiancing problems after upgrading from 1.9.7-hf4 to 1.10.1 with address groups in my load balanced with failover setup.
I tested LoadBalance with address-groups in my test network and did not notice any problems.
Please provide additiona symproms:
- show load-balance watchdog
- show load-balance status
- show firewall modify balance
> Have I made a "boo boo" earlier that did not show in 1.9.7-hf4 or have I discovered a bug?
You config looks correct except for "ethernet eth0 firewall in modify balance" rule? I don't understand what is the purpose of this rule?
> During the upgrade we lost the system name-server settings.
Please show you name-server configuration before upgrade. You can get it from previous firmware partition here -> "cat /root.dev/w.o/config/config.boot"
@innermotion
> Had issues with DHCP just dropping and routing stopping.
1) Are you talking about DHCP server or DHCP client?
2) What do you mean by "DHCP just dropping"? Please elaborate.
> reboot sorts out but happened twice now.
3) Please elaborate this statement. Did ER crashed twice?
Re: EdgeMAX EdgeRouter software version v1.10.1 has been released!
[ Edited ]- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
a month ago - last edited a month ago
> Had issues with DHCP just dropping and routing stopping.
1) Are you talking about DHCP server or DHCP client?
2) What do you mean by "DHCP just dropping"? Please elaborate.
Overall all devices (wired and wireless) on the network first became unresponsive. Then shows as no internet.
Checked WAN IP was still up, so tried to refresh lease on a wired and wireless device and got self-signed IP.
ie. no DHCP response
> reboot sorts out but happened twice now.
3) Please elaborate this statement. Did ER crashed twice?
ER had not crashed as such, I restarted the ER and DHCP worked again but it has happened twice today...so far.
and just happened again...im gonna roll back to 1.10.0
Re: EdgeMAX EdgeRouter software version v1.10.1 has been released!
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
a month ago
Thank you for you feedback, I do not know either that the "balanced" line is for.. Followed a couple of tutorials and it can be an old leftover from earlier struggling attempts.
Just upgraded to 1.10.1 again, not too many packets have passed. The router just came up.
Anyhooooh,
admin@snubben:~$ show load-balance watchdog Group G eth0 status: Running pings: 4 fails: 0 run fails: 0/3 route drops: 0 ping gateway: 192.36.125.18 - REACHABLE eth1 status: Running pings: 4 fails: 0 run fails: 0/3 route drops: 0 ping gateway: 192.36.125.18 - REACHABLE Group LB-Bahnhof eth0 status: Running pings: 4 fails: 0 run fails: 0/3 route drops: 0 ping gateway: ping.ubnt.com - REACHABLE eth1 status: Running failover-only mode pings: 4 fails: 0 run fails: 0/3 route drops: 0 ping gateway: ping.ubnt.com - REACHABLE Group LB-Comhem eth0 status: Running failover-only mode pings: 3 fails: 0 run fails: 0/3 route drops: 0 ping gateway: ping.ubnt.com - REACHABLE eth1 status: Running pings: 3 fails: 0 run fails: 0/3 route drops: 0 ping gateway: ping.ubnt.com - REACHABLE admin@snubben:~$
admin@snubben:~$ show load-balance status Group G interface : eth0 carrier : up status : active gateway : 155.4.238.1 route table : 201 weight : 50% flows WAN Out : 302 WAN In : 4 Local Out : 24 interface : eth1 carrier : up status : active gateway : 83.253.48.1 route table : 202 weight : 50% flows WAN Out : 253 WAN In : 0 Local Out : 6 Group LB-Bahnhof interface : eth0 carrier : up status : active gateway : 155.4.238.1 route table : 203 weight : 100% flows WAN Out : 2219 WAN In : 0 Local Out : 0 interface : eth1 carrier : up status : failover gateway : 83.253.48.1 route table : 204 weight : 0% flows WAN Out : 0 WAN In : 0 Local Out : 0 Group LB-Comhem interface : eth0 carrier : up status : failover gateway : 155.4.238.1 route table : 205 weight : 0% flows WAN Out : 0 WAN In : 0 Local Out : 0 interface : eth1 carrier : up status : active gateway : 83.253.48.1 route table : 206 weight : 100% flows WAN Out : 28 WAN In : 0 Local Out : 0 admin@snubben:~$
admin@snubben:~$ show firewall modify balance IPv4 Modify Firewall "balance": Active on (switch0,IN) (eth0,IN) rule action proto packets bytes ---- ------ ----- ------- ----- 10 modify all 2791 241916 condition - match-set PRIVATE_NETS dst 11 modify all 94 4169 condition - match-set LB-Comhem-clients src 12 modify all 3545 502243 condition - match-set LB-Bahnhof-clients src 20 modify all 3064 635837 condition - match-set ADDRv4_eth0 dst 30 modify all 3 156 condition - match-set ADDRv4_eth1 dst 70 modify all 5640 740283 10000 accept all 5640 740283 admin@snubben:~$
Thank you for your support! <3
// Toby
Re: EdgeMAX EdgeRouter software version v1.10.1 has been released!
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
4 weeks ago
Is this the same as 1.10.1 hotfix that I loaded 5 days ago?
I am confused.
Re: EdgeMAX EdgeRouter software version v1.10.1 has been released!
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
4 weeks ago
I've been watching the various versions over the past 6 months and finally decided to upgrade from my very stable 1.9.1.1 directly to 1.10.1. Upgrade through the GUI very smooth, although it did take a little longer than I thought for the web interface to come up.
Router (ER-Lite) appears to be snappier in performance. CPU usage does appear to be higher than before though, alternating between 12-20% jumping to 33-40% every few seconds. Why should this be? The pulses in CPU don't seem to correlate with network traffic graphs. I'm just routing from the internet to two different internal ports. Funnily enough the pattern was similar prior to upgrading but the CPU highs and lows appeared to have lower ranges.
Re: EdgeMAX EdgeRouter software version v1.10.1 has been released!
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
4 weeks ago
@UBNT-afomins as requested - config simplified to remove unnecessary stuff:
service { dns { forwarding { cache-size 2000 listen-on eth2 options listen-address=192.168.15.254 } } } system { conntrack { expect-table-size 4096 hash-size 4096 table-size 32768 tcp { half-open-connections 512 loose enable max-retrans 3 } } domain-name internal.mydomain.net.au host-name XXX-router login { user XXX { authentication { encrypted-password XXX } level admin } } name-server 8.8.8.8 name-server 8.8.4.4 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 { } } offload { hwnat disable ipsec enable ipv4 { forwarding enable gre enable pppoe enable vlan enable } ipv6 { } } static-host-mapping { host-name XXX-router { alias gateway inet 192.168.15.254 } host-name xxx { inet 192.168.15.242 } host-name vpn-client { alias remote-user inet 192.168.16.150 } host-name xxx { inet 192.168.15.240 } } syslog { global { facility all { level notice } facility protocols { level debug } } } time-zone Australia/Sydney traffic-analysis { dpi enable export enable } } /* 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:system@4:ubnt-pptp@1:ubnt-u dapi-server@1:ubnt-unms@1:ubnt-util@1:vrrp@1:webgui@1:webproxy@1:zone-policy@1" == = */ /* Release version: v1.10.0.5056246.180125.1007 */
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Sticky This Topic
- Bookmark
- Subscribe
- Printer Friendly Page