QNAP network question

Paul van der Vlis

unread,

Nov 29, 2020, 8:40:03 AM11/29/20

to

Hello,

I am using Debian 10 on an QNAP TS-219.

What I see is that the network gives problems, the link goes up and down
all the time. Anyone an idea what it can be? (see log at the end)

I've changed the cable and did a reboot on the switch, but this did not
help.

With regards,
Paul van der Vlis

From /var/log/syslog:
-----------
Feb 14 11:48:59 qnap kernel: [ 2228.540349] mv643xx_eth_port
mv643xx_eth_port.0 eth0: link up, 100 Mb/s, full duplex, flow control
disabled
Feb 14 11:49:00 qnap ntpd[617]: Listen normally on 565 eth0
192.168.178.133:123
Feb 14 11:49:00 qnap ntpd[617]: Listen normally on 566 eth0
[2001:980:beb0:1:208:9bff:fede:f83]:123
Feb 14 11:49:00 qnap ntpd[617]: Listen normally on 567 eth0
[fe80::208:9bff:fede:f83%2]:123
Feb 14 11:49:00 qnap ntpd[617]: new interface(s) found: waking up resolver
Feb 14 11:49:01 qnap kernel: [ 2230.288024] mv643xx_eth_port
mv643xx_eth_port.0 eth0: link down
Feb 14 11:49:02 qnap kernel: [ 2231.979558] mv643xx_eth_port
mv643xx_eth_port.0 eth0: link up, 100 Mb/s, full duplex, flow control
disabled
Feb 14 11:49:04 qnap kernel: [ 2234.006064] mv643xx_eth_port
mv643xx_eth_port.0 eth0: link down
Feb 14 11:49:05 qnap ntpd[617]: Deleting interface #565 eth0,
192.168.178.133#123, interface stats: received=0, sent=1, dropped=0,
active_time=5 secs
Feb 14 11:49:05 qnap ntpd[617]: 192.168.178.1 local addr 192.168.178.133
-> <null>
Feb 14 11:49:05 qnap ntpd[617]: Deleting interface #566 eth0,
2001:980:beb0:1:208:9bff:fede:f83#123, interface stats: received=0,
sent=0, dropped=0, active_time=5 secs
Feb 14 11:49:05 qnap ntpd[617]: Deleting interface #567 eth0,
fe80::208:9bff:fede:f83%2#123, interface stats: received=0, sent=0,
dropped=0, active_time=5 secs
--------

--
Paul van der Vlis Linux systeembeheer Groningen
https://www.vandervlis.nl/

basti

unread,

Dec 7, 2020, 4:40:04 PM12/7/20

to

Hello,
logs are from Feb 14 11:48:59.
Is the problem still present?

Best regrads

basti

unread,

Dec 11, 2020, 10:50:03 AM12/11/20

to

On 11.12.20 13:27, Paul van der Vlis wrote:
> Op 07-12-2020 om 22:22 schreef basti:

>> Hello,
>> logs are from Feb 14 11:48:59.
>> Is the problem still present?
>

> Yes, the system time was wrong.
> ntpd does not work always correct...
>
> With regards,
> Paul
>
>

Hello, please write to the ML so anybody can help you.
Which version of Debian/ Kernel do you run?

I think that is a Problem of buster, search at mailinglist for more info's.
Systemd should update your time, please post timedatectl or run ntpdate
at startup.

In bullseye the error is fixed but:

- it is not easy to upgrade to bullseye because of the limitation of
this size for the kernel
- at the moment it is not pretty clear if bullseye will release for armel

Best regards,

Paul van der Vlis

unread,

Dec 11, 2020, 12:00:03 PM12/11/20

to

Op 11-12-2020 om 16:29 schreef basti:

>
>
> On 11.12.20 13:27, Paul van der Vlis wrote:
>> Op 07-12-2020 om 22:22 schreef basti:
>>> Hello,
>>> logs are from Feb 14 11:48:59.
>>> Is the problem still present?
>>
>> Yes, the system time was wrong.
>> ntpd does not work always correct...
>>
>> With regards,
>> Paul
>>
>>
>
> Hello, please write to the ML so anybody can help you.

Sorry for my mistake!

> Which version of Debian/ Kernel do you run?

Debian 10 with default kernel.

> I think that is a Problem of buster, search at mailinglist for more info's.

You mean the interface what goes up/down all the time?

> Systemd should update your time, please post timedatectl or run ntpdate
> at startup.

My problem is not NTP. It's about the network interface what goes
up/down all the time.

> In bullseye the error is fixed but:
>
> - it is not easy to upgrade to bullseye because of the limitation of
> this size for the kernel
> - at the moment it is not pretty clear if bullseye will release for armel

I know.

With regards,
Paul