23 Aug
2018
23 Aug
'18
4:37 p.m.
Would you be interested in using OpenWrt on the EdgeRouter instead?
https://wiki.openwrt.org/toh/ubiquiti/ubiquiti_edgerouter_x_er-x_ka
There is a manual to setup using OpenWrt.
http://wiki.ampr.org/wiki/Setting_up_a_gateway_on_OpenWRT
- Lynwood
KB3VWG
4 Sep
4 Sep
7:58 p.m.
New subject: Trying to get set back up
https://www.qsl.net/kb9mwr/wapr/tcpip/ampr-ripd.html
Is this site still valid?
Specifically this? In the 'new way of things' will I still see traffic
from amprgw.ucsd.edu?
tcpdump -i enp3s0 -vvv host amprgw.ucsd.edu or ip proto \\icmp
Because I'm not seeing anything here from amprgw. Though I'm just monkeying with
it the first time now, so could just be 'new user stupid'
ifconfig tunl0 up 44.4.28.50 netmask 255.255.255.255
ip rule add to 44.4.28.50 table main priority 44
ip rule add dev tunl0 table 44 priority 45
ip rule add dev enp3s0 table 44 priority 46
ip rule add from 44.4.28.50 table 44 priority 47
9:08 p.m.
New subject: Trying to get set back up
All your entries on the portal appear to be correct, and
amprgw can ping your gateway's commercial IP address, so
you should be seeing IPIP traffic at least every 5 minutes.
Depending on your connection equipment, IPIP may not make
it through a DSL or cable modem without a bit of reconfiguration.
Check the web page at n1uro.ampr.org for more info on this,
under Linux conf->DMZ..
- Brian
On Tue, Sep 04, 2018 at 04:58:52PM -0700, Cathryn Mataga wrote:
https://www.qsl.net/kb9mwr/wapr/tcpip/ampr-ripd.html
Is this site still valid?
Specifically this? In the 'new way of things' will I still see traffic
from amprgw.ucsd.edu?
tcpdump -i enp3s0 -vvv host amprgw.ucsd.edu or ip proto \\icmp
Because I'm not seeing anything here from amprgw. Though I'm just monkeying with
it the first time now, so could just be 'new user stupid'
ifconfig tunl0 up 44.4.28.50 netmask 255.255.255.255
ip rule add to 44.4.28.50 table main priority 44
ip rule add dev tunl0 table 44 priority 45
ip rule add dev enp3s0 table 44 priority 46
ip rule add from 44.4.28.50 table 44 priority 47
5 Sep
5 Sep
1:15 a.m.
New subject: Trying to get set back up
As Brian suggested;
Connect something directly to your cable or DSL modem. And enable DMZ
to its address. Or bridge mode if that fails. And then run that
tcpdump command. I always suggest this as a first thing for; new
customer premise equipment, or first time trying to set up a gateway.
Once you know your modem is passing the traffic from ucsd, then you
can work out to more complex setups. Perhaps I'm work that into my
documentation.
Steve, KB9MWR
On Tue, Sep 4, 2018 at 6:58 PM, Cathryn Mataga <cathryn(a)junglevision.com> wrote:
https://www.qsl.net/kb9mwr/wapr/tcpip/ampr-ripd.html
Is this site still valid?
Specifically this? In the 'new way of things' will I still see traffic
from amprgw.ucsd.edu?
tcpdump -i enp3s0 -vvv host amprgw.ucsd.edu or ip proto \\icmp
Because I'm not seeing anything here from amprgw. Though I'm just monkeying
with it the first time now, so could just be 'new user stupid'
ifconfig tunl0 up 44.4.28.50 netmask 255.255.255.255
ip rule add to 44.4.28.50 table main priority 44
ip rule add dev tunl0 table 44 priority 45
ip rule add dev enp3s0 table 44 priority 46
ip rule add from 44.4.28.50 table 44 priority 47
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
8:17 p.m.
New subject: Trying to get set back up
Hello Cathryn,
Your AMPR IP has valid DNS details so you should be receiving ampr-rip
broadcasts:
--
$ host 44.4.28.50
50.28.4.44.in-addr.arpa domain name pointer vhf.ke6i.ampr.org.
--
To test if your ISP is forwarding you the IPIP packets, you can try
doing this on a Unix host directly connected to your ISP provided device
(cablemodem, DSL modem, etc):
#Assuming eth0 is your uplink port
tcpdump -nni eth0 proto 4
While tcpdump is running, open up a web browser to
http://yo2tm.ampr.org/nettools.php
using your standard Internet connection and enter in your active AMPR IP
address (not
subnet) and click on "IPv4 ping". You should see something like the
following on the
tcpdump screen:
--
13:12:15.876817 IP 89.122.215.236 > 96.78.144.186: IP 44.182.21.1 >
44.4.10.40: ICMP echo request, id 37699, seq 1, length 64 (ipip-proto-4)
13:12:15.877272 IP 96.78.144.186 > 89.122.215.236: IP 44.4.10.40 >
44.182.21.1: ICMP echo reply, id 37699, seq 1, length 64 (ipip-proto-4)
13:12:16.876362 IP 89.122.215.236 > 96.78.144.186: IP 44.182.21.1 >
44.4.10.40: ICMP echo request, id 37699, seq 2, length 64 (ipip-proto-4)
13:12:16.876788 IP 96.78.144.186 > 89.122.215.236: IP 44.4.10.40 >
44.182.21.1: ICMP echo reply, id 37699, seq 2, length 64 (ipip-proto-4)
13:12:17.876889 IP 89.122.215.236 > 96.78.144.186: IP 44.182.21.1 >
44.4.10.40: ICMP echo request, id 37699, seq 3, length 64 (ipip-proto-4)
--
--David
KI6ZHD
6 Sep
6 Sep
7 p.m.
New subject: Trying to get set back up
Thanks guys, after a little fussing I think I got it working. I do see
/var/lib/ampr-ripd/encap.txt filling full of routes, so I think that
that means it's functioning correctly.
https://vhf.ke6i.ampr.org
This is what I have now. I post this so you if anyone spots anything
stupid, they can let me know.
sysctl -w net.ipv4.ip_forward=1
modprobe ipip
ip addr add 44.4.28.50/32 dev tunl0
ip tunnel change ttl 64 mode ipip tunl0
ip link set dev tunl0 up
ifconfig tunl0 mtu 1480
ip rule add from 44.4.28.50/32 table 44 priority 45
ip rule add to 44.0.0.0/8 table 44 priority 44
ip route add default dev tunl0 via 169.228.34.84 onlink table 44
ip route add 44.4.28.50/32 dev tunl0 table 44
ip route add 44.0.0.0/8 via 44.4.28.50 dev tunl0
iptables -A INPUT -p 4 -j ACCEPT
iptables -A INPUT -p udp --dport 520 -j ACCEPT
ampr-ripd -s -r -t 44 -i tunl0 -a 44.4.28.50/32
On 9/5/2018 5:17 PM, David Ranch wrote:
>
> Hello Cathryn,
>
> Your AMPR IP has valid DNS details so you should be receiving ampr-rip
> broadcasts:
> --
> $ host 44.4.28.50
> 50.28.4.44.in-addr.arpa domain name pointer vhf.ke6i.ampr.org.
> --
>
>
> To test if your ISP is forwarding you the IPIP packets, you can try
> doing this on a Unix host directly connected to your ISP provided
> device (cablemodem, DSL modem, etc):
>
> #Assuming eth0 is your uplink port
> tcpdump -nni eth0 proto 4
>
> While tcpdump is running, open up a web browser to
> http://yo2tm.ampr.org/nettools.php
> using your standard Internet connection and enter in your active AMPR
> IP address (not
> subnet) and click on "IPv4 ping". You should see something like the
> following on the
> tcpdump screen:
> --
> 13:12:15.876817 IP 89.122.215.236 > 96.78.144.186: IP 44.182.21.1 >
> 44.4.10.40: ICMP echo request, id 37699, seq 1, length 64 (ipip-proto-4)
> 13:12:15.877272 IP 96.78.144.186 > 89.122.215.236: IP 44.4.10.40 >
> 44.182.21.1: ICMP echo reply, id 37699, seq 1, length 64 (ipip-proto-4)
> 13:12:16.876362 IP 89.122.215.236 > 96.78.144.186: IP 44.182.21.1 >
> 44.4.10.40: ICMP echo request, id 37699, seq 2, length 64 (ipip-proto-4)
> 13:12:16.876788 IP 96.78.144.186 > 89.122.215.236: IP 44.4.10.40 >
> 44.182.21.1: ICMP echo reply, id 37699, seq 2, length 64 (ipip-proto-4)
> 13:12:17.876889 IP 89.122.215.236 > 96.78.144.186: IP 44.182.21.1 >
> 44.4.10.40: ICMP echo request, id 37699, seq 3, length 64 (ipip-proto-4)
> --
>
> --David
> KI6ZHD
>
7 Sep
7 Sep
2:38 a.m.
New subject: Trying to get set back up
Well done
ICMP Echo request sent to: 44.4.28.50
ICMP Echo reply received from: 44.4.28.50
Ping completed in: 167ms (ttl=64)
Paul g4apl/gb7cip
2267
days inactive
2282
days old
6 comments
6 participants
participants (6)
-
Brian Kantor -
Cathryn Mataga -
David Ranch -
lleachii＠aol.com -
Paul -
Steve L