Hello,
amprd 3.0 is available in the usual locations.
http://yo2tm.ampr.org/hamprojectshttp://www.yo2loj.ro/hamprojects
What's new:
- Added support for AMPR subnets in ignore list
- Added disable/enable option for incoming multicast and broadcast traffic
- Added support for selectable PID file
In regard of the issues with those ICMP unreachable messages:
For those keen ones, I added an optional kernel module, which needs to
be compiled and installed (howto is in the module subfolder).
Also, there is a new global option in the config file to enable its use.
This is a netfilter module which intercepts the IPIP 4 protocol and
converts it to protocol 94 and the other way around, circumventing the
series 4 kernel behavior that triggered the sending of those messages.
So those that want to try it: compile it (you will need to have the
kernel toolset and kernel headers installed), install it and enable the
use_redirector option.
For the rest, the filtering option will still work as expected.
Setails are in the readme files.
Have fun!
Marius, YO2LOJ
I have a question to the sysops running gateways in Europe.
Lately, my subnets (44.182.21.0/24, 44.182.20.0/24 and 44.182.21.253
using gw 89.122.215.236 and yo2loj.go.ro) seem to have been lockout from
different regions like Germany, Poland, Portugal and Bulgaria, while
access from 44.182.21.1/32 still works.
Is this intentional or just a configuration issue?
Marius, YO2LOJ
Subject: VPN
Hello,
Due to some annoying ISP firewalling that I cant control, I'm going to have
to VPN into the network, or set up a vps somewhere and vpn into that.
Ideally the first option since its cheaper :)
The link to www.arrl.org/instructions under this article
http://wiki.ampr.org/wiki/AMPRNet_VPN is invalid however. I'm not sure who
exactly to contact about this, since I cant find an author's name in the
wiki. Any help would be appreciated.
Thanks!
-Nate
Il giorno mer 13 mar 2019 alle ore 16:43 Thomas Osterried <
thomas(a)osterried.de> ha scritto:
>
> It's always the best choice to use the official repo. See
> http://www.linux-ax25.org/wiki/GIT
> http://www.linux-ax25.org/wiki/Compilation
>
> It would always have been a good idea to send patches upstream.
>
Since three days ago, the official ax25 site is not available.... are
there any news?
Very recent, there were some updates... and there was a new release
canidates (RC5) - thanks to maintainers :)
May be they are are fixing all the issues that have been fixed in the
VE7FET repos and also others issues???
At the moment i would like to thanks and i'm hoping something new...
Lorenzo iw3her
> Google says it's my fault; I say Google has its collective head up
> its ass in marking a valid email as spam. Their official word is
> "Don't act like the bad guys" and you won't have problems. Never
> mind that it's 100% RFC-compliant, they say it's bad guy behaviour.
I agree. Sending mail to google (and also hotmail/outlook) has become
very unreliable. E.g. when using @amsat.org or other forwarding services
like @veron.nl or @vrza.nl (Dutch amateur radio societies) it will usually not work.
I do not really want to use my ISP mail address, so it looks like I have
to register my own domain to get this fixed. For now, I have set an autoreply
(from the ISP mail address) encouraging people to use a different address
and look in their spambox when they expect a reply.
I hear that it is customary in the circles of gmail/hotmail/outlook users
to send a Whatsapp message "I have sent you an e-mail"...
Rob
> Everyone happy with this? Any comments?
It would be nice if the mail had some info about what a gateway is and why you (don't) want it,
e.g. with a pointer to the wiki page.
I have found that some people add a gateway entry because they think this is some form of registration
of their existing (not IPIP mesh) router e.g. connected via radio or via one of the other VPN types
we support. They think it would be useful to be registered in some list. That is how the problematic
gateway came into existance, and there are several others like that registered in the Netherlands,
that did not become problematic only because they had no subnets.
When being listed is what they actually want, of course they should not register a gateway. But it is what
they do, partly because there is a lack of higher-level explanation of concepts. And after receiving
that mail message they probably still don't understand what they are doing wrong.
Maybe a pointer to HamnetDB could be useful. Registering there is probably what they want.
Rob
Hello,
To all amprd users (this does not affect setups using the kernel tunnel
driver and ampr-ripd).
Due to changes in the 4.x kernels, there's a problem with the system
replying with "icmp unreachable" to incoming IPIP traffic.
This will possible drop incoming traffic, including the RIP broadcasts
(resulting in incomplete route tables).
Please switch to an ampr-ripd setup or filter outgoing icmp messages on
your WAN interface, using a rule like the one below:
*iptables -A OUTPUT -o ethX -p icmp --icmp-type destination-unreachable
-m state --state RELATED -j DROP*
I hope I can find a workaround on this issue.
Marius, YO2LOJ
> I don't think folks would add a gateway if they haven't been approved for a block.
Well, actually they do.
The problem is that the visitors of the portal do not know at all what the whole concept
of the IPIP tunnel mesh looks like, how it is relevant within AMPRnet, and that it is
only one of the options for getting connected.
As there is no walk-through explanation of concepts like a registered subnet, a gateway,
the resulting IPIP tunnel mesh, etc, people just blindly click on menu items and fill
out forms.
Then they have a gateway but the still don't understand how that all works.
So they close the site and continue to look elsewhere for information, and when they find
it they never come back to delete what they created.
That is why it is good to remove that crud, but also it would be good to have some more
explanatory text and/or pointers to where that can be found. And some warnings that
this is not a system to voluntarily register some information about one's station, but
that it is actually used for something and that you can actually break things by entering
information.
(of course we should strive for a situation where one cannot break the network for other
users, but still one could break the routing of one's own subnet)
Rob
