Thanks Brian for relaying the message for me. At the moment I see I have
link so here's hoping this will make it. They're doing some pretty heavy
renovations in the center of my town and while doing so my line was cut.
This also happened a few weeks ago. The combo voip/data router took a
bit of a spike when they reconnected the cable and did it some harm.
It's an old Thomson. This second cut/repair sent another spike and
harmed it even worse. I don't have access into it, only the provider
does but the way it's acting is as if it's NAT isn't properly flushing.
I did get a replacement which is also an upgrade and hope to put it
online over the weekend pending no issues. My guess is that my IP will
change due to the new mac address. Those who have a static encap route
programmed in will need to change this, I'll post the new IP in here so
you can make the change, or delete it and let rip handle the rest.
Hopefully the transition will go smoothly - but this is networking
here...
--
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.
Hello fellows hams.
We want restart again here the 44.152 subnet from Venezuela amprnet.
In this first step mount the first gateway with 44.152.0.0./17
network, this is a Ubuntu 12.04 server machine in a dinamic IP
service.
Now for resume, think i miss something:
Internet IP-->TpLink TL-R480T firewall->UbuntuServer12.04->JNOS2.0j
Internet IP (dinamic from ISP)->Tplink LAN 192.168.1.2->Ubuntu Server
eth0 192.168.1.109->JNOS IP 44.152.0.60, tun0 192.168.1.110
in JNOS autoexec.nos:
attach tun tun0 1500 0
ifconfig tun0 ipaddress 192.168.1.110
ifconfig tun0 netmask 255.255.255.0
ifconfig tun0 mtu 1500
#
shell ifconfig tun0 192.168.1.109 pointopoint 192.168.1.110 mtu 1500 up
shell arp -s 192.168.1.110 00:19:DB:4A:CE:2A pub
shell arp -s 44.152.0.60 00:19:DB:4A:CE:2A pub
shell route add 44.152.0.60 gw 192.168.1.110 tun0
#
shell arp -sD 192.168.1.110 eth0 pub
#
shell iptables -I INPUT 1 -j ACCEPT --proto 4
shell iptables -I INPUT 1 -j ACCEPT --proto 94
shell iptables -I OUTPUT 1 -j ACCEPT --proto 4
shell iptables -I OUTPUT 1 -j ACCEPT --proto 94
shell iptables -I FORWARD 1 -j ACCEPT --proto 4
shell iptables -I FORWARD 1 -j ACCEPT --proto 94
shell /sbin/iptables -I INPUT -i tun0 -j ACCEPT
shell /sbin/iptables -I FORWARD -i tun0 -j ACCEPT
#
shell iptables -t nat -A PREROUTING -d 192.168.1.110/32 --proto 4 \-j
DNAT --to 44.152.0.60
shell iptables -t nat -A PREROUTING -d 192.168.1.110/32 --proto 94 \-j
DNAT --to 44.152.0.60
shell iptables -t nat -A POSTROUTING -s 44.152.0.60/32 -o eth0 -p 4
shell iptables -t nat -A POSTROUTING -s 44.152.0.60/32 -o eth0 -p 94
#
I am little lost here, the JNOS 44.152.0.60/ lan 192.168.1.110 work
with all Internet IP well but with ampr dont (think for encap routes
and rip2 dont work)
in Linux console:
./rip44d -v
found local address: 192.168.1.109
found local address: 127.0.0.1
found local address: 192.168.1.109
opening UDP socket 520...
entering main loop, waiting for RIPv2 datagrams
and stop here dont receive the routes BUT in JNOS trace monitor see
the incoming the rip UDP from 169.228.66.251 but my JNOS ip lan
192.168.1.110 replay a ICMP UnreachablePort
Please, I need be clear about what is the better way to RIP amproutes
in linux or jnos?
I think have any very wrong here in the routing, please any advice is
welcome to me (gmedinas(a)gmail.com)
Thanks for help, 73 de Gabriel YV5KXE
N1URO wants me to let you folks know what his site is offline
for a few days because construction work cut his network link.
His email is similarly affected.
- Brian
A few years back Vinton Cerf, was invited back to Stanford where he
graduated, to give a speech to future engineering students.
I don't know why it didn't occur to me to share the video here on this
list back when I first discovered it.
It seems relevant to what we do on this list.
There is a lot of interesting history and things to get you thinking
in his presentation.
http://kb9mwr.blogspot.com/2011/02/vint-cerf-re-thinking-internet.html
In browsing the encap file I see entries that aren't defined as
regional networks:
ex:
44.71.28.0/27
44.71.4.0/27
44.71.4.32/27
44.72.26.0/24
44.72.73.0/26
https://portal.ampr.org/networks.php?a=region&id=162
The listed regional networks skip from 44.70 to 44.74
44.70.0.0/16 Ohio
44.74.0.0/16 North Carolina
Hi all
First time poster here so be gentle :-)
Can anyone point me in the direction of where to start? I have an IP address allocated from the portal, a shiny Linux server, 2m rig and an old KAM TNC that can be put in to Kiss mode. What's missing is what to do and where to start.
Any advise very welcome and I look forward to some contacts over data.
Regards
Andy
G0HXT
44net-request(a)hamradio.ucsd.edu wrote:
> Subject:
> Re: [44net] known good routers that pass rip/44-net friendly in uk?
> From:
> ve1jot <ve1jot(a)eastlink.ca>
> Date:
> 01/08/2014 09:43 AM
>
> To:
> 44net(a)hamradio.ucsd.edu
>
>
> Anyone know of a list of routers that pass ripv2? A ham in EU is trying
> to set up ripv2 with our help but ripv2 gateway announcements don't seem to be coming through the router...yes, the pi is in the DMZ, hi hi! He's on virginmedia, any issues with their modems known?
You mean the ipip tunneling is working with static routing but you cannot get RIP to work?
Or is the situation merely "it does not work" and the diagnosis "there are no RIP announcements"?
I set up a Pi some time ago and I had a strange problem with RIP that I finally resolved, and submitted
a patch to ampr-ripd that makes it work problemfree.
I don't know if the other ripd was similarly modified, for sure it had the same issue.
The problem was that although RIP announcements made it all the way to the Pi, they were not
properly received on the UDP socket the daemon created.
Rob
- Any iptables-based device (e.g. Linux kernel/OS, DD-WRT, OpenWRT, RaspberyPi)
- DLink devices that allow selecting of "Other" protocol, DLink provides Web GUI simulators for most router models
**On D-Link
1.) Browse to Network Settings > Advanced > Virtual Server
2.) Add name and IP address of 44GW, or select IP from the list and
click the "<<" button
3.) Change Protocol to "Other" and enter "4" in the box under Protocol
4.) Click "Save Settings"
**Command for Static IP (tested on DD-WRT and OpenWRT):
iptables -t nat -I PREROUTING -p ipencap -d <GW Public IP> -j DNAT --to-destination <GW LAN IP>
iptables -t filter -I FORWARD -p ipencap -d <GW LAN IP> -j ACCEPT
**Command for Dynamic IP - (WAN is vlan1 in DD-WRT in OpenWRT it is usually eth0.1):
iptables -t nat -I PREROUTING -p ipencap -i vlan1 -j DNAT --to-destination <GW LAN IP>
iptables -t filter -I FORWARD -p ipencap -d <GW LAN IP> -j ACCEPT
73,
Lynwood
KB3VWG
Hello Brian and fellow amprnet friends.
First, let me introduce myself, I am Gabriel Medinas YV5KXE from Caracas,
Venezuela, working in the past time with the last one Venezuela amprnet
coordinator YV5CIV that is away of the activity. I work amprnet for about
20 years, in the last years the activity in my country is down with the
packet radio mode, but a group of YV-YY want rise it again. I maintain
operative the last packet radio gateway (yv5kxe.org) with VHF 145.010 YVNET
working together with APRS, in this month Brian Kantor let me the
responsability of the Amprnet Local Coordinator of 44.152.x.x Venezuela
network, I glad to share this with my friends in amprnet of many years, now
in the coordination position.
In a first step, I mount a Linux amprnet JNOS gateway with N6ROE help
(thanks Kim).
The second step is work to find the way to re-start the amprnet here, the
idea of a new gateway with static IP or see the posibility to mount a
dynaIP tool or other.
I think (personal idea) this network may grow if our fellow ham radio may
have the possibility to use their ADSL (dynamic IP) home connections to
mount their NOS amprnet system, also we are study the ways to start first a
static IP gateway to server the others via AXUDP/AXIP connections.
Now Brian, with this comercial IP list see any of our old gateway IP (not
working now), please you may delete it to clean the gateway list to be a
real and accurate network, please to all gateways sysops, delete all
44.152.x.x routes to restart in clean mode.
Grettings all for your time and hope work together in more and operative
amprnet network!
73 de Gabriel YV5KXE
AMPR Net IP Address Coordinator - Venezuela
yv5kxe.orgyv5kxe.ampr.orgwww.gmedinas.com
Message: 1
Date: Tue, 7 Jan 2014 12:32:50 -0800
From: Brian Kantor <Brian(a)UCSD.Edu>
To: 44net(a)hamradio.ucsd.edu
Subject: [44net] gateways cleanup/deletion
Message-ID: <20140107203249.GA8539(a)UCSD.Edu>
Content-Type: text/plain; charset=us-ascii
A while back I published a list of unclaimed gateways (those with no known
owner/operator). Some small number of those were subsequently claimed
and have been associated with their registered owner in the portal.
However, there remain some 91 gateways whose owner/operator remains
unknown. I intend to delete these gateways from the encap/gateways file
around the end of the month.
So in effect, this is the last chance for people operating these gateways
to get them properly registered before they go away.
If you find your gateway on this list, be sure you are personally
registered with the portal and SEND ME AN EMAIL to get the gateway
associated with your callsign in the portal.
Thank you all!
- Brian
In order by commercial IP address:
8.22.205.37
12.195.50.128
24.55.199.25
24.84.205.232
24.89.203.65
24.137.76.29
24.224.157.206
50.79.209.150
64.22.214.233
64.119.33.202
64.119.42.138
64.255.99.17
65.41.209.137
65.48.61.133
65.70.212.35
66.11.68.11
66.112.51.126
66.114.139.158
67.108.91.190
68.61.222.68
68.209.144.3
69.69.168.201
69.145.172.163
69.254.106.173
71.36.92.66
71.107.40.238
71.107.40.238
71.201.92.148
74.85.194.5
75.21.234.175
76.14.161.185
76.64.80.228
76.247.140.206
76.253.114.92
77.249.108.97
79.116.75.255
80.59.234.233
81.235.253.122
84.92.153.154
90.206.95.108
91.84.215.75
94.72.251.181
94.172.232.113
96.20.43.106
96.35.76.41
98.193.215.29
98.208.81.22
99.88.77.66
99.116.194.13
108.185.66.208
113.212.169.28
122.108.78.111
130.208.168.63
141.85.43.57
146.48.126.26
146.48.126.28
148.223.34.6
150.188.8.195
152.66.0.109
155.207.19.57
158.42.128.200
161.53.16.179
168.96.128.17
173.14.57.181
184.175.46.166
186.125.37.47
189.42.190.50
190.31.163.55
190.139.56.180
193.22.2.254
194.27.119.2
195.22.112.28
195.66.148.106
195.113.115.135
198.108.247.220
200.17.207.2
200.46.129.3
201.252.37.40
202.63.57.97
206.251.38.99
207.111.203.194
207.179.123.166
208.74.106.137
208.94.114.29
208.115.126.75
212.159.74.68
212.159.102.156
216.144.222.182
216.253.203.30
220.157.89.84
220.233.86.207
------------------------------