<p>I'm puzzled that the net mask matters here as well. You don't have to set the internal network to the same mask, you can just<br>
On Sep 28, 2012 1:25 PM, "David L. Anselmi" <<a href="mailto:anselmi@anselmi.us">anselmi@anselmi.us</a>> wrote:<br>
><br>
> Jug Knot wrote:<br>
> ><br>
> > The next speedbump appears to be a limitation from both the Service Provider (CL) and the router<br>
> > manufacturer. In acquiring a Static IP address from CL, they provide a Class A address and a<br>
> > Subnet Mask of 255.255.255.255. Turns out thats a showstopper for Cisco SoHo (Linksys)<br>
> > equipment<<a href="http://homecommunity.cisco.com/t5/Wireless-Routers/Subnet-mask-limitation/td-p/304093">http://homecommunity.cisco.com/t5/Wireless-Routers/Subnet-mask-limitation/td-p/304093</a>><br>
> > .<br>
><br>
> You're talking about the WAN port, right? Doesn't the mask get set with the IP? That seems like a<br>
> reasonable mask for PPP--if you can select PPPoE I'm surprised you have to do anything with the mask.<br>
><br>
> Dave<br>
> _______________________________________________<br>
> clue mailing list: <a href="mailto:clue@cluedenver.org">clue@cluedenver.org</a><br>
> For information, account preferences, or to unsubscribe see:<br>
> <a href="http://cluedenver.org/mailman/listinfo/clue">http://cluedenver.org/mailman/listinfo/clue</a></p>
<p>I'm surprised that you have to do anything with the mask as well. You don't have to set the internal network work to use that mask, the router should just nat to it. </p>