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
Hello, bonjour,
I have some "Simple" IPv4 tunnels (IKEv1) to customers here, 3 are
already running. Our LAN: 192.168.1.0/24, WAN IP address 80.254.x.y.
Already working tunnels are having a Phase 2 setup similar to:
- Local Network: LAN Subnet
NAT/BINAT: Type Network, Address 192.168.10.0/24
-
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
