25 Apr
2018
25 Apr
'18
1:51 p.m.
I just applied for a /24 out of 44.190/16, to help
with this endeavor.
I’ll be announcing the prefix out of a commercial
datacenter in Fremont, CA under ASN 7247.
73,
-jav k4jh
Jav is the first one to get his proxies/relays running as a result of this call.
He said "This was easy!".
Rob
25 Apr
25 Apr
2:27 p.m.
New subject: Echolink proxy/relay hosting
On Apr 25, 2018, at 10:51, Rob Janssen
<pe1chl(a)amsat.org> wrote:
Yes, it was.
1) Obtained the 44.190.5.0/24 assigned to me, configured my router at the datacenter in
Fremont, CA to announce it.
2) Created VM on the above subnet, and assigned 20 IP addresses to it.
3) Obtained and compiled Rob Jenssen’s C program, configured it per the instructions.
4) Tested with just one proxy, added all the rest of proxies and relays.
5) Registered DNS hostnames.
73,
-jav k4jh
I just applied for a /24 out of 44.190/16, to
help with this endeavor.
I’ll be announcing the prefix out of a commercial
datacenter in Fremont, CA under ASN 7247.
73,
-jav k4jh
Jav is the first one to get his proxies/relays running as a result of this call.
He said "This was easy!”. 
2:38 p.m.
New subject: Echolink proxy/relay hosting
From 2012 - https://www.youtube.com/watch?v=PMI9YSM0mzY
------------------------------
John D. Hays
K7VE
<http://k7ve.org/blog> <http://twitter.com/#!/john_hays>
<http://www.facebook.com/john.d.hays>
3:15 p.m.
New subject: Echolink proxy/relay hosting
FYI folks...I used to run proxies on my subnet in the past. The only
issue was, that since subnet is not not BGP, it was intended for your
use only (i.e. not using AMPRGW for Internet, but still able to use
EchoLink).
I used the Java JAR that was available form EchoLink (I understand you
have a C program). I also used the Linux version, but the EchoLink
Validators stated that should not be used without permission (and only
for conference servers).
73,
- Lynwood
KB3VWG
26 Apr
26 Apr
1:31 a.m.
New subject: Echolink proxy/relay hosting
On 26/04/18 04:27, Javier Henderson wrote:
Yes, it was.
For some :) My current status is:
1) Obtained the 44.190.5.0/24 assigned to me, configured my router at the datacenter in
Fremont, CA to announce it.
That's in the hands of my NSP who are also hosting
my VM, last I heard
is he has configured his routers and his upstream wanted to see the COA
- I have the notification of authority that I received from Brian and
passed it on up the chain. As of around an hour ago, still no
connectivity (.1 and .2 of my range are setup), so it's a waiting game.
2) Created VM on the above subnet, and assigned 20 IP addresses to it.
I already
have the VM, and assigning addresses should be straightforward.
3) Obtained and compiled Rob Jenssen’s C program, configured it per the instructions.
I have read the docs, looks pretty straightforward, though I have a bit
of migration to do - after initial testing, I have several existing
private proxies to migrate to the binary, then create the public ones on
the 44.x addresses.
--
73 de Tony VK3JED/VK3IRL
http://vkradio.com
1:24 a.m.
New subject: Echolink proxy/relay hosting
On 26/04/18 03:51, Rob Janssen wrote:
Jav is the first one to get his proxies/relays running
as a result of
this call.
He said "This was easy!".
I'm still waiting for my NSP's upstream
to allow the BGP announcements.
--
73 de Tony VK3JED/VK3IRL
http://vkradio.com
2401
days inactive
2402
days old
5 comments
5 participants
participants (5)
-
Javier Henderson -
K7VE - John -
lleachii＠aol.com -
Rob Janssen -
Tony Langdon