Slack 12.2 Installation

adri_ht_ · 02-24-2009, 08:02 AM

Hey guys,

Let me start by describing my HD configuration and how I did the installation:

Code:

Disk /dev/sda: 320.0 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x7ce1c824

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1          17      136521   83  Linux
/dev/sda2   *          18        3057    24418800   83  Linux
/dev/sda3            3058       12849    78654240    7  HPFS/NTFS
/dev/sda4           12850       20199    59038875    5  Extended
/dev/sda5           12850       13894     8393931   82  Linux swap / Solaris
/dev/sda6           13895       17159    26226081   83  Linux
/dev/sda7           17160       20199    24418768+  83  Linux

I installed slack to /dev/sda7 and lilo to the root sector. The installation went smoothly without any errors. After the install is done, I go ahead configure my other Linux partition to load slackware. After that, I'm able to load slackware without problems and connect to my wired or wireless network. I can ping any internet ip as well as domains.

The most weird problem comes after this, and I truly have no clue of what's causing it. When I load any web browser (Mozilla, Konqueror) and I type a domain for a site, it takes a decade for it to load it. Sometimes I won't load it at all. At first, I thought it was a network problem, but it is not. It happens with both wired and wireless connections. Further prove, I use same cable and wireless connection in my other Linux installation it works flawlessly.

Any hint will be greatly appreciated. I really want slack in my new HD, but without web-browsing is really worthless. Thanks

Didier Spaier · 02-24-2009, 08:14 AM

Hi and welcome to lQ.

Looks like a DNS problem (it takes a long time to resolve domain names).

How did-you set up the connections: through DHCP or with static IP ?

Did you check the DNS IP in /etc/resolv.conf, to see if they are the same as in your other Linux installation ?

adri_ht_ · 02-24-2009, 12:04 PM

Quote:

Originally Posted by Didier Spaier

Hi and welcome to lQ.

Looks like a DNS problem (it takes a long time to resolve domain names).

How id-you set up the connections: through DHCP or with static IP ?

Did you check the DNS IP in /etc/resolv.conf, to see if they are the same as in your other Linux installation ?

That's what I thought at first, but it is not. The network configuration is the same since I use a script I made on both (wireless). For wired connection I use:

Code:

ifconfig 192.168.2.30 netmask 255.255.255.0
route add default gw 192.168.2.1
echo "nameserver 192.168.1.254" > /etc/resolv.conf

Where 192.168.1.254 is my top router which has been resolving domains for ever. Furthermore, when I ping a domain the ip gets resolves right away, proving that it can't be a DNS issue. Thanks for your reply!

Note: a peculiar thing is that I used to have Slack 12.1 on my older HD and it worked perfectly. Therefore, to troubleshoot even more I installed that old Slack 12.1 on the new HD the same way I did before and surprisingly I'm having the same issue??? Conclusion, it is not a kernel issue.

onebuck · 02-24-2009, 12:31 PM

Hi,

Try a third level DNS to confirm it's not the problem;

Code:

verizon DNS
nameserver 4.2.2.1
nameserver 4.2.2.2
nameserver 4.2.2.3
nameserver 4.2.2.4

Place one of the above in your '/etc/resov.conf' file as a lone DNS. Just comment out any of the the other DNS nameservers within the file.

That way you will be sure that your local is not at fault.

adri_ht_ · 02-24-2009, 09:44 PM

Quote:

Originally Posted by onebuck

Hi,

Try a third level DNS to confirm it's not the problem;

Code:

verizon DNS
nameserver 4.2.2.1
nameserver 4.2.2.2
nameserver 4.2.2.3
nameserver 4.2.2.4

Place one of the above in your '/etc/resov.conf' file as a lone DNS. Just comment out any of the the other DNS nameservers within the file.

That way you will be sure that your local is not at fault.

That's what I just did and Indeed there goes my problem. Now my question is: why would Slackware slow down the DNS lookup when using an internal DNS(private ip DNS that calls the public DNS)? I would call this a bug, because every other distribution and even windows work find with an internal DNS. Thanks.

onebuck · 02-24-2009, 11:28 PM

Hi,

Quote:

Originally Posted by adri_ht_

That's what I just did and Indeed there goes my problem. Now my question is: why would Slackware slow down the DNS lookup when using an internal DNS(private ip DNS that calls the public DNS)? I would call this a bug, because every other distribution and even windows work find with an internal DNS. Thanks.

Apparently you don't have the DNS setup properly for your LAN if it works with a external third level DNS. I don't think it's a bug but a problem with your DNS server. Whoa!

I just went back to read your previous response;

Code:

ifconfig 192.168.2.30 netmask 255.255.255.0
route add default gw 192.168.2.1
echo "nameserver 192.168.1.254" > /etc/resolv.conf

Is that a typo in the above? You setup the interface with '192.168.2.30' with your DNS setup with '192.168.1.254'. How do you have your network setup? What's the output of 'route -n'?

adri_ht_ · 02-26-2009, 05:47 AM

Quote:

Originally Posted by onebuck

Hi,

Apparently you don't have the DNS setup properly for your LAN if it works with a external third level DNS. I don't think it's a bug but a problem with your DNS server. Whoa!

I just went back to read your previous response;

Code:

ifconfig 192.168.2.30 netmask 255.255.255.0
route add default gw 192.168.2.1
echo "nameserver 192.168.1.254" > /etc/resolv.conf

Is that a typo in the above? You setup the interface with '192.168.2.30' with your DNS setup with '192.168.1.254'. How do you have your network setup? What's the output of 'route -n'?

Let's say my setup is:

Code:

echo "nameserver 192.168.2.1" > /etc/resolv.conf

Still it does the same. The above is not a typo because the network 192.168.1.254/24 is on top of 192.168.2.1/24 which is performing NAT. I also tried my computer at the 192.168.1.254/24 network level and the browser lag stands.

Like I said before, I doubt the DNS setup is wrong because any other OS w/ the same physical medium does not have this problem. My DNS Server is a Netopia Router (Gateway) that points to an AT&T DNS Server.

Let me double state issue again. Connection is good, domains get resolved w/o problems but web browsers take a hell of a long time to download any web site. I should really try wireshark once I have a spare time in order to troubleshoot the problem even more. Nevertheless if any of you have an internal DNS pointing to the outside and it works without problem w/ Slack 12.2 let me know. In that case, I have no logical network explanation for this. Thanks

onebuck · 02-26-2009, 07:16 AM

Hi,

Post the 'route -n'.

adri_ht_ · 02-26-2009, 09:37 PM

Quote:

Originally Posted by onebuck

Hi,

Post the 'route -n'.

Here it is:

Code:

root@darkstar:~/Desktop# 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 wlan0
127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo
0.0.0.0         192.168.2.1     0.0.0.0         UG    0      0        0 wlan0

ISP > Default Gateway (192.168.1.0/24) > Router (192.168.2.0/24)

I'm on the second tier and both routers are performing NAT. I have had this setup for years working perfectly fine. I think someone else should test Slack as I have it set up and see the outcome. Thanks

62chevy · 02-26-2009, 10:22 PM

Quote:

Originally Posted by adri_ht_

Here it is:

Code:

root@darkstar:~/Desktop# 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 wlan0
127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo
0.0.0.0         192.168.2.1     0.0.0.0         UG    0      0        0 wlan0

ISP > Default Gateway (192.168.1.0/24) > Router (192.168.2.0/24)

I'm on the second tier and both routers are performing NAT. I have had this setup for years working perfectly fine. I think someone else should test Slack as I have it set up and see the outcome. Thanks

You keep saying your default Gateway 192.168.1.0/24 but route -n is saying your Gateway is 192.168.2.1. Try making your Gateway 192.168.2.1 and that should solve the problem. Or you could use Dhcpc and let that set your network up.

Hope this helps.

GazL · 02-27-2009, 06:17 AM

Quote:

Originally Posted by 62chevy

You keep saying your default Gateway 192.168.1.0/24 but route -n is saying your Gateway is 192.168.2.1. Try making your Gateway 192.168.2.1 and that should solve the problem. Or you could use Dhcpc and let that set your network up.

Hope this helps.

Don't get hooked up on the .2 network. I think what he's saying is he has....

Code:

    |---- 192.168.2/24 -----|          |------ 192.168.1/24 -----|
Slackware Box                NAT BOX                        ROUTER to ISP
192.168.2.30        192.168.2.1 | 192.168.1.?               192.168.1.1

Adri, if you don't use it you might want to try blacklisting the ipv6 module on you slackware box. I had a similar problem and that seemed to help for me, though I never really got to the bottom of why.

Might also be worth disabling all the plugins and javascript in the browser just to rule out anything that may be going wrong in there.

If you want to rule out dns, you could always add an host entry for one of the sites that you're experiencing the problem with and see if that makes a difference too.

acummings · 02-27-2009, 05:37 PM

Does your dmesg ever show any irq prob.?

(if your lan interface runs out of water at the water cooler) water/resource needed, don't cut off or hinder the stream.

Slackware 12.2 does not like when (often is the default) motherboard bios setting is set to "no, not a plug and play OS"

Slackware 12.2 likes bios set on "Yes, OS is a plug and play OS"

Quote:

if any of you have an internal DNS pointing to the outside and it works without problem w/ Slack 12.2 let me know.

Slackware 12.2 on 2 boxes now. at&t dsl internet

Latest 2wire gateway (my DNS points to this, which this, in turn, relays to my ISP's name servers.

Works fine. Slight lag at times (dang modern web pages with 24 plus different nameserver lookups, loading portions of the page from all over the place).

But, now dnsmasq implemented and working superbly on one of the two boxes (has its config to be so only for to benefit the box dnsmasq is on -- no nat, no routing, this box). Not even a slight lag now. Web page startle me, fly in my face -- what was that -- loaded so quick.

The other box is no different. dnsmasq will soon go on it too (this box is for a friend's household, not to be here a lot longer)

squid and adzapper are going on these boxes too. My friend's I.S.P. will like my friend (easy on bandwidth).

root@P5Q:~# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 192.168.1.254 0.0.0.0 UG 1 0 0 eth0
root@P5Q:~# ifconfig
eth0 Link encap:Ethernet HWaddr 00:1f:c6:e7:d4:f4
inet addr:192.168.1.251 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::21f:c6ff:fee7:d4f4/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
<snipped>
Alan.

adri_ht_ · 02-27-2009, 06:37 PM

Quote:

Originally Posted by GazL

Don't get hooked up on the .2 network. I think what he's saying is he has....

Code:

    |---- 192.168.2/24 -----|          |------ 192.168.1/24 -----|
Slackware Box                NAT BOX                        ROUTER to ISP
192.168.2.30        192.168.2.1 | 192.168.1.?               192.168.1.1

Adri, if you don't use it you might want to try blacklisting the ipv6 module on you slackware box. I had a similar problem and that seemed to help for me, though I never really got to the bottom of why.

Might also be worth disabling all the plugins and javascript in the browser just to rule out anything that may be going wrong in there.

If you want to rule out dns, you could always add an host entry for one of the sites that you're experiencing the problem with and see if that makes a difference too.

Yeah, maybe I didn't explain very well my network setup but you got it on top. The network 192.168.2.0 is below 192.168.1.0. In other words, the WAN interface of 192.168.2.1 resides in the 192.168.1.0/24 network.

I will try all suggestions as soon as a have a bit of free time. Thanks to all of you.