LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Laptop and Netbook (http://www.linuxquestions.org/questions/linux-laptop-and-netbook-25/)
-   -   Slackware-current Wireless Problem (http://www.linuxquestions.org/questions/linux-laptop-and-netbook-25/slackware-current-wireless-problem-826786/)

Shadow-Driver 08-17-2010 10:38 AM

Slackware-current Wireless Problem
 
Hey People,
My name is Oliver and I have a problem with
my Slackware-current .
Since my Update from Slackware13 to Slackware-Current
strikes my Inet with Wireless.
Under Lan, I have a quick connection in my Browser.
With Wlan I have a connection if I using Ip Adresses.
if I use normal links like google.de the connection is very verz slow or
death but Lan is normal and quick.
Why
Sorry for my bad Englisch
oli

EricTRA 08-17-2010 02:16 PM

Hello,

Please don't double post your problem / question in multiple forums. Stick with one thread, this one for example, to keep all conversation in one place. That will be less confusing both to you and to us. Reported the other one for closure.

Kind regards,

Eric

Shadow-Driver 08-17-2010 02:25 PM

Ok sorry ,
.
Maybe it has something to do with the dns resolution? because
I can surf in my Browser wehn I do Lan or I use Ip adresses.
I need help.
The ping to google.de is under Wlan very slow.
Under Lan it is fast.

catkin 08-17-2010 02:43 PM

What is in /etc/resolv.conf and what is the output from dig google.de a) using wired connection and b) using wireless connection?

Shadow-Driver 08-17-2010 03:00 PM

I must say before I do the Update the Wlan works.
So in the resolv.conf is : nameserver 192.168.178.1 it is right then
under Slackware 13 it works.

catkin 08-17-2010 03:06 PM

Is resolv.conf identical when using both wired and wireless?

Please supply both dig outputs.

Shadow-Driver 08-17-2010 03:17 PM

Yes the resolv.conf is identical
The Outputts are you getting tomorrow.

Shadow-Driver 08-18-2010 11:31 AM

Here is the output when I take Wireless :
root@oliver-current:~# dig google.de

; <<>> DiG 9.7.1-P2 <<>> google.de
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 13480
;; flags: qr rd ra; QUERY: 1, ANSWER: 6, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;google.de. IN A

;; ANSWER SECTION:
google.de. 76 IN A 74.125.43.99
google.de. 76 IN A 74.125.43.105
google.de. 76 IN A 74.125.43.103
google.de. 76 IN A 74.125.43.147
google.de. 76 IN A 74.125.43.106
google.de. 76 IN A 74.125.43.104

;; Query time: 57 msec
;; SERVER: 192.168.178.1#53(192.168.178.1)
;; WHEN: Wed Aug 18 18:19:50 2010
;; MSG SIZE rcvd: 123


ANd here when I take wired :
root@oliver-current:~# dig google.de

; <<>> DiG 9.7.1-P2 <<>> google.de
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 55834
;; flags: qr rd ra; QUERY: 1, ANSWER: 6, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;google.de. IN A

;; ANSWER SECTION:
google.de. 148 IN A 209.85.135.106
google.de. 148 IN A 209.85.135.147
google.de. 148 IN A 209.85.135.104
google.de. 148 IN A 209.85.135.105
google.de. 148 IN A 209.85.135.99
google.de. 148 IN A 209.85.135.103

;; Query time: 7 msec
;; SERVER: 192.168.178.1#53(192.168.178.1)
;; WHEN: Wed Aug 18 18:31:09 2010
;; MSG SIZE rcvd: 123

onebuck 08-24-2010 01:14 PM

Hi,

I will not answer in the other thread any longer. As I said keep it here.

Now, how are you switching between the wireless and wired device?

What about a static setup? Try it yet?

If you are using 'wicd' have you reverted the '/etc/rc.d/rc.inet1.conf' to the original state (original defaults)?
:hattip:

Shadow-Driver 08-24-2010 02:17 PM

Im switching wireless and wired with wicd.
I`m using the orignal rc.inet1.conf
I`ve been resetet wicd to the original default but
the problem is still there.

catkin 08-24-2010 06:07 PM

So DNS is working OK for dig but the symptoms do suggest a DNS problem. Perhaps it's in the browser DNS configuration. It might be useful to test using other DNS-dependent software. Do the ftp, hosts, ping, ssh and telnet commands work OK using both connection types? Do you have another browser to test with?

Can anyone suggest other softwares to test DNS resolution?

Shadow-Driver 08-24-2010 11:25 PM

KOnquerer has the same Problem.
The programm links is ok in the terminal .
Wget too.
Gftp is i.o
The ping time is 71 ms .
And the SSH Serive is working so I thing

Shadow-Driver 08-25-2010 08:39 AM

Edit :
The Ping time from Google.de is 71 ms
So it is strange

catkin 08-25-2010 09:29 AM

Quote:

Originally Posted by Shadow-Driver (Post 4077193)
Edit :
The Ping time from Google.de is 71 ms
So it is strange

Is that wired or wireless?

Is /etc/nsswitch.conf identical when using wired and wireless?

catkin 08-25-2010 09:38 AM

Quote:

Originally Posted by Shadow-Driver (Post 4076838)
KOnquerer has the same Problem.
The programm links is ok in the terminal .
Wget too.
Gftp is i.o
The ping time is 71 ms .
And the SSH Serive is working so I thing

By "same problem" do you mean "slow or death"? Is there any pattern to the links which timeout and those which succeed? If you retry a link that timed out, can you get it the second time?

When you write "program links" do you mean commands issued from the command prompt? Which ones? Did you time them? If so were they as quick wired and wireless? If not, test again inserting time in front of the commands.

When you write i.o. do you mean OK?

An easy way to post what happened at the command prompt terminal is to copy and paste it.


All times are GMT -5. The time now is 02:46 AM.