Hi All,
I remember seeing a list of hardware router that would work with the 44 network. Anyone know where this list is located??
If I remember there was a list of Ubiquiti Edgerouters .
Thanks.
As you know, Brian Kantor, WB6CYT passed away suddenly on November 21,
2019. We will hold a memorial service for Brian on Saturday, Feb 1 2020
at 1:30 PM in La Jolla, CA (part of San Diego). Please see this link for
details:
https://www.evite.com/event/0135NF64ATPRMYGRMEPKGPM2G3LMLQ/rsvp?utm_campaig…
Please bring any photos, mementos and (above all) stories and anecdotes
about Brian to share. Brian wasn't exactly a highly formal person who
stood on ceremony, so we'll keep this informal. If you have a story to
tell, it's up to you whether you stand up and relate it to the whole
group or just a few others at a time. There will be plenty of time for both.
Everyone who knew Brian is welcome. His friendships spanned at least
three distinct social circles, and I know he'd be very happy to see
everyone meet and enjoy everyone else's company. Even if he'd be a
little embarrassed that we were doing it in his honor.
Free snacks and refreshments will be provided, so please RSVP through
the evite link so we can tell the hotel how much to make available. If
you have special dietary needs, please say so; the hotel has a menu we
can choose from.
Please forward this email to anyone you think might be interested. Hope
to see you on the 1st.
Phil Karn, KA9Q
Hello,
Am 05.01.2020 um 11:25 schrieb Rob Janssen via 44Net <44net(a)mailman.ampr.org>:
[..]
> After investigating it appeared that an invalid name has been added to DNS by someone:
>
> dhcp-44-149-72-.db0eif IN A 44.149.72.89
thank you for your open eyes.
It must have been a bug while doing cut+paste. The archive of the source of changes shows the correct entry.
I wish a bugfree new year ;)
vy 73,
- Thomas dl9sau
I noted that since a couple of days the updates to DNS have been stuck
and it caused
a problem with out local DNS server as well.
After investigating it appeared that an invalid name has been added to
DNS by someone:
dhcp-44-149-72-.db0eif IN A 44.149.72.89
Note the trailing minus sign in the name, which is not allowed.
Bind with (default) strict name checking will issue an error on this,
and (I think that is bad)
it will refuse to load or transfer the entire zone. So the previous
version of the zone will
remain active. This was version 2001012115, while the current version
is 2001050245 so
it has been stuck for a couple of days (the format used for the version
is YYMMDDHHMM).
For now I have deleted the bad name, but it would probably be prudent to
add:
check-names warn;
to the zone configurations of the bind daemons running the ampr.org zone
so that they
have the more reasonable behavior of just ignoring that single name
instead of the entire
zone.
Rob
Brett:
Thank you for your decades of service to one of the digital sides of
amateur radio.. My jnos convers server has been linked to wa7v for many
years 24/7 and I am most grateful that you have been able to provide a
gateway and for all the work you have done.
Merry Christmas and Happy New Year to you and yours.
Ken - KD6OAT
>
>
> Date: Sat, 21 Dec 2019 12:43:00 -0800
> From: Brett Mueller <wa7v(a)wa7v.com>
> To: 44net(a)mailman.ampr.org
> Subject: [44net] WA7V Services to End
> Message-ID: <7a53f433-ed44-508b-83fd-5bce59361592(a)wa7v.com>
> Content-Type: text/plain; charset=utf-8
>
> Hello, 44net ops,
>
> An assortment of circumstances have gradually led me to the decision to
> terminate the WA7V gateway/BBS and related services at College
> Place/Walla Walla, Washington, USA.
>
> Services are scheduled to go offline on Monday, December 30, at
>
>
>
Good day,
I am looking for a smtp gateway where I will be able to send mail from
my jnos (va2om.ampr.org) to the internet.
Any taker?
Happy Holiday!.
73 de Jean,
VA2OM / VE2PKT
--
--
Sysop de: VE2PKT (BBS), VE2PKT-13 (URONode)
: VE2RCN-1, VE2RGM-1, VE2RGC-1, VE2RVA-1, (The-Net)
: VE2PKT-9 (DXCluster), VE2PKT-10 (Winlink Gateway)
RF:
147.435 Mhz (1200 Bps),
Internet:
Telnet://nodes-ve2pkt.dyndns.org port 23 (Network Node)
Telnet://fbb-ve2pkt.dyndns.org port 6300 (FBB BBS)
Telnet://ve2pkt.dyndns.org port 9000 (DXCluster)
E-Mail:
packet: ve2pkt(a)ve2pkt.#qbc.qc.can.noam
ampr net: ve2pkt(a)ve2pkt.ampr.org
Inet: ve2pkt(a)gmail.com
Hello, 44net ops,
An assortment of circumstances have gradually led me to the decision to
terminate the WA7V gateway/BBS and related services at College
Place/Walla Walla, Washington, USA.
Services are scheduled to go offline on Monday, December 30, at
approximately 00:00 UTC (Sunday afternoon/evening in the Americas).
These services include:
* Hub_NA saupp convers hub
* ALWGW:WA7V-8 NOS Gateway/BBS
* ALWBBS:WA7V FBB BBS
* ALWHUB:WA7V-4 UROnode
* PNW:WA7V-2 (X)Net Router
I believe we have a replacement lined out for Hub_NA. I should have a
confirmation shortly, and another announcement will be following.
It's been an interesting 2+ decades for me, and I'm very grateful to a
number of extremely bright and motivated hams around the world who have
contributed so much in advancing the all-encompassing art of amateur
radio. I've been the undeserving recipient of their creativity,
expertise, time and energy. For most it is a labor of love, and
certainly not something that has put any bread on their tables. To those
amateurs, I heartily say, "thank you!"
Thanks for your links, chats, assistance and friendship! We'll see what
the future holds. :)
Merry Christmas, and happy holidays!
73,
Brett Mueller
Pendleton, Oregon, USA
I'm running into an interesting problem I thought maybe someone in this community would have run into before.
We're working on a project to redesign and re-IP our entire radio network. Part of the goal is to stop using OpenVPN and IPSec tunnels (long story) and move exclusively to GRE-based tunnels. The plan is to have two Linux VPS hosts running at a provider with our 44Net allocation and an IPv6 allocation advertised and then routed into the radio network over GRE tunnels to 3 different locations that are all backhauled together. One of the primary goals is to do dual-stack throughout the network.
I have one site setup working perfectly - "gre0". It's passing IPv4 and IPv6 traffic over the GRE tunnel. One *key* point to this is that the GRE connection endpoints are iPv6. IPv4 isn't doable for this connection (again, long story but not an option). When setting up the second GRE tunnel "gre2", nothing would work even though the configuration was the same EXCEPT for the fact that the second GRE tunnel was using IPv4 addresses for the GRE tunnel endpoints. Linux keeps spitting out a very odd error when I try to ping across the tunnel I cannot find reasonably documented anywhere:
ip6_tunnel: gre2 xmit: Local address not yet configured!
The key was the "ip6_tunnel" part that took me awhile to figure out. After experimenting, I've found that if I have one GRE tunnel using IPv6 endpoints (ip -6 tunnel add gre0 mod ip6gre) and one using IPv4 endpoints (ip tunnel add gre2 mode gre), only the gre0 tunnel will work and the gre2 tunnel seems to believe it's missing an IPv6 address. If I delete the gre0 tunnel, the gre2 tunnel immediately beings working with both IPv4 and IPv6 traversing the GRE. I cannot find any documentation that describes this behavior or why it would be the case.
I can't switch to IPIP tunnels because I haven't found a way to do a dual-stack tunnel between the endpoints - seems like you can only do one IPIP tunnel between two endpoint IPs regardless of type (ipip, ipip6, ip6ip6, sit)
Anyone have any deep wisdom on GRE tunnels?
Jason
