If the "AT&T modem" is indeed a DSL modem. The issue may be one related to dialing the access number. If you only use the modem:
wall --> modem --> computer then you would need to have some sort of PPPoE (point to point protocol over ethernet) software to make the connection. In this event, you may have installed some software to perform this function on Windows. Obviously, Linux would know nothing about this. It is generally better/safer to include some kind of router between the modem and the computer: wall --> modem --> router --> computer This offers several advantages. One is that most consumer routers (wireless or wired) include a firewall to block incoming server requests (SYN) on all ports except those you specifically open. A second advantage is that multiple computers may access the Internet through this connection. Probably the most relevant here is that the router can be configured to act as the PPPoE client (needs the phone number, username, password for your AT&T account). It acts keeps the connection up and dials when necessary. The computers in your network get their IP address via DHCP. The computers using the router do not need a PPPoE client program. This may not explain why your connection would show up after multiple restarts of the machine. However if you never get a connection with Linux, then it could be the issue. If this is a regular telephone modem (not DSL) then most likely the modem in your machine is part of the motherboard and is what is called a WinModem. These rely on the operating system software to supply some of the functionality. This can be a problem for Linux in many cases. Some of these WinModems can be run with information found on http://www.LinModem.org but a cable or DSL connection is preferred if you can afford it. James -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-newbie
