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 central office and that you can't change anything about it.
Moshe On May 20, 2016 11:54 AM, "WebDawg" <webd...@gmail.com> wrote: > On Wed, May 18, 2016 at 6:14 PM, Steve Yates <st...@teamits.com> 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 invalid prefix length 64 + 4 + 64 > > dhcp6c XID mismatch (several of these) > > > > Am I correct that "invalid prefix length" means the Comcast router isn't > > delegating a /60 properly? I have it set: > > > > DHCPv6 Prefix Delegation size 60 > > Send IPv6 prefix hint checked > > > > If I as for a /56 I get "invalid prefix length 64 + 8 + 64." > > > > My second question was going to be about getting IPv6 to the PCs inside > > the tenant router but unless I'm mistaken I need a couple more /64 > networks > > for that (what a waste of IPs...I know there's a lot but still...). > > > > Thanks, > > > > Steve Yates > > ITS, Inc. > > > > _______________________________________________ > > > > > Am I correct to assume that you are putting this device in bridge mode? > _______________________________________________ > pfSense mailing list > https://lists.pfsense.org/mailman/listinfo/list > Support the project with Gold! https://pfsense.org/gold > _______________________________________________ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
