[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#706499: Ethernet with Realtek R8169 only working with IPV6



On Fri, 2013-05-03 at 09:55 +0200, Karsten Malcher wrote:
> Am 02.05.2013 12:20, schrieb Ben Hutchings:
> > If you want us, as maintainers, to investigate a bug, you must let us decide what information we need. Please provide 
> > the whole boot log. 
> 
> On one side you want to have only bug reports with a solution

No, I want bug reports that have useful information for working towards
a solution.

> and on the other side you want to be the only one who 
> decides what information will be given in the bug report without any help from me.
> Sorry - that don't fit together.
> 
> >> First i could work with eth0 and installed debian without problems.
> >> After a reboot the problems come up.
> >> Now i use eth1, because eth0 comes not up reliable.
> > I'm still unclear on what you mean by this.  Please provide the output
> > of 'ip addr' in the case where you consider that eth0 has not come up.
> >
> > Ben.
> 
> O.K. The problem is that this is my server running without keyboard
> and screen standing in the basement.
> That's the reason why eth must come up reliable to have access.
> So it is running with the onboard 100 MB now and the 1000 MB R8169 is
> not connected.
> 
> For test purposes i can connect an additional network cable to the
> R8169 and make the tests you need.
> But it seems to be senseless for a closed bug. ;-)

I reopened the bug.

> At this time:
> 
> # ip addr
> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
>      link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>      inet 127.0.0.1/8 scope host lo
>      inet6 ::1/128 scope host
>         valid_lft forever preferred_lft forever
> 2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
>      link/ether 00:e0:52:c8:d4:38 brd ff:ff:ff:ff:ff:ff
[...]

So this interface has not been brought up.  Neither IPv4 nor IPv6 will
work.

In the syslog you sent, it appears that eth0 is brought up after every
boot, and is not brought down.  So I don't think you've sent the right
part of the log.  I need to see what the kernel says in the case that
the interface is not brought up.

Ben.

-- 
Ben Hutchings
Lowery's Law:
             If it jams, force it. If it breaks, it needed replacing anyway.

Attachment: signature.asc
Description: This is a digitally signed message part


Reply to: