Good afternoon,
It would see that 44.133.48.66 is popping, snmpding, and other
amounts of traffic from time to time to various ampr.org systems
and doing so *without warning* type of thing. I just got hit with
a bunch of SNMP requests, others have been hit with POP requests.
Can anyone find out who the owner of that particular system or
network is, so that I can contact the entity or person.
Or perhaps a bit more draconian, can someone deal with it.
Thanks in advance.
Maiko Langelaar
VE4KLM
Greetings;
I've noticed recently after doing a package update on the iproute
packages I can no longer configure my tunnel interface tunl0. Mainly I'm
trying to reset the ttl to 64 for traceroute to properly work.
Everything I've searched comes up empty. Here's what I see:
root@gw:/usr/local/bin# iptunnel show
tunl0: ip/ip remote any local any ttl inherit nopmtudisc
root@gw:/usr/local/bin# ifconfig tunl0
tunl0 Link encap:IPIP Tunnel HWaddr
inet addr:44.88.0.1 Mask:255.255.255.255
UP RUNNING NOARP MULTICAST MTU:0 Metric:1
ttl is stuck on inherit and MTU autoconfigs to 0. This I know is set by
nopmtudisc however if I try to adjust things:
root@gw:/usr/local/bin# ip tunnel change tunl0 ttl 64
ttl != 0 and noptmudisc are incompatible
root@gw:/usr/local/bin# ip tunnel change pmtudisc mode ipip
add tunnel tunl0 failed: No such file or directory
Why would it try to ADD? the command is CHANGE.
Has anyone else suffered this before and if so what was the fix?
Thanks in advance.
--
73 de Brian Rogers - N1URO
email: <n1uro(a)n1uro.ampr.org>
Web: http://www.n1uro.net/
Ampr1: http://n1uro.ampr.org/
Ampr2: http://nos.n1uro.ampr.org
Linux Amateur Radio Services
axMail-Fax & URONode
AmprNet coordinator for:
Connecticut, Delaware, Maine,
Maryland, Massachusetts,
New Hampshire, Pennsylvania,
Rhode Island, and Vermont.
Greetings list members;
While I still search for a true fix, a hack fix would be to create a
tunl1 and route via that interface, however if you take tunl0 down, for
some reason rip fails.
If anyone has a better solution or a true fix, please relay it. Thanks
in advance...
--
73 de Brian Rogers - N1URO
email: <n1uro(a)n1uro.ampr.org>
Web: http://www.n1uro.net/
Ampr1: http://n1uro.ampr.org/
Ampr2: http://nos.n1uro.ampr.org
Linux Amateur Radio Services
axMail-Fax & URONode
AmprNet coordinator for:
Connecticut, Delaware, Maine,
Maryland, Massachusetts,
New Hampshire, Pennsylvania,
Rhode Island, and Vermont.
Brian,
I found the following in a Linux manual for the 'ip tunnel' command:
nopmtudisc -- disable Path MTU Discovery on this tunnel. It is
enabled by default. Note that fixed ttl is incompatible with this
option: tunnels with fixed ttl always make pmtu discovery.
If you create a tunnel that does not care about MTU state, it's also
unconcerend about the 'distance' the packet has traveled, your eth
interface would handle both tasks in that instance (being a 'dumb
tunnel,' if you will). With nopmtudisc on, your 44Router would properly
fragment the packet when transmitting on eth and sets the ttl on the
ARPA Internet, as opposed to AMPRnet. If this command worked before you
updated your IP utilities, it was probally due to the previous version
not being written true to RFC.
73,
Lynwood
KB3VWG
44net-request(a)hamradio.ucsd.edu wrote:
> Subject:
> [44net] Pi bug for ipencap?
> From:
> Brian Rogers <n1uro(a)n1uro.ampr.org>
> Date:
> 12/30/2013 12:59 AM
>
> To:
> AMPRNet working group <44net(a)hamradio.ucsd.edu>
>
>
> Greetings;
>
> I've noticed recently after doing a package update on the iproute
> packages I can no longer configure my tunnel interface tunl0.
How did you get that update? is it an update that is currently queued on
"apt-get upgrade"? or was it something you installed yourself?
(my Pi is still working but I'd like to know what to avoid)
Rob
Merry Christmas and a Happy New Year!
73
Glenn KA0MOS/VE1
---
This email is free from viruses and malware because avast! Antivirus protection is active.
http://www.avast.com
To all AMPRnet friends,
Merry Christmas and a Happy New Year with more AMPRnet Radio Links in 2014!
--
73 de SV1UY
Demetre Ch. Valaris
e-mail: demetre.sv1uy(a)gmail.com
AMPRnet: sv1uy(a)sv1uy.ampr.org
Radio e-mail: sv1uy(a)winlink.org
(to use my radio e-mail put //WL2K in the beginning of the subject line)
http://www.qsl.net/sv1uy
John,
AFAIK,
encap.txt file available via ftp site is updated once per hour,
whilst
encap.txt file available via portal.ampr.org is updated
once update was made on the portal - immediately!
--
Best regards.
Tom - sp2lob
Hello all,
I don't like the idea of regulatory discussions on this list.
However, I am curious (as it's pertinent to what we do on this list)
what the rules are in other counties for ham radio.. So far I haven't
had much luck finding the answers on the web.
Presently in US ham radio data bandwith:
2 meters is 20 khz max, 19.6 kilobauds
70 cm is 100 khz max, 56 kilobauds
Ironically, while there is plenty of space on 70 cm, other modes like
ATV are permitted to occupy up to 6 MHz of bandwidth.
Since we have a nice mix of hams from all over the world on this list,
I'd appreciated a reply (can be off list) on what is permitted in your
country on 2 meters and 70 cm.
Thanks,
Steve, KB9MWR
