Hey guys,
Anyone else having issues reaching the portal?
Dns has is going to the uk instead of uscd?
Ruben - ON3RVH
Ruben,
The portal has ALWAYS been located and hosted in the UK.
It looks like the web server on that machine is down, although the machine itself is up. I don't have sufficient privilege on that system to restart the web server. Chris will have to look into it. - Brian
On Sun, Sep 02, 2018 at 07:21:00AM +0000, Ruben ON3RVH wrote:
Hey guys,
Anyone else having issues reaching the portal?
Dns has is going to the uk instead of uscd?
Ruben - ON3RVH
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
I’ve restarted Apache.
Looks like it crashed after the logrotate cron job:
[Sun Sep 02 05:26:28.989292 2018] [mpm_worker:notice] [pid 824:tid 140562288117888] AH00297: SIGUSR1 received. Doing graceful restart [Sun Sep 02 05:26:30.164875 2018] [core:notice] [pid 824] AH00060: seg fault or similar nasty error detected in the parent process
A manual restart worked fine and this hasn’t happened before, hopefully just a one-off.
Chris
On 2 Sep 2018, at 08:40, Brian Kantor Brian@BKantor.net wrote:
Ruben,
The portal has ALWAYS been located and hosted in the UK.
It looks like the web server on that machine is down, although the machine itself is up. I don't have sufficient privilege on that system to restart the web server. Chris will have to look into it.
- Brian
On Sun, Sep 02, 2018 at 07:21:00AM +0000, Ruben ON3RVH wrote:
Hey guys,
Anyone else having issues reaching the portal?
Dns has is going to the uk instead of uscd?
Ruben - ON3RVH
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
Dear All,
A group of people in Turkey contacted us for BGP announcement of our 44.176.x.x/16 network. At first glance I ddn't want to interfere with non-amateur groups for our 44.176 IP block announcements.
The group is Turkish volunteers for the PeeringDB (details can be found on their web page https://www.peeringdb.com/ https://ixp.ofis.link/peers.html) .
As I checked other announcements of PeeringDB for 44.x.x.x network I saw that there are some other participants sharing their routing information with peeringDB.
Samples 44.x.x.x network annoucements on peeringBD are as follows;
https://bgp.he.net/AS396503#_prefixes ( 44.190.7.0/24 and 44.135.116.0/22 ) https://bgp.he.net/AS23738#_prefixes ( 44.24.193.0/24 44.127.44.0/22 44.127.45.0/24 44.127.46.0/24 44.127.47.0/24) https://bgp.he.net/AS207036#_prefixes ( 44.164.64.0/22 ) https://bgp.he.net/AS204778#_prefixes ( 44.38.10.0/24 )
My question is : Can I share the 44.176.x.x/16 network announcement with this group of people (the users on my side are all hamradio licensed amateurs, but the announcing will be done bye a non-hamradio person.
Thanks Baris DINC TA7W
Hello Baris,
BGP announcement of subnet prefixes of network 44 requires individual written permission for each announcement from the network owner, Amateur Radio Digital Communications Inc [ARDC].
Currently, NO ONE has permission to BGP announce 44.176.0.0/16 or any subnet prefix of 44.176.0.0.
If you wish to announce specific subnet prefixes of 44.176.0.0/16, you may request permission to do so by emailing your request to me.
Thank you for your interest.
Best regards and 73. - Brian
To give everyone else some more background, ixp.ofis is one of a new crop of what you might call "vanity Internet exchanges." Real Internet Exchanges are local peering points where multiple networks can exchange traffic to improve their connectivity vs only reaching other networks through your upstream Internet Service Provider (i.e. bypassing the up, over, and down hops through both network's transit providers). Some network operators think that it is "cool" to be on an IXP and have more direct peers, so they create these virtual GRE tunnel based IXPs as a way to juice their numbers and play with BGP regardless of it generally hurting the performance of their routing to any other participating networks.
That being said, in general, if anyone unsolicited offers to announce your AMPRnet prefix over BGP from their network and you don't understand why you would want to do that or what it gains you, I recommend you decline the offer. Although possibly sincere, it's likely a vanity exercise on their part, and possible they're trying to steal access to some or all of your subnet for their own use. -- Kenneth Finnegan http://blog.thelifeofkenneth.com/
On Tue, Sep 4, 2018 at 6:25 AM, Barış DİNÇ ta7w@antrak.org.tr wrote:
Dear All,
A group of people in Turkey contacted us for BGP announcement of our 44.176.x.x/16 network. At first glance I ddn't want to interfere with non-amateur groups for our 44.176 IP block announcements.
The group is Turkish volunteers for the PeeringDB (details can be found on their web page https://www.peeringdb.com/ https://ixp.ofis.link/peers.html) .
As I checked other announcements of PeeringDB for 44.x.x.x network I saw that there are some other participants sharing their routing information with peeringDB.
Samples 44.x.x.x network annoucements on peeringBD are as follows;
https://bgp.he.net/AS396503#_prefixes ( 44.190.7.0/24 and 44.135.116.0/22 ) https://bgp.he.net/AS23738#_prefixes ( 44.24.193.0/24 44.127.44.0/22 44.127.45.0/24 44.127.46.0/24 44.127.47.0/24) https://bgp.he.net/AS207036#_prefixes ( 44.164.64.0/22 ) https://bgp.he.net/AS204778#_prefixes ( 44.38.10.0/24 )
My question is : Can I share the 44.176.x.x/16 network announcement with this group of people (the users on my side are all hamradio licensed amateurs, but the announcing will be done bye a non-hamradio person.
Thanks Baris DINC TA7W
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
-
Barış DİNÇ -
Brian Kantor -
G1FEF -
Kenneth Finnegan -
Ruben ON3RVH