Hello there,
Regarding RTT v4 vs v6 I did something "interesting" recently,
would like to know your thoughs.
If you ping6 your loopback (let´s say 1000 packets) interface
with Windows or Linux, v6 is faster.
Now try the same on MAC (El capitan for example).., v6 is 20-25% slower.
I did the above with many devices (and asked some friends) and
the behavior was pretty much the same.
MAC:
--- 127.0.0.1 ping statistics ---
100 packets transmitted, 100 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.037/0.098/1.062/0.112 ms
--- ::1 ping6 statistics ---
100 packets transmitted, 100 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 0.058/0.120/0.194/0.027 ms
Linux:
--- 127.0.0.1 ping statistics ---
100 packets transmitted, 100 received, 0% packet loss, time
98999ms
rtt min/avg/max/mdev = 0.015/0.021/0.049/0.007 ms
--- ::1 ping statistics ---
100 packets transmitted, 100 received, 0% packet loss, time
99013ms
rtt min/avg/max/mdev = 0.019/0.031/0.040/0.004 ms
Windows 10:
Ping statistics for ::1:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
Ping statistics for 127.0.0.1:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 4ms, Average = 0ms
Bye,
wetheitteam.com
Where to order pain Relief without prescription
vivo v15 pro
Monday, August 21, 2017
Wednesday, March 30, 2016
Monday, February 29, 2016
Read a BGP live stream from CAIDA
Objective
Read a BGP live stream from CAIDA and insert them into a BGP session
What do we need
bgpreader from the bgpstream core package provided by Caida
bgp_simple.pl obtained in github
Overview
We will read the BGP live stream feed using bgpreader, then the standard output of it will be redirected to a pipe file (mkfifo) where a perl script called bgpsimple will be reading this file. This very same script will established the BGP session against a BGP speaker and announce the prefixes received in the stream.
LAB Topology
The configuration was already tested in Cisco & Quagga
The BGP Speaker (Cisco/Quagga) has the IPv4 address 192.168.1.1
The BGP Simple Linux box has the IP 192.168.1.2
How does it works?
bgpreader has the ability to write his output in the -m format used by libbgpdump (by RIPENCC), this is the very same format bgpsimple uses as stdin. That's why myroutes is a PIPE file (created with mkfifo).
Steps:
INSTALL BGP READER - UBUNTU 15.04
First install general some packages:
apt-get install apt-file libsqlite3-dev libsqlite3 libmysqlclient-dev libmysqlclient
apt-get install libcurl-dev libcurl autoconf git libssl-dev
apt-get install build-essential zlib1g-dev libbz2-dev
apt-get install libtool git
apt-get install zlib1g-dev
Also intall wandio
wandio-1.0.3
git clone https://github.com/alistairking/wandio
./configure
cd wandio
./bootstrap.sh
./configure && ./make && ./make install
wandiocat http://www.apple.com/library/test/success.html
to test wandio:
wandiocat http://www.apple.com/library/test/success.html
Download bgp reader tarball from:
https://bgpstream.caida.org/download
#ldconfig (before testing)
#mkfifo myroutes
to test bgpreader:
./bgpreader -p caida-bmp -w 1453912260 -m
(wait some seconds and then you will see something)
# git clone https://github.com/xdel/bgpsimple
Finally run everything
In two separate terminals (or any other way you would like to do it):
./bgpreader -p caida-bmp -w 1453912260 -m > /usr/src/bgpsimple/myroutes
./bgp_simple.pl -myas 65000 -myip 192.168.1.2 -peerip 192.168.1.1 -peeras 65000 -p myroutes
One more time, what will happen behind this?
bgpreader will read an online feed from a project called caida-bmp with starting timestamp 1453912260 (Jan 27 2016, 16:31) in "-m" format, It means a libbgpdump format (see references). The stardard output of all this will be send to the file /usr/src/bgpsimple/myroutes which is a "pipe file". At the same time, bgp_simple.pl will create an iBGP session againts peer 192.168.1.1/AS65000 (a bgp speaker such as Quagga or Cisco). bgp_simple.pl will read myroutes files and send what it seems in this file thru the iBGP Session.
Important information
- The BGP Session won't be established until there is something in the file myroutes
- eBGP multi-hop session are allowed
- You have to wait short time (few seconds) until bgpreaders start to actually see something and bgp_simple.pl starts to announce to the BGP peer
References / More information:
-Part of the work was based on:
http://evilrouters.net/2009/08/21/getting-bgp-routes-into-dynamips-with-video/
- Caida BGP Stream:
https://bgpstream.caida.org/
- bgpreader info:
https://bgpstream.caida.org/docs/tools/bgpreader
- RIPE NCC libbgpdump:
http://www.ris.ripe.net/source/bgpdump/
- Introduction of "Named Pipes" (pipe files in Linux):
http://www.linuxjournal.com/article/2156
Read a BGP live stream from CAIDA and insert them into a BGP session
What do we need
bgpreader from the bgpstream core package provided by Caida
bgp_simple.pl obtained in github
Overview
We will read the BGP live stream feed using bgpreader, then the standard output of it will be redirected to a pipe file (mkfifo) where a perl script called bgpsimple will be reading this file. This very same script will established the BGP session against a BGP speaker and announce the prefixes received in the stream.
LAB Topology
The configuration was already tested in Cisco & Quagga
The BGP Speaker (Cisco/Quagga) has the IPv4 address 192.168.1.1
The BGP Simple Linux box has the IP 192.168.1.2
How does it works?
bgpreader has the ability to write his output in the -m format used by libbgpdump (by RIPENCC), this is the very same format bgpsimple uses as stdin. That's why myroutes is a PIPE file (created with mkfifo).
Steps:
INSTALL BGP READER - UBUNTU 15.04
First install general some packages:
apt-get install apt-file libsqlite3-dev libsqlite3 libmysqlclient-dev libmysqlclient
apt-get install libcurl-dev libcurl autoconf git libssl-dev
apt-get install build-essential zlib1g-dev libbz2-dev
apt-get install libtool git
apt-get install zlib1g-dev
Also intall wandio
wandio-1.0.3
git clone https://github.com/alistairking/wandio
./configure
cd wandio
./bootstrap.sh
./configure && ./make && ./make install
wandiocat http://www.apple.com/library/test/success.html
to test wandio:
wandiocat http://www.apple.com/library/test/success.html
Download bgp reader tarball from:
https://bgpstream.caida.org/download
#ldconfig (before testing)
#mkfifo myroutes
to test bgpreader:
./bgpreader -p caida-bmp -w 1453912260 -m
(wait some seconds and then you will see something)
# git clone https://github.com/xdel/bgpsimple
Finally run everything
In two separate terminals (or any other way you would like to do it):
./bgpreader -p caida-bmp -w 1453912260 -m > /usr/src/bgpsimple/myroutes
./bgp_simple.pl -myas 65000 -myip 192.168.1.2 -peerip 192.168.1.1 -peeras 65000 -p myroutes
One more time, what will happen behind this?
bgpreader will read an online feed from a project called caida-bmp with starting timestamp 1453912260 (Jan 27 2016, 16:31) in "-m" format, It means a libbgpdump format (see references). The stardard output of all this will be send to the file /usr/src/bgpsimple/myroutes which is a "pipe file". At the same time, bgp_simple.pl will create an iBGP session againts peer 192.168.1.1/AS65000 (a bgp speaker such as Quagga or Cisco). bgp_simple.pl will read myroutes files and send what it seems in this file thru the iBGP Session.
Important information
- The BGP Session won't be established until there is something in the file myroutes
- eBGP multi-hop session are allowed
- You have to wait short time (few seconds) until bgpreaders start to actually see something and bgp_simple.pl starts to announce to the BGP peer
References / More information:
-Part of the work was based on:
http://evilrouters.net/2009/08/21/getting-bgp-routes-into-dynamips-with-video/
- Caida BGP Stream:
https://bgpstream.caida.org/
- bgpreader info:
https://bgpstream.caida.org/docs/tools/bgpreader
- RIPE NCC libbgpdump:
http://www.ris.ripe.net/source/bgpdump/
- Introduction of "Named Pipes" (pipe files in Linux):
http://www.linuxjournal.com/article/2156
Wednesday, February 17, 2016
Animation: The sad tale of the ISP that did not deploy IPv6
Hello,
The following animation is based on the story called: "The sad tale of the ISP that didn't deploy IPv6" [1]. Hope you enjoy it:
[1] http://portalipv6.lacnic.net/en/the-sad-tale-of-the-isp-that-didnt-deploy-ipv6/
Friday, January 1, 2016
Virtualbox in Windows. Bridge adapter + IPv6 not working
Introduction:
When trying to use IPv6 in Virtualbox inside a guest where the adapter is bridge to the wireless interface of the host, the VM does SLAAC correctly but HTTP or ping6 does not work.
Solution:
To solve this issue just reinstall/repair your current Virtualbox instalattion (version 5) adding the following parameters to the installer: "-Win.exe -msiparams NETWORKTYPE=NDIS5"
The result would be something like:
G:\>VirtualBox-5.0.12-104815-Win.exe -msiparams NETWORKTYPE=NDIS5
So, you cannot double click on the installer, you need to do it from command line with admin privileges.
Workaround:
The problem is only with the bridging to the wireless adapter, you, if possible, you could bridge to a non-wireless interface and IPv6 should work perfectly.
References:
https://www.virtualbox.org/ticket/14457
Good luck,
When trying to use IPv6 in Virtualbox inside a guest where the adapter is bridge to the wireless interface of the host, the VM does SLAAC correctly but HTTP or ping6 does not work.
Solution:
To solve this issue just reinstall/repair your current Virtualbox instalattion (version 5) adding the following parameters to the installer: "-Win.exe -msiparams NETWORKTYPE=NDIS5"
The result would be something like:
G:\>VirtualBox-5.0.12-104815-Win.exe -msiparams NETWORKTYPE=NDIS5
So, you cannot double click on the installer, you need to do it from command line with admin privileges.
Workaround:
The problem is only with the bridging to the wireless adapter, you, if possible, you could bridge to a non-wireless interface and IPv6 should work perfectly.
References:
https://www.virtualbox.org/ticket/14457
Good luck,
Tuesday, May 26, 2015
IPv6 Song presented during Lacnic23 (Lima, Peru) - IPv6 Latin American Forum
(note that you can turn on captioning if you wish)
Michael Schulze: Co-producer
Eidan Molina: Co-producer. Composer.
Music and Lyrics by Eidan Molina
Agrupacion de produccion: Fifth Floor Studios
Idea: Alejandro Acosta
Tuesday, February 17, 2015
Solution to quagga vtysh "Exiting: failed to connect to any daemons."
Description:
When you run the command in the linux shell vtysh to connect to the quagga daemons (such as bgpd, ospfd, etc) returns the following error "Exiting: failed to connect to any daemons"
Just like this:
alejandro @ miserver: ~ $ vtysh -d bgpd
Exiting: failed to connect to any daemons.
alejandro @ miserver: ~ $ vtysh
Exiting: failed to connect to any daemons.
Solution:
The solution is to add the user that is executing vtysh to the quagga group. To do this edit the /etc/group file.
After editing /etc/group should be something like:
quagga:x:1003:alejandro
You can specify multiple users doing:
quagga:x:1003:alejandro, john
This is necessary because vtysh tries to connect to the daemons using UNIX domain sockets and not all users (for security reasons) have access to these sockets.
Another solution:
Another solution might be during the compilation phase where you can specify the linux/unix group for sockets mentioned above. Example:
./configure --enable-vty-group = group
Good luck, I hope this helped,
When you run the command in the linux shell vtysh to connect to the quagga daemons (such as bgpd, ospfd, etc) returns the following error "Exiting: failed to connect to any daemons"
Just like this:
alejandro @ miserver: ~ $ vtysh -d bgpd
Exiting: failed to connect to any daemons.
alejandro @ miserver: ~ $ vtysh
Exiting: failed to connect to any daemons.
Solution:
The solution is to add the user that is executing vtysh to the quagga group. To do this edit the /etc/group file.
After editing /etc/group should be something like:
quagga:x:1003:alejandro
You can specify multiple users doing:
quagga:x:1003:alejandro, john
This is necessary because vtysh tries to connect to the daemons using UNIX domain sockets and not all users (for security reasons) have access to these sockets.
Another solution:
Another solution might be during the compilation phase where you can specify the linux/unix group for sockets mentioned above. Example:
./configure --enable-vty-group = group
Good luck, I hope this helped,
Subscribe to:
Posts (Atom)