We’ll be at NANOG 73 in Denver, CO, USA this week talking about routing security, MANRS, and IPv6.
The North American Network Operators Group (NANOG) is the professional association for Internet engineering, architecture and operations. Its core focus is on continuous improvement of the data transmission technologies, practices, and facilities that make the Internet function. NANOG meetings are among the largest in the region, bringing together top technologists on a wide range of topics.
On Tuesday, 26 June, at 1:30PM, Andrei Robachevsky will give a talk called, “Routing Is At Risk. Let’s Secure It Together.”
From the session abstract:
“Stolen cryptocurrency, hijacked traffic blocking access to whole countries, derailing vital Web resources for thousands of people. Routing used to fly under the radar. As long as incidents weren’t too bad, no one asked too many questions, and routing security never made it to the top of the to-do list. But these days, routing incidents are regularly making the news, executives are getting nervous, and engineers are under pressure to make sure their network isn’t next. The problem is, you cannot secure your own network entirely by yourself. But you can help secure the global routing system Continue reading
Grafana, The open platform for beautiful analytics and monitoring, recently added support for PostgreSQL.
It in now possible to connect Grafana to oVirt DWH, in order to visualize and monitor the oVirt environment.
Grafana dashboard example
Adding a Read-Only User to the History Database
You may want to add a read only user to connect the history database :
Note: In oVirt 4.2 we ship postgres 9.5 through the Software Collection.
In order to run psql you will need to run:
# su - postgres
$ scl enable rh-postgresql95 -- psql ovirt_engine_history
Create the user to be granted read-only access to the history database:
ovirt_engine_history=# CREATE ROLE [user name] WITH LOGIN ENCRYPTED PASSWORD '[password]';
Grant the newly created user permission to connect to the history database:
ovirt_engine_history=# GRANT CONNECT ON DATABASE ovirt_engine_history TO [user name];
Grant the newly created user usage of the public schema:
ovirt_engine_history=# GRANT USAGE ON SCHEMA public TO [user name];
Exit the database
ovirt_engine_history=# \q
Generate the rest of the permissions that will be granted to the newly created user and save them to a file:
$ scl enable rh-postgresql95 -- psql -U postgres -c "SELECT 'GRANT SELECT ON ' || relname Continue reading
Grafana, The open platform for beautiful analytics and monitoring, recently added support for PostgreSQL.
It in now possible to connect Grafana to oVirt DWH, in order to visualize and monitor the oVirt environment.
Grafana dashboard example
Adding a Read-Only User to the History Database
You may want to add a read only user to connect the history database :
Note: In oVirt 4.2 we ship postgres 9.5 through the Software Collection.
In order to run psql you will need to run:
# su - postgres
$ scl enable rh-postgresql95 -- psql ovirt_engine_history
Create the user to be granted read-only access to the history database:
ovirt_engine_history=# CREATE ROLE [user name] WITH LOGIN ENCRYPTED PASSWORD '[password]';
Grant the newly created user permission to connect to the history database:
ovirt_engine_history=# GRANT CONNECT ON DATABASE ovirt_engine_history TO [user name];
Grant the newly created user usage of the public schema:
ovirt_engine_history=# GRANT USAGE ON SCHEMA public TO [user name];
Exit the database
ovirt_engine_history=# \q
Generate the rest of the permissions that will be granted to the newly created user and save them to a file:
$ scl enable rh-postgresql95 -- psql -U postgres -c "SELECT 'GRANT SELECT ON ' || relname Continue reading
Routing information protocol (RIP) is a interior distance vector routing protocol originally defined in RFC1058. RIP has had a number of improvements over the years with version 2 being defined RFC2453 and RIPng adding IPv6 support in RFC2080. Transport RIPv1 and RIPv2...continue reading
I have spent some time studying the CCDE materials. One broken design example that has come up involves route reflector clients that don’t align with the physical topology. This article examines that example and some solutions to the problem.
To illustrate this example we have built the topology below. I used loopback addresses 1.1.1.1 through 6.6.6.6 (based on csr1000v-x). The router on the top is a eBGP neighbor with csr1000v-1 and csr1000v-2. The four routers forming a square in the center have an initial configuration of OSFP and BGP (iBGP as shown). Both Route Reflectors are peered with both clients.
//csr1000v-2 shown, csr1000v-3 similar router ospf 1 router-id 2.2.2.2 passive-interface GigabitEthernet2 network 2.2.2.2 0.0.0.0 area 0 network 10.0.0.0 0.255.255.255 area 0 router bgp 64513 bgp router-id 2.2.2.2 bgp log-neighbor-changes neighbor 3.3.3.3 remote-as 64513 neighbor 3.3.3.3 update-source Loopback0 neighbor 4.4.4.4 remote-as 64513 neighbor 4.4.4.4 update-source Loopback0 neighbor 4.4.4.4 route-reflector-client neighbor 5.5.5.5 remote-as 64513 Continue reading
I have spent some time studying the CCDE materials. One broken design example that has come up involves route reflector clients that don’t align with the physical topology. This article examines that example and some solutions to the problem.
To illustrate this example we have built the topology below. I used loopback addresses 1.1.1.1 through 6.6.6.6 (based on csr1000v-x). The router on the top is a eBGP neighbor with csr1000v-1 and csr1000v-2. The four routers forming a square in the center have an initial configuration of OSFP and BGP (iBGP as shown). Both Route Reflectors are peered with both clients.
//csr1000v-2 shown, csr1000v-3 similar router ospf 1 router-id 2.2.2.2 passive-interface GigabitEthernet2 network 2.2.2.2 0.0.0.0 area 0 network 10.0.0.0 0.255.255.255 area 0 router bgp 64513 bgp router-id 2.2.2.2 bgp log-neighbor-changes neighbor 3.3.3.3 remote-as 64513 neighbor 3.3.3.3 update-source Loopback0 neighbor 4.4.4.4 remote-as 64513 neighbor 4.4.4.4 update-source Loopback0 neighbor 4.4.4.4 route-reflector-client neighbor 5.5.5.5 remote-as 64513 Continue reading
I have spent some time studying the CCDE materials. One broken design example that has come up involves route reflector clients that don’t align with the physical topology. This article examines that example and some solutions to the problem.
To illustrate this example we have built the topology below. I used loopback addresses 1.1.1.1 through 6.6.6.6 (based on csr1000v-x). The router on the top is a eBGP neighbor with csr1000v-1 and csr1000v-2. The four routers forming a square in the center have an initial configuration of OSFP and BGP (iBGP as shown). Both Route Reflectors are peered with both clients.
//csr1000v-2 shown, csr1000v-3 similar router ospf 1 router-id 2.2.2.2 passive-interface GigabitEthernet2 network 2.2.2.2 0.0.0.0 area 0 network 10.0.0.0 0.255.255.255 area 0 router bgp 64513 bgp router-id 2.2.2.2 bgp log-neighbor-changes neighbor 3.3.3.3 remote-as 64513 neighbor 3.3.3.3 update-source Loopback0 neighbor 4.4.4.4 remote-as 64513 neighbor 4.4.4.4 update-source Loopback0 neighbor 4.4.4.4 route-reflector-client neighbor 5.5.5.5 remote-as 64513 Continue reading
Developer concern over Microsoft's $7.5 billion acquisition of GitHub could provide a long-term opportunity in the open source Git repository community.
With the DNSSEC Root Key Rollover coming up on October 11, how prepared are we as an industry? What kind of data can we collect in preparation? What is the cost benefit (or not) of implementing DANE? What can we learn from an existing rollover of a cryptographic algorithm?
All those questions and more will be discussed at the DNSSEC Workshop at the ICANN 62 meeting in Panama City, Panama, on Monday, June 25, 2018. The session will begin at 9:00 and conclude at 12:15 EST (UTC-5). [Note: this is one hour different than current US Eastern Daylight Time – Panama does not change to daylight savings time – and so this will begin at 10:00 EDT (UTC-4).]
The agenda includes:
It should be an outstanding session! For those onsite, the workshop will be in Salon 4, the ccNSO room.
The business of business is continuing to move out of the traditional datacenter. …
Putting Enterprise Applications At The Edge was written by Jeffrey Burt at .
Dubbed Lazy FP State Restore, the vulnerability (CVE-2018-3665) within Intel Core and Xeon processors has just been confirmed by Intel, and vendors are now rushing to roll out security updates in order to fix the flaw and keep their customers protected. The company has not yet released technical details about the vulnerability, but since the vulnerability resides in the CPU, the flaw affects all devices running Intel Core-based microprocessors regardless of the installed operating systems, except some modern versions of Continue reading
We are happy to share the videos from the top 5 rated sessions from last week’s DockerCon 2018 in San Francisco. The DockerCon on-demand sessions videos are ready for you to explore.
Note: The Ecosystem sessions will not be available.
Watch the past videos from DockerCon SF:
Pre-registration open for:
Missed @DockerCon SF? Here are the top 5 rated sessions.
Click To Tweet
The post DockerCon 2018: Top 5 Rated Sessions appeared first on Docker Blog.
International Speedway Corporation needed its applications to run as fast as the race cars on its tracks.
T-Mobile’s acquisition of Sprint will mean a larger 5G footprint and a higher capacity network, says Sprint’s CTO.
The company's stock plunged as much as 13 percent early Friday having just hit a new 52-week high last week.
ZTE stock sinks after U.S. Senate bill; T-Mobile and Sprint advance their proposed merger; and VMware works with the U.S. government and public sector.
In this episode, the Packet Pushers dive into optical networking. Optical networking tends to be a specialized area of networking. It’s much less about packets and paths and more about physical properties of fiber optic cables, signal propagation, and remote operations.
In recent times, optical companies have been moving into Data Center Interconnect (DCI) and selling direct to enterprises using dark fiber as well as offering DCI services via infrastructure suppliers.
Joining us today to offer their expertise on optical are Scott Wilkinson, Senior Director, Portfolio Marketing at ECI Telecom; and Andrew Schmitt, founder of Cignal AI.
We discuss the basics of silicon photonics and how it impacts optical networking, particularly for DCI. We also examine the open optical movement being driven by the Facebook-backed Telecom Infrastructure Project.
Cignal AI Newsletter sign-up – Cignal AI
IP and Optical integration white paper – ECI Telecom (PDF)
ONF s ODTN Project Brings Disaggregation and Open Source to Optical Networking – Open Networking.org
Infinera – Following the Open Road(map) – YouTube
Download an overview of latest news from last big optical conference – OFC2018
Pulse-amplitude modulation – Wikipedia
Quadrature amplitude modulation – Wikipedia