44net

44net@mailman.ampr.org

2 participants
3205 discussions

Re: [44net] Comcast Xfinity Routing
by Brian Kantor 12 Jul '19

12 Jul '19

On Fri, Jul 12, 2019 at 02:27:15AM -0700, Nate Sales via 44Net wrote: > Date: Fri, 12 Jul 2019 02:27:15 -0700 > From: Nate Sales <nate.wsales(a)gmail.com> > To: AMPRNet working group <44net(a)mailman.ampr.org> > Subject: Comcast Xfinity Routing > > Hello, > I'm wondering if anyone here has had success with an IPIP gateway on > Xfinity by Comcast. I haven't had a lot of success with it, and I'm > wondering if even in "bridge" mode the CPE modem/router that they give you > is still blocking protocol 4. > 73, > KJ7DMC Nate: Whatever your current modem configuration is, it's blocking protocol 4 (IPIP). Specifically, a traceroute to your gateway, 157.230.161.245 using ordinary UDP traceroute succeeds. Doing the same thing with protocol 4 (IPIP) gets a "Protocol Unreachable" ICMP return from your gateway. Viz: # traceroute -n 157.230.161.245 traceroute to 157.230.161.245 (157.230.161.245), 64 hops max, 40 byte packets 1 169.228.34.82 0.575 ms 0.569 ms 0.561 ms 2 132.239.255.49 0.223 ms 0.206 ms 0.200 ms 3 132.239.254.162 0.247 ms 0.536 ms 0.235 ms 4 132.239.254.149 0.356 ms 0.393 ms 0.265 ms 5 137.164.23.57 2.871 ms 2.841 ms 2.740 ms 6 137.164.22.46 5.335 ms 137.164.11.2 5.129 ms 137.164.22.46 5.165 ms 7 4.35.156.65 4.972 ms 4.911 ms 4.968 ms 8 * * * 9 4.14.33.70 12.617 ms 19.749 ms 4.14.33.54 14.277 ms 10 * * * 11 * * * 12 157.230.161.245 13.960 ms 12.958 ms 14.074 ms ...and... # traceroute -n -P 4 157.230.161.245 traceroute to 157.230.161.245 (157.230.161.245), 64 hops max, 40 byte packets 1 169.228.34.82 0.613 ms 0.611 ms 0.577 ms 2 132.239.255.49 0.218 ms 0.197 ms 0.215 ms 3 132.239.254.162 0.363 ms 0.227 ms 0.224 ms 4 132.239.254.149 0.364 ms 0.258 ms 0.263 ms 5 137.164.23.57 3.111 ms 3.025 ms 3.108 ms 6 137.164.11.2 5.091 ms 5.122 ms 5.094 ms 7 4.35.156.65 5.219 ms 4.967 ms 4.974 ms 8 * * * 9 4.14.33.70 13.814 ms 13.901 ms 13.844 ms 10 * * * 11 * * * 12 157.230.161.245 14.829 ms !P 14.102 ms !P 13.926 ms !P - Brian

2 1

Re: [44net] Comcast Xfinity Routing
by Brian 12 Jul '19

12 Jul '19

Nate; On Fri, 2019-07-12 at 02:27 -0700, Nate Sales via 44Net wrote: > email message attachment (Comcast Xfinity Routing) > > I'm wondering if anyone here has had success with an IPIP gateway on > > Xfinity by Comcast. I haven't had a lot of success with it, and I'm > > wondering if even in "bridge" mode the CPE modem/router that they give you > > is still blocking protocol 4. I'm on Xfinity and it took me about 2 years to figure out what's going on with them and how to fix it. I wrote a white paper on the topic: https://uronode.n1uro.com/linux/amprcable.html It's a 44-net IP so if you can't see it let me know and I'll send you the text off-list. -- Rain is caused by big, high-pressure areas; cold fronts; warm, moist air; And the first day of your vacation. ----- 73 de Brian N1URO IPv6 Certified SMTP: n1uro-at-n1uro.ampr.org

1 0

Comcast Xfinity Routing
by Nate Sales 12 Jul '19

12 Jul '19

Hello, I'm wondering if anyone here has had success with an IPIP gateway on Xfinity by Comcast. I haven't had a lot of success with it, and I'm wondering if even in "bridge" mode the CPE modem/router that they give you is still blocking protocol 4. 73, KJ7DMC

1 0

Re: [44net] NPR kits for sale! (New Packet Radio)
by Brian 09 Jul '19

09 Jul '19

Pete; I wanted to set something up so I could but his mail server is blocking me. On Tue, 2019-07-09 at 18:28 +0000, pete M via 44Net wrote: > email message attachment (Re: [44net] NPR kits for sale! (New Packet > Radio)) > > -------- Forwarded Message -------- > > From: pete M <petem001(a)hotmail.com> > > To: AMPRNet working group <44net(a)mailman.ampr.org> > > Subject: Re: [44net] NPR kits for sale! (New Packet Radio) > > Date: Tue, 9 Jul 2019 18:28:38 +0000 > > > > When someone will distribute those in north america I am in line for 2! > > > > Tlcharger Outlook pour Android<https://aka.ms/ghei36> > > > > ________________________________ > > From: 44Net <44net-bounces+petem001=hotmail.com(a)mailman.ampr.org> on behalf of f4hdk <f4hdk(a)free.fr> > > Sent: Tuesday, July 9, 2019 1:28:54 PM > > To: 44net(a)mailman.ampr.org > > Subject: [44net] NPR kits for sale! (New Packet Radio) > > > > Hello, > > > > NPR kits (New Packet Radio) are now for sale from this German web-shop, > > currently shipping to Europe only (EU+EFTA). > > https://shop.thinkstack.de/en/ham-radio/20-new-packet-radio-npr.html > > > > If you have questions about this sale, please contact directly the > > web-shop : mailto:info@thinkstack.de > > > > If you want to sell NPR kits from another region (USA or other > > countries), please contact me directly. > > > > If you have technical questions, please ask me directly on this > > mailing-list. > > > > 73, > > Guillaume F4HDK > > _________________________________________ > > 44Net mailing list > > 44Net(a)mailman.ampr.org > > https://mailman.ampr.org/mailman/listinfo/44net > _________________________________________ > 44Net mailing list > 44Net(a)mailman.ampr.org > https://mailman.ampr.org/mailman/listinfo/44net -- Rain is caused by big, high-pressure areas; cold fronts; warm, moist air; And the first day of your vacation. ----- 73 de Brian N1URO IPv6 Certified SMTP: n1uro-at-n1uro.ampr.org

2 2

NPR kits for sale! (New Packet Radio)
by f4hdk 09 Jul '19

09 Jul '19

Hello, NPR kits (New Packet Radio) are now for sale from this German web-shop, currently shipping to Europe only (EU+EFTA). https://shop.thinkstack.de/en/ham-radio/20-new-packet-radio-npr.html If you have questions about this sale, please contact directly the web-shop : mailto:info@thinkstack.de If you want to sell NPR kits from another region (USA or other countries), please contact me directly. If you have technical questions, please ask me directly on this mailing-list. 73, Guillaume F4HDK

3 2

Re: [44net] Vultr.com - "Invalid BGP RPKI Entries"
by Brian Kantor 07 Jul '19

07 Jul '19

I have heard no other complaints nor has Vultr contacted me. It might have been helpful if you had specified WHICH 44 subnet(s) you think are having problems. - Brian On Sun, Jul 07, 2019 at 05:45:54PM -0400, Ty Bermea via 44Net wrote: > Date: Sun, 7 Jul 2019 17:45:54 -0400 > From: Ty Bermea <ty(a)tybermea.net> > To: AMPRNet working group <44net(a)mailman.ampr.org> > Subject: Re: [44net] Vultr.com - "Invalid BGP RPKI Entries" > > Has anyone else had trouble in the last few days with Vultr suddenly no > longer routing/announcing 44 subnets? > > On Tue, Jun 18, 2019 at 2:42 AM Toussaint OTTAVI <t.ottavi(a)bc-109.com> > wrote: > > > Hi, > > > > Le 17/06/2019 à 23:13, Brian Kantor a écrit : > > > If you are one of the 35 or so people who received a letter from > > > support(a)vultr.com informing you that there is a problem with your > > > subnet RPKI settings, feel free to ignore and discard it. > > > > Thank you for your action. It means we are 35+ using BGP at Vultr for > > $5/month. That's good news :-) > > > > 73 de TK1BI > > > > _________________________________________ > > 44Net mailing list > > 44Net(a)mailman.ampr.org > > https://mailman.ampr.org/mailman/listinfo/44net > > > _________________________________________ > 44Net mailing list > 44Net(a)mailman.ampr.org > https://mailman.ampr.org/mailman/listinfo/44net

2 3

Vultr.com - "Invalid BGP RPKI Entries"
by Brian Kantor 07 Jul '19

07 Jul '19

If you are one of the 35 or so people who received a letter from support(a)vultr.com informing you that there is a problem with your subnet RPKI settings, feel free to ignore and discard it. There is nothing wrong with your RPKI settings. In fact, most of you don't have any RPKI settings at all. Maybe someday. Vultr has a problem with their audit software which has been sending out false alarms. There appears to be no cause for concern. - Brian

3 2

Ping N1URO - PacComm email
by Nick G4IRX (44.131.x.x) 30 Jun '19

30 Jun '19

Brian N1URO - Have tried to reply to email you sent me about PacComm stuff a week ago but my reply has been returned undeliverable. If you are still interested, please contact me off-list with an alternative address? Thanks, Nick G4IRX

1 0

Re: [44net] Connecting to 44net
by Brian 30 Jun '19

30 Jun '19

Cathryn; I'm also on Comcast. To let you know in my 4 year battle with them, it took me contacting Cisco direct to find out what the problem was. They simply deploy broken CPE units to the end user by design. What's probably happening is that they disable certain menu functions which allows them to say they don't filter certain things, however the natural behavior of the CPE will still filter. There's 2 solutions available. You may read about them at: https://uronode.n1uro.com/linux/amprcable.html On Sat, 2019-06-29 at 10:51 -0700, Cathryn Mataga via 44Net wrote: > email message attachment (Re: [44net] Connecting to 44net) > > -------- Forwarded Message -------- > > From: Cathryn Mataga <cathryn(a)junglevision.com> > > To: Brian Kantor <Brian(a)bkantor.net>, AMPRNet working group > > <44net(a)mailman.ampr.org> > > Subject: Re: [44net] Connecting to 44net > > Date: Sat, 29 Jun 2019 10:51:06 -0700 > > > > Thanks, this is useful, though is grim news. Last time I talked to > > comcast, basically they had me reset power on my router, over and over, > > for an issue that had nothing to do with my router, until they sent me > > to another phone number that was disconnected. > > > > On 6/29/2019 10:38 AM, Brian Kantor wrote: > > > Cathryn, > > > > > > I see your ping requests arriving at 169.228.34.84 no problem, > > > and they are being encapsulated at sent to 50.79.209.150, again, > > > no problem. Nothing is coming back from 50.79.209.150. > > > > > > This suggests that something is filtering out protocol 4 (IPIP) > > > between 169.228.34.84 and 50.79.209.150. > > > > > > A traceroute from 169.228.34.84 to 50.79.209.150 using ordinary > > > UDP works, completing after 18 hops. The last few hops in that > > > path look like this: > > > > > > 14 162.151.87.226 12.097 ms 12.315 ms 12.088 ms > > > 15 162.151.79.134 12.735 ms 12.744 ms 12.773 ms > > > 16 68.87.227.122 13.080 ms 12.983 ms 12.920 ms > > > 17 * * * > > > 18 50.79.209.150 37.676 ms 42.664 ms 33.084 ms > > > > > > A traceroute from 169.228.34.84 to 50.79.209.150 using protocol 4 > > > (IPIP) does not complete, and there are no responses beyond hop > > > 15. The last few hops are: > > > > > > 12 68.86.84.150 11.117 ms 12.601 ms 12.734 ms > > > 13 68.86.94.154 11.761 ms 11.743 ms 11.340 ms > > > 14 162.151.87.226 12.469 ms 12.162 ms 12.392 ms > > > 15 162.151.79.134 12.757 ms 12.800 ms 12.797 ms > > > 16 * * * > > > 17 * * * > > > 18 * * * > > > > > > This suggests that hop 16, 68.87.227.122, is not accepting/passing > > > protocol 4 packets. The hostname for that host is > > > lag-2-240-acr07.pinole.ca.sfba.comcast.net. > > > > > > I hate to throw you to the wolves of comcast's customer service line, > > > but you may need to find out from them if they suddenly started filtering > > > out inbound IPIP packets at that router. > > > - Brian > > > > > > > > > On Sat, Jun 29, 2019 at 09:50:40AM -0700, Cathryn Mataga via 44Net wrote: > > >> Date: Sat, 29 Jun 2019 09:50:40 -0700 > > >> From: Cathryn Mataga <cathryn(a)junglevision.com> > > >> To: AMPRNet working group <44net(a)mailman.ampr.org> > > >> Subject: Connecting to 44net > > >> > > >> I'm not connected to 44net anymore, when I ping, to me at least, my > > >> outgoing packets look correct, but I get no response ever. > > >> > > >> I'm trying to put together as much as I can. My gateway ips 44.4.28.50 > > >> at 50.79.209.150, I have a static IP. > > >> > > >> I'm current on the portal, far as I can tell with no error messages. > > >> > > >> > > >> ping 44.0.0.1 > > >> PING 44.0.0.1 (44.0.0.1) 56(84) bytes of data. > > >> *no response ever > > >> > > >> I see the outgoing, but never the ping back. > > >> > > >> tcpdump -vv -i enp4s0 host 169.228.34.84 > > >> tcpdump: listening on enp4s0, link-type EN10MB (Ethernet), capture size > > >> 262144 bytes > > >> 09:39:25.982188 IP (tos 0x0, ttl 64, id 54479, offset 0, flags [DF], > > >> proto IPIP (4), length 104) > > >> hamradio.junglevision.com > amprgw.ucsd.edu: IP (tos 0x0, ttl 64, > > >> id 14161, offset 0, flags [DF], proto ICMP (1), length 84) > > >> ke6i.ampr.org > gw.ampr.org: ICMP echo request, id 25489, seq 105, > > >> length 64 > > >> 09:39:27.006173 IP (tos 0x0, ttl 64, id 54594, offset 0, flags [DF], > > >> proto IPIP (4), length 104) > > >> hamradio.junglevision.com > amprgw.ucsd.edu: IP (tos 0x0, ttl 64, > > >> id 15137, offset 0, flags [DF], proto ICMP (1), length 84) > > >> ke6i.ampr.org > gw.ampr.org: ICMP echo request, id 25489, seq 106, > > >> length 64 > > >> > > >> I occasionally see one of these, which hints to me that ipip is making > > >> it to my gateway. > > >> > > >> 09:39:15.386222 IP (tos 0x20, ttl 48, id 32657, offset 0, flags [none], > > >> proto IPIP (4), length 60) > > >> amprgw.ucsd.edu > hamradio.junglevision.com: IP (tos 0x0, ttl 237, > > >> id 33644, offset 0, flags [none], proto TCP (6), length 40) > > >> no-reverse-dns-configured.com.46324 > ke6i.ampr.org.finger: Flags > > >> [S], cksum 0x039d (correct), seq 2046795537, win 1024, length 0 > > >> > > >> > > >> ip tunnel list tunl0 > > >> tunl0: any/ip remote any local any ttl 64 > > >> > > >> ifconfig tunl0 > > >> > > >> tunl0: flags=4289<UP,RUNNING,NOARP,MULTICAST> mtu 1480 > > >> inet 44.4.28.50 netmask 255.255.255.255 > > >> tunnel txqueuelen 1000 (IPIP Tunnel) > > >> RX packets 2259 bytes 305270 (298.1 KiB) > > >> RX errors 0 dropped 0 overruns 0 frame 0 > > >> TX packets 2874 bytes 233904 (228.4 KiB) > > >> TX errors 232 dropped 0 overruns 0 carrier 0 collisions 232 > > >> > > >> ifconfig enp4s0 > > >> enp4s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 > > >> inet 50.79.209.150 netmask 255.255.255.240 broadcast > > >> 50.79.209.159 > > >> ether 8c:89:a5:64:04:4c txqueuelen 1000 (Ethernet) > > >> RX packets 140452 bytes 25244334 (24.0 MiB) > > >> RX errors 0 dropped 473 overruns 0 frame 0 > > >> TX packets 53461 bytes 5807456 (5.5 MiB) > > >> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > >> > > >> ampr-ripd -d -t 44 -a 44.4.28.50/32 -s -L ke6i@cm87uu > > >> Using gateway 50.79.209.158 for direct 44net endpoints via interface enp4s0. > > >> Calling home > > >> Waiting for RIPv2 broadcasts... > > >> Simple password: *********** > > >> > > >> > > >> ip rule list > > >> > > >> 0: from all lookup local > > >> 44: from all to 44.0.0.0/8 lookup hamradio > > >> 45: from all iif tunl0 lookup hamradio > > >> 45: from 44.4.28.50 lookup hamradio > > >> 32766: from all lookup main > > >> 32767: from all lookup default > > >> > > >> > > >> ip route list table hamradio > > >> 44.0.0.1 via 169.228.34.84 dev tunl0 proto 44 onlink window 840 > > >> 44.2.0.1 via 191.183.136.1 dev tunl0 proto 44 onlink window 840 > > >> 44.2.2.0/24 via 216.218.207.198 dev tunl0 proto 44 onlink window 840 > > >> ... > > >> > > >> I don't think it's a firewall issue, I've turned off firewall and it > > >> doesn't fix anything. > > >> > > >> My route table looks healthy, so I think ampr-ripd is worrking correctly? > > >> > > >> Tried to include as much information as I can, thanks for any help! > > >> > > >> > > >> _________________________________________ > > >> 44Net mailing list > > >> 44Net(a)mailman.ampr.org > > >> https://mailman.ampr.org/mailman/listinfo/44net > _________________________________________ > 44Net mailing list > 44Net(a)mailman.ampr.org > https://mailman.ampr.org/mailman/listinfo/44net -- If a rabbit is raised indoors, would it be an ingrown hare? ----- 73 de Brian N1URO IPv6 Certified n1uro-dawt-ampr-dawt-org uronode-dawt-n1uro-dawt-com

1 0

44Net VPN?
by KJ7DMC 29 Jun '19

29 Jun '19

Hello, This is sort of a follow up to my last email, which I ended up figuring out. This link, http://he.fi/amprnet-vpn/amprnet-vpn-win.zip to download the amprnet crt file is invalid. Any idea where I would obtain that file from? Thanks! -Nate

3 2

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

44net