#edgeos — Public Fediverse posts

Just weeks after me bitching that #Ubiquiti has abandoned their line of #EdgeRouter Light routers, they publish version 3.0 of #EdgeOS. You're welcome!

Frankly, the functionality is exactly the same; there's just a new CSS skin and some buttons have moved. Was hoping for better #IPv6 support in the GUI. I should dig up the changelog later.

Just weeks after me bitching that #Ubiquiti has abandoned their line of #EdgeRouter Light routers, they publish version 3.0 of #EdgeOS. You're welcome!

Frankly, the functionality is exactly the same; there's just a new CSS skin and some buttons have moved. Was hoping for better #IPv6 support in the GUI. I should dig up the changelog later.

Just weeks after me bitching that #Ubiquiti has abandoned their line of #EdgeRouter Light routers, they publish version 3.0 of #EdgeOS. You're welcome!

Frankly, the functionality is exactly the same; there's just a new CSS skin and some buttons have moved. Was hoping for better #IPv6 support in the GUI. I should dig up the changelog later.

Just weeks after me bitching that #Ubiquiti has abandoned their line of #EdgeRouter Light routers, they publish version 3.0 of #EdgeOS. You're welcome!

Frankly, the functionality is exactly the same; there's just a new CSS skin and some buttons have moved. Was hoping for better #IPv6 support in the GUI. I should dig up the changelog later.

Just weeks after me bitching that #Ubiquiti has abandoned their line of #EdgeRouter Light routers, they publish version 3.0 of #EdgeOS. You're welcome!

Frankly, the functionality is exactly the same; there's just a new CSS skin and some buttons have moved. Was hoping for better #IPv6 support in the GUI. I should dig up the changelog later.

Since #Ubiquiti has long abandoned its #EdgeRouter Lite products and abandoned #EdgeOS, what are all the cool kids using for their home #router and #firewall? Is there a community firmware for this? Or should I look around for something just as powerful? A WebUI is great, but I'm also cool with CLI.

Since #Ubiquiti has long abandoned its #EdgeRouter Lite products and abandoned #EdgeOS, what are all the cool kids using for their home #router and #firewall? Is there a community firmware for this? Or should I look around for something just as powerful? A WebUI is great, but I'm also cool with CLI.

Since #Ubiquiti has long abandoned its #EdgeRouter Lite products and abandoned #EdgeOS, what are all the cool kids using for their home #router and #firewall? Is there a community firmware for this? Or should I look around for something just as powerful? A WebUI is great, but I'm also cool with CLI.

Since #Ubiquiti has long abandoned its #EdgeRouter Lite products and abandoned #EdgeOS, what are all the cool kids using for their home #router and #firewall? Is there a community firmware for this? Or should I look around for something just as powerful? A WebUI is great, but I'm also cool with CLI.

Since #Ubiquiti has long abandoned its #EdgeRouter Lite products and abandoned #EdgeOS, what are all the cool kids using for their home #router and #firewall? Is there a community firmware for this? Or should I look around for something just as powerful? A WebUI is great, but I'm also cool with CLI.

#FBI Dismantles #Ubiquiti Router Botnet Controlled by #Russia
“Non-GRU cybercriminals installed the Moobot malware on Ubiquiti #EdgeOS routers that still used publicly known default administrator #passwords. #GRU hackers then used the #Moobot #malware to install their own bespoke scripts and files that repurposed the botnet, turning it into a global cyber #espionage platform,” agency said
https://www.securityweek.com/fbi-dismantles-ubiquiti-router-botnet-controlled-by-russian-cyberspies/ #ForestBlizzard #Sofacy #FancyBear #APT28

Please patch and change #defaultpasswords

#FBI Dismantles #Ubiquiti Router Botnet Controlled by #Russia
“Non-GRU cybercriminals installed the Moobot malware on Ubiquiti #EdgeOS routers that still used publicly known default administrator #passwords. #GRU hackers then used the #Moobot #malware to install their own bespoke scripts and files that repurposed the botnet, turning it into a global cyber #espionage platform,” agency said
https://www.securityweek.com/fbi-dismantles-ubiquiti-router-botnet-controlled-by-russian-cyberspies/ #ForestBlizzard #Sofacy #FancyBear #APT28

Please patch and change #defaultpasswords

#FBI Dismantles #Ubiquiti Router Botnet Controlled by #Russia
“Non-GRU cybercriminals installed the Moobot malware on Ubiquiti #EdgeOS routers that still used publicly known default administrator #passwords. #GRU hackers then used the #Moobot #malware to install their own bespoke scripts and files that repurposed the botnet, turning it into a global cyber #espionage platform,” agency said
https://www.securityweek.com/fbi-dismantles-ubiquiti-router-botnet-controlled-by-russian-cyberspies/ #ForestBlizzard #Sofacy #FancyBear #APT28

Please patch and change #defaultpasswords

#FBI Dismantles #Ubiquiti Router Botnet Controlled by #Russia
“Non-GRU cybercriminals installed the Moobot malware on Ubiquiti #EdgeOS routers that still used publicly known default administrator #passwords. #GRU hackers then used the #Moobot #malware to install their own bespoke scripts and files that repurposed the botnet, turning it into a global cyber #espionage platform,” agency said
https://www.securityweek.com/fbi-dismantles-ubiquiti-router-botnet-controlled-by-russian-cyberspies/ #ForestBlizzard #Sofacy #FancyBear #APT28

Please patch and change #defaultpasswords

#FBI Dismantles #Ubiquiti Router Botnet Controlled by #Russia
“Non-GRU cybercriminals installed the Moobot malware on Ubiquiti #EdgeOS routers that still used publicly known default administrator #passwords. #GRU hackers then used the #Moobot #malware to install their own bespoke scripts and files that repurposed the botnet, turning it into a global cyber #espionage platform,” agency said
https://www.securityweek.com/fbi-dismantles-ubiquiti-router-botnet-controlled-by-russian-cyberspies/ #ForestBlizzard #Sofacy #FancyBear #APT28

Please patch and change #defaultpasswords

Sigh. #Ubiquiti clearly don't give a fuck about EdgeMax routers or switches anymore. There haven’t been any firmware releases for a long time, and I discovered today (https://github.com/jamesog/tailscale-edgeos/issues/29) that after all this time #EdgeOS STILL doesn't have a fix for Let's Encrypt's root CA expiration back in 2021.

I like the hardware of the EdgeRouter 4 but EdgeOS clearly isn't sustainable. I'd love to do something like gokrazy/rtr7 on it but man that's more work than I have the energy for.

Sigh. #Ubiquiti clearly don't give a fuck about EdgeMax routers or switches anymore. There haven’t been any firmware releases for a long time, and I discovered today (https://github.com/jamesog/tailscale-edgeos/issues/29) that after all this time #EdgeOS STILL doesn't have a fix for Let's Encrypt's root CA expiration back in 2021.

I like the hardware of the EdgeRouter 4 but EdgeOS clearly isn't sustainable. I'd love to do something like gokrazy/rtr7 on it but man that's more work than I have the energy for.

Sigh. #Ubiquiti clearly don't give a fuck about EdgeMax routers or switches anymore. There haven’t been any firmware releases for a long time, and I discovered today (https://github.com/jamesog/tailscale-edgeos/issues/29) that after all this time #EdgeOS STILL doesn't have a fix for Let's Encrypt's root CA expiration back in 2021.

I like the hardware of the EdgeRouter 4 but EdgeOS clearly isn't sustainable. I'd love to do something like gokrazy/rtr7 on it but man that's more work than I have the energy for.

Sigh. #Ubiquiti clearly don't give a fuck about EdgeMax routers or switches anymore. There haven’t been any firmware releases for a long time, and I discovered today (https://github.com/jamesog/tailscale-edgeos/issues/29) that after all this time #EdgeOS STILL doesn't have a fix for Let's Encrypt's root CA expiration back in 2021.

I like the hardware of the EdgeRouter 4 but EdgeOS clearly isn't sustainable. I'd love to do something like gokrazy/rtr7 on it but man that's more work than I have the energy for.

Sigh. #Ubiquiti clearly don't give a fuck about EdgeMax routers or switches anymore. There haven’t been any firmware releases for a long time, and I discovered today (https://github.com/jamesog/tailscale-edgeos/issues/29) that after all this time #EdgeOS STILL doesn't have a fix for Let's Encrypt's root CA expiration back in 2021.

I like the hardware of the EdgeRouter 4 but EdgeOS clearly isn't sustainable. I'd love to do something like gokrazy/rtr7 on it but man that's more work than I have the energy for.

Finally got around to setting up #unbound and DNS over TLS on the #edgerouter. Was pretty painless. Though I am disappointed #edgeos 2 is using debian Stretch repositories, so everything in it is wildly out of date. Might look into cross compiling unbound myself.

Finally got around to setting up #unbound and DNS over TLS on the #edgerouter. Was pretty painless. Though I am disappointed #edgeos 2 is using debian Stretch repositories, so everything in it is wildly out of date. Might look into cross compiling unbound myself.

Does anybody know if it's possible to statically assign an #IPv6 address to a PPPoE WAN interface on an #EdgerouterX?

The configuration options I can see only seem to allow autoconf. This does then have 'secondary' and 'eui64' options but the former seems to do nothing and the latter fails with an error about no MAC address.

For the other interfaces I have a /56 correctly set up via pd so no problems there, but the WAN interface IP changes every reboot using autoconf...

#EdgeOS #Ubiquiti

Does anybody know if it's possible to statically assign an #IPv6 address to a PPPoE WAN interface on an #EdgerouterX?

The configuration options I can see only seem to allow autoconf. This does then have 'secondary' and 'eui64' options but the former seems to do nothing and the latter fails with an error about no MAC address.

For the other interfaces I have a /56 correctly set up via pd so no problems there, but the WAN interface IP changes every reboot using autoconf...

#EdgeOS #Ubiquiti

Switching from #EdgeOS to #Vyos has been pretty straightforward since #EdgeOS is a Vyatta fork, but one annoyance I have had with #Vyos is that it can't use groups everywhere.
For example, on EdgeOS I had a DNAT rule for Captive DNS, to capture any port 53 requests. I was able to specify a group:

set nat rule 10 destination group address-group '!dns-servers'

dns-servers being a address-group of my servers.

With Vyos, it doesn't look like you can specify a group like that in a NAT rule.

Switching from #EdgeOS to #Vyos has been pretty straightforward since #EdgeOS is a Vyatta fork, but one annoyance I have had with #Vyos is that it can't use groups everywhere.
For example, on EdgeOS I had a DNAT rule for Captive DNS, to capture any port 53 requests. I was able to specify a group:

set nat rule 10 destination group address-group '!dns-servers'

dns-servers being a address-group of my servers.

With Vyos, it doesn't look like you can specify a group like that in a NAT rule.

Switching from #EdgeOS to #Vyos has been pretty straightforward since #EdgeOS is a Vyatta fork, but one annoyance I have had with #Vyos is that it can't use groups everywhere.
For example, on EdgeOS I had a DNAT rule for Captive DNS, to capture any port 53 requests. I was able to specify a group:

set nat rule 10 destination group address-group '!dns-servers'

dns-servers being a address-group of my servers.

With Vyos, it doesn't look like you can specify a group like that in a NAT rule.

Switching from #EdgeOS to #Vyos has been pretty straightforward since #EdgeOS is a Vyatta fork, but one annoyance I have had with #Vyos is that it can't use groups everywhere.
For example, on EdgeOS I had a DNAT rule for Captive DNS, to capture any port 53 requests. I was able to specify a group:

set nat rule 10 destination group address-group '!dns-servers'

dns-servers being a address-group of my servers.

With Vyos, it doesn't look like you can specify a group like that in a NAT rule.

Switching from #EdgeOS to #Vyos has been pretty straightforward since #EdgeOS is a Vyatta fork, but one annoyance I have had with #Vyos is that it can't use groups everywhere.
For example, on EdgeOS I had a DNAT rule for Captive DNS, to capture any port 53 requests. I was able to specify a group:

set nat rule 10 destination group address-group '!dns-servers'

dns-servers being a address-group of my servers.

With Vyos, it doesn't look like you can specify a group like that in a NAT rule.

Just remembered that the Elephant wants hashtags.

#paper #edge #edge-cloud #latency #os #rtss #edgeos #real-time

Just remembered that the Elephant wants hashtags.

#paper #edge #edge-cloud #latency #os #rtss #edgeos #real-time

Just remembered that the Elephant wants hashtags.

#paper #edge #edge-cloud #latency #os #rtss #edgeos #real-time

Just remembered that the Elephant wants hashtags.

#paper #edge #edge-cloud #latency #os #rtss #edgeos #real-time

Just remembered that the Elephant wants hashtags.

#paper #edge #edge-cloud #latency #os #rtss #edgeos #real-time