According to records on the portal, the following 120 (of 275 total) entries in the gateways list are unclaimed - that is, no one has come forward to take ownership of the entry. They therefore appear to be inactive.
I propose we mark these as no longer in service. That will have the effect of no longer including them in the encap list. Eventually we'll delete them from the database if they're not reactivated.
If a gateway that is still valid is listed below, contact me or Chris to get it assigned to the proper registered owner. - Brian
8.22.205.37 12.195.50.128 24.55.199.25 24.84.205.232 24.89.203.65 24.137.76.29 24.212.252.100 24.212.252.109 24.212.252.110 24.224.157.206 50.79.209.150 62.49.17.234 64.22.214.233 64.119.33.202 64.119.42.138 64.255.99.17 65.41.209.137 65.48.61.133 65.70.212.35 66.11.68.11 66.112.51.126 66.114.139.158 67.108.91.190 68.61.222.68 68.188.234.106 68.209.144.3 69.69.168.201 69.137.244.193 69.145.172.163 69.178.117.150 69.254.106.173 70.137.68.217 71.36.92.66 71.107.40.238 71.107.40.238 71.201.92.148 74.85.194.5 75.21.234.175 76.14.161.185 76.64.80.228 76.247.140.206 76.253.114.92 77.249.108.97 79.116.75.255 79.116.81.105 80.59.234.233 80.229.68.173 81.235.253.122 84.92.153.154 89.228.59.72 90.206.95.108 91.84.215.75 94.72.251.181 94.101.48.134 94.172.232.113 96.20.43.106 96.35.76.41 97.84.11.198 98.193.215.29 98.208.81.22 99.88.77.66 99.116.194.13 108.185.66.208 113.212.169.28 118.22.1.194 118.82.200.153 122.108.78.111 130.208.168.63 131.155.192.172 141.85.43.57 142.103.194.1 146.48.126.26 146.48.126.28 148.223.34.6 150.188.8.195 152.66.0.109 155.207.19.57 158.42.128.200 161.53.16.179 168.96.128.17 173.14.57.181 173.177.124.119 173.208.214.53 184.175.46.166 186.125.37.47 189.42.190.50 190.31.163.55 190.139.56.180 192.147.172.252 193.22.2.254 194.27.119.2 195.22.112.28 195.113.115.135 195.150.236.251 198.108.247.220 200.17.207.2 200.46.129.3 201.252.37.40 202.63.57.97 203.5.58.162 203.24.120.198 203.24.120.199 203.24.120.200 203.26.188.134 203.59.134.49 206.251.38.99 207.111.203.194 207.179.123.166 208.74.106.137 208.94.114.29 208.115.126.75 208.127.104.172 212.159.74.68 212.159.90.90 213.73.1.100 216.86.85.144 216.144.222.182 217.42.40.69 220.157.89.84 220.233.86.207
Hello Brian Surprise to see this in your list which is bi-directional and very active 62.49.17.234 this is active on the portal 44.131.244.0 (gb7cip.ampr.org) 73 de Paul g4apl (gb7cip) hope that this does not get bounced ;) In message 20131213222422.GA21861@UCSD.Edu, Brian Kantor Brian@ucsd.edu writes
(Please trim inclusions from previous messages) _______________________________________________ According to records on the portal, the following 120 (of 275 total) entries in the gateways list are unclaimed - that is, no one has come forward to take ownership of the entry. They therefore appear to be inactive.
I propose we mark these as no longer in service. That will have the effect of no longer including them in the encap list. Eventually we'll delete them from the database if they're not reactivated.
If a gateway that is still valid is listed below, contact me or Chris to get it assigned to the proper registered owner. - Brian
8.22.205.37 12.195.50.128 24.55.199.25 24.84.205.232 24.89.203.65 24.137.76.29 24.212.252.100 24.212.252.109 24.212.252.110 24.224.157.206 50.79.209.150 62.49.17.234 64.22.214.233 64.119.33.202 64.119.42.138 64.255.99.17 65.41.209.137 65.48.61.133 65.70.212.35 66.11.68.11 66.112.51.126 66.114.139.158 67.108.91.190 68.61.222.68 68.188.234.106 68.209.144.3 69.69.168.201 69.137.244.193 69.145.172.163 69.178.117.150 69.254.106.173 70.137.68.217 71.36.92.66 71.107.40.238 71.107.40.238 71.201.92.148 74.85.194.5 75.21.234.175 76.14.161.185 76.64.80.228 76.247.140.206 76.253.114.92 77.249.108.97 79.116.75.255 79.116.81.105 80.59.234.233 80.229.68.173 81.235.253.122 84.92.153.154 89.228.59.72 90.206.95.108 91.84.215.75 94.72.251.181 94.101.48.134 94.172.232.113 96.20.43.106 96.35.76.41 97.84.11.198 98.193.215.29 98.208.81.22 99.88.77.66 99.116.194.13 108.185.66.208 113.212.169.28 118.22.1.194 118.82.200.153 122.108.78.111 130.208.168.63 131.155.192.172 141.85.43.57 142.103.194.1 146.48.126.26 146.48.126.28 148.223.34.6 150.188.8.195 152.66.0.109 155.207.19.57 158.42.128.200 161.53.16.179 168.96.128.17 173.14.57.181 173.177.124.119 173.208.214.53 184.175.46.166 186.125.37.47 189.42.190.50 190.31.163.55 190.139.56.180 192.147.172.252 193.22.2.254 194.27.119.2 195.22.112.28 195.113.115.135 195.150.236.251 198.108.247.220 200.17.207.2 200.46.129.3 201.252.37.40 202.63.57.97 203.5.58.162 203.24.120.198 203.24.120.199 203.24.120.200 203.26.188.134 203.59.134.49 206.251.38.99 207.111.203.194 207.179.123.166 208.74.106.137 208.94.114.29 208.115.126.75 208.127.104.172 212.159.74.68 212.159.90.90 213.73.1.100 216.86.85.144 216.144.222.182 217.42.40.69 220.157.89.84 220.233.86.207 _________________________________________ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
On Fri, Dec 13, 2013 at 10:30:57PM +0000, Paul Lewis wrote:
(Please trim inclusions from previous messages) _______________________________________________ Hello Brian Surprise to see this in your list which is bi-directional and very active 62.49.17.234 this is active on the portal 44.131.244.0 (gb7cip.ampr.org) 73 de Paul g4apl (gb7cip)
Thanks, I'll correct that. - Brian
Hello Brian,
203.5.58.162 no longer has a ham license and is not active and may be deleted from the list.
I have also retired from the establishment and changed my call from VK1ZQR to VK1KW but still have my home packet running via vk1kw.dyndns.org 44.136.3.92 and do not have a fixed IP.
Cheers, Thanks and Best Wishes Rob
-----Original Message----- From: 44net-bounces+vk1kw=netspace.net.au@hamradio.ucsd.edu [mailto:44net-bounces+vk1kw=netspace.net.au@hamradio.ucsd.edu] On Behalf Of Brian Kantor Sent: Saturday, December 14, 2013 9:24 AM To: 44net@hamradio.ucsd.edu Subject: [44net] unclaimed gateways
(Please trim inclusions from previous messages) _______________________________________________ According to records on the portal, the following 120 (of 275 total) entries in the gateways list are unclaimed - that is, no one has come forward to take ownership of the entry. They therefore appear to be inactive.
I propose we mark these as no longer in service. That will have the effect of no longer including them in the encap list. Eventually we'll delete them from the database if they're not reactivated.
If a gateway that is still valid is listed below, contact me or Chris to get it assigned to the proper registered owner. - Brian
8.22.205.37 12.195.50.128 24.55.199.25 24.84.205.232 24.89.203.65 24.137.76.29 24.212.252.100 24.212.252.109 24.212.252.110 24.224.157.206 50.79.209.150 62.49.17.234 64.22.214.233 64.119.33.202 64.119.42.138 64.255.99.17 65.41.209.137 65.48.61.133 65.70.212.35 66.11.68.11 66.112.51.126 66.114.139.158 67.108.91.190 68.61.222.68 68.188.234.106 68.209.144.3 69.69.168.201 69.137.244.193 69.145.172.163 69.178.117.150 69.254.106.173 70.137.68.217 71.36.92.66 71.107.40.238 71.107.40.238 71.201.92.148 74.85.194.5 75.21.234.175 76.14.161.185 76.64.80.228 76.247.140.206 76.253.114.92 77.249.108.97 79.116.75.255 79.116.81.105 80.59.234.233 80.229.68.173 81.235.253.122 84.92.153.154 89.228.59.72 90.206.95.108 91.84.215.75 94.72.251.181 94.101.48.134 94.172.232.113 96.20.43.106 96.35.76.41 97.84.11.198 98.193.215.29 98.208.81.22 99.88.77.66 99.116.194.13 108.185.66.208 113.212.169.28 118.22.1.194 118.82.200.153 122.108.78.111 130.208.168.63 131.155.192.172 141.85.43.57 142.103.194.1 146.48.126.26 146.48.126.28 148.223.34.6 150.188.8.195 152.66.0.109 155.207.19.57 158.42.128.200 161.53.16.179 168.96.128.17 173.14.57.181 173.177.124.119 173.208.214.53 184.175.46.166 186.125.37.47 189.42.190.50 190.31.163.55 190.139.56.180 192.147.172.252 193.22.2.254 194.27.119.2 195.22.112.28 195.113.115.135 195.150.236.251 198.108.247.220 200.17.207.2 200.46.129.3 201.252.37.40 202.63.57.97 203.5.58.162 203.24.120.198 203.24.120.199 203.24.120.200 203.26.188.134 203.59.134.49 206.251.38.99 207.111.203.194 207.179.123.166 208.74.106.137 208.94.114.29 208.115.126.75 208.127.104.172 212.159.74.68 212.159.90.90 213.73.1.100 216.86.85.144 216.144.222.182 217.42.40.69 220.157.89.84 220.233.86.207 _________________________________________ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
Użytkownik Brian Kantor napisał:
(Please trim inclusions from previous messages) _______________________________________________ According to records on the portal, the following 120 (of 275 total) entries in the gateways list are unclaimed - that is, no one has come forward to take ownership of the entry. They therefore appear to be inactive.
I propose we mark these as no longer in service. That will have the effect of no longer including them in the encap list. Eventually we'll delete them from the database if they're not reactivated.
If a gateway that is still valid is listed below, contact me or Chris to get it assigned to the proper registered owner.
- Brian
Hi Brian Sending the information contained on the web site of the Polish Gateways: http://www.poland.net-44.ampr.org/
Ad.
195.150.236.251
Route to Gate QTH CallRegistered domains ---------------------------------------------------------------------------------------- route addprivate 44.165.152/23 encap 195.150.236.251 Kraków SR9ZAAWykaz: http://www.poland.net-44.ampr.org/152.html [84]
Gateway works and is active ....
[root@server ~]# telnet sr9zaa.ampr.org Trying 44.165.152.192... Connected to sr9zaa.ampr.org (44.165.152.192). Escape character is '^]'.
KA9Q NOS - KO4KS-TNOS/LINUX v3.01a1/ELF (sr9zaa.ampr.org) Uprawnienia / Permisions - mail to sysop@sr9zaa.ampr.org Podaj znak i haslo * Your callsign and password login:
Ad.
213.73.1.100
* * Route to Gate QTH CallRegistered domains* ------------------------------------------------------------------------------------------- *route addprivate 44.165.68/24 encap 213.73.1.100 Olsztyn SR4DONWykaz: http://www.poland.net-44.ampr.org/68.html [10] route addprivate 44.165.70/24 encap 213.73.1.100 Olsztyn SR4DONWykaz: http://www.poland.net-44.ampr.org/70.html [0]
Gateway works and is active....
[root@server ~]# telnet olsztyn.ampr.org Trying 44.165.68.254... Connected to olsztyn.ampr.org (44.165.68.254). Escape character is '^]'.
JNOS (olsztyn.ampr.org) Your callsign >> Login (your call) - Wpisz (swoj znak):
Użytkownik Brian Kantor napisał:
(Please trim inclusions from previous messages) _______________________________________________ According to records on the portal, the following 120 (of 275 total) entries in the gateways list are unclaimed - that is, no one has come forward to take ownership of the entry. They therefore appear to be inactive.
I propose we mark these as no longer in service. That will have the effect of no longer including them in the encap list. Eventually we'll delete them from the database if they're not reactivated.
If a gateway that is still valid is listed below, contact me or Chris to get it assigned to the proper registered owner.
- Brian
Hi Brian Sending the information contained on the web site of the Polish Gateways: http://www.poland.net-44.ampr.org/
Ad.
195.150.236.251
Route to Gate QTH Call Registered domains ---------------------------------------------------------------------------------------- route addprivate 44.165.152/23 encap 195.150.236.251 Kraków SR9ZAA Wykaz: [84]
Gateway works and is active ....
[root@server ~]# telnet sr9zaa.ampr.org Trying 44.165.152.192... Connected to sr9zaa.ampr.org (44.165.152.192). Escape character is '^]'.
KA9Q NOS - KO4KS-TNOS/LINUX v3.01a1/ELF (sr9zaa.ampr.org) Uprawnienia / Permisions - mail to sysop@sr9zaa.ampr.org Podaj znak i haslo * Your callsign and password login: Ad.
213.73.1.100
Route to Gate QTH Call Registered domains ------------------------------------------------------------------------------------- route addprivate 44.165.68/24 encap 213.73.1.100 Olsztyn SR4DON Wykaz: [10] route addprivate 44.165.70/24 encap 213.73.1.100 Olsztyn SR4DON Wykaz: [0]
Gateway works and is active....
[root@server ~]# telnet olsztyn.ampr.org Trying 44.165.68.254... Connected to olsztyn.ampr.org (44.165.68.254). Escape character is '^]'.
JNOS (olsztyn.ampr.org) Your callsign >> Login (your call) - Wpisz (swoj znak):
Sounds like an excellent PLAN... :)
Happy Holidays..
Jerry
-----Original Message----- From: 44net-bounces+n9lya=blueriver.net@hamradio.ucsd.edu [mailto:44net-bounces+n9lya=blueriver.net@hamradio.ucsd.edu] On Behalf Of Brian Kantor Sent: Friday, December 13, 2013 5:24 PM To: 44net@hamradio.ucsd.edu Subject: [44net] unclaimed gateways
(Please trim inclusions from previous messages) _______________________________________________ According to records on the portal, the following 120 (of 275 total) entries in the gateways list are unclaimed - that is, no one has come forward to take ownership of the entry. They therefore appear to be inactive.
I propose we mark these as no longer in service. That will have the effect of no longer including them in the encap list. Eventually we'll delete them from the database if they're not reactivated.
If a gateway that is still valid is listed below, contact me or Chris to get it assigned to the proper registered owner. - Brian
8.22.205.37 12.195.50.128 24.55.199.25 24.84.205.232 24.89.203.65 24.137.76.29 24.212.252.100 24.212.252.109 24.212.252.110 24.224.157.206 50.79.209.150 62.49.17.234 64.22.214.233 64.119.33.202 64.119.42.138 64.255.99.17 65.41.209.137 65.48.61.133 65.70.212.35 66.11.68.11 66.112.51.126 66.114.139.158 67.108.91.190 68.61.222.68 68.188.234.106 68.209.144.3 69.69.168.201 69.137.244.193 69.145.172.163 69.178.117.150 69.254.106.173 70.137.68.217 71.36.92.66 71.107.40.238 71.107.40.238 71.201.92.148 74.85.194.5 75.21.234.175 76.14.161.185 76.64.80.228 76.247.140.206 76.253.114.92 77.249.108.97 79.116.75.255 79.116.81.105 80.59.234.233 80.229.68.173 81.235.253.122 84.92.153.154 89.228.59.72 90.206.95.108 91.84.215.75 94.72.251.181 94.101.48.134 94.172.232.113 96.20.43.106 96.35.76.41 97.84.11.198 98.193.215.29 98.208.81.22 99.88.77.66 99.116.194.13 108.185.66.208 113.212.169.28 118.22.1.194 118.82.200.153 122.108.78.111 130.208.168.63 131.155.192.172 141.85.43.57 142.103.194.1 146.48.126.26 146.48.126.28 148.223.34.6 150.188.8.195 152.66.0.109 155.207.19.57 158.42.128.200 161.53.16.179 168.96.128.17 173.14.57.181 173.177.124.119 173.208.214.53 184.175.46.166 186.125.37.47 189.42.190.50 190.31.163.55 190.139.56.180 192.147.172.252 193.22.2.254 194.27.119.2 195.22.112.28 195.113.115.135 195.150.236.251 198.108.247.220 200.17.207.2 200.46.129.3 201.252.37.40 202.63.57.97 203.5.58.162 203.24.120.198 203.24.120.199 203.24.120.200 203.26.188.134 203.59.134.49 206.251.38.99 207.111.203.194 207.179.123.166 208.74.106.137 208.94.114.29 208.115.126.75 208.127.104.172 212.159.74.68 212.159.90.90 213.73.1.100 216.86.85.144 216.144.222.182 217.42.40.69 220.157.89.84 220.233.86.207 _________________________________________ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
On 13-12-13 02:24 PM, Brian Kantor wrote:
(Please trim inclusions from previous messages) _______________________________________________ According to records on the portal, the following 120 (of 275 total) entries in the gateways list are unclaimed - that is, no one has come forward to take ownership of the entry. They therefore appear to be inactive.
I propose we mark these as no longer in service. That will have the effect of no longer including them in the encap list. Eventually we'll delete them from the database if they're not reactivated.
If a gateway that is still valid is listed below, contact me or Chris to get it assigned to the proper registered owner.
- Brian
An excellent kick in the backside to finally finish setting up the gateway again ... a simple setup using rip44d seems the way to go, but it doesn't look like our gateway is getting the RIP packets yet. Are the gateways below supposed to be getting them or do I need to become the 'proper registered owner' first ?
(142.103.194.1 is our box at UBC ...)
... Niall
8.22.205.37 12.195.50.128 24.55.199.25 24.84.205.232 24.89.203.65 24.137.76.29 24.212.252.100 24.212.252.109 24.212.252.110 24.224.157.206 50.79.209.150 62.49.17.234 64.22.214.233 64.119.33.202 64.119.42.138 64.255.99.17 65.41.209.137 65.48.61.133 65.70.212.35 66.11.68.11 66.112.51.126 66.114.139.158 67.108.91.190 68.61.222.68 68.188.234.106 68.209.144.3 69.69.168.201 69.137.244.193 69.145.172.163 69.178.117.150 69.254.106.173 70.137.68.217 71.36.92.66 71.107.40.238 71.107.40.238 71.201.92.148 74.85.194.5 75.21.234.175 76.14.161.185 76.64.80.228 76.247.140.206 76.253.114.92 77.249.108.97 79.116.75.255 79.116.81.105 80.59.234.233 80.229.68.173 81.235.253.122 84.92.153.154 89.228.59.72 90.206.95.108 91.84.215.75 94.72.251.181 94.101.48.134 94.172.232.113 96.20.43.106 96.35.76.41 97.84.11.198 98.193.215.29 98.208.81.22 99.88.77.66 99.116.194.13 108.185.66.208 113.212.169.28 118.22.1.194 118.82.200.153 122.108.78.111 130.208.168.63 131.155.192.172 141.85.43.57 142.103.194.1 146.48.126.26 146.48.126.28 148.223.34.6 150.188.8.195 152.66.0.109 155.207.19.57 158.42.128.200 161.53.16.179 168.96.128.17 173.14.57.181 173.177.124.119 173.208.214.53 184.175.46.166 186.125.37.47 189.42.190.50 190.31.163.55 190.139.56.180 192.147.172.252 193.22.2.254 194.27.119.2 195.22.112.28 195.113.115.135 195.150.236.251 198.108.247.220 200.17.207.2 200.46.129.3 201.252.37.40 202.63.57.97 203.5.58.162 203.24.120.198 203.24.120.199 203.24.120.200 203.26.188.134 203.59.134.49 206.251.38.99 207.111.203.194 207.179.123.166 208.74.106.137 208.94.114.29 208.115.126.75 208.127.104.172 212.159.74.68 212.159.90.90 213.73.1.100 216.86.85.144 216.144.222.182 217.42.40.69 220.157.89.84 220.233.86.207 _________________________________________ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
Greetings Brian (et al),
On Fri, 13 Dec 2013, Brian Kantor wrote:
(Please trim inclusions from previous messages) _______________________________________________ According to records on the portal, the following 120 (of 275 total) entries in the gateways list are unclaimed - that is, no one has come forward to take ownership of the entry. They therefore appear to be inactive.
I propose we mark these as no longer in service. That will have the effect of no longer including them in the encap list. Eventually we'll delete them from the database if they're not reactivated.
If a gateway that is still valid is listed below, contact me or Chris to get it assigned to the proper registered owner.
- Brian
Hold on there gang! I suspect that many of those gateways are still operational but haven't been able to perform any updates because the Portal is *STILL* quite broken - or at least it is for some of us.
Back in March of this year I was seeing notices to my email (as the IP Address Coordinator for Michigan 44.102/16) for NEW gateway request, but had absolutely NO control over ANY OTHER gateway within the allocation that I am responsible for (44.102/16). I could not edit or correct them. I could not delete them and recreate a new record for them. I couldn't even manage my own gateway (hamgate.washtenaw) as the blasted database said it wasn't assigned to me! Well that blows! I'm listed as the coordinator for 44.102/16, but can't DO anything to manage that address space.
Following a request that Chris had posted around this same timeframe, I emailed him with some 17 gateway updates that he "said" he would edit by hand until the Portal got fixed. Well, THAT never happened. Subsequent emails to Chris went unanswered.... I figure it's a volunteer driven network and he has a life like the rest of us... so I waited...
I log into the Portal every month or so and continue to see the following under "Co-Ordinators":
IP Requests --- You currently have no outstanding requests.
DNS Requests --- You currently have no outstanding requests.
Allocations --- No networks found You have no pending requests.
Yet, under "Gateways / Manage" it shows requests that I had submitted that just sit there. The Portal has NEVER emailed me to let me know that they are pending nor have I been able to 'Okay' any of them for addition into the ENCAP database.
Gateway Encap Actions 24.247.165.49 IPIP Edit | Del 66.129.40.19 IPIP Edit | Del 68.188.234.106 IPIP Edit | Del 216.86.85.144 IPIP Edit | Del 216.245.225.3 IPIP Edit | Del
But wait! It gets worse!
So in July of this year I had a gateway operator here in Michigan create an account on the Portal, and then submit his data so that the coordinator (me) could be alerted to the request and Okay it for inclusion in the database. NO email was ever received from the Portal regarding the pending request, nor did it ever show up as a pending request under any of the Portal's 'Co-Ordinator' tools!!!! So where did the request go????
I emailed Chris again about the problem and noted that other coordinators were mentioning the same kind of problem on this mailing list. Chris never responded nor did the problem ever get fixed or addressed.
This suck folks!!! This new and improved tool was SUPPOSED to make things easier, and all it has accomplished from my perspective is that we have what "looks" like a cool tool, but it fails to work for us in any way shape or form.
I don't think I am alone in these problems with the Portal. Other coordinators have spoken up about these issues. Either fix the Portal or scrap it and go back to the email/procmail tools that Jim Fuller used in the past. At least THOSE tools worked dependably for over 20 years.
The following nodes are part of the Michigan AMPRnet network, and if I can gain access as the coordinator to manage these addresses I can correct their public IP addresses and get on with managing the network. In the meantime, I have to hand edit our own ENCAP.TXT file here in Michigan and distribute it myself. We really would like things to work correctly and link back in with the rest of the worldwide AMPRnet :)
66.112.51.126 hamgate.leelanau 67.108.91.190 hamgate.macomb 68.188.234.106 hamgate.alcona 74.85.194.5 hamgate.midland 96.35.76.41 hamgate.crawford (.38) 198.108.247.220 hamgate.mackinac 207.179.123.166 hamgate.eaton 216.86.85.144 hamgate.washtenaw 216.144.222.182 hamgate.wayne49
(there are a LOT more but these were the ones I could identify quickly)
Thank You, --- Jay Nugent WB8TKL Michigan AMPRnet IP Address Coordinator
() ascii ribbon campaign in /\ support of plain text e-mail
Averaging at least 3 days of MTBWTF!?!?!? The solution for long term Internet growth is IPv6. +------------------------------------------------------------------------+ | Jay Nugent jjn@nuge.com (734)484-5105 (734)649-0850/Cell | | Nugent Telecommunications [www.nuge.com] | | Internet Consulting/Linux SysAdmin/Engineering & Design | | ISP Monitoring [www.ispmonitor.org] ISP & Modem Performance Monitoring | +------------------------------------------------------------------------+ 21:01:01 up 22 days, 3:18, 2 users, load average: 0.41, 0.23, 0.15
On Fri, Dec 13, 2013 at 10:52:20PM -0500, Jay Nugent wrote:
24.247.165.49 IPIP Edit | Del
In the database twice, once as managed by WB8TKL and once by N8BJX. Which is correct?
66.129.40.19 IPIP Edit | Del
In the database twice, once as managed by WB8TKL and once by N8IT. Which is correct?
68.188.234.106 IPIP Edit | Del
In the database twice, once as managed by WB8TKL and once not owned. The latter has been deleted.
216.86.85.144 IPIP Edit | Del
In the database twice, once as managed by WB8TKL and once not owned. The latter has been deleted.
216.245.225.3 IPIP Edit | Del
In the database twice, once as managed by WB8TKL and once by W8VPC. Which is correct?
The duplications may explain some of the confusion. - Brian
Greetings Brian,
On Fri, 13 Dec 2013, Brian Kantor wrote:
(Please trim inclusions from previous messages) _______________________________________________ On Fri, Dec 13, 2013 at 10:52:20PM -0500, Jay Nugent wrote:
24.247.165.49 IPIP Edit | Del
In the database twice, once as managed by WB8TKL and once by N8BJX. Which is correct?
Please use the N8BJX entry.
66.129.40.19 IPIP Edit | Del
In the database twice, once as managed by WB8TKL and once by N8IT. Which is correct?
Please use the N8IT entry.
68.188.234.106 IPIP Edit | Del
In the database twice, once as managed by WB8TKL and once not owned. The latter has been deleted.
Thanks!
216.86.85.144 IPIP Edit | Del
In the database twice, once as managed by WB8TKL and once not owned. The latter has been deleted.
Thanks!
216.245.225.3 IPIP Edit | Del
In the database twice, once as managed by WB8TKL and once by W8VPC. Which is correct?
Please use the W8VPC entry.
The duplications may explain some of the confusion.
No doubt that they did. I will search through the rest of the 44.102/16 gateways and look for further gateways that the owners have always just had me manage them on their behalf. Some of the ones above, the node operators have the smarts/training to manage on their own. But most have chosen that I just keep their records updated for them, and that is Okay with me.
I'll be in touch as I compile another list :)
Thanks! --- Jay WB8TKL
Hi Jay,
You appear to getting the different aspects of the portal confused:
The gateways section is currently separate from DNS & IP Allocation.
If you submitted a "request" for a new gateway, it's not actually a "request", in fact as soon as you add a new gateway to the portal it is live right away, there is nothing further the portal or we volunteers need to do, no emails are sent, you can view your gateways on the portal at any time, if they appear in your list, they are live and in the database.
Both myself and Brian have asked many times for anyone that is running a gateway to contact us and claim it so we can allocate it to their account, we have received several such "claims" and all of them have been actioned. The emails you sent me before were related to IP allocation requests, not gateways.
Some folks have gone onto the portal and added their gateway, rather than claiming their existing one which has resulted in some duplications, when someone has done this I haven't then assigned the unclaimed gateway to their account as well as that would just cause confusion, some of these duplicates are still in the database waiting to be removed.
I repeat from previous emails:
- The gateways portion of the portal is functioning perfectly and has been for a long time now.
- There are known issues with the IP Allocation portion of the portal that are being looked at (basically it works, but not in the way many co-ordinators would prefer it to, so it is being re-designed to be less restrictive and allow co-ordinators more control).
- Although it works, the DNS portion of the portal is currently NOT live, Brian and I are still in discussion over how best to move forward on this due to the huge amount of legacy data and the need for an email/bulk update facility.
Please do not confuse the three completely separate parts of the portal.
Thanks, Chris
On Fri, Dec 13, 2013 at 2:24 PM, Brian Kantor Brian@ucsd.edu wrote:
173.208.214.53
you can go ahead and recycle this one as I was allocated a larger subnet.
Any idea when DNS management will be up in the portal as it's the only thing keeping me back from utilizing 44net as without a DNS record, I won't be in the encap file.
On Fri, Dec 13, 2013 at 10:00:53PM -0800, Don Fanning wrote:
173.208.214.53
you can go ahead and recycle this one as I was allocated a larger subnet.
Ok, thanks.
Any idea when DNS management will be up in the portal as it's the only thing keeping me back from utilizing 44net as without a DNS record, I won't be in the encap file.
It'll be a while since we've discovered that we need to design and implement some sort of bulk DNS entry function to take the place of the old email robot. Until then, the old email robot-based DNS remains functional; if you need a DNS update most coordinators have access to it or you can send me a note and I'll make the change for you.
However, there's a slight misunderstanding here; if you're in the gateways database you'll be in the encap file. Being in the DNS only controls whether the address is reachable from the commercial internet via the amprgw gateway. - Brian
Hello Brian,
118.22.1.194 is active and is administrated by myself.
73 Isao / JM1WBB
2013/12/14 7:24、Brian Kantor Brian@ucsd.edu のメール：
(Please trim inclusions from previous messages) _______________________________________________ According to records on the portal, the following 120 (of 275 total) entries in the gateways list are unclaimed - that is, no one has come forward to take ownership of the entry. They therefore appear to be inactive.
I propose we mark these as no longer in service. That will have the effect of no longer including them in the encap list. Eventually we'll delete them from the database if they're not reactivated.
If a gateway that is still valid is listed below, contact me or Chris to get it assigned to the proper registered owner.
- Brian
8.22.205.37 12.195.50.128 24.55.199.25 24.84.205.232 24.89.203.65 24.137.76.29 24.212.252.100 24.212.252.109 24.212.252.110 24.224.157.206 50.79.209.150 62.49.17.234 64.22.214.233 64.119.33.202 64.119.42.138 64.255.99.17 65.41.209.137 65.48.61.133 65.70.212.35 66.11.68.11 66.112.51.126 66.114.139.158 67.108.91.190 68.61.222.68 68.188.234.106 68.209.144.3 69.69.168.201 69.137.244.193 69.145.172.163 69.178.117.150 69.254.106.173 70.137.68.217 71.36.92.66 71.107.40.238 71.107.40.238 71.201.92.148 74.85.194.5 75.21.234.175 76.14.161.185 76.64.80.228 76.247.140.206 76.253.114.92 77.249.108.97 79.116.75.255 79.116.81.105 80.59.234.233 80.229.68.173 81.235.253.122 84.92.153.154 89.228.59.72 90.206.95.108 91.84.215.75 94.72.251.181 94.101.48.134 94.172.232.113 96.20.43.106 96.35.76.41 97.84.11.198 98.193.215.29 98.208.81.22 99.88.77.66 99.116.194.13 108.185.66.208 113.212.169.28 118.22.1.194 118.82.200.153 122.108.78.111 130.208.168.63 131.155.192.172 141.85.43.57 142.103.194.1 146.48.126.26 146.48.126.28 148.223.34.6 150.188.8.195 152.66.0.109 155.207.19.57 158.42.128.200 161.53.16.179 168.96.128.17 173.14.57.181 173.177.124.119 173.208.214.53 184.175.46.166 186.125.37.47 189.42.190.50 190.31.163.55 190.139.56.180 192.147.172.252 193.22.2.254 194.27.119.2 195.22.112.28 195.113.115.135 195.150.236.251 198.108.247.220 200.17.207.2 200.46.129.3 201.252.37.40 202.63.57.97 203.5.58.162 203.24.120.198 203.24.120.199 203.24.120.200 203.26.188.134 203.59.134.49 206.251.38.99 207.111.203.194 207.179.123.166 208.74.106.137 208.94.114.29 208.115.126.75 208.127.104.172 212.159.74.68 212.159.90.90 213.73.1.100 216.86.85.144 216.144.222.182 217.42.40.69 220.157.89.84 220.233.86.207 _________________________________________ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
Hello Brian,
Today at 10:10UTC noticed that whole 44.165 national block is TOTALLY missing in rip44v2 broadcasts from amprgw!
Therefore any software relaying on OH7LZB's rip44d or YO2LOJ's ampr-ripd daemons is useless at the moment.
Although encap.txt file downloaded directly from portal.ampr.org is __pretty correct__!
Best regards. Tom - sp2lob
They're not missing when I checked just now. 'tcpdump' shows them to be present in the pseudo-RIP transmissions. Could there be a problem on your end? - Brian
On Sun, Dec 15, 2013 at 11:28:13AM +0100, sp2lob wrote:
Today at 10:10UTC noticed that whole 44.165 national block is TOTALLY missing in rip44v2 broadcasts from amprgw!
Therefore any software relaying on OH7LZB's rip44d or YO2LOJ's ampr-ripd daemons is useless at the moment.
Although encap.txt file downloaded directly from portal.ampr.org is __pretty correct__!
Best regards. Tom - sp2lob
Użytkownik Brian Kantor napisał:
They're not missing when I checked just now. 'tcpdump' shows them to be present in the pseudo-RIP transmissions. Could there be a problem on your end?
- Brian
Hi Brian... Why me of my network 44.165.25.0/24 do not have access to all the 44.0.0.0/8 ??? I use encap.txt and tunnel:
tunl0 Link encap: IPIP Tunnel HWaddr inet addr: 44.165.25.232 Mask: 255.255.255.255 UP RUNNING NOARP MTU: 1024 Metric: 1 RX packets: 100704 errors: 0 dropped: 0 overruns: 0 frame: 0 TX packets: 71193 errors: 0 dropped: 0 overruns: 0 carrier: 0 collisions: 0 txqueuelen: 0 RX bytes: 15150482 (14.4 MiB) TX bytes: 8963045 (8.5 MiB)
On Sun, Dec 15, 2013 at 05:13:04PM +0100, Janusz Przybylski SP1LOP wrote:
Why me of my network 44.165.25.0/24 do not have access to all the 44.0.0.0/8 ??? I use encap.txt and tunnel:
tunl0 Link encap: IPIP Tunnel HWaddr inet addr: 44.165.25.232 Mask: 255.255.255.255 UP RUNNING NOARP MTU: 1024 Metric: 1 RX packets: 100704 errors: 0 dropped: 0 overruns: 0 frame: 0 TX packets: 71193 errors: 0 dropped: 0 overruns: 0 carrier: 0 collisions: 0 txqueuelen: 0 RX bytes: 15150482 (14.4 MiB) TX bytes: 8963045 (8.5 MiB)
I don't know. I can send pings to your system but I do not get a response. tcpdump shows that the ping is being properly encapsulated and sent to your gateway:
amprgw# tcpdump -v -s0 -n proto ipencap | grep 44.165.25.232 tcpdump: listening on em0, link-type EN10MB (Ethernet), capture size 65535 bytes 08:16:09.776303 IP (tos 0x0, ttl 64, id 765, offset 0, flags [none], proto IPIP (4), length 104) 169.228.66.251 > 62.69.192.233: IP (tos 0x0, ttl 48, id 0, offset 0, flags [DF], proto ICMP (1), length 84) 75.80.130.94 > 44.165.25.232: ICMP echo request, id 26187, seq 60, length 64
- Brian
[01;34ve1jot-14@linux.ve1jot.ampr.org:/uronode$ ping 44.165.25.232 ICMP Echo request sent to: 44.165.25.232 ICMP Echo reply received from: 44.165.25.232 Ping completed in: 144ms (ttl=64) [01;34ve1jot-14@linux.ve1jot.ampr.org:/uronode$
encapped ripv2 from 44.135.32.201
Because the correct netmask for the tunnel is 255.0.0.0.
-----Original Message----- From: 44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu [mailto:44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu] On Behalf Of Janusz Przybylski SP1LOP Sent: Sunday, December 15, 2013 18:13 To: AMPRNet working group Subject: Re: [44net] rip44v2 broadcasts missing 44.165 national block
(Please trim inclusions from previous messages) _______________________________________________ Uzytkownik Brian Kantor napisal:
They're not missing when I checked just now. 'tcpdump' shows them to be present in the pseudo-RIP transmissions. Could there be a problem on your end?
- Brian
Hi Brian... Why me of my network 44.165.25.0/24 do not have access to all the 44.0.0.0/8 ??? I use encap.txt and tunnel:
tunl0 Link encap: IPIP Tunnel HWaddr inet addr: 44.165.25.232 Mask: 255.255.255.255 UP RUNNING NOARP MTU: 1024 Metric: 1 RX packets: 100704 errors: 0 dropped: 0 overruns: 0 frame: 0 TX packets: 71193 errors: 0 dropped: 0 overruns: 0 carrier: 0 collisions: 0 txqueuelen: 0 RX bytes: 15150482 (14.4 MiB) TX bytes: 8963045 (8.5 MiB)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 15/12/2013 20:58, Marius Petrescu wrote:
(Please trim inclusions from previous messages) _______________________________________________ Because the correct netmask for the tunnel is 255.0.0.0.
FUD. The route(s) must have the correct netmask, the tunnel interface can have of 255.255.255.255. Discussed a zillion times over here.
73 de Marc
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Why me of my network 44.165.25.0/24 do not have access to all the 44.0.0.0/8 ??? I use encap.txt and tunnel:
tunl0 Link encap: IPIP Tunnel HWaddr inet addr: 44.165.25.232 Mask: 255.255.255.255 UP RUNNING NOARP MTU: 1024 Metric: 1 RX packets: 100704 errors: 0 dropped: 0 overruns: 0 frame: 0 TX packets: 71193 errors: 0 dropped: 0 overruns: 0 carrier: 0 collisions: 0 txqueuelen: 0 RX bytes: 15150482 (14.4 MiB) TX bytes: 8963045 (8.5 MiB)
I cannot ping 44.165.25.232 nor traceroute towards it.
# ADDRESS LOSS SENT LAST AVG BEST WORST STD-DEV STATUS
1 100% 1 timeout
2 100% 1 timeout
3 100% 1 timeout
However if I traceroute to any other IP within 44.165.25.0/24 I get at least a reply from 62.69.192.233.
# ADDRESS LOSS SENT LAST AVG BEST WORST STD-DEV STATUS
1 62.69.192.233 0% 1 42.3ms 42.3 42.3 42.3 0
2 100% 1 timeout
3 100% 1 timeout
Eventually a routing or firewalling issue...
Can you ping and traceroute towards some 44/8 destinations. Try 44.161.255.3 and let me know the results.
73 de Marc
Ping works for me...
C:\Users\Marius>ping 44.165.25.232
Pinging 44.165.25.232 with 32 bytes of data: Reply from 44.165.25.232: bytes=32 time=87ms TTL=63 Reply from 44.165.25.232: bytes=32 time=85ms TTL=63 Reply from 44.165.25.232: bytes=32 time=88ms TTL=63 Reply from 44.165.25.232: bytes=32 time=87ms TTL=63
Ping statistics for 44.165.25.232: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 85ms, Maximum = 88ms, Average = 86ms
Użytkownik Marc, LX1DUC napisał:
Why me of my network 44.165.25.0/24 do not have access to all the
44.0.0.0/8 ??? I use encap.txt and tunnel:
tunl0 Link encap: IPIP Tunnel HWaddr inet addr: 44.165.25.232 Mask: 255.255.255.255 UP RUNNING NOARP MTU: 1024 Metric: 1 RX packets: 100704 errors: 0 dropped: 0 overruns: 0 frame: 0 TX packets: 71193 errors: 0 dropped: 0 overruns: 0 carrier: 0 collisions: 0 txqueuelen: 0 RX bytes: 15150482 (14.4 MiB) TX bytes: 8963045 (8.5 MiB)
I cannot ping 44.165.25.232 nor traceroute towards it. # ADDRESS LOSS SENT LAST AVG BEST WORST STD-DEV STATUS 1 100% 1 timeout 2 100% 1 timeout 3 100% 1 timeout
However if I traceroute to any other IP within 44.165.25.0/24 I get at least a reply from 62.69.192.233.
# ADDRESS LOSS SENT LAST AVG BEST WORST STD-DEV STATUS 1 62.69.192.233 0% 1 42.3ms 42.3 42.3 42.3 0 2 100% 1 timeout 3 100% 1 timeout
Eventually a routing or firewalling issue...
Can you ping and traceroute towards some 44/8 destinations. Try 44.161.255.3 and let me know the results.
Here I have a problem, my command: [root@server ~]# tcpdump -v -s0 -n proto ipencap | grep 44.165.25 ... 23:09:06.745031 IP (tos 0x0, ttl 39, id 30037, offset 0, flags [none], proto: IPIP (4), length: 104) 169.228.66.251 > 62.69.192.233: IP (tos 0x0, ttl 48, id 0, offset 0, flags [DF], proto: ICMP (1), length: 84) 75.80.130.94 > 44.165.25.232: ICMP echo request, id 26187, seq 21126, length 64 ... My server does not respond to such a frame tunnel (Public_IP > 44Net_IP) ' 75.80.130.94 > 44.165.25.232:'
Tunnel (44Net_IP > 44Net_IP) I have no problems. ... 23:09:10.556700 IP (tos 0x0, ttl 235, id 16048, offset 0, flags [none], proto: IPIP (4), length: 60) 213.73.1.100 > 62.69.192.233: IP (tos 0x0, ttl 253, id 20086, offset 0, flags [none], proto: TCP (6), length: 40) 44.165.68.254.15928 > 44.165.25.232.14580: ., cksum 0x2cd8 (correct), ack 1031 win 1024 ...
Here is my problem with the tunnel (Public_IP > 44Net_IP)
Użytkownik Janusz Przybylski SP1LOP napisał:
(Please trim inclusions from previous messages) _______________________________________________ Użytkownik Marc, LX1DUC napisał:
Why me of my network 44.165.25.0/24 do not have access to all the
44.0.0.0/8 ??? I use encap.txt and tunnel:
tunl0 Link encap: IPIP Tunnel HWaddr inet addr: 44.165.25.232 Mask: 255.255.255.255 UP RUNNING NOARP MTU: 1024 Metric: 1 RX packets: 100704 errors: 0 dropped: 0 overruns: 0 frame: 0 TX packets: 71193 errors: 0 dropped: 0 overruns: 0 carrier: 0 collisions: 0 txqueuelen: 0 RX bytes: 15150482 (14.4 MiB) TX bytes: 8963045 (8.5 MiB)
I cannot ping 44.165.25.232 nor traceroute towards it. # ADDRESS LOSS SENT LAST AVG BEST WORST STD-DEV STATUS 1 100% 1 timeout 2 100% 1 timeout 3 100% 1 timeout
However if I traceroute to any other IP within 44.165.25.0/24 I get at least a reply from 62.69.192.233.
# ADDRESS LOSS SENT LAST AVG BEST WORST STD-DEV STATUS 1 62.69.192.233 0% 1 42.3ms 42.3 42.3 42.3 0 2 100% 1 timeout 3 100% 1 timeout
Eventually a routing or firewalling issue...
Can you ping and traceroute towards some 44/8 destinations. Try 44.161.255.3 and let me know the results.
Here I have a problem, my command: [root@server ~]# tcpdump -v -s0 -n proto ipencap | grep 44.165.25 ... 23:09:06.745031 IP (tos 0x0, ttl 39, id 30037, offset 0, flags [none], proto: IPIP (4), length: 104) 169.228.66.251 > 62.69.192.233: IP (tos 0x0, ttl 48, id 0, offset 0, flags [DF], proto: ICMP (1), length: 84) 75.80.130.94 > 44.165.25.232: ICMP echo request, id 26187, seq 21126, length 64 ... My server does not respond to such a frame tunnel (Public_IP > 44Net_IP) ' 75.80.130.94
44.165.25.232:'
Tunnel (44Net_IP > 44Net_IP) I have no problems. ... 23:09:10.556700 IP (tos 0x0, ttl 235, id 16048, offset 0, flags [none], proto: IPIP (4), length: 60) 213.73.1.100 > 62.69.192.233: IP (tos 0x0, ttl 253, id 20086, offset 0, flags [none], proto: TCP (6), length: 40) 44.165.68.254.15928 > 44.165.25.232.14580: ., cksum 0x2cd8 (correct), ack 1031 win 1024 ...
Here is my problem with the tunnel (Public_IP > 44Net_IP)
[root@server ~]# tcpdump -i eth0 -nn | grep 44.165.25 ... 00:17:03.031527 IP 169.228.66.251 > 62.69.192.233: IP 75.80.130.94 > 44.165.25.232: ICMP echo request, id 26187, seq 25195, length 64 (ipip-proto-4) 00:17:03.031648 IP 44.165.25.232 > 75.80.130.94: ICMP echo reply, id 26187, seq 25195, length 64 ... I do not know if these frames arrive. Maybe my ISP blocks the frame 44Net from my server and not released in the World?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Here I have a problem, my command: [root@server ~]# tcpdump -v -s0 -n proto ipencap | grep 44.165.25 ... 23:09:06.745031 IP (tos 0x0, ttl 39, id 30037, offset 0, flags [none], proto: IPIP (4), length: 104) 169.228.66.251 > 62.69.192.233: IP (tos 0x0, ttl 48, id 0, offset 0, flags [DF], proto: ICMP (1), length: 84) 75.80.130.94 > 44.165.25.232: ICMP echo request, id 26187, seq 21126, length 64 ... My server does not respond to such a frame tunnel (Public_IP > 44Net_IP) ' 75.80.130.94 > 44.165.25.232:'
Tunnel (44Net_IP > 44Net_IP) I have no problems. ... 23:09:10.556700 IP (tos 0x0, ttl 235, id 16048, offset 0, flags [none], proto: IPIP (4), length: 60) 213.73.1.100 > 62.69.192.233: IP (tos 0x0, ttl 253, id 20086, offset 0, flags [none], proto: TCP (6), length: 40) 44.165.68.254.15928 > 44.165.25.232.14580: ., cksum 0x2cd8 (correct), ack 1031 win 1024 ...
Here is my problem with the tunnel (Public_IP > 44Net_IP)
44net to 44net seems to work fine:
traceroute to 44.165.25.232 (44.165.25.232), 64 hops max, 52 byte packets 1 rtr-255-240-28 (44.161.255.241) 1.089 ms 5.158 ms 1.760 ms 2 rtr-255-0-28 (44.161.255.1) 1539.184 ms 140.218 ms 727.749 ms 3 aprs.poland.ampr.org (44.165.25.232) 738.033 ms 791.899 ms 399.726 ms
73 de Marc,
Hi Brian,
173.177.124.119 gateway information is below and is runnung 24/7.
Gateway: 173.177.124.119 Sent By: "Y. Robert Sismanyan" <ve2har<at>videotron.ca> Password: xxxxxxxxxx Subnets: 44.135.48/24, 44.188.1.1/32 AMPRnet address: 44.135.48.40 <ve2har.ampr.org> System Op.: Robert Sismanyan, VE2HAR Gateway Area: Laval, Quebec, Canada Located at: 3886 Fafard, Chomedey, Laval, Quebec, Canada H7T 1Y1
Regards,
Robert, VE2HAR
----- Original Message ----- From: "Brian Kantor" Brian@UCSD.Edu To: 44net@hamradio.ucsd.edu Sent: Friday, December 13, 2013 5:24 PM Subject: [44net] unclaimed gateways
(Please trim inclusions from previous messages) _______________________________________________ According to records on the portal, the following 120 (of 275 total) entries in the gateways list are unclaimed - that is, no one has come forward to take ownership of the entry. They therefore appear to be inactive.
I propose we mark these as no longer in service. That will have the effect of no longer including them in the encap list. Eventually we'll delete them from the database if they're not reactivated.
If a gateway that is still valid is listed below, contact me or Chris to get it assigned to the proper registered owner.
- Brian
8.22.205.37 12.195.50.128 24.55.199.25 24.84.205.232 24.89.203.65 24.137.76.29 24.212.252.100 24.212.252.109 24.212.252.110 24.224.157.206 50.79.209.150 62.49.17.234 64.22.214.233 64.119.33.202 64.119.42.138 64.255.99.17 65.41.209.137 65.48.61.133 65.70.212.35 66.11.68.11 66.112.51.126 66.114.139.158 67.108.91.190 68.61.222.68 68.188.234.106 68.209.144.3 69.69.168.201 69.137.244.193 69.145.172.163 69.178.117.150 69.254.106.173 70.137.68.217 71.36.92.66 71.107.40.238 71.107.40.238 71.201.92.148 74.85.194.5 75.21.234.175 76.14.161.185 76.64.80.228 76.247.140.206 76.253.114.92 77.249.108.97 79.116.75.255 79.116.81.105 80.59.234.233 80.229.68.173 81.235.253.122 84.92.153.154 89.228.59.72 90.206.95.108 91.84.215.75 94.72.251.181 94.101.48.134 94.172.232.113 96.20.43.106 96.35.76.41 97.84.11.198 98.193.215.29 98.208.81.22 99.88.77.66 99.116.194.13 108.185.66.208 113.212.169.28 118.22.1.194 118.82.200.153 122.108.78.111 130.208.168.63 131.155.192.172 141.85.43.57 142.103.194.1 146.48.126.26 146.48.126.28 148.223.34.6 150.188.8.195 152.66.0.109 155.207.19.57 158.42.128.200 161.53.16.179 168.96.128.17 173.14.57.181 173.177.124.119 173.208.214.53 184.175.46.166 186.125.37.47 189.42.190.50 190.31.163.55 190.139.56.180 192.147.172.252 193.22.2.254 194.27.119.2 195.22.112.28 195.113.115.135 195.150.236.251 198.108.247.220 200.17.207.2 200.46.129.3 201.252.37.40 202.63.57.97 203.5.58.162 203.24.120.198 203.24.120.199 203.24.120.200 203.26.188.134 203.59.134.49 206.251.38.99 207.111.203.194 207.179.123.166 208.74.106.137 208.94.114.29 208.115.126.75 208.127.104.172 212.159.74.68 212.159.90.90 213.73.1.100 216.86.85.144 216.144.222.182 217.42.40.69 220.157.89.84 220.233.86.207 _________________________________________ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
I can't assign the gateway to you because there is no entry in the portal for VE2HAR. Are you sure you're registered as a portal user? - Brian
On Sat, Dec 14, 2013 at 11:07:30AM -0500, Robert wrote:
173.177.124.119 gateway information is below and is runnung 24/7.
Gateway: 173.177.124.119 Sent By: "Y. Robert Sismanyan" <ve2har<at>videotron.ca> Password: xxxxxxxxxx Subnets: 44.135.48/24, 44.188.1.1/32 AMPRnet address: 44.135.48.40 <ve2har.ampr.org> System Op.: Robert Sismanyan, VE2HAR Gateway Area: Laval, Quebec, Canada Located at: 3886 Fafard, Chomedey, Laval, Quebec, Canada H7T 1Y1 Regards, Robert, VE2HAR
Hi
I have see in list https://portal.ampr.org/gateways_list.php
twice entry with my dynamic IP address for (sp2ong.no-ip.org) 31.2.15.13 2013-10-07 20:32:15Viewhttps://portal.ampr.org/gateways_list.php?a=view&id=437 31.2.15.132013-12-14 12:07:25Viewhttps://portal.ampr.org/gateways_list.php?a=view&id=466 First is form may entry but I don't know who put sencond information
31.2.15.132013-12-14 12:07:25Viewhttps://portal.ampr.org/gateways_list.php?a=view&id=466 Please remove second entry
*208.127.104.172 *is alive and well and active enough. Forgive me for not really paying attention as to how to step up and yell YAWP. Maybe you can direct me to a primer on how to use the new system.
73,
Kim Wicker
n6roe.ampr.org
44.16.3.24
208.127.104.172
On Fri, Dec 13, 2013 at 2:24 PM, Brian Kantor Brian@ucsd.edu wrote:
(Please trim inclusions from previous messages) _______________________________________________ According to records on the portal, the following 120 (of 275 total) entries in the gateways list are unclaimed - that is, no one has come forward to take ownership of the entry. They therefore appear to be inactive.
I propose we mark these as no longer in service. That will have the effect of no longer including them in the encap list. Eventually we'll delete them from the database if they're not reactivated.
If a gateway that is still valid is listed below, contact me or Chris to get it assigned to the proper registered owner. - Brian
8.22.205.37 12.195.50.128 24.55.199.25 24.84.205.232 24.89.203.65 24.137.76.29 24.212.252.100 24.212.252.109 24.212.252.110 24.224.157.206 50.79.209.150 62.49.17.234 64.22.214.233 64.119.33.202 64.119.42.138 64.255.99.17 65.41.209.137 65.48.61.133 65.70.212.35 66.11.68.11 66.112.51.126 66.114.139.158 67.108.91.190 68.61.222.68 68.188.234.106 68.209.144.3 69.69.168.201 69.137.244.193 69.145.172.163 69.178.117.150 69.254.106.173 70.137.68.217 71.36.92.66 71.107.40.238 71.107.40.238 71.201.92.148 74.85.194.5 75.21.234.175 76.14.161.185 76.64.80.228 76.247.140.206 76.253.114.92 77.249.108.97 79.116.75.255 79.116.81.105 80.59.234.233 80.229.68.173 81.235.253.122 84.92.153.154 89.228.59.72 90.206.95.108 91.84.215.75 94.72.251.181 94.101.48.134 94.172.232.113 96.20.43.106 96.35.76.41 97.84.11.198 98.193.215.29 98.208.81.22 99.88.77.66 99.116.194.13 108.185.66.208 113.212.169.28 118.22.1.194 118.82.200.153 122.108.78.111 130.208.168.63 131.155.192.172 141.85.43.57 142.103.194.1 146.48.126.26 146.48.126.28 148.223.34.6 150.188.8.195 152.66.0.109 155.207.19.57 158.42.128.200 161.53.16.179 168.96.128.17 173.14.57.181 173.177.124.119 173.208.214.53 184.175.46.166 186.125.37.47 189.42.190.50 190.31.163.55 190.139.56.180 192.147.172.252 193.22.2.254 194.27.119.2 195.22.112.28 195.113.115.135 195.150.236.251 198.108.247.220 200.17.207.2 200.46.129.3 201.252.37.40 202.63.57.97 203.5.58.162 203.24.120.198 203.24.120.199 203.24.120.200 203.26.188.134 203.59.134.49 206.251.38.99 207.111.203.194 207.179.123.166 208.74.106.137 208.94.114.29 208.115.126.75 208.127.104.172 212.159.74.68 212.159.90.90 213.73.1.100 216.86.85.144 216.144.222.182 217.42.40.69 220.157.89.84 220.233.86.207 _________________________________________ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
-
Brian Kantor -
Chris -
Don Fanning -
Isao SEKI - JM1WBB -
Janusz Przybylski SP1LOP -
Jay Nugent -
Jerry -
jj -
kwicker ＠dslextreme.com -
Marc, LX1DUC -
Marius Petrescu -
Niall Parker -
Paul Lewis -
Robert -
sp2lob -
vk1kw -
Waldek SPdwaONG