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
Marc, LX1DUC,
Per Brian in a Jan 22 note:
44.0.0.1 responds to pings received from the Internet. It does not
respond to pings coming into it over an encap connection to it, for
some reason that I've not been able to figure out. I believe it to
be a difficulty in getting it to recognize decapped pings.
If you are receiving the rip44 announcements, you have properly
configured your tunnel to receive IP-in-IP encapsulation from 44.0.0.1.
Feel free to use:
http://44.60.44.10/tools
or
http://kb3vwg-010.ampr.org/tools
I see your encap as:
44.161.202.0 via 46.29.183.253 dev tunl0 onlink window 840
44.161.203.0 via 46.29.183.253 dev tunl0 onlink window 840
44.161.229.0 via 46.29.183.253 dev tunl0 onlink window 840
Also, I am unable to ping 44.161.229.126. What script/configuration did
you use to enable your tunnel; did you specify a local or remote IP
(un-needed)? Feel free to look at my script at http://44.60.44.13/startampr
73,
Lynwood
KB3VWG
POL: Potrzebuje pomocy.
Jak modem podłączę pod ttyS0 (iobase 3f8 irq 4) na płycie głównej modem
działa idealnie nadaje
i odbiera. A jak podłączę go do ttyS1 (iobase 2400 irq 177) na karcie I/O
to tylko odbiera nie
chce nadawać
ENG: I need help.
How do I plug the modem into ttyS0 (iobase 3f8 irq 4) on the main board
modem works perfectly
transmits and receives. And when I connect it to ttyS1 (iobase 2400 irq
177) on the I/O just
does not want to give answers
------
POL: Mam komputer z 2 modemami Baycom
Linux CentOS 5, Kernel 2.6.18-274.18.1.el5ax25.2,
używam sterownik: baycom_ser_fdx
ENG: I have a computer with two modems Baycom
Linux CentOS 5 Kernel 2.6.18-274.18.1.el5ax25.2,
I use the driver: baycom_ser_fdx
------
POL: Używam modemów Baycom, podłączone do karty I/O PCI
Modemy tylko odbierają (Rx) ale nie nadają (not Tx)
ENG: I use Baycom modems, connected to the I/O PCI
Modems only receive (Rx), but does not transmit (Tx not)
------
POL: A to konfiguracja karty I/O z komendy: lspci -vvv
ENG: And this is the configuration I/O card with the command: lspci-vvv
Serial controller: Device 4348:3253 (rev 10) (prog-if 02 [16550])
Subsystem: Device 4348:3253
Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Interrupt: pin A routed to IRQ 177
Region 0: I/O ports at 2400 [size=8]
Region 1: I/O ports at 2000 [size=8]
Kernel driver in use: serial
------
ttyS0, iobase: 0x03f8, irq: 4 (mainboard)
ttyS1, iobase: 0x2400, irq: 177 (Card I/O)
ttyS2, iobase: 0x2000, irq: 177 (Card I/O)
------
baycom_ser_fdx: version 0.10 compiled
hdlcdrv: version 0.8 compiled
POL: Może ktoś mi powie dlaczego na ttyS0 działa idealnie a na karcie I/O tylko
odbiera ....
Gdzie mam błąd. Może w baycom_ser_fdx.c ???
ENG: Can someone tell me why the ttyS0 works perfectly and on the I/O only ....
Where do I receive an error. Maybe baycom_ser_fdx.c???
--
73 de Janusz / SP1LOP
===== Janusz J. Przybylski, SP1LOP ==================
Poland AMPRNet Co-ordinator [44.165/16] from Mar 2003
=====================================================
from the wiki at http://en.wikipedia.org/wiki/AMPRNet:
*44.128.0.0/16*
*44.128.x.x is the testing subnet and consists of 65,536 (216) addresses.
Much akin to 10.0.0.0/8, 172.16.0.0/12, 169.254.0.0/16 or 192.168.0.0/16,
this is an unroutable private IP
block<http://en.wikipedia.org/wiki/Private_network>.
Connectivity to the rest of the network should be given through router
gateways <http://en.wikipedia.org/wiki/Gateway_(telecommunications)> much
as one would do with Network address
translation<http://en.wikipedia.org/wiki/Network_address_translation>
in
any other private IP block.*
There is no attribution to that statement, and nothing I could find at
AMPR.org
Is this the best way to address devices when doing NAT into a private
network? Any issues?
Or are there advantages to requesting assigned numbers?
thanks & 73,
Jim Alles
I just made some requests via the AMPRNet portal to create some DNS records in the ampr.org domain, and the requests were rejected with the following remark:
"DNS is not active yet, please subscribe to the 44-Net mailing list to keep advised of progress."
I presume they are referring to this mail list.
So, how do I get DNS records created in the ampr.org domain? I understand that in the past, there was an email robot, but I have been unable to find any details on how to use it. Can anyone point me in the right direction?
Many thanks,
Matt VK2RQ
Brian K.:
*"This is precisely the situation that our longstanding method of tunnel
gateways is designed to overcome.
You do this by setting up a Linux host that is assigned a single PSU
address, probably something that isn't too hard to do. You shouldn't need
to have them open any holes in the firewall or ask for special treatment
as long as the existing firewall allows IPIP (internet protocol #4)
through, which most do because the firewall managers never thought to
block it, and also because some VPN schemes used to use it.
The PSU folks don't have to do anything about network 44 routing or BGP
or whatever.
You then get a subnet allocation from your regional AMPRNet IP address
coordinator and register a gateway for that subnet (via the PSU address)
on the portal. Voila', you now have a subnet of AMPRNet routed to your
Linux host via IP-IP encapsulation, and through the technique of tunnel
gatewaying that Linux host is now connected to the AMPRNet, albeit at
a somewhat limited bandwidth."*
*
*
I am not opposed to this, especially since I have not tried it yet.
However, PSU has resources, that if they can be tapped, might enable PSARC
do something equivalant to what USC is doing, but for the state of
Pennsylvania. For one, to further experiment, and also to improve the
bandwidth limitations down the road.
The 'Backbone" connection I expect to get through PSU will be 1
gigabit/sec. If co-located w/ PennREN, we would be sitting on a statewide
10Gb/s middle mile network. And, that is IPv6 now.
It would be a heck of a way to learn!
73, Jim A.
Jim,
Your question sounds similar to one I just asked last week. In my
case, convincing the IT department to forward IPIP to our internal
address isn't likely.
So I have been playing with OpenVpn, and started documenting things.
It looks like it will do what I want. Requests will come to my IPIP
Rip gateway, which will also double as an OpenVPN server, and I'll
route the traffic though that statefull connection.
I have been trying to track down notes/papers/documents that might be of use:
http://www.qsl.net/k/kb9mwr//wapr/tcpip/index.html
Speaking of which, does anyone else have any recommendations on things
that have been written over the years?
I swear I am the only ham in my local club that has at least a basic
understanding of TCP/IP. So anything I can use to help explain things
to newbies would be helpful. I usually just reference the O'Reilly
Books, TCP/IP Administration comes to mind.
Has anything ever been written explaining DNS records with a ham slant?
A gateway had his internet address change yesterday and the new address was
changed to the new address at the gateway successfully..
We've noticed that the RIP process has the correct address but the
encap.txt file does not.
Is there a problem at the gateway with the way it is handling the encap.txt
file when data is changed? It appears that the old file is sent and not
the new one..
73, Don - ve3zda
Excellent explanation Marius.
So how does PPTP compare to openvpn?
I have tried to find a good explanation for the various VPN types,
hamachi, openvpn, pptp, etc.. haven't really found such yet.
C.J. thanks for the examples. I think I know the answer to what I am going
to ask, but..
Could an IPIP tunnel accomplish the same thing that OpenVPN can for the
situation I described (NAT and no modification to a remote firewall)?
Why not?
