On Fri, May 20, 2016 at 1:31 PM, Moshe Katz wrote:
> On Fri, May 20, 2016 at 12:19 PM, WebDawg wrote:
>
> > On Fri, May 20, 2016 at 11:06 AM, Moshe Katz
> wrote:
>
> They will not let you bring your own modem if you have a static IP.
>
> I wrote the last message on my tablet, so I had to keep i
On Fri, May 20, 2016 at 12:19 PM, WebDawg wrote:
> On Fri, May 20, 2016 at 11:06 AM, Moshe Katz wrote:
>
> > If you have static IPs from Comcast, you cannot put the device in bridge
> > mode. The way that Comcast static IPs work is that your Comcast device
> > advertises itself to the rest of Co
On Fri, May 20, 2016 at 11:06 AM, Moshe Katz wrote:
> If you have static IPs from Comcast, you cannot put the device in bridge
> mode. The way that Comcast static IPs work is that your Comcast device
> advertises itself to the rest of Comcast's network as the route to your
> static addresses. In
If you have static IPs from Comcast, you cannot put the device in bridge
mode. The way that Comcast static IPs work is that your Comcast device
advertises itself to the rest of Comcast's network as the route to your
static addresses. In effect, just pretend that this Comcast device is in
Comcast's
On Wed, May 18, 2016 at 6:14 PM, Steve Yates wrote:
> We have an application with a Comcast-provided SMC router and two pfSense
> routers (Comcast <- building <- tenant). The building router (v2.3.0) gets
> an IPv6 address and can ping out. However in its DHCP logs I see:
>
> dhcp6c in
There's indeed no NAT concept in IPv6 but you can use NPt to assign globally
routable IPs on WAN and have them match to a translated locally routable prefix.
Say you have x:y:z:a::/64 on the WAN side which translate to fd01::/64 on the
LAN side.
--
Meilleures salutations, Met vriendelijke groe
016 2:13 PM
To: pfSense Support and Discussion Mailing List
Subject: Re: [pfSense] IPv6 with Comcast and two pfSense - invalid prefix
length, XID mismatch
I'm going to have to guess that you are out of luck for IPv6 then.
If you find anyone at Comcast who is 1) capable of understanding
fixs Delegations2601:249::::/64
>
> ...with the LAN IP range. (yes, it is spelled "prefixs")
>
> --
>
> Steve Yates
> ITS, Inc.
>
> -Original Message-
> From: List [mailto:list-boun...@lists.pfsense.org] On Behalf Of Moshe Katz
> Sent:
e Support and Discussion Mailing List
Subject: Re: [pfSense] IPv6 with Comcast and two pfSense - invalid prefix
length, XID mismatch
On Wed, May 18, 2016 at 7:14 PM, Steve Yates wrote:
> We have an application with a Comcast-provided SMC router and two
> pfSense routers (Comcast <- bu
On Wed, May 18, 2016 at 7:14 PM, Steve Yates wrote:
> We have an application with a Comcast-provided SMC router and two pfSense
> routers (Comcast <- building <- tenant). The building router (v2.3.0) gets
> an IPv6 address and can ping out. However in its DHCP logs I see:
>
> dhcp6c in
We have an application with a Comcast-provided SMC router and two pfSense
routers (Comcast <- building <- tenant). The building router (v2.3.0) gets an
IPv6 address and can ping out. However in its DHCP logs I see:
dhcp6c invalid prefix length 64 + 4 + 64
dhcp6c XID mismatch
11 matches
Mail list logo
