RE: Xfinity with IPv6 clue?
Nanog is magical. I have working IPv6 now. From: Janet Sullivan Sent: Sunday, August 4, 2019 6:29 PM To: 'nanog@nanog.org' Subject: Xfinity with IPv6 clue? I hate resorting to NANOG, but I've spent over 5 hours on the phone with Xfinity the past two days, and I can't seem to get someone who understands my problem. I do not have working IPv6 - I do not get an address or PD. I have working IPv4. Xfinity wanted to blame this on my modem, so I went and picked up a Xfinity modem. From the 10.0.0.1 web site on the xfinity modem, I can ping IPv4 addresses fine. I can not ping IPv6 addresses from the modem itself, thus taking my equipment out of the picture. This is a new activation. Xfinity keeps asking questions like "well, can you surf the internet", which shows that they seem to totally lack understanding. I've talked to at least 7 people, and have reached my breaking point. I know, I know, its residential and I should have low expectations. I'm sorry for the noise, but I can't seem to find anyone with clue.
Xfinity with IPv6 clue?
I hate resorting to NANOG, but I've spent over 5 hours on the phone with Xfinity the past two days, and I can't seem to get someone who understands my problem. I do not have working IPv6 - I do not get an address or PD. I have working IPv4. Xfinity wanted to blame this on my modem, so I went and picked up a Xfinity modem. From the 10.0.0.1 web site on the xfinity modem, I can ping IPv4 addresses fine. I can not ping IPv6 addresses from the modem itself, thus taking my equipment out of the picture. This is a new activation. Xfinity keeps asking questions like "well, can you surf the internet", which shows that they seem to totally lack understanding. I've talked to at least 7 people, and have reached my breaking point. I know, I know, its residential and I should have low expectations. I'm sorry for the noise, but I can't seem to find anyone with clue.
Anyone on from Comcast?
I've spent my morning in customer support hell. Sorry for the noise, but if someone with clue could help a gig residential customer getting 3 Mbit/s, I'd love you.
Comcast Support
I hate to use NANOG for this, but support has now ended a chat with me twice without fixing anything, they just kicked me off. I'm not getting an IPv6 address on the Comcast provided cable modem/router. I'm not getting a PD. My machines thus have no IPv6. I've hard reset my router 4 times while working with Comcast, and I've been told to do things like switch to a static IPv4 address, which shows a level of clue that is scary. And before that they were convinced it was a wireless problem even though I have a wired connection, and told them that multiple times. I've wasted two hours with Comcast today, and even when I asked for escalation I got nothing. Just hung up on. It's honestly the worst customer support I've ever received. I don't think I ever got them to understand the difference between IPv4 and IPv6.
RE: Anyone from frontiernet.net on here?
Thank you, I really appreciate you looking into this. In return, I'll offer up that I'm a senior network engineer at Microsoft - if you ever have issues with AS8075, ping me, and I'll see what I can do. -Original Message- From: Jeff Richmond [mailto:jeff.richm...@gmail.com] Sent: Tuesday, July 9, 2013 8:36 PM To: Warren Bailey Cc: Janet Sullivan; nanog@nanog.org Subject: Re: Anyone from frontiernet.net on here? All it looks like I am seeing packet loss there across all of our peering sessions with them, so looks like a problem on their network. I'll ask our NOC to open up a ticket with them though just to see if we can find out what the issue is. Thanks, -Jeff On Jul 9, 2013, at 7:18 PM, Warren Bailey wrote: > There are some decent sized attacks taking place on gear near London, I > believe. Could be a result of that? > > > Sent from my Mobile Device. > > > ---- Original message > From: Janet Sullivan > Date: 07/09/2013 5:01 PM (GMT-08:00) > To: nanog@nanog.org > Subject: Anyone from frontiernet.net on here? > > > I've been seeing really bad packet loss between PCCW and frontier, and so far > haven't been able to make any traction with anyone on either side. I'm > betting that the ??? is a peering point either in London or Ashburn. > > uk.bgp4.net (0.0.0.0)Tue Jul 9 20:39:53 2013 > Keys: Help Display mode Restart statistics Order of fields qu > it Packets Pings > Host Loss% Snt Last Avg Best Wrst StDev > 1. 212.111.33.230 0.0%431.7 0.7 0.5 1.8 0.3 > 2. 212.111.33.237 0.0%432.3 1.9 1.1 22.7 3.3 > 3. 63.218.13.221 0.0%432.3 15.6 1.1 230.3 45.9 > 4. ??? > 5. 74.40.2.17323.3%43 177.9 150.3 147.8 177.9 7.0 > 6. 74.40.2.19320.9%43 149.9 149.9 149.1 161.2 2.1 > 7. 74.40.3.24118.6%43 149.6 152.4 149.1 193.2 8.8 > 8. 74.40.5.49 28.6%43 148.1 150.8 147.8 192.1 9.9 > 9. 74.40.5.54 26.2%43 148.3 150.5 147.9 218.7 12.6 > 10. 74.40.5.46 33.3%42 149.5 154.0 149.2 212.8 14.0 > 11. 74.40.3.13716.7%42 147.4 148.7 146.9 163.0 4.1 > 12. 74.40.1.15429.3%42 148.2 153.6 147.7 206.7 14.2 > 13. 50.34.2.16235.7%42 150.2 150.4 149.8 156.3 1.2 > 14. 50.46.150.55 26.2%42 150.7 151.0 150.5 152.0 0.4 >
Anyone from frontiernet.net on here?
I've been seeing really bad packet loss between PCCW and frontier, and so far haven't been able to make any traction with anyone on either side. I'm betting that the ??? is a peering point either in London or Ashburn. uk.bgp4.net (0.0.0.0)Tue Jul 9 20:39:53 2013 Keys: Help Display mode Restart statistics Order of fields qu it Packets Pings Host Loss% Snt Last Avg Best Wrst StDev 1. 212.111.33.230 0.0%431.7 0.7 0.5 1.8 0.3 2. 212.111.33.237 0.0%432.3 1.9 1.1 22.7 3.3 3. 63.218.13.221 0.0%432.3 15.6 1.1 230.3 45.9 4. ??? 5. 74.40.2.17323.3%43 177.9 150.3 147.8 177.9 7.0 6. 74.40.2.19320.9%43 149.9 149.9 149.1 161.2 2.1 7. 74.40.3.24118.6%43 149.6 152.4 149.1 193.2 8.8 8. 74.40.5.49 28.6%43 148.1 150.8 147.8 192.1 9.9 9. 74.40.5.54 26.2%43 148.3 150.5 147.9 218.7 12.6 10. 74.40.5.46 33.3%42 149.5 154.0 149.2 212.8 14.0 11. 74.40.3.13716.7%42 147.4 148.7 146.9 163.0 4.1 12. 74.40.1.15429.3%42 148.2 153.6 147.7 206.7 14.2 13. 50.34.2.16235.7%42 150.2 150.4 149.8 156.3 1.2 14. 50.46.150.55 26.2%42 150.7 151.0 150.5 152.0 0.4
[OT] Internet connectivity options in Afghanistan?
I'm looking for cheap/slow internet connectivity options in Kabul, Jalalabad, and Herat. The connections will be used by AFCECO orphanages, so speed isn't as much of an issue as cost. I'm guessing that satellite might be the only game in town, but if any of you fine folks know of connectivity options, I'd appreciate an email.
Re: Introducing draft-denog-v6ops-addresspartnaming
On Nov 22, 2010, at 5:05 PM, TJ wrote: > On Fri, Nov 19, 2010 at 08:14, Scott Morris wrote: > >> If 8 bits is a byte, then 16 bits should be a mouthful. >> >> Scott >> > If we can't choose mouthful (which for some reason sounds thematically > correct), "chunk" gets my vote. > *(Chunk = Maybe not the most technical, but has been working for me all > along ...)* > > /TJ I think each section should be a nom, and :: can be a om. My lolcat agrees.
Re: [NANOG] Microsoft.com PMTUD black hole? (working with Microsoft on issues)
I thought I'd post a few constructive comments on this thread. (Full disclosure: I am an ex-Microsoft employee. I do not speak for the company, I'm just trying to help out the network community.) 1) Yes, Microsoft blocks ICMP for the most part, which will break Path MTU Discovery. This is a known issue. If you run into it, its most likely because the servers you are trying to talk to in MS-land don't have black hole router detection turned on. 2) Instead of trying to get all the various ACLs and firewalls in Microsoft fixed to allow PMTUD, you are more likely to experience joy if you can contact the server owners. Ask if they have black hole router detection turned on, and if not, if they can do so. 3) So how do you get in contact with the server owners or MSN's networking people? [EMAIL PROTECTED] is your best bet. That's the email address monitored by the basic Tier 1 "Service Operations Center". They cut tickets, follow scripts, and do very basic front line work. They probably won't be able to fix the problem for you, but they CAN get you in touch with the right people. 4) FINDING the right people can be a challenge, even internally. Microsoft is a very big company, and its far from centralized. Be specific in what URLs and IPs you are having trouble with, and be prepared to bounce around a bit. The people who run microsoft.com's servers aren't the same group that does hotmail, etc. Have patience, and try to get ticket numbers for tracking at much as possible. 5) Try to give a realistic estimate of how many users are being impacted by the problem. Your problem will be triaged as it moves through various groups, and yes, the response time may not be what you want. Your problem is one fire among many, and there aren't enough firefighters. 6) Be nice. Seriously. People love to hate Microsoft, and sometimes take it out on the poor overworked geeks who are trying to actually make things better. Every vulnerability, BSOD, or Vista delay is not the fault of the network or systems engineer you get in touch with. ;-) ___ NANOG mailing list NANOG@nanog.org http://mailman.nanog.org/mailman/listinfo/nanog
