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
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>
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?/
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
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
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
I have not played with NOS and JNOS in years. I would like to use some
of my 44 network address again. I see that a lot of the
IRIP, Allstar Dstar etc are using 44 for stations, reflectors and so on.
I purchased an Ubiquiti Networks ER-10X as a tunnel to the 44 network.
Is there anyone that has done this already?? Anyone would like to be
an Elmer to me in helping get this setup up and running??
Angelo Glorioso / N5UXT gw.n5uxt.ampr.org ( still there )
To learn the routing protocol, I created an Amazon EC2 instance of a Linux
Ubuntu router inside a virtual private cloud (VPC) where I have full
control over IP and can open 0.0.0.0/0 in both directions over all
protocols (EC2 without a VPC only permits TCP/UDP/ICMP access control).
When I run the daemon in verbose mode it is stuck calling home:
ubuntu@ip-192-168-44-12:~$ sudo ampr-ripd -d -v -L KZ0FOX@EM89mx
Using metric 0 for routes.
Using TCP window 840 for routes.
Using gateway 192.168.44.1 for direct 44net endpoints via interface eth0.
Calling home
Waiting for RIPv2 broadcasts...
Calling home
Calling home
Calling home
This system is online in the portal as 3.135.62.22 (
ec2-3-135-62-22.us-east-2.compute.amazonaws.com) and subnet 44.76.0.12/32.
Setting up a reference implementation like this one may be good for
learning the basic premise and ability to test out a configuration with
less variables than one may have at home with an ISP.
I welcome any constructive comments or suggestions.
Best regards,
Stephen Thomas
Very sad news. I was talking to him just the other day. What a shock. My condolences to his family and those close to him. As busy as I imagine he must have been, he always had time to help.
Roger
VA7LBB
> On Nov 23, 2019, at 12:00, 44net-request(a)mailman.ampr.org wrote:
>
> Send 44Net mailing list submissions to
> 44net(a)mailman.ampr.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://mailman.ampr.org/mailman/listinfo/44net
> or, via email, send a message with subject or body 'help' to
> 44net-request(a)mailman.ampr.org
>
> You can reach the person managing the list at
> 44net-owner(a)mailman.ampr.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of 44Net digest..."
> Today's Topics:
>
> 1. Brian Kantor, WB6CYT, SK (Phil Karn)
> 2. Re: Brian Kantor, WB6CYT, SK (vk2tv)
> 3. Re: Brian Kantor, WB6CYT, SK (Donald Jacob)
> 4. Re: Brian Kantor, WB6CYT, SK (Doug)
> 5. Re: Brian Kantor, WB6CYT, SK (John Ricketts)
> 6. Re: Brian Kantor, WB6CYT, SK (Fortney, Jim - K6IYK)
> 7. Brian Kantor, WB6CYT, SK (Brian)
> 8. Re: Brian Kantor, WB6CYT, SK (vk4aa(a)vk4aa.com.au)
> 9. Re: Brian Kantor, WB6CYT, SK (Albert Lawson)
> 10. Re: Brian Kantor, WB6CYT, SK (pete M)
> 11. Re: [44ngn] Brian Kantor, WB6CYT, SK (Marius Petrescu)
> 12. Brian Kantor, WB6CYT, SK (Paul)
> 13. Re: Brian Kantor, WB6CYT, SK (Tony Langdon)
> 14. Re: Brian Kantor, WB6CYT, SK (Tommy Chen)
> 15. Re: Brian Kantor, WB6CYT, SK (Tim Po??r)
> <mime-attachment>
> <mime-attachment>
> <mime-attachment>
> <mime-attachment>
> <mime-attachment>
> <mime-attachment>
> <mime-attachment>
> <mime-attachment>
> <mime-attachment>
> <mime-attachment>
> <mime-attachment>
> <mime-attachment>
> <mime-attachment>
> <mime-attachment>
> <mime-attachment>
> _______________________________________________
> 44Net mailing list
> 44Net(a)mailman.ampr.org
> https://mailman.ampr.org/mailman/listinfo/44net
