public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sergio Polini <sp_rm_it@yahoo.it>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] OT: wlan0 is sssloooow
Date: Mon, 27 Nov 2006 22:04:33 +0100	[thread overview]
Message-ID: <200611272204.33717.sp_rm_it@yahoo.it> (raw)
In-Reply-To: <7573e9640611261436i7d1e73bfl6b367e0203484992@mail.gmail.com>

Richard Fish:
> On 11/26/06, Sergio Polini <sp_rm_it@yahoo.it> wrote:
> > My pings (perhaps all DNS lookups) are slow even if connect my PC
> > to both the wireless router and the cable, i.e. when there are
> > both a "fast" (metric 0) and a "slow" (metric 2000) interface.
> >
> > > What do "ifconfig wlan" and "iwconfig wlan" report for the fast
> > > and slow states?
> >
> > Fast (i.e. normal ;-) state happens only when net.wlan0 is
> > stopped. When I start net.wlan0:
>
> Are both wired and wireless enabled?  Your original posting doesn't
> show any records for eth0.  In the 'slow' state, what is the output
> of 'ifconfig -a' and route?

I apologize for my error.
However....

Case #1 - Cold boot, only wire enabled
--------------------------------------
(without CONFIG_NET_IPGRE)
net.eth0 in default runlevel.

sergio ~ # ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:16:D3:09:2D:17
  inet addr:XX.XXX.XXX.250  Bcast:255.255.255.255  Mask:255.255.248.0
  UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:20 errors:0 dropped:0 overruns:0 frame:0
  TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:1578 (1.5 Kb)  TX bytes:1669 (1.6 Kb)
  Interrupt:16

lo        Link encap:Local Loopback
  inet addr:127.0.0.1  Mask:255.0.0.0
  UP LOOPBACK RUNNING  MTU:16436  Metric:1
  RX packets:19 errors:0 dropped:0 overruns:0 frame:0
  TX packets:19 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0
  RX bytes:1119 (1.0 Kb)  TX bytes:1119 (1.0 Kb)

sergio ~ # route
Kernel IP routing table
Destination  Gateway      Genmask       Flags Metric Ref Use Iface
23.252.112.0 *            255.255.248.0 U     0      0     0 eth0
loopback     *            255.0.0.0     U     0      0     0 lo
default      23.252.112.1 0.0.0.0       UG    0      0     0 eth0

sergio ~ # cat /etc/resolv.conf
# Generated by dhcpcd for interface eth0
search fastwebnet.it
nameserver 213.156.54.80
nameserver 213.156.54.81

NB: route and ping www.google.com are fast.

Case #2 - Cold boot, only wireless enabled
------------------------------------------
net.eth0 deleted from default runlevel.
After modprobe ndiswrapper and /etc/init.d/net.wlan0 start:

sergio ~ # ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:16:D3:09:2D:17
   UP BROADCAST MULTICAST  MTU:1500  Metric:1
   RX packets:0 errors:0 dropped:0 overruns:0 frame:0
   TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
   collisions:0 txqueuelen:1000
   RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
   Interrupt:16

lo        Link encap:Local Loopback
   inet addr:127.0.0.1  Mask:255.0.0.0
   UP LOOPBACK RUNNING  MTU:16436  Metric:1
   RX packets:19 errors:0 dropped:0 overruns:0 frame:0
   TX packets:19 errors:0 dropped:0 overruns:0 carrier:0
   collisions:0 txqueuelen:0
   RX bytes:1119 (1.0 Kb)  TX bytes:1119 (1.0 Kb)

wlan0     Link encap:Ethernet  HWaddr 00:14:A5:E1:D2:B9
   inet addr:192.168.2.2  Bcast:192.168.2.255  Mask:255.255.255.0
   UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1
   RX packets:11 errors:0 dropped:0 overruns:0 frame:0
   TX packets:17 errors:0 dropped:0 overruns:0 carrier:0
   collisions:0 txqueuelen:1000
   RX bytes:1483 (1.4 Kb)  TX bytes:1922 (1.8 Kb)
   Interrupt:20 Memory:c3000000-c3004000

sergio ~ # route
Kernel IP routing table
Destination Gateway     Genmask       Flags Metric Ref Use Iface
192.168.2.0 *           255.255.255.0 U     2000   0     0 wlan0
loopback    *           255.0.0.0     U     0      0     0 lo
default     192.168.2.1 0.0.0.0       UG    2000   0     0 wlan0

sergio ~ # cat /etc/resolv.conf
# Generated by dhcpcd for interface wlan0
search Belkin
nameserver 192.168.2.1
nameserver 213.156.54.80
nameserver 213.156.54.81

NB: ping www.google.com is slow, ping 192.168.2.1 is either too much 
slow or blocked ;-) But works under Windows.
route is slow, route -n is fast.

Case #3 - Cold boot, wire and wireless enabled
----------------------------------------------
net.eth0 in default runlevel.
After modprobe ndiswrapper:

sergio ~ # ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:16:D3:09:2D:17
  inet addr:XX.XXX.XXX.250  Bcast:255.255.255.255  Mask:255.255.248.0
  UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:18 errors:0 dropped:0 overruns:0 frame:0
  TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:1559 (1.5 Kb)  TX bytes:1795 (1.7 Kb)
  Interrupt:16

lo        Link encap:Local Loopback
  inet addr:127.0.0.1  Mask:255.0.0.0
  UP LOOPBACK RUNNING  MTU:16436  Metric:1
  RX packets:19 errors:0 dropped:0 overruns:0 frame:0
  TX packets:19 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0
  RX bytes:1119 (1.0 Kb)  TX bytes:1119 (1.0 Kb)

wlan0     Link encap:Ethernet  HWaddr 00:14:A5:E1:D2:B9
  inet addr:192.168.2.2  Bcast:192.168.2.255  Mask:255.255.255.0
  UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:4 errors:0 dropped:0 overruns:0 frame:0
  TX packets:11 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:834 (834.0 b)  TX bytes:1316 (1.2 Kb)
  Interrupt:20 Memory:c3000000-c3004000

sergio ~ # route
Kernel IP routing table
Destination  Gateway      Genmask       Flags Metric Ref Use Iface
192.168.2.0  *            255.255.255.0 U     2000   0     0 wlan0
23.252.112.0 *            255.255.248.0 U     0      0     0 eth0
loopback     *            255.0.0.0     U     0      0     0 lo
default      23.252.112.1 0.0.0.0       UG    0      0     0 eth0
default      192.168.2.1  0.0.0.0       UG    2000   0     0 wlan0

sergio ~ # cat /etc/resolv.conf
# Generated by dhcpcd for interface wlan0
search Belkin
nameserver 192.168.2.1
nameserver 213.156.54.80
nameserver 213.156.54.81

NB: ping www.google.com is slow, ping 192.168.2.1 is either too much 
slow or blocked.
route is slow, route -n is fast.

Thank for your patience.
Sergio
-- 
gentoo-user@gentoo.org mailing list



  parent reply	other threads:[~2006-11-27 21:09 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-26 15:48 [gentoo-user] OT: wlan0 is sssloooow Sergio Polini
2006-11-26 19:59 ` Richard Fish
2006-11-26 21:35   ` Sergio Polini
2006-11-26 22:08     ` [gentoo-user] Screen(s) found, but none have a usable configuration burmata
2006-11-26 22:31       ` Richard Fish
2006-11-27  5:32         ` burmata
2006-11-26 22:36     ` [gentoo-user] OT: wlan0 is sssloooow Richard Fish
2006-11-27 19:27       ` Sergio Polini
2006-11-27 19:28       ` Sergio Polini
2006-11-27 21:04       ` Sergio Polini [this message]
2006-11-27 21:48         ` Hans de Hartog
2006-11-27 22:54         ` Richard Fish
2006-11-28 21:53           ` [gentoo-user] OT: wlan0 is sssloooow [99% SOLVED] Sergio Polini
2006-12-11 20:56             ` [gentoo-user] OT: wlan0 is sssloooow [100% SOLVED] Sergio Polini
2006-12-12  8:15               ` Mick
2006-12-12 21:03                 ` Sergio Polini
2006-12-12  9:08               ` Alan McKinnon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200611272204.33717.sp_rm_it@yahoo.it \
    --to=sp_rm_it@yahoo.it \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox