17 Feb
2016
17 Feb
'16
6:29 p.m.
Hi Brian:
I am curious about BGP routing; since the agreements all go through you,
here are a few questions:
1) How many AMPRNet subnets are currently being advertised via BGP?
2) Do you have any notion if specific ISPs are more open to allow BGP
advertising than others?
3) Have any AMPRNet users had luck getting BGP agreements with home class
service?
Assi
17 Feb
17 Feb
6:32 p.m.
On Wed, Feb 17, 2016 at 03:29:47PM -0800, Assi Friedman wrote:
1) How many AMPRNet subnets are currently being
advertised via BGP?
about 70.
2) Do you have any notion if specific ISPs are more
open to allow BGP
advertising than others?
I'm told that some, Comcast for instance, are not interested.
3) Have any AMPRNet users had luck getting BGP
agreements with home class
service?
I don't know. I've never asked the class of service.
- Brian
18 Feb
18 Feb
1:45 a.m.
And if we talk on the subject
is there any tool on the net that can show the Sub nets that advertised for the BGP for
the AMPRNET ?
I used to see BGP advertisements in one of the looking glass tools of the biggest ISP
tools page
Regards
Ronen - 4Z4ZQ
http://www.ronen.org
________________________________________
From: 44Net <44net-bounces+ronenp=hotmail.com(a)hamradio.ucsd.edu> on behalf of Brian
Kantor <Brian(a)UCSD.Edu>
Sent: Wednesday, February 17, 2016 3:32 PM
To: AMPRNet working group
Subject: Re: [44net] BGP stats for AMPRNet
(Please trim inclusions from previous messages)
_______________________________________________
On Wed, Feb 17, 2016 at 03:29:47PM -0800, Assi Friedman wrote:
1) How many AMPRNet subnets are currently being
advertised via BGP?
about 70.
2) Do you have any notion if specific ISPs are more
open to allow BGP
advertising than others?
I'm told that some, Comcast for instance, are not interested.
3) Have any AMPRNet users had luck getting BGP
agreements with home class
service?
I don't know. I've never asked the class of service.
- Brian
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
3:05 a.m.
New subject: how can i know what network allocated to me ?;
Hi there
I have requested a Subnet in my Country long ago
I saw that now there is allocated network that belong to my country buy it is not the
subnet I requested
I requested 44.138.45/24 and the available network is 44.138.1/24
before I add this network to me (and maybe takes anyone else network)
Is there a way to know who this network belong to ?
Maybe the portal managers have log and can see who allocated this network and to which
request ?
Please advice
Thanks Forward
Ronen -4Z4ZQ
http://www.ronen.org
10:35 a.m.
New subject: how can i know what network allocated to me ?;
On Thu, Feb 18, 2016 at 08:05:38AM +0000, R P wrote:
I have requested a Subnet in my Country long ago
I saw that now there is allocated network that belong to my country buy it is not
the subnet I requested
I requested 44.138.45/24 and the available network is 44.138.1/24
before I add this network to me (and maybe takes anyone else network)
Is there a way to know who this network belong to ?
Maybe the portal managers have log and can see who allocated this network and to which
request ?
It is allocated to you and no one else has been using it.
Since there is apparently no active coordinator for
Israel and your request had been sitting for months, I acted upon
the request so you could get started on your networking project.
There are NO other networks allocated in Israel so the first one
starts with 1.
If you find the allocated network to be
unusable for some reason, I can delete it and you can request another.
- Brian
10:54 a.m.
New subject: how can i know what network allocated to me ?;
Thank you for your dedicated work
Im now fitting the Cisco Router to the correct network addresses
hopefully (if the ISP doesnt block IPIP protocole4) i will be connected later this
evening
Ronen - 4Z4ZQ
-----------------------------
It is allocated to you and no one else has been using it.
Since there is apparently no active coordinator for
Israel and your request had been sitting for months, I acted upon
the request so you could get started on your networking project.
1:04 p.m.
New subject: how can i know what network allocated to me ?;
Ronen,
Are you aware that you need to set up 1 tunnel for each registered gateway
in the portal?
The AMPR network is a full mesh network, so a single tunnel will not do.
There is NO gateway for all connections.
Marius, YO2LOJ
-----Original Message-----
From: R P
Sent: Thursday, February 18, 2016 17:54
To: AMPRNet working group
Subject: Re: [44net] how can i know what network allocated to me ?;
(Please trim inclusions from previous messages)
_______________________________________________
Thank you for your dedicated work
Im now fitting the Cisco Router to the correct network addresses
hopefully (if the ISP doesnt block IPIP protocole4) i will be connected
later this evening
Ronen - 4Z4ZQ
1:14 p.m.
New subject: how can i know what network allocated to me ?;
Dear Marius
There are several solutions for that
i did it with Cisco 20 years ago and I know that there is at least one gateway that use
Cisco active and running now
So im not the first one who use Cisco
Best Regards
Ronen - 4Z4ZQ
http://www.ronen.org
________________________________________
From: 44Net <44net-bounces+ronenp=hotmail.com(a)hamradio.ucsd.edu> on behalf of Marius
Petrescu <marius(a)yo2loj.ro>
Sent: Thursday, February 18, 2016 10:04 AM
To: AMPRNet working group
Subject: Re: [44net] how can i know what network allocated to me ?;
(Please trim inclusions from previous messages)
_______________________________________________
Ronen,
Are you aware that you need to set up 1 tunnel for each registered gateway
in the portal?
The AMPR network is a full mesh network, so a single tunnel will not do.
There is NO gateway for all connections.
Marius, YO2LOJ
1:26 p.m.
New subject: how can i know what network allocated to me ?;
Dear Ronen,
No problem, have fun with it :-)
Because that's the primary role of our hobby.
Just that the network changed a little bit. 20 years ago you had a default
route 44.0.0.0/8 via mirrorshades.uscd.edu, which allowed forwarding between
tunnels.
This does not work anymore in the current configuration. The gateway only
forwards from/to the internet, not between tunnel endpoints.
I don't want to discourage you, but this is more than a single evening job
in my oppinion.
Marius, YO2LOJ
-----Original Message-----
From: R P
Sent: Thursday, February 18, 2016 20:14
To: AMPRNet working group
Subject: Re: [44net] how can i know what network allocated to me ?;
(Please trim inclusions from previous messages)
_______________________________________________
Dear Marius
There are several solutions for that
i did it with Cisco 20 years ago and I know that there is at least one
gateway that use Cisco active and running now
So im not the first one who use Cisco
Best Regards
Ronen - 4Z4ZQ
http://www.ronen.org
________________________________________
From: 44Net <44net-bounces+ronenp=hotmail.com(a)hamradio.ucsd.edu> on behalf
of Marius Petrescu <marius(a)yo2loj.ro>
Sent: Thursday, February 18, 2016 10:04 AM
To: AMPRNet working group
Subject: Re: [44net] how can i know what network allocated to me ?;
(Please trim inclusions from previous messages)
_______________________________________________
Ronen,
Are you aware that you need to set up 1 tunnel for each registered gateway
in the portal?
The AMPR network is a full mesh network, so a single tunnel will not do.
There is NO gateway for all connections.
Marius, YO2LOJ
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
1:24 p.m.
New subject: Help in finding Tunnel Problem
Hello Folks
I have setup My Cisco to do Tunnel to 132.239.255.131
I have entered the name in AMPR DNS but (as i was afraid) no connectivity
The Cisco is open from the outside world in its Commercial IP (in name resolving its
4z4zq-cam.no-ip.org)
I can traceoute to its IP from the outside world and of course can traceoute from it to
the outside world
but when tracing out to its its 44 net ip it stop at UCSD
any one have ideas what to check ?
Please Advice
Thanks Forward
Ronen - 4Z4ZQ
http://www.ronen.org
enclosed traceroute from outside world
traceroute to 44.138.1.1 (44.138.1.1), 30 hops max, 38 byte packets
1 r-bbone3.lim.thunderworx.net (217.27.32.1) 0.431 ms 0.272 ms 0.328 ms
2 primetel.j1.lim.nsp-transit.net (78.158.134.198) 0.258 ms 0.452 ms 0.289 ms
3 ae1-3033.j1.fra-nsp-transit.net (78.158.141.189) 54.223 ms
ae0-3067-j1.lon.nsp-transit.net (194.154.142.65) 84.694 ms 84.061 ms
4 ffm-b10-link.telia.net (80.239.193.177) 61.008 ms ldn-b3-link.telia.net
(80.239.193.173) 73.028 ms 78.573 ms
5 ldn-bb3-link.telia.net (80.91.249.171) 83.242 ms ffm-bb2-link.telia.net
(80.91.247.188) 60.446 ms ldn-bb2-link.telia.net (80.91.249.177) 83.127 ms
6 ffm-b12-link.telia.net (62.115.142.51) 54.323 ms adm-bb4-link.telia.net
(62.115.136.192) 83.152 ms ffm-b12-link.telia.net (62.115.142.41) 61.720 ms
7 limelight-ic-308377-ffm-b12.c.telia.net (213.248.89.38) 69.432 ms
adm-b7-link.telia.net (213.155.134.95) 83.094 ms limelight-ic-141253-ffm-b12.c.telia.net
(213.248.95.146) 58.128 ms
8 tge10-3.fr3.ams.llnw.net (69.28.172.159) 74.244 ms tge10-1.fr3.ams.llnw.net
(69.28.172.157) 78.235 ms tge14-4.fr4.ams.llnw.net (69.28.171.55) 82.757 ms
9 tge2-6.fr4.lga.llnw.net (69.28.189.49) 146.822 ms tge1-2.fr4.ams.llnw.net
(69.28.171.53) 66.660 ms tge2-6.fr4.lga.llnw.net (69.28.189.49) 143.679 ms
10 ve5.fr4.lga.llnw.net (69.28.172.206) 164.259 ms tge1-2.fr4.ord.llnw.net
(69.28.172.198) 154.737 ms tge2-6.fr4.lga.llnw.net (69.28.189.49) 161.865 ms
11 tge1-3.fr4.sjc.llnw.net (69.28.172.77) 229.464 ms tge1-2.fr4.ord.llnw.net
(69.28.172.198) 160.873 ms tge1-3.fr4.sjc.llnw.net (69.28.172.77) 227.680 ms
12 paix-px1--limelight-10ge.cenic.net (198.32.251.193) 247.958 ms
tge1-3.fr4.sjc.llnw.net (69.28.172.77) 226.358 ms paix-px1--limelight-10ge.cenic.net
(198.32.251.193) 231.058 ms
13 paix-px1--limelight-10ge.cenic.net (198.32.251.193) 222.219 ms
dc-lax-agg6--svl-agg4-100ge.cenic.net (137.164.11.0) 207.587 ms
paix-px1--limelight-10ge.cenic.net (198.32.251.193) 227.640 ms
14 dc-tus-agg3--lax-agg6-100ge.cenic.net (137.164.11.7) 223.558 ms
dc-lax-agg6--svl-agg4-100ge.cenic.net (137.164.11.0) 213.351 ms
dc-tus-agg3--lax-agg6-100ge.cenic.net (137.164.11.7) 228.071 ms
15 dc-tus-agg3--lax-agg6-100ge.cenic.net (137.164.11.7) 221.416 ms
dc-sdg-agg4--tus-agg3-100ge.cenic.net (137.164.11.9) 244.668 ms
dc-tus-agg3--lax-agg6-100ge.cenic.net (137.164.11.7) 235.076 ms
16 dc-sdg-agg4--tus-agg3-100ge.cenic.net (137.164.11.9) 253.750 ms 239.376 ms
dc-ucsd-1--sdg-agg4.cenic.net (137.164.23.54) 231.692 ms
17 mcore-flow-bypass-mx0-p2p.ucsd.edu (132.239.254.61) 235.549 ms 241.887 ms 249.523
ms
18 nodem-core-6807-vlan2767-gw.ucsd.edu (132.239.254.61) 231.799 ms
ebu3b-6509-720-vlan910-gw1.ucsd.edu (132.239.255.131) 226.411 ms 218.265 ms
19 ebu3b-6509-nodem-core-interconnect-vl910-bcast-255-131.ucsd.edu (132.239.255.131)
238.085 ms amprgw.sysnet.ucsd.edu (169.228.66.251) 239.359 ms
ebu3b-6509-720-vlan910-gw1.ucsd.edu (132.239.255.131) 220.126 ms
20 * * *
21 * *
for the Cisco Experts i can give the config of it
here is the interfaces setup
Async1 is down, line protocol is down
Hardware is QUICC Async
MTU 1500 bytes, BW 9 Kbit, DLY 100000 usec, rely 255/255, load 1/255
Encapsulation SLIP, loopback not set
DTR is pulsed for 5 seconds on reset
Last input never, output 7w0d, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: weighted fair
Output queue: 0/1000/64/0 (size/max total/threshold/drops)
Conversations 0/0/256 (active/max active/max total)
Reserved Conversations 0/0 (allocated/max allocated)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 packets output, 0 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 output buffer failures, 0 output buffers swapped out
0 carrier transitions
Ethernet0 is up, line protocol is up
Hardware is QUICC Ethernet, address is 00d0.58da.4fd8 (bia 00d0.58da.4fd8)
Description: connected to EthernetLAN_HAIFA
Internet address is 10.0.0.180/24
MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec, rely 255/255, load 1/255
Encapsulation ARPA, loopback not set, keepalive set (10 sec)
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:00, output 00:00:07, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue 0/40 (size/max)
5 minute input rate 0 bits/sec, 2 packets/sec
5 minute output rate 1000 bits/sec, 1 packets/sec
651456 packets input, 53783714 bytes, 8 no buffer
Received 642348 broadcasts, 0 runts, 0 giants, 8 throttles
1 input errors, 0 CRC, 1 frame, 0 overrun, 0 ignored, 0 abort
0 input packets with dribble condition detected
658579 packets output, 60213808 bytes, 0 underruns
247 output errors, 26 collisions, 2 interface resets
0 babbles, 0 late collision, 156 deferred
247 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out
Tunnel0 is up, line protocol is up
Hardware is Tunnel
Interface is unnumbered. Using address of Ethernet0 (10.0.0.180)
MTU 1514 bytes, BW 9 Kbit, DLY 500000 usec, rely 255/255, load 1/255
Encapsulation TUNNEL, loopback not set, keepalive set (10 sec)
Tunnel source 10.0.0.180 (Ethernet0), destination 132.239.255.131
Tunnel protocol/transport IP/IP, key disabled, sequencing disabled
Checksumming of packets disabled
Last input never, output 00:00:19, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 93677
Queueing strategy: fifo
Output queue 0/0 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
152885 packets output, 16457928 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 output buffer failures, 0 output buffers swapped out
Cisco1005_HAIFA#
________________________________________
1:28 p.m.
New subject: Help in finding Tunnel Problem
Unless your 44 IP has a DNS entry at ucsd, it will not be forwarded and not
reachable from the internet.
-----Original Message-----
From: R P
Sent: Thursday, February 18, 2016 20:24
To: AMPRNet working group
Subject: [44net] Help in finding Tunnel Problem
(Please trim inclusions from previous messages)
_______________________________________________
Hello Folks
I have setup My Cisco to do Tunnel to 132.239.255.131
I have entered the name in AMPR DNS but (as i was afraid) no
connectivity
The Cisco is open from the outside world in its Commercial IP (in name
resolving its 4z4zq-cam.no-ip.org)
I can traceoute to its IP from the outside world and of course can
traceoute from it to the outside world
but when tracing out to its its 44 net ip it stop at UCSD
any one have ideas what to check ?
Please Advice
Thanks Forward
Ronen - 4Z4ZQ
http://www.ronen.org
enclosed traceroute from outside world
traceroute to 44.138.1.1 (44.138.1.1), 30 hops max, 38 byte packets
1 r-bbone3.lim.thunderworx.net (217.27.32.1) 0.431 ms 0.272 ms 0.328 ms
2 primetel.j1.lim.nsp-transit.net (78.158.134.198) 0.258 ms 0.452 ms
0.289 ms
3 ae1-3033.j1.fra-nsp-transit.net (78.158.141.189) 54.223 ms
ae0-3067-j1.lon.nsp-transit.net (194.154.142.65) 84.694 ms 84.061 ms
4 ffm-b10-link.telia.net (80.239.193.177) 61.008 ms ldn-b3-link.telia.net
(80.239.193.173) 73.028 ms 78.573 ms
5 ldn-bb3-link.telia.net (80.91.249.171) 83.242 ms ffm-bb2-link.telia.net
(80.91.247.188) 60.446 ms ldn-bb2-link.telia.net (80.91.249.177) 83.127 ms
6 ffm-b12-link.telia.net (62.115.142.51) 54.323 ms adm-bb4-link.telia.net
(62.115.136.192) 83.152 ms ffm-b12-link.telia.net (62.115.142.41) 61.720
ms
7 limelight-ic-308377-ffm-b12.c.telia.net (213.248.89.38) 69.432 ms
adm-b7-link.telia.net (213.155.134.95) 83.094 ms
limelight-ic-141253-ffm-b12.c.telia.net (213.248.95.146) 58.128 ms
8 tge10-3.fr3.ams.llnw.net (69.28.172.159) 74.244 ms
tge10-1.fr3.ams.llnw.net (69.28.172.157) 78.235 ms tge14-4.fr4.ams.llnw.net
(69.28.171.55) 82.757 ms
9 tge2-6.fr4.lga.llnw.net (69.28.189.49) 146.822 ms
tge1-2.fr4.ams.llnw.net (69.28.171.53) 66.660 ms tge2-6.fr4.lga.llnw.net
(69.28.189.49) 143.679 ms
10 ve5.fr4.lga.llnw.net (69.28.172.206) 164.259 ms tge1-2.fr4.ord.llnw.net
(69.28.172.198) 154.737 ms tge2-6.fr4.lga.llnw.net (69.28.189.49) 161.865
ms
11 tge1-3.fr4.sjc.llnw.net (69.28.172.77) 229.464 ms
tge1-2.fr4.ord.llnw.net (69.28.172.198) 160.873 ms tge1-3.fr4.sjc.llnw.net
(69.28.172.77) 227.680 ms
12 paix-px1--limelight-10ge.cenic.net (198.32.251.193) 247.958 ms
tge1-3.fr4.sjc.llnw.net (69.28.172.77) 226.358 ms
paix-px1--limelight-10ge.cenic.net (198.32.251.193) 231.058 ms
13 paix-px1--limelight-10ge.cenic.net (198.32.251.193) 222.219 ms
dc-lax-agg6--svl-agg4-100ge.cenic.net (137.164.11.0) 207.587 ms
paix-px1--limelight-10ge.cenic.net (198.32.251.193) 227.640 ms
14 dc-tus-agg3--lax-agg6-100ge.cenic.net (137.164.11.7) 223.558 ms
dc-lax-agg6--svl-agg4-100ge.cenic.net (137.164.11.0) 213.351 ms
dc-tus-agg3--lax-agg6-100ge.cenic.net (137.164.11.7) 228.071 ms
15 dc-tus-agg3--lax-agg6-100ge.cenic.net (137.164.11.7) 221.416 ms
dc-sdg-agg4--tus-agg3-100ge.cenic.net (137.164.11.9) 244.668 ms
dc-tus-agg3--lax-agg6-100ge.cenic.net (137.164.11.7) 235.076 ms
16 dc-sdg-agg4--tus-agg3-100ge.cenic.net (137.164.11.9) 253.750 ms
239.376 ms dc-ucsd-1--sdg-agg4.cenic.net (137.164.23.54) 231.692 ms
17 mcore-flow-bypass-mx0-p2p.ucsd.edu (132.239.254.61) 235.549 ms 241.887
ms 249.523 ms
18 nodem-core-6807-vlan2767-gw.ucsd.edu (132.239.254.61) 231.799 ms
ebu3b-6509-720-vlan910-gw1.ucsd.edu (132.239.255.131) 226.411 ms 218.265
ms
19 ebu3b-6509-nodem-core-interconnect-vl910-bcast-255-131.ucsd.edu
(132.239.255.131) 238.085 ms amprgw.sysnet.ucsd.edu (169.228.66.251)
239.359 ms ebu3b-6509-720-vlan910-gw1.ucsd.edu (132.239.255.131) 220.126 ms
20 * * *
21 * *
for the Cisco Experts i can give the config of it
here is the interfaces setup
Async1 is down, line protocol is down
Hardware is QUICC Async
MTU 1500 bytes, BW 9 Kbit, DLY 100000 usec, rely 255/255, load 1/255
Encapsulation SLIP, loopback not set
DTR is pulsed for 5 seconds on reset
Last input never, output 7w0d, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: weighted fair
Output queue: 0/1000/64/0 (size/max total/threshold/drops)
Conversations 0/0/256 (active/max active/max total)
Reserved Conversations 0/0 (allocated/max allocated)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 packets output, 0 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 output buffer failures, 0 output buffers swapped out
0 carrier transitions
Ethernet0 is up, line protocol is up
Hardware is QUICC Ethernet, address is 00d0.58da.4fd8 (bia 00d0.58da.4fd8)
Description: connected to EthernetLAN_HAIFA
Internet address is 10.0.0.180/24
MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec, rely 255/255, load 1/255
Encapsulation ARPA, loopback not set, keepalive set (10 sec)
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:00, output 00:00:07, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue 0/40 (size/max)
5 minute input rate 0 bits/sec, 2 packets/sec
5 minute output rate 1000 bits/sec, 1 packets/sec
651456 packets input, 53783714 bytes, 8 no buffer
Received 642348 broadcasts, 0 runts, 0 giants, 8 throttles
1 input errors, 0 CRC, 1 frame, 0 overrun, 0 ignored, 0 abort
0 input packets with dribble condition detected
658579 packets output, 60213808 bytes, 0 underruns
247 output errors, 26 collisions, 2 interface resets
0 babbles, 0 late collision, 156 deferred
247 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out
Tunnel0 is up, line protocol is up
Hardware is Tunnel
Interface is unnumbered. Using address of Ethernet0 (10.0.0.180)
MTU 1514 bytes, BW 9 Kbit, DLY 500000 usec, rely 255/255, load 1/255
Encapsulation TUNNEL, loopback not set, keepalive set (10 sec)
Tunnel source 10.0.0.180 (Ethernet0), destination 132.239.255.131
Tunnel protocol/transport IP/IP, key disabled, sequencing disabled
Checksumming of packets disabled
Last input never, output 00:00:19, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 93677
Queueing strategy: fifo
Output queue 0/0 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
152885 packets output, 16457928 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 output buffer failures, 0 output buffers swapped out
Cisco1005_HAIFA#
________________________________________
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
2:23 p.m.
New subject: Help in finding Tunnel Problem
Ok I have little progress with the correct tunnel address
the tunnel interface seem to receive packets when i trace route to its 44 net from the
outside world and appear to send packet as reply but still no go
I have taken all access list out
any help is welcome
Please Advice
Ronen - 4Z4ZQ
http://www.ronen.org
Cisco1005_HAIFA#sh int tun0
Tunnel0 is up, line protocol is up
Hardware is Tunnel
Interface is unnumbered. Using address of Ethernet0 (10.0.0.180)
MTU 1514 bytes, BW 9 Kbit, DLY 500000 usec, rely 255/255, load 1/255
Encapsulation TUNNEL, loopback not set, keepalive set (10 sec)
Tunnel source 10.0.0.180 (Ethernet0), destination 169.228.66.251
Tunnel protocol/transport IP/IP, key disabled, sequencing disabled
Checksumming of packets disabled
Last input 00:00:02, output 00:00:28, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 93677
Queueing strategy: fifo
Output queue 0/0 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
395 packets input, 94081 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
153001 packets output, 16476952 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 output buffer failures, 0 output buffers swapped out
Cisco1005_HAIFA#
Cisco1005_HAIFA#
Cisco1005_HAIFA#sh int tun0
Tunnel0 is up, line protocol is up
Hardware is Tunnel
Interface is unnumbered. Using address of Ethernet0 (10.0.0.180)
MTU 1514 bytes, BW 9 Kbit, DLY 500000 usec, rely 255/255, load 1/255
Encapsulation TUNNEL, loopback not set, keepalive set (10 sec)
Tunnel source 10.0.0.180 (Ethernet0), destination 169.228.66.251
Tunnel protocol/transport IP/IP, key disabled, sequencing disabled
Checksumming of packets disabled
Last input 00:00:01, output 00:00:08, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 93677
Queueing strategy: fifo
Output queue 0/0 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
505 packets input, 120749 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
153015 packets output, 16479248 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 output buffer failures, 0 output buffers swapped out
Cisco1005_HAIFA#
________________________________________
From: 44Net <44net-bounces+ronenp=hotmail.com(a)hamradio.ucsd.edu> on behalf of Brian
Kantor <Brian(a)UCSD.Edu>
Sent: Thursday, February 18, 2016 10:29 AM
To: AMPRNet working group
Subject: Re: [44net] Help in finding Tunnel Problem
(Please trim inclusions from previous messages)
_______________________________________________
On Thu, Feb 18, 2016 at 06:24:15PM +0000, R P wrote:
I have setup My Cisco to do Tunnel to
132.239.255.131
That is the wrong address. The UCSD tunnel is at 169.228.66.251.
- Brian
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
4:39 p.m.
New subject: Help in finding Tunnel Problem
Can you check that the replies use the tunnel endpoint's address as source
(44.138.1.1), and use the tunnel interface as outgoing If?
It happens on some machines that the replies are sent through the external
interface instead of the tunnel...
-----Original Message-----
From: R P
Sent: Thursday, February 18, 2016 21:23
To: AMPRNet working group
Subject: Re: [44net] Help in finding Tunnel Problem
(Please trim inclusions from previous messages)
_______________________________________________
Ok I have little progress with the correct tunnel address
the tunnel interface seem to receive packets when i trace route to its 44
net from the outside world and appear to send packet as reply but still
no go
I have taken all access list out
any help is welcome
Please Advice
Ronen - 4Z4ZQ
http://www.ronen.org
Cisco1005_HAIFA#sh int tun0
Tunnel0 is up, line protocol is up
Hardware is Tunnel
Interface is unnumbered. Using address of Ethernet0 (10.0.0.180)
MTU 1514 bytes, BW 9 Kbit, DLY 500000 usec, rely 255/255, load 1/255
Encapsulation TUNNEL, loopback not set, keepalive set (10 sec)
Tunnel source 10.0.0.180 (Ethernet0), destination 169.228.66.251
Tunnel protocol/transport IP/IP, key disabled, sequencing disabled
Checksumming of packets disabled
Last input 00:00:02, output 00:00:28, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 93677
Queueing strategy: fifo
Output queue 0/0 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
395 packets input, 94081 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
153001 packets output, 16476952 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 output buffer failures, 0 output buffers swapped out
Cisco1005_HAIFA#
Cisco1005_HAIFA#
Cisco1005_HAIFA#sh int tun0
Tunnel0 is up, line protocol is up
Hardware is Tunnel
Interface is unnumbered. Using address of Ethernet0 (10.0.0.180)
MTU 1514 bytes, BW 9 Kbit, DLY 500000 usec, rely 255/255, load 1/255
Encapsulation TUNNEL, loopback not set, keepalive set (10 sec)
Tunnel source 10.0.0.180 (Ethernet0), destination 169.228.66.251
Tunnel protocol/transport IP/IP, key disabled, sequencing disabled
Checksumming of packets disabled
Last input 00:00:01, output 00:00:08, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 93677
Queueing strategy: fifo
Output queue 0/0 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
505 packets input, 120749 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
153015 packets output, 16479248 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 output buffer failures, 0 output buffers swapped out
Cisco1005_HAIFA#
________________________________________
From: 44Net <44net-bounces+ronenp=hotmail.com(a)hamradio.ucsd.edu> on behalf
of Brian Kantor <Brian(a)UCSD.Edu>
Sent: Thursday, February 18, 2016 10:29 AM
To: AMPRNet working group
Subject: Re: [44net] Help in finding Tunnel Problem
(Please trim inclusions from previous messages)
_______________________________________________
On Thu, Feb 18, 2016 at 06:24:15PM +0000, R P wrote:
I have setup My Cisco to do Tunnel to
132.239.255.131
That is the wrong address. The UCSD tunnel is at 169.228.66.251.
- Brian
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
5:06 p.m.
New subject: Help in finding Tunnel Problem
how can i check it the only thing is to i can do is publish the config file ...
is there any tool that i can use to verify this ? if ill put network analyzer (as
wireshark) will it be able to help
________________________________________
From: 44Net <44net-bounces+ronenp=hotmail.com(a)hamradio.ucsd.edu> on behalf of Marius
Petrescu <marius(a)yo2loj.ro>
Sent: Thursday, February 18, 2016 1:39 PM
To: AMPRNet working group
Subject: Re: [44net] Help in finding Tunnel Problem
(Please trim inclusions from previous messages)
_______________________________________________
Can you check that the replies use the tunnel endpoint's address as source
(44.138.1.1), and use the tunnel interface as outgoing If?
It happens on some machines that the replies are sent through the external
interface instead of the tunnel...
5:13 p.m.
New subject: Help in finding Tunnel Problem
If you can run wireshark on your external interface, you can see exactly if
the replies are ok:
They must have a first IP layer, IP proto 4 (IPIP) with src your GW public
address and destination 169.228.66.251.
The second layer has to have IP proto 1 (ICMP) or 6(TCP) or 17 (UDP)
depending on the connection you use, have src address 44.138.1.1 and
destination the public IP of the machine from which you are testing.
I hope this helps...
Marius, YO2LOJ
-----Original Message-----
From: R P
Sent: Friday, February 19, 2016 00:06
To: AMPRNet working group
Subject: Re: [44net] Help in finding Tunnel Problem
(Please trim inclusions from previous messages)
_______________________________________________
how can i check it the only thing is to i can do is publish the config
file ...
is there any tool that i can use to verify this ? if ill put network
analyzer (as wireshark) will it be able to help
________________________________________
From: 44Net <44net-bounces+ronenp=hotmail.com(a)hamradio.ucsd.edu> on behalf
of Marius Petrescu <marius(a)yo2loj.ro>
Sent: Thursday, February 18, 2016 1:39 PM
To: AMPRNet working group
Subject: Re: [44net] Help in finding Tunnel Problem
(Please trim inclusions from previous messages)
_______________________________________________
Can you check that the replies use the tunnel endpoint's address as source
(44.138.1.1), and use the tunnel interface as outgoing If?
It happens on some machines that the replies are sent through the external
interface instead of the tunnel...
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
5:21 p.m.
New subject: Help in finding Tunnel Problem
Thank you i will do it tomorrow i have also copied the old good Jnos i used to run 20
years ago it was using bi directional tunnel i will see if it will work tomorrow (its
now midnight here)
Ill probably ask more questions tomorrow
Thanks For all your efforts
73's
Ronen - 4Z4ZQ
http:/www.ronen.org
________________________________________
From: 44Net <44net-bounces+ronenp=hotmail.com(a)hamradio.ucsd.edu> on behalf of Marius
Petrescu <marius(a)yo2loj.ro>
Sent: Thursday, February 18, 2016 2:13 PM
To: AMPRNet working group
Subject: Re: [44net] Help in finding Tunnel Problem
(Please trim inclusions from previous messages)
_______________________________________________
If you can run wireshark on your external interface, you can see exactly if
the replies are ok:
They must have a first IP layer, IP proto 4 (IPIP) with src your GW public
address and destination 169.228.66.251.
The second layer has to have IP proto 1 (ICMP) or 6(TCP) or 17 (UDP)
depending on the connection you use, have src address 44.138.1.1 and
destination the public IP of the machine from which you are testing.
I hope this helps...
Marius, YO2LOJ
-
19 Feb
19 Feb
11:16 a.m.
New subject: Help in finding Tunnel Problem
Ok i have run the old good Jnos-Dos that used to run on our gateways 20 years ago on
my PC
I have changed the UCSD tunnel to the updated adress and ..... Its working
I have 44 net connectivity
Now i know that the ISP doesnt block IPIP Protocole 4
The Cisco Router refuse to give me connectivity
Is there anyone that may look on my cisco ? its accessible from the Internet to all
addresses
and im willing to give the Passwords
Thanks for any assistance
Regards
Ronen - 4Z4ZQ
http://www.ronen.org
traceroute to 44.138.1.1 (44.138.1.1), 30 hops max, 38 byte packets
1 r-bbone3.lim.thunderworx.net (217.27.32.1) 0.308 ms 3.663 ms 0.633 ms
2 primetel.j1.lim.nsp-transit.net (78.158.134.198) 0.519 ms 0.292 ms 0.284 ms
3 v3038.j1.fra.prime-tel.net (78.158.141.201) 71.966 ms ae0-3072-j1.lon.nsp-transit.net
(194.154.142.218) 61.180 ms 61.386 ms
4 ldn-b3-link.telia.net (80.239.193.173) 72.930 ms 73.066 ms 73.982 ms
5 ldn-bb2-link.telia.net (62.115.140.250) 78.027 ms ldn-bb3-link.telia.net
(80.91.250.242) 83.353 ms ffm-bb2-link.telia.net (80.91.247.188) 114.631 ms
6 ffm-b12-link.telia.net (62.115.142.69) 66.343 ms ffm-b12-link.telia.net
(62.115.142.47) 68.232 ms adm-bb3-link.telia.net (62.115.134.24) 80.982 ms
7 adm-b7-link.telia.net (213.155.133.37) 86.444 ms adm-b7-link.telia.net
(80.91.245.245) 84.839 ms adm-b7-link.telia.net (80.91.245.247) 86.594 ms
8 limelight-ic-154704-adm-b7.c.telia.net (80.239.194.114) 85.180 ms 73.212 ms
tge10-3.fr3.ams.llnw.net (69.28.172.159) 93.671 ms
9 tge2-6.fr4.lga.llnw.net (69.28.189.49) 184.769 ms tge14-4.fr4.ams.llnw.net
(69.28.171.55) 72.771 ms tge1-6.fr3.lga.llnw.net (69.28.189.45) 164.258 ms
10 tge2-6.fr4.lga.llnw.net (69.28.189.49) 157.808 ms tge8-4.fr3.ord.llnw.net
(69.28.171.193) 181.141 ms tge1-2.fr4.ord.llnw.net (69.28.172.198) 159.312 ms
11 tge1-2.fr4.ord.llnw.net (69.28.172.198) 151.579 ms 183.250 ms 183.850 ms
12 tge1-3.fr4.sjc.llnw.net (69.28.172.77) 230.780 ms paix-px1--limelight-10ge.cenic.net
(198.32.251.193) 232.363 ms 228.501 ms
13 dc-lax-agg6--svl-agg4-100ge.cenic.net (137.164.11.0) 207.446 ms 207.895 ms
paix-px1--limelight-10ge.cenic.net (198.32.251.193) 236.867 ms
14 dc-tus-agg3--lax-agg6-100ge.cenic.net (137.164.11.7) 228.807 ms 228.557 ms 235.841
ms
15 dc-sdg-agg4--tus-agg3-100ge.cenic.net (137.164.11.9) 227.139 ms
dc-tus-agg3--lax-agg6-100ge.cenic.net (137.164.11.7) 229.143 ms 236.821 ms
16 dc-sdg-agg4--tus-agg3-100ge.cenic.net (137.164.11.9) 252.493 ms 249.273 ms 252.745
ms
17 dc-ucsd-1--sdg-agg4.cenic.net (137.164.23.54) 243.466 ms
ucsd--sdg-agg4-10g-2.cenic.net (137.164.23.178) 229.376 ms 237.121 ms
18 mcore-flow-bypass-mx0-p2p.ucsd.edu (132.239.254.61) 253.590 ms 270.037 ms
ebu3b-6509-nodem-core-interconnect-vl910-bcast-255-131.ucsd.edu (132.239.255.131) 233.553
ms
19 amprgw.sysnet.ucsd.edu (169.228.66.251) 249.997 ms 249.896 ms
ebu3b-6509-nodem-core-interconnect-vl910-bcast-255-131.ucsd.edu (132.239.255.131) 250.050
ms
20 amprgw.sysnet.ucsd.edu (169.228.66.251) 260.708 ms 250.738 ms *
21 * * *
22 * haifa-cisco-1005.ampr.org (44.138.1.1) 2640.418 ms
________________________________________
From: 44Net <44net-bounces+ronenp=hotmail.com(a)hamradio.ucsd.edu> on behalf of R P
<ronenp(a)hotmail.com>
Sent: Thursday, February 18, 2016 2:21 PM
To: AMPRNet working group
Subject: Re: [44net] Help in finding Tunnel Problem
(Please trim inclusions from previous messages)
_______________________________________________
Thank you i will do it tomorrow i have also copied the old good Jnos i used to run 20
years ago it was using bi directional tunnel i will see if it will work tomorrow (its
now midnight here)
Ill probably ask more questions tomorrow
Thanks For all your efforts
73's
Ronen - 4Z4ZQ
http:/www.ronen.org
________________________________________
From: 44Net <44net-bounces+ronenp=hotmail.com(a)hamradio.ucsd.edu> on behalf of Marius
Petrescu <marius(a)yo2loj.ro>
Sent: Thursday, February 18, 2016 2:13 PM
To: AMPRNet working group
Subject: Re: [44net] Help in finding Tunnel Problem
(Please trim inclusions from previous messages)
_______________________________________________
If you can run wireshark on your external interface, you can see exactly if
the replies are ok:
They must have a first IP layer, IP proto 4 (IPIP) with src your GW public
address and destination 169.228.66.251.
The second layer has to have IP proto 1 (ICMP) or 6(TCP) or 17 (UDP)
depending on the connection you use, have src address 44.138.1.1 and
destination the public IP of the machine from which you are testing.
I hope this helps...
Marius, YO2LOJ
-
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
17 Feb
17 Feb
6:41 p.m.
On February 17, 2016 6:29:47 PM EST, Assi Friedman <assi(a)kiloxray.com> wrote:
2) Do you have any notion if specific ISPs are more
open to allow BGP
advertising than others?
Most people are doing this by having friends or friendly ISPs or benefactors. I would
think very few are paying for commercial bgp sessions for 44net only.
3) Have any AMPRNet users had luck getting BGP
agreements with home
class
service?
No. Most (all) home broadband services will not do bgp in the traditional sense. CMTS
are not keen on it, but some times they will do BGP multihop, generally most MSOs are
large enough that a custom config is not possible for your cable modem. Same goes for
PON, most are doing DPOE, and can't/won't change for one customer.
Hamwan Seattle will announce it for you and tunnel it back, and I'll do the same from
Tampa if you want, but at that point doing BGP routing doesn't have much value over
UCSD.
73s
--
Bryan Fields
727-409-1194
http://bryanfields.net
6:50 p.m.
On Wed, Feb 17, 2016 at 3:29 PM, Assi Friedman <assi(a)kiloxray.com> wrote:
1) How many AMPRNet subnets are currently being
advertised via BGP?
This is a fun exercise to test yourself:
telnet route-views.oregon-ix.net
route-views>show ip route 44.0.0.0
Routing entry for 44.0.0.0/8, 74 known subnets
Variably subnetted with 8 masks
B 44.0.0.0/8 [20/0] via 216.218.252.164, 3w5d
B 44.4.44.0/24 [20/0] via 216.218.252.164, 2w5d
B 44.4.64.0/22 [20/0] via 202.232.0.2, 3w5d
B 44.4.128.0/22 [20/0] via 216.218.252.164, 4d06h
B 44.10.10.0/24 [20/0] via 202.232.0.2, 3w0d
B 44.12.6.0/24 [20/0] via 216.218.252.164, 2w5d
B 44.16.15.0/24 [20/39] via 129.250.0.11, 2w6d
B 44.24.132.0/24 [20/0] via 216.218.252.164, 3w1d
B 44.24.200.0/23 [20/0] via 216.218.252.164, 04:22:17
B 44.24.221.0/24 [20/0] via 216.218.252.164, 2w5d
B 44.24.240.0/20 [20/0] via 12.0.1.63, 3w3d
B 44.24.240.0/21 [20/0] via 216.218.252.164, 2w5d
B 44.24.248.0/21 [20/0] via 216.218.252.164, 2w5d
B 44.25.0.0/16 [20/0] via 4.69.184.193, 2w6d
B 44.34.96.0/24 [20/78] via 129.250.0.11, 1d19h
B 44.34.128.0/21 [20/0] via 216.218.252.164, 1d12h
B 44.36.240.0/21 [20/0] via 216.218.252.164, 5d14h
B 44.48.16.0/24 [20/0] via 216.218.252.164, 2w6d
B 44.48.24.0/22 [20/0] via 12.0.1.63, 3w5d
B 44.68.52.0/24 [20/10] via 89.149.178.10, 3w5d
B 44.74.128.0/24 [20/0] via 217.192.89.50, 3w0d
B 44.98.252.0/24 [20/0] via 4.69.184.193, 3w5d
B 44.98.254.0/24 [20/0] via 4.69.184.193, 3w5d
B 44.103.0.0/19 [20/0] via 216.218.252.164, 2w3d
B 44.103.32.0/23 [20/0] via 216.218.252.164, 3w5d
B 44.103.34.0/24 [20/0] via 4.69.184.193, 6d16h
B 44.103.35.0/24 [20/0] via 216.218.252.164, 3w0d
B 44.103.39.0/24 [20/0] via 216.218.252.164, 6d02h
B 44.110.0.0/24 [20/57] via 129.250.0.11, 5d07h
B 44.127.1.0/24 [20/0] via 4.69.184.193, 1w0d
B 44.127.16.0/20 [20/0] via 216.218.252.164, 1w5d
B 44.127.128.0/24 [20/0] via 103.247.3.45, 3w5d
B 44.130.99.0/24 [20/0] via 103.247.3.45, 3w5d
B 44.130.112.0/24 [20/0] via 103.247.3.45, 4d21h
B 44.130.120.0/24 [20/0] via 216.218.252.164, 3w5d
B 44.131.10.0/24 [20/13863] via 208.51.134.254, 1w6d
B 44.131.12.0/24 [20/0] via 216.218.252.164, 2w0d
B 44.134.38.0/23 [20/0] via 4.69.184.193, 3w2d
B 44.135.120.0/24 [20/0] via 216.218.252.164, 3w5d
B 44.135.130.0/23 [20/0] via 206.24.210.80, 6d04h
B 44.135.193.0/24 [20/10] via 89.149.178.10, 3w5d
B 44.135.218.0/24 [20/10] via 89.149.178.10, 3w5d
B 44.136.60.0/23 [20/0] via 103.247.3.45, 2w1d
B 44.136.64.0/22 [20/0] via 103.247.3.45, 2w5d
B 44.136.68.0/24 [20/0] via 103.247.3.45, 2w5d
B 44.136.128.0/23 [20/0] via 202.232.0.2, 1w4d
B 44.136.138.0/24 [20/0] via 203.62.252.83, 2w0d
B 44.136.139.0/24 [20/0] via 103.255.249.22, 3w5d
B 44.136.150.0/24 [20/0] via 203.62.252.83, 1w0d
B 44.136.151.0/24 [20/0] via 103.255.249.22, 3w5d
B 44.136.152.0/23 [20/0] via 203.62.252.83, 1w0d
B 44.136.152.0/24 [20/0] via 203.62.252.83, 1w0d
B 44.136.153.0/24 [20/0] via 203.62.252.83, 1w0d
B 44.136.154.0/24 [20/0] via 103.255.249.22, 3w5d
B 44.136.155.0/24 [20/0] via 103.255.249.22, 3w5d
B 44.136.158.0/23 [20/0] via 114.31.199.1, 2d02h
B 44.136.201.0/24 [20/0] via 103.247.3.45, 3w5d
B 44.136.224.0/24 [20/0] via 203.62.252.83, 2d18h
B 44.136.227.0/24 [20/0] via 203.62.252.83, 2w4d
B 44.137.0.0/16 [20/0] via 5.101.110.2, 6d22h
B 44.139.0.0/16 [20/0] via 202.232.0.2, 3w5d
B 44.140.0.0/16 [20/0] via 217.192.89.50, 3w3d
B 44.141.124.0/24 [20/0] via 216.218.252.164, 6d03h
B 44.141.132.0/24 [20/0] via 216.218.252.164, 6d03h
B 44.141.140.0/22 [20/0] via 144.228.241.130, 3w5d
B 44.144.0.0/16 [20/0] via 103.247.3.45, 3w5d
B 44.159.80.0/20 [20/0] via 216.218.252.164, 2w6d
B 44.161.204.0/23 [20/0] via 216.218.252.164, 12:43:08
B 44.161.222.0/24 [20/0] via 216.218.252.164, 13:08:07
B 44.161.230.0/24 [20/0] via 216.218.252.164, 13:08:07
B 44.161.252.0/22 [20/0] via 216.218.252.164, 13:08:07
B 44.169.48.0/20 [20/0] via 216.218.252.164, 1d09h
B 44.188.128.0/20 [20/0] via 193.0.0.56, 06:47:53
B 44.208.0.0/16 [20/0] via 216.218.252.164, 2w6d
Tom KD7LXL
3198
days inactive
3200
days old
19 comments
6 participants
participants (6)
-
Assi Friedman -
Brian Kantor -
Bryan Fields -
Marius Petrescu -
R P -
Tom Hayward