Kent, Meni ... or anyone who knows the way things work around here ...
Should I submit a bug report on this? I don't know in which package
the bug is, or even if it really is a kernel problem.
But I think that it is clear that there is a problem here - it's not
just my the config of my machine or
If I make /etc/resolv.conf point directly to the DNS, nothing works,
on either kernel. I think the router is blocking direct DNS. I could
probably change that but don't really want to mess with it as it seems
to be working fine. If I get some time mayeb I will.
--
Daniel McBrearty
Electronics and
On Wed, Jun 01, 2005 at 04:39:31PM +0200, Daniel McBrearty wrote:
> Hi Meni
>
> The really weird thing that I don't get is that I only get the problem
> with 2.6 - not with 2.4.
>
> It seems that I'm not the only person to experience this problem:
>
> http://lists.debian.org/debian-user/2004/06/
Daniel McBrearty wrote:
It's the same in both cases. They point to the router.
IIRC, you said in another post that your /etc/resolv.conf file pointed
to your router; just for kicks, try pointing it to the DNS servers of
your ISP to see what happens.
--
Kent
--
To UNSUBSCRIBE, email to [
Hi Kent
It's the same in both cases. They point to the router.
I tried some other browsers. Firefox, mozilla and epiphany all have
the same problem. Konqueror doesn't. So it is both kernel dependent
AND browser dependent (I think firefox and moz are pretty much the
same beast underneath, so I'm n
Hi Meni
The really weird thing that I don't get is that I only get the problem
with 2.6 - not with 2.4.
It seems that I'm not the only person to experience this problem:
http://lists.debian.org/debian-user/2004/06/msg01209.html
(but this guy received no answer, and his email address no longer e
Daniel McBrearty wrote:
>Thanks Kent and Meni.
>
>Hmmm. Yes, things got a bit better after I sorted out the router (I
>had been tweaking in desperation, restored factory defaults and set up
>the DSL iface).
>
>I now have all OK with my 2.4.27 kernel. But with 2.6.8 kernel, still problems:
>- can
sorry ... I forgot to add:
1. mozilla is configured for direct connection - no proxy.
2. DNS in the linux box points to the router which forwards back to
the ISP DNS (seems to get auto-configured and I haven't changed it.
Wouldn't know what to change it to ...)
Problem is exactly the same in othe
Hi,
did you try traceroute to domain-name?
Did you check mozilla preferences?? may you have a problem with proxy defenisions??
I would try to enabale proxy on http traffic and see if that helps?
(the proxy will catch the request and try to resolve it himself - not using your dns's)
MeniOn 6/1/0
Thanks Kent and Meni.
Hmmm. Yes, things got a bit better after I sorted out the router (I
had been tweaking in desperation, restored factory defaults and set up
the DSL iface).
I now have all OK with my 2.4.27 kernel. But with 2.6.8 kernel, still problems:
- can ping hosts by name
- can ping hos
Hi,
Have you try telnet from consol to domain port 80? or to IP port 80?
Did you get a connection?
If not, do you run a firewall? if so reconfigure it or just disable it.
If you do get a connection with IP and not domain name, then you should
check /etc/resolv.conf and put there you ISP nameserver
Daniel McBrearty wrote:
>Hi
>
>Have an odd problem that I can't work out.
>
>I I recently took out my wireless networking (driver was ndiswrapper
>for a dlink card) and replaced it with a normal wired connection via
>eth0. Since then, I can ping any website as a normal user, but mozilla
>waits ind
Hi
Have an odd problem that I can't work out.
I I recently took out my wireless networking (driver was ndiswrapper
for a dlink card) and replaced it with a normal wired connection via
eth0. Since then, I can ping any website as a normal user, but mozilla
waits indefinitely for a response from tha
13 matches
Mail list logo
