Hi Everyone,
I was running a JNOS BBS a few months ago and I was able to connect to other nodes on the 44net. I had to take JNOS offline for a few months while some changes to the network were made. No changes were made to the JNOS node, though. The gateway IP did change and it was updated on the AMPR gateway. I have brought the JNOS back up, but now I am not able to ping any 44net node. I am able to ping other servers like google.com.
I performed a packet capture and I see that the ICMP request is being sent from JNOS, but the ICMP response is not being received.
jnos> ping 44.135.92.10
jnos> Resolving 44.135.92.10...
jnos>
jnos>
jnos> ping google.com
jnos> Resolving google.com... 172.217.14.110: rtt 21
It is the same story with other nodes as well.
Any recommendations?
73, de KG7UJH Christopher Kelley
Did your IP change because it is dynamic, or did you change ISP ? And do you still have the same ISP router? I don't see your callsign in the portal gatways list. Which entry is yours?
Rob
On 8/5/21 3:33 PM, CJ Kelley via 44Net wrote:
Hi Everyone,
I was running a JNOS BBS a few months ago and I was able to connect to other nodes on the 44net. I had to take JNOS offline for a few months while some changes to the network were made. No changes were made to the JNOS node, though. The gateway IP did change and it was updated on the AMPR gateway. I have brought the JNOS back up, but now I am not able to ping any 44net node. I am able to ping other servers like google.com.
Christopher,
What is your ip address? And, are you on the ipip network?
FWIW, from northern NJ
$ ping 44.135.92.10 PING 44.135.92.10 (44.135.92.10) 56(84) bytes of data. 64 bytes from 44.135.92.10: icmp_seq=1 ttl=61 time=38.4 ms 64 bytes from 44.135.92.10: icmp_seq=2 ttl=61 time=40.3 ms 64 bytes from 44.135.92.10: icmp_seq=3 ttl=61 time=33.9 ms 64 bytes from 44.135.92.10: icmp_seq=4 ttl=61 time=36.1 ms
73, Mark
On 8/5/21 9:33 AM, CJ Kelley wrote:
Hi Everyone,
I was running a JNOS BBS a few months ago and I was able to connect to other nodes on the 44net. I had to take JNOS offline for a few months while some changes to the network were made. No changes were made to the JNOS node, though. The gateway IP did change and it was updated on the AMPR gateway. I have brought the JNOS back up, but now I am not able to ping any 44net node. I am able to ping other servers like google.com.
I performed a packet capture and I see that the ICMP request is being sent from JNOS, but the ICMP response is not being received.
jnos> ping 44.135.92.10
jnos> Resolving 44.135.92.10...
jnos>
jnos>
jnos> ping google.com
jnos> Resolving google.com... 172.217.14.110: rtt 21
It is the same story with other nodes as well.
Any recommendations?
73, de KG7UJH Christopher Kelley
Getting back to the discussion of improvement to AMPRnet, a minimal test script is needed so that people like Christopher can know what ip addresses *are* active.
Without that list, is it my end in trouble? is the intervening connectivity in trouble? or is the far end simply off the air or down?
Eliminating one of those 3 unknowns is a great start to troubleshooting connectivity issues.
Mark, N2MH
On 8/5/21 9:33 AM, CJ Kelley wrote:
Hi Everyone,
I was running a JNOS BBS a few months ago and I was able to connect to other nodes on the 44net. I had to take JNOS offline for a few months while some changes to the network were made. No changes were made to the JNOS node, though. The gateway IP did change and it was updated on the AMPR gateway. I have brought the JNOS back up, but now I am not able to ping any 44net node. I am able to ping other servers like google.com.
I performed a packet capture and I see that the ICMP request is being sent from JNOS, but the ICMP response is not being received.
jnos> ping 44.135.92.10
jnos> Resolving 44.135.92.10...
jnos>
jnos>
jnos> ping google.com
jnos> Resolving google.com... 172.217.14.110: rtt 21
It is the same story with other nodes as well.
Any recommendations?
73, de KG7UJH Christopher Kelley
Hello Christopher,
Just like you I want to start a JNOS BBS, do you have a tutorial or any other documentation/link on it? Hope your problem was resolved. Thanks in advance for your help.
73 de Davy - F4TQP
-----Message d'origine----- De : 44Net [mailto:44net-bounces+zagg=nirvanet.org@mailman.ampr.org] De la part de CJ Kelley via 44Net Envoyé : jeudi 5 août 2021 15:33 À : 44Net general discussion 44net@mailman.ampr.org Cc : CJ Kelley debiani386@gmail.com Objet : [44net] Unable to ping any nodes
Hi Everyone,
I was running a JNOS BBS a few months ago and I was able to connect to other nodes on the 44net. I had to take JNOS offline for a few months while some changes to the network were made. No changes were made to the JNOS node, though. The gateway IP did change and it was updated on the AMPR gateway. I have brought the JNOS back up, but now I am not able to ping any 44net node. I am able to ping other servers like google.com.
I performed a packet capture and I see that the ICMP request is being sent from JNOS, but the ICMP response is not being received.
jnos> ping 44.135.92.10
jnos> Resolving 44.135.92.10...
jnos>
jnos>
jnos> ping google.com
jnos> Resolving google.com... 172.217.14.110: rtt 21
It is the same story with other nodes as well.
Any recommendations?
73, de KG7UJH Christopher Kelley _________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
https://www.langelaar.net/jnos2/
Above is the site of Maiko VE4KLM, the maintainer of jnos. There is a mailing list called, nos-bbs. (See tapr.org for how to subscribe)
Sorry to hijack the thread.
Bob
On 2021-08-06 04:38, Zagg via 44Net wrote:
Hello Christopher,
Just like you I want to start a JNOS BBS, do you have a tutorial or any other documentation/link on it? Hope your problem was resolved. Thanks in advance for your help.
73 de Davy - F4TQP
Did your IP change because it is dynamic, or did you change ISP ?
It is a static IP. It changed because we decided to use the original IP for
another purpose. We got the new IP a bit later and decided to use that for 44-net activity.
And do you still have the same ISP router?
We are still with the same ISP and it is still the same router. No changes
other than the IP.
I don't see your callsign in the portal gatways list. Which entry is yours?
I am working with KC7KNE - he owns the JNOS PC and the network it is on.
I administer the JNOS system.
What is your ip address? And, are you on the ipip network?
The IP is 44.124.1.18 and I am on IPIP
73, de KG7UJH
On Fri, Aug 6, 2021 at 3:45 AM Boudewijn (Bob) Tenty via 44Net < 44net@mailman.ampr.org> wrote:
https://www.langelaar.net/jnos2/
Above is the site of Maiko VE4KLM, the maintainer of jnos. There is a mailing list called, nos-bbs. (See tapr.org for how to subscribe)
Sorry to hijack the thread.
Bob
On 2021-08-06 04:38, Zagg via 44Net wrote:
Hello Christopher,
Just like you I want to start a JNOS BBS, do you have a tutorial or any other documentation/link on it? Hope your problem was resolved. Thanks in advance for your help.
73 de Davy - F4TQP
-- There is nothing permanent except change
-Heraclitus
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
Is there anything else that I am missing here? I am still not able to ping any 44net nodes from within jnos.
Is there any more information I can provide that would be helpful here?
de KG7UJH Christopher Kelley
Sent with ProtonMail Secure Email.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Friday, August 6th, 2021 at 4:11 AM, CJ Kelley via 44Net 44net@mailman.ampr.org wrote:
Did your IP change because it is dynamic, or did you change ISP ?
It is a static IP. It changed because we decided to use the original IP for
another purpose. We got the new IP a bit later and decided to use that for
44-net activity.
And do you still have the same ISP router?
We are still with the same ISP and it is still the same router. No changes
other than the IP.
I don't see your callsign in the portal gatways list. Which entry is yours?
I am working with KC7KNE - he owns the JNOS PC and the network it is on.
I administer the JNOS system.
What is your ip address? And, are you on the ipip network?
The IP is 44.124.1.18 and I am on IPIP
73, de KG7UJH
On Fri, Aug 6, 2021 at 3:45 AM Boudewijn (Bob) Tenty via 44Net <
44net@mailman.ampr.org> wrote:
https://www.langelaar.net/jnos2/
Above is the site of Maiko VE4KLM, the maintainer of jnos.
There is a mailing list called, nos-bbs. (See tapr.org for how to
subscribe)
Sorry to hijack the thread.
Bob
On 2021-08-06 04:38, Zagg via 44Net wrote:
Hello Christopher,
Just like you I want to start a JNOS BBS, do you have a tutorial or any
other documentation/link on it?
Hope your problem was resolved.
Thanks in advance for your help.
73 de Davy - F4TQP
--
There is nothing permanent except change
-Heraclitus
44Net mailing list
44Net@mailman.ampr.org
44Net mailing list
44Net@mailman.ampr.org
Monitor with tcpdump in Linux to see what happens, like or it is leaving the right interface as IPIP packet, responses, etc.
Bob VE3TOK
On 2021-08-12 07:09, debiani386 via 44Net wrote:
Is there anything else that I am missing here? I am still not able to ping any 44net nodes from within jnos.
Is there any more information I can provide that would be helpful here?
de KG7UJH Christopher Kelley
Sent with ProtonMail Secure Email.
I ran tcpdump on both the tun0 interface on the Linux host and the ethernet interface. Here are my findings:
tun0:
jnos@jnos:~$ tcpdump -ttttnnr tun0.pcap reading from file tun0.pcap, link-type RAW (Raw IP) 2021-08-03 07:20:59.480853 IP 192.168.3.2 > 70.30.145.159: IP 44.124.1.18 > 44.135.92.10: ICMP echo request, id 132, seq 0, length 12 (ipip-proto-4) jnos@jnos:~$
enp0s3 (ethernet interface):
tcpdump -ttttnnr enp0s3.pcap reading from file enp0s3.pcap, link-type EN10MB (Ethernet) 2021-08-03 07:27:07.539858 IP 192.168.2.109.22 > 68.230.83.177.52286: Flags [P.], seq 960163137:960163181, ack 1484797025, win 501, options [nop,nop,TS val 2519792167 ecr 101725450$ 2021-08-03 07:27:07.540185 IP 192.168.2.109.22 > 68.230.83.177.52286: Flags [P.], seq 44:152, ack 1, win 501, options [nop,nop,TS val 2519792168 ecr 1017254502], length 108 2021-08-03 07:27:07.540474 IP 192.168.2.109.22 > 68.230.83.177.52286: Flags [P.], seq 152:188, ack 1, win 501, options [nop,nop,TS val 2519792168 ecr 1017254502], length 36 2021-08-03 07:27:07.545856 IP 68.230.83.177.52286 > 192.168.2.109.22: Flags [.], ack 0, win 4094, options [nop,nop,TS val 1017254529 ecr 2519792149], length 0 2021-08-03 07:27:07.563693 IP 68.230.83.177.52286 > 192.168.2.109.22: Flags [.], ack 44, win 4094, options [nop,nop,TS val 1017254544 ecr 2519792167], length 0 2021-08-03 07:27:07.569058 IP 68.230.83.177.52286 > 192.168.2.109.22: Flags [.], ack 152, win 4092, options [nop,nop,TS val 1017254548 ecr 2519792168], length 0 2021-08-03 07:27:07.569074 IP 68.230.83.177.52286 > 192.168.2.109.22: Flags [.], ack 188, win 4094, options [nop,nop,TS val 1017254548 ecr 2519792168], length 0 2021-08-03 07:27:09.924559 IP 68.230.83.177.52388 > 192.168.2.109.22: Flags [P.], seq 3618295632:3618295668, ack 3618018734, win 4096, options [nop,nop,TS val 1017256892 ecr 251978$ 2021-08-03 07:27:09.925664 IP 192.168.2.109.22 > 68.230.83.177.52388: Flags [P.], seq 1:237, ack 36, win 501, options [nop,nop,TS val 2519794553 ecr 1017256892], length 236 2021-08-03 07:27:09.946944 IP 68.230.83.177.52388 > 192.168.2.109.22: Flags [.], ack 237, win 4088, options [nop,nop,TS val 1017256916 ecr 2519794553], length 0 2021-08-03 07:27:10.692162 IP 68.230.83.177.52388 > 192.168.2.109.22: Flags [P.], seq 36:80, ack 237, win 4096, options [nop,nop,TS val 1017257656 ecr 2519794553], length 44 2021-08-03 07:27:10.692776 IP 192.168.2.109.22 > 68.230.83.177.52388: Flags [P.], seq 237:313, ack 80, win 501, options [nop,nop,TS val 2519795320 ecr 1017257656], length 76 2021-08-03 07:27:10.711861 IP 68.230.83.177.52388 > 192.168.2.109.22: Flags [.], ack 313, win 4093, options [nop,nop,TS val 1017257678 ecr 2519795320], length 0 2021-08-03 07:27:11.183381 IP 68.230.83.177.52388 > 192.168.2.109.22: Flags [P.], seq 80:116, ack 313, win 4096, options [nop,nop,TS val 1017258142 ecr 2519795320], length 36 2021-08-03 07:27:11.184038 IP 192.168.2.109 > 70.30.145.159: IP 44.124.1.18 > 44.135.92.10: ICMP echo request, id 132, seq 0, length 12 (ipip-proto-4) 2021-08-03 07:27:11.184639 IP 192.168.2.109.22 > 68.230.83.177.52388: Flags [P.], seq 313:573, ack 116, win 501, options [nop,nop,TS val 2519795812 ecr 1017258142], length 260 2021-08-03 07:27:11.210903 IP 68.230.83.177.52388 > 192.168.2.109.22: Flags [.], ack 573, win 4087, options [nop,nop,TS val 1017258167 ecr 2519795812], length 0 jnos@jnos:~$
I sampled 44.135.92.10 and I can see the ICMP request goes out the tun0 and the enp3s0 interface. My iptables NAT is set to allow all traffic:
Chain POSTROUTING (policy ACCEPT) target prot opt source destination MASQUERADE all -- anywhere anywhere jnos@jnos:~$
Sent with ProtonMail Secure Email.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Thursday, August 12th, 2021 at 11:48 PM, Boudewijn (Bob) Tenty via 44Net 44net@mailman.ampr.org wrote:
Monitor with tcpdump in Linux to see what happens, like or it is leaving the right interface as IPIP packet,
responses, etc.
Bob VE3TOK
On 2021-08-12 07:09, debiani386 via 44Net wrote:
Is there anything else that I am missing here? I am still not able to ping any 44net nodes from within jnos.
Is there any more information I can provide that would be helpful here?
de KG7UJH
Christopher Kelley
Sent with ProtonMail Secure Email.
44Net mailing list
44Net@mailman.ampr.org
-
Boudewijn (Bob) Tenty -
CJ Kelley -
debiani386 -
Mark Herson, N2MH -
Rob PE1CHL -
Zagg