On 11/12/2012 10:26 AM, Jonathan Nieder wrote:
> Patrik Nilsson wrote:
>
>> Ping doesn't work to ip address 8.8.8.8.
>
> Let's start there. What is its output?
>
100% Packet Loss.
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble?
Patrik Nilsson wrote:
> Ping doesn't work to ip address 8.8.8.8.
Let's start there. What is its output?
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20121112092
On 11/12/2012 10:06 AM, Jonathan Nieder wrote:
> Thanks. I think you misunderstood, though: I meant that we need a
> trace illustrating what it means that the connection just doesn't
> work.
>
Example:
nslookup doesn't work. Times out.
Firefox can't look up Internet addresses.
Firefox can't c
Patrik Nilsson wrote:
> On 11/05/2012 02:59 AM, Jonathan Nieder wrote:
>> Patrik Nilsson wrote:
>>> No error messages or anything else is shown: The connection just doesn't
>>> work
[...]
>>Also could you strace a
>> program that tries to connect and fai
On Sun, 2012-11-04 at 17:59 -0800, Jonathan Nieder wrote:
> Patrik Nilsson wrote:
>
> > No error messages or anything else is shown: The connection just doesn't
> > work when I try it. It is why I suspect that if a (background) program
> > holds a socket open, the kernel can't set the route. Altho
Patrik Nilsson wrote:
> No error messages or anything else is shown: The connection just doesn't
> work when I try it. It is why I suspect that if a (background) program
> holds a socket open, the kernel can't set the route. Although it reports
> the correct route.
I don't know anything about the
On 11/04/2012 07:00 PM, Jonathan Nieder wrote:
> Hi Patrik,
> I suspect there was a miscommunication here: if I understand
> correctly, Ben was looking for a simple sequence of steps and, for
> each step, a routing table from after that step. This would help him
> to understand what was happeni
Hi Patrik,
Ben Hutchings wrote:
> On Thu, 2012-11-01 at 13:58 +0100, Patrik Nilsson wrote:
>> I suspect this bug is when a task (i.e. ntp, virus updater, ...) tries
>> to connect to the Internet through a socket using the first interface,
>> holds it open, the kernel won't reroute to the new one
Giving up on this as the submitter won't explain himself.
Ben.
--
Ben Hutchings
No political challenge can be met by shopping. - George Monbiot
signature.asc
Description: This is a digitally signed message part
On 11/02/2012 06:22 AM, Ben Hutchings wrote:
> You haven't sent this:
>
>>> - The routing table (as shown by 'ip r') after each reconfiguration
>
> Ben.
>
patrik@debian:~$ ip r
213.232.200.170 via 192.168.1.1 dev eth1
192.168.1.0/24 dev eth1 proto kernel scope link src 192.168.1.3
metric 2
You haven't sent this:
> > - The routing table (as shown by 'ip r') after each reconfiguration
Ben.
--
Ben Hutchings
I'm always amazed by the number of people who take up solipsism because
they heard someone else explain it. - E*Borg on alt.fan.pratchett
signature.asc
Description: This is a d
On 11/01/2012 03:13 PM, Ben Hutchings wrote:
> On Thu, 2012-11-01 at 13:58 +0100, Patrik Nilsson wrote:
>> Package: linux
>> Version: linux-image
>
> Can we have a real version number please? (/proc/version will show the
> Debian package version for the running kernel).
>
Linux version 2.6.32
On Thu, 2012-11-01 at 13:58 +0100, Patrik Nilsson wrote:
> Package: linux
> Version: linux-image
Can we have a real version number please? (/proc/version will show the
Debian package version for the running kernel).
> Severity: important
> Tags: upstream
>
> When one lan interface is connected
Package: linux
Version: linux-image
Severity: important
Tags: upstream
When one lan interface is connected and you try to connect an other one,
often you can't connect to the Internet after that. You need to retry the
connection.
I suspect this bug is when a task (i.e. ntp, virus updater, ...) tr
14 matches
Mail list logo
