aah... makes sense. if you have two ports on the same network, total confusion arises. try adding this to your /etc/network/interfaces:
allow-hotplug eth0
i believe this brings the interface up/down when the cable is inserted/removed thus saving the necessity of manually doing it. perhaps it used to be in your interfaces file and something changed it?
regards
bryan
--- On Sun, 25/1/09, Clive Woodfine <clivewoodfine@???> wrote:
From: Clive Woodfine <clivewoodfine@???>
Subject: Re: [Hampshire] Wireless problem.
To: "Hampshire LUG Discussion List" <hampshire@???>
Date: Sunday, 25 January, 2009, 8:54 PM
2009/1/25 B STEVENS <b.stevens611@???>:
> hi, clive
> for what it's worth, my GUI network manager editor doesn't work
either but
> it's low priority as i can connect wirelessly using those commands.
>
> anyway, i'm glad the information i gave helped you as i see myself
more of a
> "leech" on the linux community as opposed to a contributor! :-)
>
> regards
>
> bryan
Bryan,
I have now found a simpler method in my case. When I boot the wired
interface eth0 is active (even though it is not physically attached)
as shown by 'route -n'
clive@vaio:~$ route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 eth0
0.0.0.0 my-router-address 0.0.0.0 UG 100 0
0 eth1
0.0.0.0 my-router-address 0.0.0.0 UG 100 0
0 eth0
If do 'ifdown eth0' to remove eth0 from the route table the wireless
immediately works! Why this should be necessary now I have no idea.
Clive Woodfine
--
Please post to: Hampshire@???
Web Interface:
https://mailman.lug.org.uk/mailman/listinfo/hampshire
LUG URL:
http://www.hantslug.org.uk
--------------------------------------------------------------
