Skip to content

StarNet

New problem solver

Joined 

February 13th, 2013

About me

No bio added

StarNet has won 6 Badges (View Badges)

StarNet's Activities

All Activities
Selected All Activities

StarNet
commented on 's post

8 years ago

Sometime around 6pm Pacific time this evening, I noticed some odd connectivity issues to certain sites. The problem appears to be that I lost my IPv6 /56 PD, as my OpenBSD router running wide-dhcpv6 dhcp6c is now only receiving a /64.  My IPv6 dhcp6c configuration hasn't changed for several years (h

I have a novice IPv6 question regarding your problem.I was reading about DHCPv6 and learned that most hosts receive their IPv6 addresses through stateless address autoconfiguration (SLAAC) (which uses ICMPv6), and only need DHCPv6 for things that SLA

StarNet
posted a question

April 11, 2017

8 years ago

For the first time, I logged into my Comcast Business account, went to the "Manage Services", "Internet", page, and noticed a link to "View Static IP", so I clicked on it.It brings up a page that not only shows the static IPv4 addresses I know very well, but also "Static IPv6 Information", which is

StarNet
commented on 's post

8 years ago

I am using Comcast with my small business, I have a new cable modem (Model: DPC3941B) which supports IPv6. I am using DHCP on the modem. I have configured the DNS server settings in DHCP for IPv4 to point at my servers. I have an AD domain and need clients to talk to my DNS servers.I would like to d

I have a similar problem. We're using a Peplink Balance router, a dual-WAN router that NAT-balances the office traffic between Comcast and AT&T (for IPv4 only). It also bridges IPv6 to the Comcast modem. The Balance router is also a proxy DNS server,

StarNet
commented on
StarNet
's post

8 years ago

I thought this problem would be solved with a new modem, but it happened again. Sometime between yesterday and today, all IPv6 packets are being dropped. The modem is still assigning us IPv6 addresses, but pings to IPv6 addresses (e.g. ipv6.google.com) always time out with no response. Power-cycling

Yes, the modem was replaced and now IPv6 is working again.

StarNet
posted a question

March 22, 2017

8 years ago

I thought this problem would be solved with a new modem, but it happened again. Sometime between yesterday and today, all IPv6 packets are being dropped. The modem is still assigning us IPv6 addresses, but pings to IPv6 addresses (e.g. ipv6.google.com) always time out with no response. Power-cycling

StarNet
commented on
StarNet
's post

9 years ago

After about a week (I'll try to get a better measure of time next time) the Comcast modem refuses to respond to IPv6 packets. A power-cycle always fixes the problem, but unfortunately, it sometimes gives me different addresses.

Now IPv4 isn't working either... I will power cycle the modem.

StarNet
commented on
StarNet
's post

9 years ago

After about a week (I'll try to get a better measure of time next time) the Comcast modem refuses to respond to IPv6 packets. A power-cycle always fixes the problem, but unfortunately, it sometimes gives me different addresses.

In response to your last private message, I called the support number yesterday and spoke with someone who moved the ticket to tier 2. When they didn't contact me in 24 hours as promised, I called them today and didn't get very far. After a long conv

StarNet
commented on
StarNet
's post

9 years ago

After about a week (I'll try to get a better measure of time next time) the Comcast modem refuses to respond to IPv6 packets. A power-cycle always fixes the problem, but unfortunately, it sometimes gives me different addresses.

Yes, someone here just noticed that it wasn't working today. (We don't often notice quickly, because IPv4 continues to work. What brought it up was that we have a Debian system directly on our Comcast network, and the admin was using apt-get, which c

StarNet
commented on
StarNet
's post

9 years ago

Troubleshooting an email problem, I found this in our logs (after some cleaning):550-5.7.1 [2601:647:4900:8d00:d830:edff:feb2:8d1f] Our system has detected that 550-5.7.1 this message does not meet IPv6 sending guidelines regarding PTR 550-5.7.1 records and authentication. Please review 550-5.7.1 h

@FeldmanLaw wrote:  So the only fix for this is to comlpetely disable IPv6 on your Exchange server so that it forces it to communicate with Gmail on IPv4?If you're unfortunate enough to run Exchange, then that may be your best solution. If, however,

StarNet
posted a question

September 24, 2015

9 years ago

Troubleshooting an email problem, I found this in our logs (after some cleaning):550-5.7.1 [2601:647:4900:8d00:d830:edff:feb2:8d1f] Our system has detected that 550-5.7.1 this message does not meet IPv6 sending guidelines regarding PTR 550-5.7.1 records and authentication. Please review 550-5.7.1 h