Problem with ethernet -- SOLVED

[Michael S. Peek]

Derek Broughton wrote:
> It doesn't _get_ this weird IP6 address. If you look at the HW address
> you'll see that every IP6 address is related to the MAC address.  The idea
> being that every interface should have a unique address on the internet,
> eliminating the need for NAT and private subnets.
>   

IPv4 I at least understand the basics.  But IPv6 is still magic and 
mystery to me.  I should read up on it I guess.

> My (possibly erroneous) understanding of that is that you have to roll your
> own if you want to be able to choose to route via different interfaces. 
> It's not possible in a default install.
>   

Really?  <Huff>  'Cause it used to work.  I could open up the Network 
Settings tool, de-select "Wireless connection", select "Wired 
connection", and go to town.

> I think you need to turn off the wireless transmitter, remove the network
> cable, ensure both interfaces are down, then insert the network cable and
> watch what happens.
>   

...


Okay, I guess I'm just hallucinating, but now it seems to be working again.

I restarted the machine and booted from the install cd with the wire 
plugged in.  That found the ethernet device and configured it via DHCP 
and everything worked fine.  Now at least I know that the device is 
still working.

So the next thing I did was restart and boot from the hard drive -- and 
after that the static IP that it was previously configured started 
working fine.

So I turned off the device in Network Settings, removed the static 
configuration, set it back to DHCP, and turned the interface back on -- 
and viola, it worked.

So, just to check, I turned off the wired connection and turned on the 
wireless -- OK.

Then I turned off the wireless and turned the wired back on -- still OK.

I have no idea why this wasn't working for a while, but rebooting seems 
to have fixed it.  (<Gag>:  Reboot to fix?  Too many Windows memories...)



Thanks to all for your help.

Michael Peek