<p>I hope some of that helps. </p>
<div class="gmail_quote">On Sep 25, 2012 7:55 PM, "Charles Burton" <<a href="mailto:charles.d.burton@gmail.com">charles.d.burton@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<p>As far as I can tell century doesn't have to change anything. Also, unless you specifically bought a static wan ip they're assigned dynamically when you authenticate with the distant end. You just have to have your username and password that century link gives you to use with pppoe. Another point I would like to mention that while I like running it over my own router don't expect support to understand if something goes wrong. It's really difficult to get them to understand that the reason they can't get into the modem is because it's a dumb bridge handling just the encapsulation. </p>
<div class="gmail_quote">On Sep 25, 2012 7:46 PM, "David L. Anselmi" <<a href="mailto:anselmi@anselmi.us" target="_blank">anselmi@anselmi.us</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Jug Knot wrote:<br>
> I'm looking for a SoHo NW person who can help me sort out a Public Address<br>
> Space (server) + SoHo Wireless NW (192.168.x.x) space behind a CenturyLink<br>
> DSL Modem (Zyxel PK5000z) with residential Internet service.<br>
><br>
> I've installed a Cisco Linksys (E1200) router and my 1st attempt to set the<br>
> DSL modem in 'Transparent Bridging Mode' dropped the network for about 2<br>
> hours today.<br>
<br>
Why do you want bridging mode? (Just curious.)<br>
<br>
Do you have any idea what wasn't working?<br>
<br>
Do you have any directions on how to set up the modem to bridge? (I've sort of been under the<br>
impression that it might require a change on the CL end but Charles's answer seems to indicate<br>
otherwise.)<br>
<br>
So roughly the router will have to have the public IP assigned to its external interface. The modem<br>
should tell you what that is, or maybe traceroute, or one of those "your IP is" web pages.<br>
<br>
The internal side of the router will have to be the 192... network (it needs an IP there that will<br>
be the gateway for all the internal machines).<br>
<br>
The router will have to do NAT, like the modem is now.<br>
<br>
Does that help at all?<br>
<br>
Dave<br>
_______________________________________________<br>
clue mailing list: <a href="mailto:clue@cluedenver.org" target="_blank">clue@cluedenver.org</a><br>
For information, account preferences, or to unsubscribe see:<br>
<a href="http://cluedenver.org/mailman/listinfo/clue" target="_blank">http://cluedenver.org/mailman/listinfo/clue</a><br>
</blockquote></div>
</blockquote></div>