10 Jul
2014
10 Jul
'14
6:42 p.m.
On Thu, Jul 10, 2014 at 10:21 AM, K7VE - John <k7ve(a)k7ve.org> wrote:
These are the applications we need to bring to 44-Net
We're [HamWAN] doing pretty good so far! Hostnames below...
On Thu, Jul 10, 2014 at 4:56 AM,
<lx1duc(a)laru.lu> wrote:
> - 2 DMR repeaters
> - several D-Star HotSpots
None yet.
> - DNS resolvers open to 44net (Anycasted),
secondary DNS Service available for fellow YLs and OMs
HamWAN's recursive DNS is at 44.24.244.1 and 44.24.245.1, anycasted of
course. This will work within 44.24.240.0/20 for resolving any domain.
Authoritative DNS is
a.ns.hamwan.net (44.24.244.2)
b.ns.hamwan.net (44.24.245.2)
> - NTP servers (Anycasted)
NTP.hamwan.net (44.24.244.4)
NTP.hamwan.net (44.24.245.4)
Also anycasted. At least one of the members in this anycast pool is
GPS-synced statum-1.
> - VoIP (SIP)
voip.k7nvh.hamwan.net (44.24.255.5)
Ask Nigel for an extension if you want to register your SIP phone. We
have three local numbers for dialing in and out, but I believe they
lack long distance service and are limited to Seattle, Bellevue, and
Olympia (don't quote me on that). We do conference calls
semi-regularly.
> - VPN
> - (planned) APRS Server
northwest.aprs2.net (on HamWAN's Seattle-SRV1)
> - (planned) connect existing APRS I-GATEs
baldi-aprs.kd7lxl.hamwan.net (44.24.240.203) is a dual-channel igate
(144.39 @ 1200 baud and 144.35 @ 9600 baud) connected to
northwest.aprs2.net
> - (planned) Hosting of HAM webs
> - (planned) Hosting of HAM email services
We have postfix configured so that outgoing mail works, but no one has
bothered with incoming.
Tom KD7LXL
11 Jul
11 Jul
6:14 a.m.
New subject: [HamWAN PSDR] Fwd: 44net and internal BGP tests
Tom et al;
Incoming is slick with axMail and the plugins, and you can even use a cell
phone to do your mail with as this should be proof of concept. The software
is at linux.radio.org.au and on my ftp site at n1uro.ampr.org. I suppose I
could code it to auto make a public _ html directory automatically so that
could tie in with Apache for auto user Web space as well.
Sent with AquaMail for Android
http://www.aqua-mail.com
On July 10, 2014 1:43:10 PM Tom Hayward <esarfl(a)gmail.com> wrote:
(Please trim inclusions from previous messages)
_______________________________________________
On Thu, Jul 10, 2014 at 10:21 AM, K7VE - John <k7ve(a)k7ve.org> wrote:
These are the applications we need to bring to
44-Net
We're [HamWAN] doing pretty good so far! Hostnames below...
On Thu, Jul 10, 2014 at 4:56 AM,
<lx1duc(a)laru.lu> wrote:
> - 2 DMR repeaters
> - several D-Star HotSpots
None yet.
> - DNS resolvers open to 44net (Anycasted),
secondary DNS Service
available for fellow YLs and OMs
HamWAN's recursive DNS is at 44.24.244.1 and 44.24.245.1, anycasted of
course. This will work within 44.24.240.0/20 for resolving any domain.
Authoritative DNS is
a.ns.hamwan.net (44.24.244.2)
b.ns.hamwan.net (44.24.245.2)
> - NTP servers (Anycasted)
NTP.hamwan.net (44.24.244.4)
NTP.hamwan.net (44.24.245.4)
Also anycasted. At least one of the members in this anycast pool is
GPS-synced statum-1.
> - VoIP (SIP)
voip.k7nvh.hamwan.net (44.24.255.5)
Ask Nigel for an extension if you want to register your SIP phone. We
have three local numbers for dialing in and out, but I believe they
lack long distance service and are limited to Seattle, Bellevue, and
Olympia (don't quote me on that). We do conference calls
semi-regularly.
> - VPN
> - (planned) APRS Server
northwest.aprs2.net (on HamWAN's Seattle-SRV1)
> - (planned) connect existing APRS I-GATEs
baldi-aprs.kd7lxl.hamwan.net (44.24.240.203) is a dual-channel igate
(144.39 @ 1200 baud and 144.35 @ 9600 baud) connected to
northwest.aprs2.net
> - (planned) Hosting of HAM webs
> - (planned) Hosting of HAM email services
We have postfix configured so that outgoing mail works, but no one has
bothered with incoming.
Tom KD7LXL
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
9:27 a.m.
New subject: [HamWAN PSDR] Fwd: 44net and internal BGP tests
Brian,
I can't reach n1uro.ampr.org from here although I have the ipip route
to you.
This is already a problem for a long time and effects also other subnets
I route.
ping to your commercial gateway address 76.28.121.159 is OK.
Can you reach 44.135.85.151 or 44.135.85.30 from there over amprnet?
Bob VE3TOK
On 14-07-11 01:14 AM, Brian wrote:
(Please trim inclusions from previous messages)
_______________________________________________
Tom et al;
Incoming is slick with axMail and the plugins, and you can even use a
cell phone to do your mail with as this should be proof of concept.
The software is at linux.radio.org.au and on my ftp site at
n1uro.ampr.org. I suppose I could code it to auto make a public _
html directory automatically so that could tie in with Apache for auto
user Web space as well.
Sent with AquaMail for Android
http://www.aqua-mail.com
10:38 a.m.
New subject: [HiJacked Thread] 44.135.85.151 unreachable
Hi Bob,
I usually don't reply to hijacked threads, but every now and then I
make an exception.
I cannot reach 44.135.85.151 either
traceroute to 44.135.85.151 (44.135.85.151), 30 hops max, 60 byte packets
1 rtr-255-224-28.lx.ampr.org (44.161.255.225) 0.685 ms 0.637 ms 0.596 ms
2 ampr-gw1.lx.ampr.org (44.161.255.255) 21.895 ms 22.193 ms 22.141 ms
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
According to information currently available to me the commercial
gateway is 69.165.175.62.
73 de Marc, LX1DUC
Quoting "Boudewijn (Bob) Tenty" <bobtenty(a)gmail.com>om>:
> (Please trim inclusions from previous messages)
> _______________________________________________
> Brian,
>
> I can't reach n1uro.ampr.org from here although I have the ipip route
> to you.
> This is already a problem for a long time and effects also other
> subnets I route.
> ping to your commercial gateway address 76.28.121.159 is OK.
>
> Can you reach 44.135.85.151 or 44.135.85.30 from there over amprnet?
>
> Bob VE3TOK
>
> On 14-07-11 01:14 AM, Brian wrote:
>> (Please trim inclusions from previous messages)
>> _______________________________________________
>> Tom et al;
>> Incoming is slick with axMail and the plugins, and you can even use
>> a cell phone to do your mail with as this should be proof of
>> concept. The software is at linux.radio.org.au and on my ftp site
>> at n1uro.ampr.org. I suppose I could code it to auto make a public
>> _ html directory automatically so that could tie in with Apache for
>> auto user Web space as well.
>>
>>
>> Sent with AquaMail for Android
>> http://www.aqua-mail.com
>>
>
>
12:05 p.m.
New subject: [HiJacked Thread] 44.135.85.151 unreachable
Hello Bob!
I can not reach 44.135.85.151 as well...
root@deb:~# traceroute 44.135.85.151
traceroute to 44.135.85.151 (44.135.85.151), 30 hops max, 60 byte packets
1 linux.sp2lob.ampr.org (44.165.2.2) 0.668 ms 0.677 ms 0.706 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
Best regards.
Tom - sp2lob
10:35 p.m.
New subject: [HiJacked Thread] 44.135.85.151 unreachable
Hi Tom!
Tnx.
I can ping (traceroute) linux.sp2lob.ampr.org fine from here.
You can also try 44.135.85.30
Cheers,
Bob VE3TOK
On 14-07-11 07:05 AM, sp2lob wrote:
I can not reach 44.135.85.151 as well...
Best regards.
Tom - sp2lob
11:23 p.m.
New subject: [HiJacked Thread] 44.135.85.151 unreachable
Hello Bob!
I did not mention 44.135.85.30
as I can ping it and do traceroute too.
You may check my other addresses ending
with 3, 5, 6, 8 and 9; all of them are up& running.
Best regards.
Tom - sp2lob
Sent from Sony Xperia Z1
http://www.aqua-mail.com
10:22 p.m.
New subject: [HiJacked Thread] 44.135.85.151 unreachable
Hi Marc,
Sorry to "hijack" your thread.
My commercial ip is OK
pinging your commercial ip 141.75.245.225 is fine.
ping/traceroute to 44.161.255.255 is ok from 44.135.85.151 but not to
44.161.255.225
73,
Bob VE3TOK
On 14-07-11 05:38 AM, lx1duc(a)laru.lu wrote:
(Please trim inclusions from previous messages)
_______________________________________________
Hi Bob,
I usually don't reply to hijacked threads, but every now and then I
make an exception.
I cannot reach 44.135.85.151 either
traceroute to 44.135.85.151 (44.135.85.151), 30 hops max, 60 byte packets
1 rtr-255-224-28.lx.ampr.org (44.161.255.225) 0.685 ms 0.637 ms
0.596 ms
2 ampr-gw1.lx.ampr.org (44.161.255.255) 21.895 ms 22.193 ms 22.141 ms
3 * * *
12:33 p.m.
New subject: [HamWAN PSDR] Fwd: 44net and internal BGP tests
On 07/11/2014 08:27 PM, Boudewijn (Bob) Tenty wrote:
(Please trim inclusions from previous messages)
_______________________________________________
Brian,
I can't reach n1uro.ampr.org from here although I have the ipip route
to you.
This is already a problem for a long time and effects also other
subnets I route.
ping to your commercial gateway address 76.28.121.159 is OK.
Can you reach 44.135.85.151 or 44.135.85.30 from there over amprnet?
Bob VE3TOK
Hi Bob,
Likewise, I can not reach n1uro.ampr.org but your address
44.135.85.151 is all ok from here in NZ.
Regards ...... Peter ZL2BAU
10:43 p.m.
New subject: [HamWAN PSDR] Fwd: 44net and internal BGP tests
Hi I cam telnet to 44.135.85 151 from gb7cip,.ampr.org
and also FROM n1uro.ampr.org
So you may have a local firewall issue maybe??
73 de Paul g4apl/gb7cip
________________________________________
From: 44net-bounces+paul=skywaves.demon.co.uk(a)hamradio.ucsd.edu
[44net-bounces+paul=skywaves.demon.co.uk(a)hamradio.ucsd.edu] on behalf of Boudewijn (Bob)
Tenty [bobtenty(a)gmail.com]
Sent: 11 July 2014 09:27
To: AMPRNet working group
Subject: Re: [44net] [HamWAN PSDR] Fwd: 44net and internal BGP tests
(Please trim inclusions from previous messages)
_______________________________________________
Brian,
I can't reach n1uro.ampr.org from here although I have the ipip route
to you.
This is already a problem for a long time and effects also other subnets
I route.
ping to your commercial gateway address 76.28.121.159 is OK.
Can you reach 44.135.85.151 or 44.135.85.30 from there over amprnet?
Bob VE3TOK
On 14-07-11 01:14 AM, Brian wrote:
(Please trim inclusions from previous messages)
_______________________________________________
Tom et al;
Incoming is slick with axMail and the plugins, and you can even use a
cell phone to do your mail with as this should be proof of concept.
The software is at linux.radio.org.au and on my ftp site at
n1uro.ampr.org. I suppose I could code it to auto make a public _
html directory automatically so that could tie in with Apache for auto
user Web space as well.
Sent with AquaMail for Android
http://www.aqua-mail.com
12 Jul
12 Jul
11:55 a.m.
New subject: [HamWAN PSDR] Fwd: 44net and internal BGP tests
Nice job Tom on your HamWAN setup.
And access to the works flawless with proper tunneling set-up (I was sceptic
at first to use a 44net tunnel endpoint for your 44.24.240.0/20...).
Congratulations.
Marius, YO2LOJ
-----Original Message-----
From: 44net-bounces+marius=yo2loj.ro(a)hamradio.ucsd.edu
[mailto:44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu] On Behalf Of Tom
Hayward
Sent: Thursday, July 10, 2014 20:42
To: Puget Sound Data Ring; AMPRNet working group; All things digital and fun
Subject: Re: [44net] [HamWAN PSDR] Fwd: 44net and internal BGP tests
(Please trim inclusions from previous messages)
_______________________________________________
On Thu, Jul 10, 2014 at 10:21 AM, K7VE - John <k7ve(a)k7ve.org> wrote:
These are the applications we need to bring to 44-Net
We're [HamWAN] doing pretty good so far! Hostnames below...
On Thu, Jul 10, 2014 at 4:56 AM,
<lx1duc(a)laru.lu> wrote:
> - 2 DMR repeaters
> - several D-Star HotSpots
None yet.
> - DNS resolvers open to 44net (Anycasted),
secondary DNS Service
available for fellow YLs and OMs
HamWAN's recursive DNS is at 44.24.244.1 and 44.24.245.1, anycasted of
course. This will work within 44.24.240.0/20 for resolving any domain.
Authoritative DNS is
a.ns.hamwan.net (44.24.244.2)
b.ns.hamwan.net (44.24.245.2)
> - NTP servers (Anycasted)
NTP.hamwan.net (44.24.244.4)
NTP.hamwan.net (44.24.245.4)
Also anycasted. At least one of the members in this anycast pool is
GPS-synced statum-1.
> - VoIP (SIP)
voip.k7nvh.hamwan.net (44.24.255.5)
Ask Nigel for an extension if you want to register your SIP phone. We
have three local numbers for dialing in and out, but I believe they
lack long distance service and are limited to Seattle, Bellevue, and
Olympia (don't quote me on that). We do conference calls
semi-regularly.
> - VPN
> - (planned) APRS Server
northwest.aprs2.net (on HamWAN's Seattle-SRV1)
> - (planned) connect existing APRS I-GATEs
baldi-aprs.kd7lxl.hamwan.net (44.24.240.203) is a dual-channel igate
(144.39 @ 1200 baud and 144.35 @ 9600 baud) connected to
northwest.aprs2.net
> - (planned) Hosting of HAM webs
> - (planned) Hosting of HAM email services
We have postfix configured so that outgoing mail works, but no one has
bothered with incoming.
Tom KD7LXL
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
3798
days inactive
3800
days old
10 comments
9 participants
participants (9)
-
Boudewijn (Bob) Tenty -
Brian -
lx1duc＠laru.lu -
Marius Petrescu -
Paul Lewis -
Peter Mallett -
sp2lob -
sp2lob＠tlen
-
Tom Hayward