Good Morning Guys:
I have been working to get my chunk of .44 active for a little while now. I've become quite familiar with the concepts of how the network is set up etc.
That being said, no matter what I do I cannot seem to get the RIP password that is supposed to be broadcasted from 44.0.0.1. I have go as far as to monitor, log, and filter every packet coming in the cable modem from anything AMPRNet to verify it is arriving. It just seems like the packet is never making it to my public IP.
I've gone through all the basics - protocol 4(IPIP) forwarding, UDP port 520 forwarding etc. Like I said, I've even captured all packets pre firewall and I'm not seeing anything AMPRNet.
Is it possible that even though my gateway/public IP is registered, the packets aren't being sent out?
The last portion of getting this going is that elusive RIP pass.
Any suggestions?
Thanks,
Jason - KD4CBM '73
On Mon, Jun 06, 2016 at 07:49:45AM -0600, kd4cbm@charter.net wrote:
Is it possible that even though my gateway/public IP is registered, the packets aren't being sent out?
They are being sent. However, your public IP is returning a 'host unreachable' ICMP so apparently nothing is getting through to it:
07:15:03.233650 IP (tos 0xc0, ttl 46, id 19795, offset 0, flags [none], proto ICMP (1), length 576) 24.151.216.22 > 169.228.66.251: ICMP host 24.151.216.22 unreachable, length 556
I do not know why this is happening. - Brian
On Mon, 6 Jun 2016, Brian Kantor wrote:
(Please trim inclusions from previous messages) _______________________________________________ On Mon, Jun 06, 2016 at 07:49:45AM -0600, kd4cbm@charter.net wrote:
Is it possible that even though my gateway/public IP is registered, the packets aren't being sent out?
They are being sent. However, your public IP is returning a 'host unreachable' ICMP so apparently nothing is getting through to it:
07:15:03.233650 IP (tos 0xc0, ttl 46, id 19795, offset 0, flags [none], proto ICMP (1), length 576) 24.151.216.22 > 169.228.66.251: ICMP host 24.151.216.22 unreachable, length 556
I do not know why this is happening.
- Brian
I have a strong suspicion that my ISP (Charter Communications) has implemented some kind of filtering on my home cable-based (DOCSIS) internet connection. My reception of the RIP44d table broadcase has all but ceased. ip-ip tunnel communication to a friend's machine in a neighboring county only seems to work for a limited time, and only AFTER I initiate a connection from my end. It's as if they're using some kind of NAT or port knocking filter, and only opening the gate for incoming proto 4 traffic for a limited time after I initiate an outgoing request to a specific host.
With the FCCs declaration of the ISPs as 'Common Carriers' under the telecommunications laws, this and all other forms of port blocking or preferential traffic handling should have been eliminated. It's time again to make some noise in Washington.>
I've caught and reported Comcast for exact issues you mention... which stems from their faulty devices they're deliberately deploying (as per their admittance). There may be a work around but it'll cost you a few dollars perhaps. --- Pardon my brevity, I'm on a Samsung Galaxy smartphone. --- Sent via axMail-Fax by N1URO.
On June 6, 2016 11:44:15 AM Rick Green rtg@aapsc.com wrote:
(Please trim inclusions from previous messages) _______________________________________________ On Mon, 6 Jun 2016, Brian Kantor wrote:
(Please trim inclusions from previous messages) _______________________________________________ On Mon, Jun 06, 2016 at 07:49:45AM -0600, kd4cbm@charter.net wrote:
Is it possible that even though my gateway/public IP is registered, the packets aren't being sent out?
They are being sent. However, your public IP is returning a 'host unreachable' ICMP so apparently nothing is getting through to it:
07:15:03.233650 IP (tos 0xc0, ttl 46, id 19795, offset 0, flags [none], proto ICMP (1), length 576) 24.151.216.22 > 169.228.66.251: ICMP host 24.151.216.22 unreachable, length 556
I do not know why this is happening.
- Brian
I have a strong suspicion that my ISP (Charter Communications) has implemented some kind of filtering on my home cable-based (DOCSIS) internet connection. My reception of the RIP44d table broadcase has all but ceased. ip-ip tunnel communication to a friend's machine in a neighboring county only seems to work for a limited time, and only AFTER I initiate a connection from my end. It's as if they're using some kind of NAT or port knocking filter, and only opening the gate for incoming proto 4 traffic for a limited time after I initiate an outgoing request to a specific host.
With the FCCs declaration of the ISPs as 'Common Carriers' under the telecommunications laws, this and all other forms of port blocking or preferential traffic handling should have been eliminated. It's time again to make some noise in Washington.>
-- Rick Green, N8BJX
We, the People of the United States of America, reject the U.S. Supreme Court's Citizens United ruling, and move to amend our Constitution to firmly establish that money is not speech, and that human beings, not corporations, are persons entitled to constitutional rights.
http://www.MoveToAmend.org
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
-
Brian -
Brian Kantor -
kd4cbm＠charter.net -
Rick Green