In this week's IPv6 Buzz episode, Ed and Tom talk in depth about IPv6 Router Advertisements (or RAs), what they are, what they do, and why they're critical to IPv6 operations.
The post IPv6 Buzz 043: Let’s Explore IPv6 Router Advertisements! appeared first on Packet Pushers.
“We build this distributed software that runs in the switches themselves, and so we leverage the...
CloudGenix CEO Kumar Ramachandran credited much of the SD-WAN vendor's growth in 2019 —...
If your automation solution relies on a back-end database with strict database schema you can stop reading… but if you (like most others) still live in the land of text files encoded in your favorite presentation format (because it’s hip to hate YAML), you might appreciate the solution Donald Johnson uses to check his data models before committing them into Git repository.
A World Economic Forum (WEF) report released today recommends that Internet Service Providers (ISPs) should strongly consider joining the Mutually Agreed Norms for Routing Security (MANRS) initiative to improve the security of the Internet’s global routing system.
Systemic security issues about how traffic is routed on the Internet make it a relatively easy target for criminals. MANRS helps reduce the most common routing threats and increase efficiency and transparency among ISPs on peering relationships.
The WEF Centre for Cybersecurity identifies four actionable principles as effective in preventing malicious activities from getting “down the pipes” from network providers to consumers in the report Cybercrime Prevention: Principles for Internet Service Providers, released today in Davos, Switzerland.
The principles were developed and tested over a year with leading ISPs around the world and multilateral organizations, including BT, Deutsche Telekom, Du Telecom, Europol, Global Cyber Alliance, Korea Telecom, Proximus, Saudi Telcom, Singtel, Telstra, and ITU, WEF says in a press release.
One of the principles is to “take action to shore up the security of routing and signalling to reinforce effective defence against attacks”, and MANRS, a global initiative supported by the Internet Society, is one of the recommendations to achieve the principle Continue reading
VMware bought AIOps vendor Nyansa; Red Hat was integral to IBM's Q4 success; and Vapor IO scored...
The proposed funding pales in comparison to the amount of money Huawei and other RAN stalwarts are...
Financial networks are at a constant risk — especially since they rely on risky IoT devices....
Several incumbent networking players, including Cisco, Dell Technologies, VMware, Juniper Networks,...
I have visited my home and was doing some hobby IT setup with Raspberry Pi’s, the problem is that i had problems many times accessing my home PC is another Remote Location due to many reasons, lets say crappy ISP. I contacted my ISP and they said I need to take a static IP and also pay for opening up two non standard ports. Its like you pay to get tortured and then additional headache of Port forwarding.
To add more to the pain, the IP that i get from my upstream provider is a Private IP, wow I havent seen that for a while. Anyways, to get around this I was thinking about using OPENVPN as a solution along with Dyndns.
Now, setup is very simple
Clint-pc (Location 1) ———-AWS(OPENVPN)————Client-pc (Location 2)
Why AWS -> Accessible and Cost
Problem is changing IP, I dont have any business requirement or criticality to buy a Elastic IP , but whole point will be lost if my clients wont know what to access, worse I will never have access to location-2 if am in location-1 to change IP Addresses
I have mapped OPENVPN with dyndns script.
https://help.dyn.com/ddclient/
This really solved Continue reading

One of the most requested features for the docker-compose tool is definitely support for building using Buildkit which is an alternative builder with great capabilities, like caching, concurrency and ability to use custom BuildKit front-ends just to mention a few… Ahhh with a nice blue output! And the good news is that Docker Compose 1.25.1 – that was just released early January – includes BuildKit support!
BuildKit support for Docker Compose is actually achieved by redirecting the docker-compose build to the Docker CLI with a limited feature set.
To enable this, we have to align some stars.
First, it requires that the Docker CLI binary present in your PATH:
$ whichdocker/usr/local/bin/docker
Second, docker-compose has to be run with the environment variable COMPOSE_DOCKER_CLI_BUILD set to 1 like in:
$ COMPOSE_DOCKER_CLI_BUILD=1 docker-compose build
This instruction tells docker-compose to use the Docker CLI when executing a build. You should see the same build output, but starting with the experimental warning.
As docker-compose passes its environment variables to the Docker CLI, we can also tell the CLI to use BuildKit instead of the default builder. To accomplish that, we can execute this:
$ COMPOSE_DOCKER_CLI_BUILD=1 DOCKER_BUILDKIT=1 docker-compose build

Autocorrect to improve my writing
The post Writing Tip: Auto-spelling to Avoid Words appeared first on EtherealMind.
