On Sunday 19 December 2010 11:53:33 Dale wrote:

> This was fun.

:-)

> I tried to set it up the way you explained but
> apparently I ain't to good with this.  Now the router don't work at
> all and I had to hit the reset button on the modem.  I'm glad I
> could remember the password.  :/

Ook!

> OK.  The IP I get from AT&T is set by them and it changes.  I think
> that is dynamic not static.  So, I assume that part of the
> connection has to be DHCP.  Correct?  That was how I left it anyway.

Yes, that's right. So your modem's outer connection sends a DHCP request 
over the phone line, gets a name and an address and sets itself up to 
use them. So far so good.

> Where does this network idiot go from here?  I think the modem got
> mad when I told it to let the router set the IP between it and the
> modem.

Ah! I think I see what happened here. The modem won't be able to ask for 
an address on its inner side; you'll have to tell it what address to use 
as it's going to be the fixed point that other devices use to get out to 
the Internet. Then tell your router what address to use to talk to it. 
(If you're like me you'll get confused over which connection you're 
working on while setting up two-interface devices.)

Would you mind telling me why you have a router between yourself and the 
modem? (Maybe you've told us already and I missed it.) If all the 
connections are via Ethernet you can omit the router for the moment and 
get a connection established direct to the modem. Once that's working 
you can put the router back and we can think about getting it working 
too.

> P.S. Going to look for a howto to see if it at least helps me
> understand how this works.

Good idea - maybe it'll make better sense to you than I do   :-)

-- 
Rgds
Peter.          Linux Counter 5290, 1994-04-23.

Reply via email to