oops. No longer able to connect to the internet through my DSL
 

OK. I don't understand how this happened. I was attempting to connect my fedora computer to the internet. I turned off the suse computer that has the internet, moved the modem cable to the other computer and powered on the second computer. I left the first computer turned off (in fact, I unplugged the power cord). I figured that if I turned the computer on without the modem, it would only confuse the system.

I couldn't get the internet to connect on the fedora computer, so I took the modem back to the suse computer. That computer doesn't connect anymore and I don't understand how it figured out that the modem was detached for a few hours since it was powered off. So now how do I reconnect it?

I know the modem is good and that the internet service is still active. I am using it to type this. I had to connect to one of the Windows systems I have to get it to work.

The error it is giving me is that it cannot find the host or domain of anything I try to look for online. It is also telling me during the startup messages that eth0 and eth1 could not be set up. They are both configured with DHCP. A little later it says that samba was skipped and networking failed.

Any ideas?

Connecting to the Internet
 

You need to ensure that your "old connection", the SuSE machine, gets a new IP address from the DHCP server. Its possible that you did not power off the modem when you switched machines, which means that the modem had "assumed" that the IP address it had earlier dished out was "in-use", which was actually being used by the Fedora machine.

You can do one of the two following things :

1. Reboot the modem ( power-off & restart ) & then reboot the Fedora, or

2. Run the command
#dhclient
from the command line as root.

If the dhcp utils package has been installed, then the dhclient command would get a new negotiated IP address from the modem.

RK

Well, I just ripped suse off of my computer and installed fedora. It connected up, but I am not entirely sure how. I have eth0 set up to configure with DHCP and have the DSL modem connected to it. However, when I go to the Network Configuration tool and try to set up an xDSL connection, it fails. Im just curious at this point. Does anyone know why this is working?

Arp
 

Address Resolution Protocol maps a logical IP address to the hardwired flat addressing of your Network Interface. All Interfaces have a MAC address, and this is fixed and unique worldwide. IP addresses, however may be duplicated in separate networks, and for a given machine in any particular network, it can be changed. When you have established a connection from NIC-A to DSL-B, each set up an ARP table entry that maps designated IP-address-A with NIC-MAC-A and DSL-address-B with DSL-MAC-B. This table is maintained on a periodic basis so that ARP is not required for every session. That would be too inefficient. You can see the arp table on your Linux machine using "arp -an". If you have attempted a connection, it will have an entry for the target machine's IP address, and its MAC address. If you then unplug the cable and connect it to a machine that will necessarily have a different MAC address, this table is now incorrect for the new configuration. You can delete the arp entry by hand using the -d option with the arp command. You also have to work out which machine's arp table is incorrect - the DSL router or just your linux? You might need to reset the DSL router.

... OK ... I think I understood at least part of that. I ran the arp command and this is what I got.

[@pool-71-111-73-144 ]$ arp -an
bash: arp: command not found
[@pool-71-111-73-144 ]$ /sbin/arp -an
? (71.111.73.1) at 00:90:1A:41:45:C8 [ether] on eth0

It is interesting that the numbers in the local hostname is almost the same as the entry in the arp table. I also didn't set up that host name. I would have chosen something better than pool.

I realize that this is getting a bit off the topic of this thread. Should /sbin be on the command path? This is the second time that a command that is suggested to me has failed to run because I have to add the /sbin/ to it first.

/sbin
 

/sbin is not in your normal path for tidiness. Ordinary users should not have to use these probramsm and do not need to place any of the sbin directories in their path.

Your 'pool' name would be assigned by the DHCP machine. It is a sensible choice for something that has a group if IP addresses to deal out. (a 'pool' of IP addresses). Your arp entry shows the IP address and MAC address of the DHCP device - most likely your DSL router.

@mbreith:
The config tool of your distro?
Of course it does.
You are using a dsl router, if I got this right, and all you have to do
is establish a regular network connection within the correct subnet mask...

baik

I thought it was just a DSL modem.
...
Actually, since a modem (modulator/demodulator) deals with analog signals, it would be better described as a single port DSL router.

On Suse, I had to set up the DSL... Well, I assume that I did. It may have just ignored anything I told it there. Yast is very nice in some ways, but is also a "magical black box." I have no idea what it was actually doing when it was configuring things.

a modem would not serve as a dhcp server...
and it wouldn't have it's own ip-address.
do you have a web-interface to interact with
that thing? If you do, then you manage the outbound connection
there, right? That would be a router, then.

regards,
Baik

Multiple computers connected to one DSL modem.
 

You should purchase a DSL/Cable router. It will allow you to connect multiple computers to your DSL modem. You can use them all at the same time or any one and not have to connect/reconnect cables.

Yes, but that costs :twocents: which is in short supply when you are a college student, married and have two kids. ;)