Salix Forums

I am waiting for Salix 14.2 and playing with other Distros...
So I figured out, that the couple Firefox/Thunderbird of other Distros
is much faster than in Salix 14.1!
(Chromium is fast in new Zenwalk but Firefox/Thunderbird has
the same problem) I have no virtual machine!

There is a notable symptom:
I also have tested with an second router at home (from my company)
There are no issues with Firefox and Thunderbird!!!
Only the constellation private Router-Slackware-Firefox slows down
surfing. (DNS-requests - "looking up ... "; transfering Data is perfect)
So neither the kernel or Firefox/Thunderbird are guilty - it is only the constellation!

I have solved the problem with the parameter
network.dns.disableIPv6 "true" in "about:config"
Now Firefox and Thunderbird are as fast as in the other distros!

But now I am in doubt with this solution.
Is there a better one?
Can I solve this problem with a "sysctl" parameter or with "nscd"?
Is there a specific feature to activate in the Slackware-kernel?
(for DNS-Lookup and IPv6)

Thanks

OK - if nobody wants to write to me, then i write with myself

I have take a step forward!
Firefox/Thunderbird has nothing to do with it!
If I start "spi -u", for instance, it requires really a lot of time!
This behaviour never attract attention before because our internet link was very bad.
But now we got fibreglass and I have the problem with DNS/ipv6.

Then I have "blacklist ipv6" and the DNS-Lookup was perfect! ("spi -u" was very fast)
I forgot to mention: I have tested on 2 Computers and both has equal Qualcomm Atheros AR2417 Wireless Network Adapters.

It is insane:
When I start "spi -u" on my Salix-Laptop the DNS-Speed is perfect (it's a Intel-Wlan)
So i thought, it is a problem with the ath5k-Modul...
But why does it work with the company-router? (same internet link)

Ok - so I tested again with other Distros (Solus and Manjaro) and made a countercheck.
Then I recognised there was no ipv6-Modul loaded!
There are apparently rarely situations where the ipv6-Module disturbs!
So I can precise my question:
Is there really need of this ipv6-Module?
Why is it loaded in Slackware and not in other Distros?

Thanks

sjox wrote:OK - if nobody wants to write to me, then i write with myself

I have take a step forward!
Firefox/Thunderbird has nothing to do with it!

That does not look like a problem with Salix. Maybe that's why no one has responded so far.

I tried your configuration change. A change I could only notice when I have greatly raised the expectation level.

sjox wrote:If I start "spi -u", for instance, it requires really a lot of time!
This behaviour never attract attention before because our internet link was very bad.
But now we got fibreglass and I have the problem with DNS/ipv6.

Then I have "blacklist ipv6" and the DNS-Lookup was perfect! ("spi -u" was very fast)
I forgot to mention: I have tested on 2 Computers and both has equal Qualcomm Atheros AR2417 Wireless Network Adapters.

It is insane:
When I start "spi -u" on my Salix-Laptop the DNS-Speed is perfect (it's a Intel-Wlan)
So i thought, it is a problem with the ath5k-Modul...
But why does it work with the company-router? (same internet link)

Ok - so I tested again with other Distros (Solus and Manjaro) and made a countercheck.
Then I recognised there was no ipv6-Modul loaded!
There are apparently rarely situations where the ipv6-Module disturbs!
So I can precise my question:
Is there really need of this ipv6-Module?
Why is it loaded in Slackware and not in other Distros?

E.g., the man page for the Linux IPv6 protocol implementation says:
IPv4 connections can be handled with the v6 API by using the v4-mapped-on-v6 address type; thus a program only needs to support this API type to support both protocols. This is handled transparently by the address handling functions in the C library.
How would you call that? Simplification?
With Slackware, Salix respectively, we are therefore a bit further than the others.

And then, Salix is all in all, ready to use. Since it would disturb if IPv6 still have to be fumbled in. So it's good as it is, I think.

From your first message: I am waiting for Salix 14.2 and playing with other Distros...
You could be deceived and go astray.

But if you have time, you could help test Salix Xfce 14.2alpha1 and play around with it.

Hi Westms!

You wrote about expectation level!
It is really boring if you are waiting and you see "looking up" in the bottom left
corner of Firefox but now I can present you numbers!

I had a brilliant idea - I installed Slackel on my netbook an made the "SPI-Test"
I start "spi-u" and measure the time...
(of course there is nothing to update - it's the second run)

Here the results with ipv6 activated:
1) attached with Thomsen Speedtouch-DSL-Modem: 34 seconds
2) attached with Pirelli PRGAV4202N-DSL-Modem: 132 seconds

Here the results with ipv6 blacklisted:
1) attached with Thomsen Speedtouch-DSL-Modem: 34 seconds
2) attached with Pirelli PRGAV4202N-DSL-Modem: 29 seconds

It's insane - the Pirelli is now faster then Thomson!
(But 5 seconds depending from Internet-Situations and are irrelevant)

I have also tested with my Desktop-PC with different WLAN-Adapter.
TP-LINK TL-WN350GD (PCI card) and TP-LINK TL-WN721N (Usb-Stick).
I started Slackel Live - so the ipv6 Modul was aktivated.
The measurement was about equal!

In the resolv.conf is booked 10.0.0.138 (Pirelli)
or 192.168.0.254 (Thomson)
The DNS-Server is always the Modem.

Interesting:
The resolution of "www.slackel.gr" is always fast!
The resolution of "salix.hostingxtreme.com" lasts "forever"
(Pirelli and activated ipv6-modul)


Conclusion:
The lookup-Process depends of the Modem, the Internet address AND the Modul ipv6!
Now i have to inform me how to manipulate the modem or to manipulate the "resolv.conf" with a fixed DNS-Server...
What do you mean?

And sorry for playing with other Distros
I hope to concilliate by using Slackel!
(for this specific tests i don't want to use a alpha version)

Joking aside:
Salix (and Xfce) is truly the best distribution for me!
The other distros growing more bloated and complex!


Thanks

Hi!

I think I have found the answer but i don't realize it!
There is a difference between the "resolv.conf" of Thomsen Speedtouch-DSL-Modem (the good guy)
and Pirelli PRGAV4202N-DSL-Modem (the bad one).

The Pirelli send me:

search home (or domain home in Slackel)
nameserver 10.0.0.138

The Thomson send me:

search lan (or domain lan in Slackel)
nameserver 192.168.0.254

Now I only have to change "domain home" -> "domain lan" and it works!

I don't understand why this solution solve the problem with ipv6-modul and designated IP-addresses!
The address "http://salix.hostingxtreme.com" now is as fast as "www.slackel.gr"
But "www.slackel.gr" is fast every time - doesn't matter if "domain home" or "domain lan"
(or activated/not activated ipv6-modul)
I can replicate this solution every time!

With other words:
If i blacklist the ipv6-modul ALL DNS-resolution is fast!
If i activate the ipv6-modul - I have to book "domain lan" in the "resolv.conf" or the resolving of
designated IP-addresses last intolerable long!

I think the next step is to call my provider and ask how i can avoid the line "domain home"?

Hi sjox,

you have a very terrible problem that you have perhaps not yet realized.

Your resolv.conf contains local IP addresses for the nameservers. Perhaps you run local DNS servers in the DSL modems. But why? You like to have DNS IP addresses assigned to the nameserver options in resolv.conf.

Are these DSL modems DSL routers with integrated DSL modems and the routers can be used as such or are the DSL modems crippled DSL modem routers?

The three IP address intervals for local use are: The name server DNS IP addresses should are from the your internet service provider or from other DNS address services.

sjox wrote: search home (or domain home in Slackel)
nameserver 10.0.0.138

The Thomson send me:

search lan (or domain lan in Slackel)
nameserver 192.168.0.254

You must not ask your ISP. 10.0.0.138 and 192.168.0.254 do not come from your provider. Rather, you should check the configurations of both DSL modems. Those configurations are not even the same, otherwise they would use the same local IP addresses.

You are lucky to be able to play with various DSL modems. I can not change mine. Which (German) provider do you use?

Hi Westms!

I think I have "solved" the problem, but one by one...

--> "Perhaps you run local DNS servers in the DSL modems."
YES!

--> "or are the DSL modems crippled DSL modem routers"
YES
(The Pirelli is a cheap one - designed for individual deposits -
the Thomson is the better one, designed for corporate customers)

The IP-configuration was send from the modem (dhcp)!

My provider is "A1" in Austria: "https://www.a1.net"
The provider of my company is also "A1"

I haven't not ask my provider yet, because I think he will fob me off!
(only support MS-Windows)

I hope you are interested in further tests?
I have installed bind and tested with "dig", "nslookup" and "host".
No matter how - it is fast and perfect - I can't find any problem...

But now, I think, it becomes interesting again...
I edit my "resolv.conf" and made various "spi-u" tests:
I changed the "domain" to "f**k_you" or "blablabla" or "HOME" and other nonsense.
E.g. it looks like:

# Generated by dhcpd from wlan0.dhcp
domain f**k_you
nameserver 10.0.0.138

The DNS-Lookup is always(!) fast and perfect!
I remember: always!

Here are the numbers:
(tested with "time spi -u")

it last between 30 - 35 seconds with aktivated ipv6
it last between 25 - 30 seconds with deaktivated ipv6

Then I changed the string to "domain home" and aktivated ipv6!

The result: 5 Minutes and 40 seconds
(it last more then 5 minutes longer - this is not an orthographic mistake)
The resolution of "salix.hostingxtreme.com" and "sourceforge.net" last "forever"
"Sourceforge.net" was come along after update/upgrade of the new Slackel.

Remember:
if i deactivate the ipv6-modul it is fast again (30-35 seconds)
It seems only the string "home" (case-sensitive) get the module out of step...

Then i have made the ultimate test:

I connected to the Thomson-Modem (the good one) and booked "domain home" in the "resolv.conf"
The result: The "time spi-u" test last about 33 seconds!

This is really nasty:
There is NO general problem with the ipv6-modul and NO general problem with the Pirelli-modem!
I only have misfortune with the mix of Pirelli-modem and ipv6-modul

Conclusion:
a) I have to overwrite the "resolv.conf" after starting!
b) I handle the Pirelli-modem to send another domain-string.
c) or I ask my provider for a substitution of the Pirelli-modem.

What do you think?
Thanks

I have made my choice:
To prevent the dhcpcd daemon from overwriting "resolv.conf" you have to book
"nohook resolv.conf" to the last section of "dhcpd.conf!
It works only after one reboot! (After the first reboot the resolv.conf is empty!)

Now its looks like:
search nothing
nameserver 10.0.0.138

And it works for me...
Maybe there is a firmwareupgrade for the Pirelli in few month, that solve
this maniac problem...
Thanks

since this is working for you can add these two lines in the end of /etc/rc.d/rc.local
It is the last script is executed at boot

echo search nothing > /etc/resolv.conf
echo nameserver 10.0.0.138 >> /etc/resolv.conf

sjox, after your problem description, I had already the feeling it could be incorrectly configurations of the INET1 level and the DSL router modem.

Now I have procured the manual for the 'Pirelli PRGAV4202N' and am now sure. The router is misconfigured and all other problems result from that. The performed "corrections" of INET1 level in Salix, are only aggravations. You do not run a DNS server in the DSL router modem, because this router does not have a DNS server.

To obtain a DNS server from the provider automatically, select in router firmware: Engl.: drop down menu 'DNS Server' -> 'Obtain DNS Server Address Automatically'.

If instead, a different server is required for address resolution, then choose: Engl.: drop down menu 'DNS Server' -> 'Use the Following DNS Server Addresses' and specify the desired addresses. Suitable addresses are previously communicated by the provider. If you do not want to use these, then any other DNS IP address server can be used.

10.0.0.138 and 192.168.0.254, are not appropriate addresses, because those are the addresses of the router gateway.

If you are dissatisfied with the state reached, perhaps, because the current function is bent toward by force and it may yet go more elegant, perhaps try it again as described above. Before return to the initial state in Salix and router.