View Single Post
  #2 (permalink)  
Old 28-Jun-2009, 22:23
PV
Guest
 
Posts: n/a
Default Re: suse 11.1 extremely slow beyond my router?

On Sun June 28 2009 04:06 pm, back to suse wrote:

>
> This has been a fun excercise, lol.
>
> It started out with me upgrading my mobo to a Gigabyte GA-X48-DS4.
>
> Obviously, Windows bailed when faced with the new devices, so I had no
> choice after 3 reboots of it's lengthy time consuming self
> diagnostic/repair tools, to just reinstall.
>
> Then came the fact that Windows did not like the new NICs but of course
> there was a set of drivers included in the mobo's box so no real
> problems there. You can see where this is going right^^
>
> Hooray for shell & mkinitrd. With a quick boot in to the SUSE 10.3
> rescue shell, I mounted the drives and ran mkinitrd. Job done, the
> system instantly booted with the new mobo.
>
> However, SUSE 10.3 did not like the new nics either and no matter what
> I could do, it just was not gonna work. So, as I was planning on
> upgrading to 11.1 anyway, I did and it took less than half the time the
> similar Vista reinstall took. Not bad considering I was upgrading from
> 32 bit SUSE 10.3 to 64 bit SUSE 11.1
>
> So here's where it starts to get frustrating. The nics in question are
> the dreaded Realtek 8169 chips that apparently are actually 8168B/8111B
> chips.
>
> SUSE 10.3 saw the nics and let me supply configuration data but refused
> to accept that they were actually wired
>
> SUSE 11.1 sees the nics, lets me supply configuration data and accepts
> that they are wired.
>
> I can even access my router's admin page via a browser over the lan.
> Using the router's admin tools, I can see the Internet connection is
> working because I can resolve addresses and ping them.
>
> Yet I cannot access anything beyond my router from the SUSE system,
> regardless of whether I am using the shell or gnome, or whether I use
> dns or ip addresses. Well sort of
>
> For one thing, the dns resolver is definitely not working. I cannot
> resolve addreses in any gui or cli application.
>
> If I resolve the name of say 'BBC - Homepage' (http://www.bbc.co.uk)
> using the router's admin tools and then access the website via the ip
> address in firefox, I actualy get the page after a time span that can
> only be measured accurately in eons
>
> I cannot ping nor traceroute the dns servers which are 2 hops beyond my
> router.
>
> I checked the nic settings using ethtool and it all looks good, which
> is a relief considering all the posts I read said that the nic would
> suffer the same problems it did in SUSE 10.3.
>
> So to recap, I can access my routers admin interface using Firefox over
> the lan. The routers internal admin dns resolver and ping tools work
> perfectly. A laptop on the same lan, using the same router at the same
> time, gets instant Internet responses. Of course when the same computer
> is booted in to Vista it gets perfect Internet access using exactly the
> same nics, router and cable.
>
> My system is
>
> O/S: openSUSE 11.1 64bit (no updates/patches)
> MOBO: GA-X48-DS4
> CPU: Q6600 @ 3.2Ghz
> RAM: 4GB PC2-1066
>
> The nics are onboard and are reported as RTR8168B/8111B in the boot log
> but are loaded with the r8619 module, which is used by the MII module
> according to lsmod output.
>
> ethtool confirms the nics advertise auto negotiation and are running
> 100Mb/s full duplex on MII port, current message level 51 (decimal).
>
> Now ordinarily I would suspect that if I could solve why I cannot ping
> beyond the router, then the dns resolver problem would be solved.
>
> However, I am confused by the fact that I could load 'BBC - Homepage'
> (http://www.bbc.co.uk) by ip address in Firefox, albeit excrutiatingly
> slowly.
>
> So any ideas anyone?
>
>

back to suse;
1. If you have not done so already disable IPv6 globally with YaST and in
Firefox. If this solves your problem just quit. With some ISPs IPv6 causes
problems.
2 Assuming the above does not help, can you post the results of the following
commands:
Code:
/sbin/ifconfig -a
/sbin/route -n
cat /etc/resolv.conf
If you are using dhcp, it is possible that your router is not setting the DNS
server. In this case set a static DNS with your ISP's DNS server's IP.
(Their DNS server's address should be available on their web site)

This HowTo might be of value: http://opensuse.swerdna.org/susenic.html

--
P. V.
"We're all in this together, I'm pulling for you." Red Green
Reply With Quote