44net

44net@mailman.ampr.org

1 participants
3194 discussions

Re: [44net] PKTerrors.
by lleachii＠aol.com 27 Jan '20

27 Jan '20

Bill, The crash truncated the IPs in the search; showing my IP. Forcing a dynamic IP change on WAN helped me realize my error. But now, I get ICMP unreachable messages in reply to my pings. root@OpenWrt:~# tcpdump -vv -i eth0.2 host 90.155.50.1 -ntcpdump: listening on eth0.2, link-type EN10MB (Ethernet), capture size 262144 bytes16:46:24.510501 IP (tos 0x0, ttl 64, id 36329, offset 0, flags [DF], proto IPIP (4), length 104) 138.88.77.109 > 90.155.50.1: IP (tos 0x0, ttl 64, id 64173, offset 0, flags [DF], proto ICMP (1), length 84) 44.60.44.1 > 44.131.170.1: ICMP echo request, id 8551, seq 0, length 6416:46:24.626840 IP (tos 0xc0, ttl 54, id 44297, offset 0, flags [none], proto ICMP (1), length 132) 90.155.50.1 > 138.88.77.109: ICMP 90.155.50.1 protocol 4 port 84 unreachable, length 112 IP (tos 0x0, ttl 56, id 36329, offset 0, flags [none], proto IPIP (4), length 104) 138.88.77.109 > 90.155.50.1: IP (tos 0x0, ttl 64, id 64173, offset 0, flags [DF], proto ICMP (1), length 84) 44.60.44.1 > 44.131.170.1: ICMP echo request, id 8551, seq 0, length 6416:46:25.510864 IP (tos 0x0, ttl 64, id 37129, offset 0, flags [DF], proto IPIP (4), length 104) 138.88.77.109 > 90.155.50.1: IP (tos 0x0, ttl 64, id 64530, offset 0, flags [DF], proto ICMP (1), length 84) 44.60.44.1 > 44.131.170.1: ICMP echo request, id 8551, seq 1, length 6416:46:25.614088 IP (tos 0xc0, ttl 54, id 44337, offset 0, flags [none], proto ICMP (1), length 132) 90.155.50.1 > 138.88.77.109: ICMP 90.155.50.1 protocol 4 port 84 unreachable, length 112 IP (tos 0x0, ttl 56, id 37129, offset 0, flags [none], proto IPIP (4), length 104) 138.88.77.109 > 90.155.50.1: IP (tos 0x0, ttl 64, id 64530, offset 0, flags [DF], proto ICMP (1), length 84) 44.60.44.1 > 44.131.170.1: ICMP echo request, id 8551, seq 1, length 6416:46:26.511170 IP (tos 0x0, ttl 64, id 37676, offset 0, flags [DF], proto IPIP (4), length 104) 138.88.77.109 > 90.155.50.1: IP (tos 0x0, ttl 64, id 64733, offset 0, flags [DF], proto ICMP (1), length 84) 44.60.44.1 > 44.131.170.1: ICMP echo request, id 8551, seq 2, length 6416:46:26.637354 IP (tos 0xc0, ttl 54, id 44392, offset 0, flags [none], proto ICMP (1), length 132) 90.155.50.1 > 138.88.77.109: ICMP 90.155.50.1 protocol 4 port 84 unreachable, length 112 IP (tos 0x0, ttl 56, id 37676, offset 0, flags [none], proto IPIP (4), length 104) 138.88.77.109 > 90.155.50.1: IP (tos 0x0, ttl 64, id 64733, offset 0, flags [DF], proto ICMP (1), length 84) 44.60.44.1 > 44.131.170.1: ICMP echo request, id 8551, seq 2, length 6416:46:27.511520 IP (tos 0x0, ttl 64, id 38445, offset 0, flags [DF], proto IPIP (4), length 104) 138.88.77.109 > 90.155.50.1: IP (tos 0x0, ttl 64, id 64775, offset 0, flags [DF], proto ICMP (1), length 84) 44.60.44.1 > 44.131.170.1: ICMP echo request, id 8551, seq 3, length 6416:46:27.617907 IP (tos 0xc0, ttl 54, id 44428, offset 0, flags [none], proto ICMP (1), length 132) 90.155.50.1 > 138.88.77.109: ICMP 90.155.50.1 protocol 4 port 84 unreachable, length 112 IP (tos 0x0, ttl 56, id 38445, offset 0, flags [none], proto IPIP (4), length 104) 138.88.77.109 > 90.155.50.1: IP (tos 0x0, ttl 64, id 64775, offset 0, flags [DF], proto ICMP (1), length 84) 44.60.44.1 > 44.131.170.1: ICMP echo request, id 8551, seq 3, length 64^C8 packets captured8 packets received by filter0 packets dropped by kernel - KB3VWG

1 1

PKTerrors.
by W.B.Hill 27 Jan '20

27 Jan '20

Hi, Just been looking through https://gw.ampr.org/private/pkterrors.txt and I noticed there's entries for the external IP for the net I run. I'm running 44.131.170.0/30 with a RaspberryPi on 44.131.170.1 using IPIP with amprd, external IP address 90.155.50.1 The errors are like: 90.155.50.1 51.89.173.198 2 [19] dropped: non-44 inner source address What does this mean? And I can't seem to ping to 44.131.170.1 from the big bad internet, is this related? Thanks. Bill (M1BKF)

4 8

Re: [44net] PKTerrors.
by lleachii＠aol.com 27 Jan '20

27 Jan '20

All, I'm able to ping all three of Steve's IPs from 44.60.44.0/24. - LynwoodKB3VWG

1 0

Re: [44net] PKTerrors.
by lleachii＠aol.com 27 Jan '20

27 Jan '20

Bill, Can you reach me now as well? root@OpenWrt:~# ping 44.131.170.1 -I 44.60.44.1PING 44.131.170.1 (44.131.170.1) from 44.60.44.1: 56 data bytes^C--- 44.131.170.1 ping statistics ---4 packets transmitted, 0 packets received, 100% packet loss I still receive no IPIP packets on my WAN from 90.155.50.1. I also ran "tcpdump -vv -i eth0.2 -n proto 4" - I see no replies from any IP. 44.60.44.144.60.44.254 73, - Lynwood KB3VWG

1 0

Re: [44net] PKTerrors.
by lleachii＠aol.com 26 Jan '20

26 Jan '20

Bill, That error means that you are encapsulating an IP that does not equal a 44 IP (e.g. you're improperly sending multicast, broadcast or your Public IP onto the tunnel). Ensure that you only send 44-net SRC IPs inside the tunnel. Also, any 44 IP that you want to reach the Internet must have a DNS entry in the AMPR.ORG and 44 reverse zones. That seems to be properly setup already: 1.170.131.44.in-addr.arpa name = m1bkf.ampr.org. --- I ping and receive no reply - this is a TCPDUMP of my tunnel: 21:23:10.793135 IP (tos 0x0, ttl 64, id 46020, offset 0, flags [DF], proto IPIP (4), length 104) 138.88.77.89 > 90.155.50.1: IP (tos 0x0, ttl 64, id 48759, offset 0, flags [DF], proto ICMP (1), length 84) 44.60.44.1 > 44.131.170.1: ICMP echo request, id 19216, seq 7, length 64 21:23:11.793459 IP (tos 0x0, ttl 64, id 46092, offset 0, flags [DF], proto IPIP (4), length 104) 138.88.77.89 > 90.155.50.1: IP (tos 0x0, ttl 64, id 48962, offset 0, flags [DF], proto ICMP (1), length 84) 44.60.44.1 > 44.131.170.1: ICMP echo request, id 19216, seq 8, length 64 21:23:12.793801 IP (tos 0x0, ttl 64, id 46294, offset 0, flags [DF], proto IPIP (4), length 104) 138.88.77.89 > 90.155.50.1: IP (tos 0x0, ttl 64, id 49447, offset 0, flags [DF], proto ICMP (1), length 84) 44.60.44.1 > 44.131.170.1: ICMP echo request, id 19216, seq 9, length 64 21:23:13.794158 IP (tos 0x0, ttl 64, id 46674, offset 0, flags [DF], proto IPIP (4), length 104) 138.88.77.89 > 90.155.50.1: IP (tos 0x0, ttl 64, id 49657, offset 0, flags [DF], proto ICMP (1), length 84) 44.60.44.1 > 44.131.170.1: ICMP echo request, id 19216, seq 10, length 64 21:23:14.794465 IP (tos 0x0, ttl 64, id 47472, offset 0, flags [DF], proto IPIP (4), length 104) 138.88.77.89 > 90.155.50.1: IP (tos 0x0, ttl 64, id 50140, offset 0, flags [DF], proto ICMP (1), length 84) 44.60.44.1 > 44.131.170.1: ICMP echo request, id 19216, seq 11, length 64 73, - Lynwood KB3VWG

4 9

Link(s)
by gm4upx＠gb7jd.co.uk 25 Jan '20

25 Jan '20

Hello Matt, You may by now have found a solution to your problem; I had a similar problem when setting up a remote node last week via a mobile phone sim card ( cell net phone ! ). I found I could not connect from the remote node until I removed the default entry in iptables and used ip rules to get a two way connection. Regards, Ian.. A totally in-experienced user <smile>

1 0

Help troubleshooting AXIP link
by VE3OY Matt 24 Jan '20

24 Jan '20

Hello 44Net. I'm looking for some help from those who have experience! I have recently set up my first AXIP link through the 44Net, but I'm having trouble connecting to my AXIP partner. My IP is 44.135.88.200 and my partner is 44.135.32.201 So far I can TELNET and PING back and forth from ANY 44 node, yet all attempts to make a AX25 connection to my AXIP partner fail. I can TELNET/PING from my partner to my node okay. I can TELNET/PING to my partner from my node okay. I can PING the 44 gateway without issue. I have also been broadcasting my NODES table to my partner. My partner does not seem to "hear" my CONN REQ's or NODES broadcasts. My partner is also broadcasting his NODES table to me. I am not hearing his broadcasts. Using TCPDUMP and WIRESHARK, I can see the traffic going out my tunnel to my regional gateway. I have tried to capture AX25 packets FROM my partner ... nothing heard. I have been able to capture AX25 packets TO my partner ... all looks correct. I have been able to capture packets when TELNETing or PINGing. TRACEROUTEs to my partner work fine (2 hops). My situation is a little more complex because I am not going direct to the UCSD gateway. Instead, I am sending all my 44Net traffic through my regional gateway (44.135.88.252). It has been suggested that my ISP may be "source filtering", but i have no way of verifying that. I am running both my router and node on a Raspberry Pi (I know ... plug your nose! LOL) I am using IPTABLES, which I have disabled for testing to see if it was interfering (it wasn't). My router/node is behind a CPE router, and is in the DMZ. I have several AX-UDP ports working fine. So here are my questions: Does it sound like I am suffering from source filtering? How can I verify whether my ISP is source filtering? What have I overlooked in my troubleshooting? What would you suggest as my next step? Any and all suggestions are welcome. I'm going bald quickly pulling out my hair! Thanks in advance, Matt VE3OY (FN03gq) Toronto, Canada -- /My mind is like a web browser. 27 tabs are open, 9 aren't responding, lots of pop-ups...and where is that annoying music coming from?/

1 0

Re: [44net] 44 compatible Routers
by lleachii＠aol.com 24 Jan '20

24 Jan '20

Angelo, You can search the archive; but everyone's been fairly diligent in adding configuration information for supported devices/NOSes and linking on the main Wiki page: http://wiki.ampr.org/wiki/Main_Page 73, - Lynwood KB3VWG

1 0

Re: [44net] Need TraceRoute from UCSD router
by lleachii＠aol.com 24 Jan '20

24 Jan '20

Charles and Quan, Please read Friday's email digest, the password was provided. Also, since you have an account in the portal...doesn't that mean you have a gateway? - Lynwood KB3VWG

1 0

Vultr BGP routing KO in Paris ?
by Toussaint OTTAVI 24 Jan '20

24 Jan '20

Hi all, Our subnet 44.190.11.0/24 does not seem to be reachable anymore from Internet. It's announced in BGP via a Vultr VPS located in Paris. I had notices from Vultr in the last few days about network upgrades. Currently, the route to our gateway 44.190.11.1 seems to be the default route via UCSD. I opened a support ticket. I know some of us are using Vultr. Do you encounter similar problems ? Thank you in advance, 73 de TK1BI

5 10

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

44net