On Thu, Mar 17, 2011 at 8:21 PM, Philippe LeCavalier < supp...@plecavalier.com> wrote:
> Pahin. The purpose of a list like this is for others to benefit from > experiences/fixes and the like. Omitting the list after finding a > helpful hand is counter productive. Please address the list when > replying to help. > > Excerpts from pahnin sd's message of Thu Mar 17 10:35:45 -0400 2011: > > On Thu, Mar 17, 2011 at 7:59 PM, Philippe LeCavalier < > > supp...@plecavalier.com> wrote: > > > > > Excerpts from pahnin sd's message of Thu Mar 17 10:23:37 -0400 2011: > > > > I am using debian 6.0 > > > > My wifi is working fine but I couldn't use lan on my laptop.. > > > > It shows in gnome panel that, wired networks is not managed .. I have > > > > searched on internet but I could nt find gud solution. > > > > Please help me... > > > > > > What do lspci and ifconfig show? dmesg | grep eth could also help us > > > help you. > > > -- > > > > > > > when I connectd lan wire dmesg | grep eth > > > > [ 1.850489] sky2 eth0: addr 00:24:be:b8:13:7c > > [ 15.630845] sky2 eth0: enabling interface > > [ 15.631279] ADDRCONF(NETDEV_UP): eth0: link is not ready > > [ 101.670659] sky2 eth0: disabling interface > > [ 102.931253] sky2 eth0: enabling interface > > [ 102.931707] ADDRCONF(NETDEV_UP): eth0: link is not ready > > [ 9597.445540] sky2 eth0: Link is up at 100 Mbps, full duplex, flow > control > > both > > [ 9597.445976] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready > > [ 9607.681270] eth0: no IPv6 routers present > > > > Ifconfig > > > > eth0 Link encap:Ethernet HWaddr 00:24:be:b8:13:7c > > inet addr:192.168.212.53 Bcast:192.168.215.255 > > Mask:255.255.252.0 > > inet6 addr: fe80::224:beff:feb8:137c/64 Scope:Link > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:2333 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:86 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:1000 > > RX bytes:184831 (180.4 KiB) TX bytes:9817 (9.5 KiB) > > Interrupt:18 > [...] > > wlan0 Link encap:Ethernet HWaddr 2c:81:58:eb:95:45 > > inet addr:192.168.2.101 Bcast:192.168.2.255 > Mask:255.255.255.0 > > inet6 addr: fe80::2e81:58ff:feeb:9545/64 Scope:Link > > UP BROADCAST RUNNING MULTICAST MTU:1300 Metric:1 > > RX packets:39810 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:39744 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:1000 > > RX bytes:27940617 (26.6 MiB) TX bytes:7032624 (6.7 MiB) > > > > LSPCI > [...] > 03:00.4 SD Host controller: Ricoh Co Ltd MMC/SD Host Controller > > 04:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8057 PCI-E > > Gigabit Ethernet Controller (rev 10) > > 3f:00.0 Host bridge: Intel Corporation Core Processor QuickPath > Architecture > > Generic Non-core Registers (rev 02) > > 3f:00.1 Host bridge: Intel Corporation Core Processor QuickPath > Architecture > > System Address Decoder (rev 02) > > 3f:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 02) > > 3f:02.1 Host bridge: Intel Corporation Core Processor QPI Physical 0 (rev > > 02) > > 3f:02.2 Host bridge: Intel Corporation Core Processor Reserved (rev 02) > > 3f:02.3 Host bridge: Intel Corporation Core Processor Reserved (rev 02) > > > > > Thanks, > > > Phil > > > > > Thanks for your help > > > looks fine as long as > > inet addr:192.168.212.53 Bcast:192.168.215.255 Mask:255.255.252.0 > how to change this > > is correct for your network? Your wifi is getting an address from a > different subnet. Is that what you want? You may be completely aware but > in case you're not you'll need some routing between the two to get that > working. Have you added some routes for that? > > I dont know how to do the above > Also, and this is unorthodox, but you might not be getting a default route. > what does route show? > > And I know Marvell doesn't like Linux and vis-versa pre 2.6.something. > Although I don't think it would get an address from dhclient if this > were an issue - not sure there - What kernel are you running... uname -r > would help > -- > 2.6.32-5-686 Thanks, > Phil >
