new picohub in data center

UVic computer science
Post Reply
pan
Posts: 59874
Joined: Mon Sep 11, 2006 10:23 am

new picohub in data center

Post by pan »

Code: Select all

+----------------------------------------------------------------+
+                    PicoNet  0.01 (Alpha)                       +
+----------------------------------------------------------------+
+ Hosts:                                                         +
+    h1  (h1-eth0 192.168.1.100)                                 +
+    h2  (h2-eth0 10.10.1.100)                                   +
+    r   (eth0 192.168.1.1, eth1 10.10.1.1)                      +
+    dns (172.16.1.1)                                            +
+----------------------------------------------------------------+
Actual changes:
tx-checksumming: off
        tx-checksum-ip-generic: off
        tx-checksum-sctp: off
tx-udp-segmentation: off [requested on]
Actual changes:
tx-checksumming: off
        tx-checksum-ip-generic: off
        tx-checksum-sctp: off
tx-udp-segmentation: off [requested on]
Actual changes:
tx-checksumming: off
        tx-checksum-ip-generic: off
        tx-checksum-sctp: off
tx-udp-segmentation: off [requested on]
Actual changes:
tx-checksumming: off
        tx-checksum-ip-generic: off
        tx-checksum-sctp: off
tx-udp-segmentation: off [requested on]
Actual changes:
tx-checksumming: off
        tx-checksum-ip-generic: off
        tx-checksum-sctp: off
tx-udp-segmentation: off [requested on]
iptables v1.8.7 (nf_tables): Could not fetch rule set generation id: Invalid argument

iptables v1.8.7 (nf_tables): Could not fetch rule set generation id: Invalid argument

iptables v1.8.7 (nf_tables): Couldn't load match `state':No such file or directory

Try `iptables -h' or 'iptables --help' for more information.
iptables v1.8.7 (nf_tables): Could not fetch rule set generation id: Invalid argument

ERROR:systemctl: dbus.service: Executable path is not absolute, ignoring: @/usr/bin/dbus-daemon @dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
root@h1:/home/jovyan#

Code: Select all

+----------------------------------------------------------------+
+                    PicoNet  0.01 (Alpha)                       +
+----------------------------------------------------------------+
+ Hosts:                                                         +
+    h1  (h1-eth0 192.168.1.100)                                 +
+    h2  (h2-eth0 10.10.1.100)                                   +
+    r   (eth0 192.168.1.1, eth1 10.10.1.1)                      +
+    dns (172.16.1.1)                                            +
+----------------------------------------------------------------+
root@h2:/home/jovyan#

Code: Select all

+----------------------------------------------------------------+
+                    PicoNet  0.01 (Alpha)                       +
+----------------------------------------------------------------+
+ Hosts:                                                         +
+    h1  (h1-eth0 192.168.1.100)                                 +
+    h2  (h2-eth0 10.10.1.100)                                   +
+    r   (eth0 192.168.1.1, eth1 10.10.1.1)                      +
+    dns (172.16.1.1)                                            +
+----------------------------------------------------------------+
root@r:/home/jovyan#

Code: Select all

+----------------------------------------------------------------+
+                    PicoNet  0.01 (Alpha)                       +
+----------------------------------------------------------------+
+ Hosts:                                                         +
+    h1  (h1-eth0 192.168.1.100)                                 +
+    h2  (h2-eth0 10.10.1.100)                                   +
+    r   (eth0 192.168.1.1, eth1 10.10.1.1)                      +
+    dns (172.16.1.1)                                            +
+----------------------------------------------------------------+
pan@jupyter:~$
Top
pan
Posts: 59874
Joined: Mon Sep 11, 2006 10:23 am

Re: new picohub in data center

Post by pan »

Code: Select all

root@h1:/home/jovyan# ip a
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
4: h1-eth0@if3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 7e:0e:df:c0:fe:40 brd ff:ff:ff:ff:ff:ff link-netns r
    inet 192.168.1.100/24 scope global h1-eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::7c0e:dfff:fec0:fe40/64 scope link 
       valid_lft forever preferred_lft forever
root@h1:/home/jovyan# ip r
default via 192.168.1.1 dev h1-eth0 
192.168.1.0/24 dev h1-eth0 proto kernel scope link src 192.168.1.100

Code: Select all

oot@h2:/home/jovyan# ip a
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
6: h2-eth0@if5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 0e:dd:8a:86:01:5d brd ff:ff:ff:ff:ff:ff link-netns r
    inet 10.10.1.100/24 scope global h2-eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::cdd:8aff:fe86:15d/64 scope link 
       valid_lft forever preferred_lft forever
root@h2:/home/jovyan# ip r
default via 10.10.1.1 dev h2-eth0 
10.10.1.0/24 dev h2-eth0 proto kernel scope link src 10.10.1.100

Code: Select all

root@r:/home/jovyan# ip a
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
3: r-eth0@if4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether ce:6a:93:00:79:79 brd ff:ff:ff:ff:ff:ff link-netns h1
    inet 192.168.1.1/24 scope global r-eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::cc6a:93ff:fe00:7979/64 scope link 
       valid_lft forever preferred_lft forever
5: r-eth1@if6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 26:47:e1:d9:3a:b1 brd ff:ff:ff:ff:ff:ff link-netns h2
    inet 10.10.1.1/24 scope global r-eth1
       valid_lft forever preferred_lft forever
    inet6 fe80::2447:e1ff:fed9:3ab1/64 scope link 
       valid_lft forever preferred_lft forever
8: r-eth2@if7: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether b2:2b:f6:05:c3:09 brd ff:ff:ff:ff:ff:ff link-netnsid 2
    inet 172.16.1.1/24 scope global r-eth2
       valid_lft forever preferred_lft forever
    inet6 fe80::b02b:f6ff:fe05:c309/64 scope link 
       valid_lft forever preferred_lft forever
root@r:/home/jovyan# ip r
default via 172.16.1.2 dev r-eth2 
10.10.1.0/24 dev r-eth1 proto kernel scope link src 10.10.1.1 
172.16.1.0/24 dev r-eth2 proto kernel scope link src 172.16.1.1 
192.168.1.0/24 dev r-eth0 proto kernel scope link src 192.168.1.1

Code: Select all

pan@jupyter:~$ ip a
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 noprefixroute 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc pfifo_fast state UP group default qlen 1000
    link/ether ee:df:ae:3c:36:a8 brd ff:ff:ff:ff:ff:ff
    inet 10.236.104.36/32 brd 10.236.104.36 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::ecdf:aeff:fe3c:36a8/64 scope link 
       valid_lft forever preferred_lft forever
7: host-nat@if8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether c2:6c:c6:0c:41:a1 brd ff:ff:ff:ff:ff:ff link-netns r
    inet 172.16.1.2/32 scope global host-nat
       valid_lft forever preferred_lft forever
    inet6 fe80::c06c:c6ff:fe0c:41a1/64 scope link 
       valid_lft forever preferred_lft forever
pan@jupyter:~$ ip r
default via 169.254.1.1 dev eth0 
169.254.1.1 dev eth0 scope link 
172.16.1.0/24 via 172.16.1.2 dev host-nat
Top
pan
Posts: 59874
Joined: Mon Sep 11, 2006 10:23 am

Re: new picohub in data center

Post by pan »

Code: Select all

root@h1:/home/jovyan# ping -c 3 h2
PING h2 (10.10.1.100) 56(84) bytes of data.
64 bytes from h2 (10.10.1.100): icmp_seq=1 ttl=63 time=0.123 ms
64 bytes from h2 (10.10.1.100): icmp_seq=2 ttl=63 time=0.036 ms
64 bytes from h2 (10.10.1.100): icmp_seq=3 ttl=63 time=0.036 ms

--- h2 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2043ms
rtt min/avg/max/mdev = 0.036/0.065/0.123/0.041 ms
root@h1:/home/jovyan# traceroute h2
traceroute to h2 (10.10.1.100), 30 hops max, 60 byte packets
 1  r-net1 (192.168.1.1)  0.084 ms  0.005 ms  0.003 ms
 2  h2 (10.10.1.100)  0.010 ms  0.005 ms  0.004 ms

Code: Select all

root@h2:/home/jovyan# ping -c 3 h1
PING h1 (192.168.1.100) 56(84) bytes of data.
64 bytes from h1 (192.168.1.100): icmp_seq=1 ttl=63 time=0.025 ms
64 bytes from h1 (192.168.1.100): icmp_seq=2 ttl=63 time=0.045 ms
64 bytes from h1 (192.168.1.100): icmp_seq=3 ttl=63 time=0.039 ms

--- h1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2055ms
rtt min/avg/max/mdev = 0.025/0.036/0.045/0.008 ms
root@h2:/home/jovyan# traceroute h1
traceroute to h1 (192.168.1.100), 30 hops max, 60 byte packets
 1  r-net2 (10.10.1.1)  0.044 ms  0.004 ms  0.003 ms
 2  h1 (192.168.1.100)  0.010 ms  0.004 ms  0.003 ms
Top
pan
Posts: 59874
Joined: Mon Sep 11, 2006 10:23 am

Re: new picohub in data center

Post by pan »

finally traceroute is working (to 1.1.1.1 only now) but ping not

Code: Select all

pan@jupyter:~$ ping -c 10 1.1.1.1
pan@jupyter:~$ traceroute 1.1.1.1
traceroute to 1.1.1.1 (1.1.1.1), 30 hops max, 60 byte packets
 1  142-104-116-104.kube-prometheus-stack-kube-proxy.kube-system.svc.dcs-cosinetlab-k8s.local (142.104.116.104)  0.156 ms  0.095 ms  0.066 ms
 2  142.104.116.125 (142.104.116.125)  0.313 ms  0.223 ms  0.247 ms
 3  10.88.99.83 (10.88.99.83)  0.465 ms 10.88.99.82 (10.88.99.82)  0.441 ms 10.88.99.83 (10.88.99.83)  0.439 ms
 4  142.104.124.122 (142.104.124.122)  0.674 ms  0.775 ms  0.693 ms
 5  cma1bcpbi32.bb.uvic.ca (10.0.2.1)  0.611 ms  0.540 ms  0.470 ms
 6  142.104.100.11 (142.104.100.11)  1.111 ms  1.069 ms  1.057 ms
 7  xe-5-1-0-0-2921-ix-cr1.vctr3.bc.net (207.23.244.233)  27.913 ms  27.840 ms  27.774 ms
 8  lo0-ix-cr1.vantx1.bc.net (134.87.0.254)  3.284 ms  3.211 ms  3.249 ms
 9  * as13335.vanix.ca (206.41.104.52)  10.572 ms *
10  1.1.1.1 (1.1.1.1)  3.031 ms  3.023 ms  2.952 ms

vs cosi desktop

Code: Select all

% ping -c 10 1.1.1.1
PING 1.1.1.1 (1.1.1.1): 56 data bytes
64 bytes from 1.1.1.1: icmp_seq=0 ttl=56 time=3.606 ms
64 bytes from 1.1.1.1: icmp_seq=1 ttl=56 time=3.449 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=56 time=3.267 ms
64 bytes from 1.1.1.1: icmp_seq=3 ttl=56 time=3.598 ms
64 bytes from 1.1.1.1: icmp_seq=4 ttl=56 time=3.338 ms
64 bytes from 1.1.1.1: icmp_seq=5 ttl=56 time=3.449 ms
64 bytes from 1.1.1.1: icmp_seq=6 ttl=56 time=3.356 ms
64 bytes from 1.1.1.1: icmp_seq=7 ttl=56 time=3.223 ms
64 bytes from 1.1.1.1: icmp_seq=8 ttl=56 time=3.207 ms
64 bytes from 1.1.1.1: icmp_seq=9 ttl=56 time=3.607 ms

--- 1.1.1.1 ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 3.207/3.410/3.607/0.148 ms
% traceroute 1.1.1.1
traceroute to 1.1.1.1 (1.1.1.1), 64 hops max, 52 byte packets
 1  192.168.100.1 (192.168.100.1)  0.649 ms  0.311 ms  0.200 ms
 2  desktop-i6sp2r3.cs.uvic.ca (142.104.68.3)  0.608 ms  0.657 ms  0.577 ms
 3  142.104.124.106 (142.104.124.106)  0.788 ms  5.599 ms  0.664 ms
 4  10.0.2.1 (10.0.2.1)  0.625 ms  12.146 ms  0.604 ms
 5  142.104.100.11 (142.104.100.11)  16.812 ms  1.474 ms  1.527 ms
 6  xe-5-1-0-0-2921-ix-cr1.vctr3.bc.net (207.23.244.233)  1.802 ms  2.016 ms  1.736 ms
 7  lo0-ix-cr1.vantx1.bc.net (134.87.0.254)  3.336 ms  3.402 ms  3.209 ms
 8  as13335.vanix.ca (206.41.104.52)  3.957 ms  3.930 ms  3.819 ms
 9  one.one.one.one (1.1.1.1)  3.103 ms  3.265 ms  3.214 ms

vs uvic wifi

Code: Select all

% ping -c 10 1.1.1.1
PING 1.1.1.1 (1.1.1.1): 56 data bytes
64 bytes from 1.1.1.1: icmp_seq=0 ttl=58 time=5.744 ms
64 bytes from 1.1.1.1: icmp_seq=1 ttl=58 time=5.914 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=58 time=6.067 ms
64 bytes from 1.1.1.1: icmp_seq=3 ttl=58 time=6.341 ms
64 bytes from 1.1.1.1: icmp_seq=4 ttl=58 time=5.755 ms
64 bytes from 1.1.1.1: icmp_seq=5 ttl=58 time=46.083 ms
64 bytes from 1.1.1.1: icmp_seq=6 ttl=58 time=90.006 ms
64 bytes from 1.1.1.1: icmp_seq=7 ttl=58 time=134.419 ms
64 bytes from 1.1.1.1: icmp_seq=8 ttl=58 time=179.801 ms
64 bytes from 1.1.1.1: icmp_seq=9 ttl=58 time=226.178 ms

--- 1.1.1.1 ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 5.744/70.631/226.178/78.784 ms
% traceroute 1.1.1.1
traceroute to 1.1.1.1 (1.1.1.1), 64 hops max, 52 byte packets
 1  w87-167-253 (206.87.167.253)  18.832 ms  5.569 ms  11.342 ms
 2  10.0.2.1 (10.0.2.1)  14.009 ms  9.788 ms  5.987 ms
 3  142.104.100.11 (142.104.100.11)  5.827 ms  3.847 ms  3.882 ms
 4  xe-5-1-0-0-2921-ix-cr1.vctr3.bc.net (207.23.244.233)  4.521 ms  4.312 ms  4.001 ms
 5  lo0-ix-cr1.vantx1.bc.net (134.87.0.254)  5.803 ms  5.740 ms  4.755 ms
 6  as13335.vanix.ca (206.41.104.52)  39.268 ms  11.107 ms *
 7  one.one.one.one (1.1.1.1)  78.288 ms  5.742 ms  5.367 ms

in fact, uvic wifi can traceroute to anywhere

Code: Select all

% traceroute 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 64 hops max, 52 byte packets
 1  w87-167-253 (206.87.167.253)  240.787 ms  3.726 ms  20.000 ms
 2  10.0.2.1 (10.0.2.1)  3.103 ms  4.072 ms  3.912 ms
 3  142.104.100.11 (142.104.100.11)  3.303 ms  3.874 ms  3.741 ms
 4  xe-5-1-0-0-2921-ix-cr1.vctr3.bc.net (207.23.244.233)  4.074 ms  3.952 ms  4.111 ms
 5  vctr3rtr3.network.canarie.ca (199.212.24.98)  3.942 ms  3.788 ms  3.261 ms
 6  199.212.24.228 (199.212.24.228)  6.111 ms  6.046 ms  6.313 ms
 7  199.212.24.229 (199.212.24.229)  5.972 ms  5.905 ms  6.083 ms
 8  192.178.105.129 (192.178.105.129)  5.746 ms  6.334 ms
    108.170.255.175 (108.170.255.175)  6.525 ms
 9  72.14.232.193 (72.14.232.193)  6.106 ms
    142.251.55.203 (142.251.55.203)  5.755 ms
    209.85.243.97 (209.85.243.97)  5.993 ms
10  dns.google (8.8.8.8)  5.843 ms  4.816 ms  4.747 ms

except being blocked by the other side

Code: Select all

% traceroute 9.9.9.9
traceroute to 9.9.9.9 (9.9.9.9), 64 hops max, 52 byte packets
 1  w87-167-253 (206.87.167.253)  83.519 ms  3.120 ms  3.201 ms
 2  10.0.2.1 (10.0.2.1)  2.895 ms  3.211 ms  3.615 ms
 3  142.104.100.11 (142.104.100.11)  3.874 ms  3.963 ms  3.717 ms
 4  xe-2-0-1-2920-tx-cr1.vctr3.bc.net (207.23.241.185)  4.128 ms  4.240 ms  3.877 ms
 5  * * *
 6  rd1cv-be32-1.gv.shawcable.net (66.163.72.5)  139.570 ms  5.450 ms  5.169 ms
 7  rd1lp-be1.gv.shawcable.net (66.163.72.22)  5.715 ms  4.349 ms  4.338 ms
 8  rc1wt-be40.wa.shawcable.net (66.163.68.18)  6.761 ms  6.139 ms  6.730 ms
 9  six.woodynet.net (206.81.80.80)  6.728 ms  7.388 ms  20.685 ms
10  * * *
11  * * *
12  * * *

isp and network admin: please preserve the ability of being traceroute'd, so our students can still understand how the internet works as well

Top
pan
Posts: 59874
Joined: Mon Sep 11, 2006 10:23 am

Re: new picohub in data center

Post by pan »

now works. use

Code: Select all

Piconet Bryan test image Ubuntu 24.04

last but not the first server image on the list

Code: Select all

pan@jupyter:~$ ping -c 10 1.1.1.1
PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
64 bytes from 1.1.1.1: icmp_seq=1 ttl=55 time=3.88 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=55 time=4.28 ms
64 bytes from 1.1.1.1: icmp_seq=3 ttl=55 time=3.43 ms
64 bytes from 1.1.1.1: icmp_seq=4 ttl=55 time=4.22 ms
64 bytes from 1.1.1.1: icmp_seq=5 ttl=55 time=3.97 ms
64 bytes from 1.1.1.1: icmp_seq=6 ttl=55 time=3.03 ms
64 bytes from 1.1.1.1: icmp_seq=7 ttl=55 time=3.76 ms
64 bytes from 1.1.1.1: icmp_seq=8 ttl=55 time=4.23 ms
64 bytes from 1.1.1.1: icmp_seq=9 ttl=55 time=3.11 ms
64 bytes from 1.1.1.1: icmp_seq=10 ttl=55 time=3.06 ms

--- 1.1.1.1 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9015ms
rtt min/avg/max/mdev = 3.031/3.697/4.281/0.476 ms

Code: Select all

pan@jupyter:~$ traceroute 1.1.1.1
traceroute to 1.1.1.1 (1.1.1.1), 30 hops max, 60 byte packets
 1  142-104-116-104.kube-prometheus-stack-kube-proxy.kube-system.svc.dcs-cosinetlab-k8s.local (142.104.116.104)  0.149 ms  0.097 ms  0.093 ms
 2  142.104.116.125 (142.104.116.125)  0.435 ms  0.269 ms  0.309 ms
 3  10.88.99.82 (10.88.99.82)  0.442 ms  0.423 ms 10.88.99.83 (10.88.99.83)  0.471 ms
 4  142.104.124.122 (142.104.124.122)  0.496 ms  0.451 ms  0.419 ms
 5  cma1bcpbi32.bb.uvic.ca (10.0.2.1)  0.544 ms  0.481 ms  0.384 ms
 6  142.104.100.11 (142.104.100.11)  1.200 ms  1.156 ms  1.015 ms
 7  xe-5-1-0-0-2921-ix-cr1.vctr3.bc.net (207.23.244.233)  3.181 ms  3.098 ms  2.941 ms
 8  lo0-ix-cr1.vantx1.bc.net (134.87.0.254)  3.223 ms  3.204 ms  3.245 ms
 9  as13335.vanix.ca (206.41.104.52)  3.561 ms  4.144 ms  4.184 ms
10  1.1.1.1 (1.1.1.1)  2.966 ms  3.012 ms  2.972 ms
Top
Post Reply

Return to “UVic CS”