<div dir="ltr">Huzzah! The evil DSL modem of NATing is defeated. After adding the correct password, things worked wonderfully. I thought about the DMZ option, but I just didn't feel the need to have it setup that way. Bridging sounded to me like the simplest setting, modem forwards packets to router, router does the NAT magic and pushed packet to correct computer. I'm not smart enough for the DMZ piece :-)<br>
<br><div class="gmail_quote">On Wed, Jul 16, 2008 at 10:13 PM, Matthew Nuzum <<a href="mailto:newz@bearfruit.org">newz@bearfruit.org</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Wed, Jul 16, 2008 at 5:13 PM, Dave Weis <<a href="mailto:djweis@internetsolver.com">djweis@internetsolver.com</a>> wrote:<br>
> Aaron Korver wrote:<br>
>><br>
>> The reason that I want to use "Bridged" mode is so I can open up ports<br>
>> through the router to the outside world. If I leave things as-is, my modem<br>
>> gives my router an internal IP Address <a href="http://192.168.0.2" target="_blank">192.168.0.2</a> <<a href="http://192.168.0.2" target="_blank">http://192.168.0.2</a>>, and<br>
>> then my router hands out IP addresses to my computers on a different subnet.<br>
>> Thus my computers get assigned 192.168.1.X. The Modem can't see the<br>
>> computers, only the router, and my ports only get opened on the router, not<br>
>> the modem.<br>
>><br>
>> This becomes problematic when you want to do things like VoIP, torrents,<br>
>> WoW, etc :-)<br>
><br>
> The easiest thing to do is just use a modem with wireless built and and not<br>
> use the second level of NAT.<br>
<br>
</div>I've got a similar setup... main diff being I have a buffalo router.<br>
<br>
When I set mine up initially I goofed it up and had to call qwest. I<br>
booted my laptop into windows, connected it to the modem via ethernet<br>
and then set it up using their software. Once done I disconnected my<br>
pc and turned off the modem - plugged it into my router and voila! it<br>
worked.<br>
<br>
My router is set to handout 192.168.1.x IP addresses - this is only<br>
important because it has to be something other than 192.168.0.x since<br>
that's used by the link between the modem and router. In the actiontec<br>
firmware you can change settings via <a href="http://192.168.0.1/" target="_blank">http://192.168.0.1/</a> (which you<br>
probably know). In there go to advanced settings and change the DMZ<br>
host IP to <a href="http://192.168.0.2" target="_blank">192.168.0.2</a>. This will cause it to forward all ports to<br>
your router and then you can deal with your port forwarding settings<br>
on the router. Other than this I didn't need to change anything on the<br>
modem after I configured it in Windows the first time. My router<br>
doesn't know anything about ppoe or etc.<br>
<br>
I don't like the modems with the built in wireless. Maybe there's<br>
different models but the one I saw had a hard time handling lots of<br>
connections.<br>
<font color="#888888"><br>
--<br>
Matthew Nuzum<br>
newz2000 on freenode<br>
</font><div><div></div><div class="Wj3C7c">_______________________________________________<br>
Cialug mailing list<br>
<a href="mailto:Cialug@cialug.org">Cialug@cialug.org</a><br>
<a href="http://cialug.org/mailman/listinfo/cialug" target="_blank">http://cialug.org/mailman/listinfo/cialug</a><br>
</div></div></blockquote></div><br></div>