[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Comcast cablemodems and IPV6

To: "'OpenBSD general usage list'" <misc@openbsd.org>
Subject: Re: Comcast cablemodems and IPV6
From: stan <stanb@panix.com>
Date: Thu, 12 Feb 2004 10:40:32 -0500
Content-Disposition: inline
Mail-Followup-To: 'OpenBSD general usage list' <misc@openbsd.org>
References: <20040212131519.GC3812@teddy.fas.com> <ADCFA6B7CA0C754EB837B423E5A521D2791386@mailbox.noc.dls.net>
User-Agent: Mutt/1.5.4i

On Thu, Feb 12, 2004 at 09:12:43AM -0600, robert wrote:
> That dosent really make any sense. Comcast must have implemented
> Something to still deliver ipv4 content/traffic to an ipv6 enduser.
> 
I'm _assuming_ that these reports are of getting _both_ an IPV4, _and_ a
IPV6 address. Nothing else would (as you say) make sense.

Since OpenBSD by default enables IPV6, I was really wondering if anyone hre
had seen an IPV6 address assigned?

-- 
"They that would give up essential liberty for temporary safety deserve
neither liberty nor safety."
						-- Benjamin Franklin

Follow-Ups:
- Re: Comcast cablemodems and IPV6
  - From: Hugo Villeneuve <harpagon@jwales.EINTR.net>
- Re: Comcast cablemodems and IPV6
  - From: Paul de Weerd <paul@mail.me.maar.nu>

References:
- Comcast cablemodems and IPV6
  - From: stan <stanb@panix.com>
- Re: Comcast cablemodems and IPV6
  - From: "robert" <r@dls.net>

Prev by Date: Re: Comcast cablemodems and IPV6
Next by Date: Re: PF (CBQ) restriction ?
Prev by thread: Re: Comcast cablemodems and IPV6
Next by thread: Re: Comcast cablemodems and IPV6
Index(es):
- Date
- Thread