Re: Network interface "stops working"

From: Turbo Fredriksson
Date: Tue Jan 23 2018 - 05:30:34 EST


Not sure itâs a bug yet, but anyone have any ideas on how I can find out?

> On 22 Jan 2018, at 23:32, Cong Wang <xiyou.wangcong@xxxxxxxxx> wrote:
>
> (Please always Cc netdev for networking related bugs.)
>
> On Mon, Jan 22, 2018 at 2:02 AM, Turbo Fredriksson <turbo@xxxxxxxxxx> wrote:
>> I just got a new broadband delivered at home. It is "Hyperoptic 1Gbps fiber" which comes as a ethernet connector at home. I wasnât around
>> when they connected up everything, so Iâm not sure *where* the fiber starts, but either way, I have an ethernet jack in one of my rooms.
>>
>> They also provided me with a ZTE router. I have need for my own services (firewalling, NATing, IPSEC and what not), so donât want to use
>> the provided router..
>>
>> However, Iâm having serious trouble keeping the interface up! Works for a few minutes and then just âstops workingâ. Donât know why, thereâs
>> nothing in the logs or from dmesg..
>>
>> Taking the interface down and then up again usually solves it. For a few minutes.
>>
>> Also, when running the interface (a Intel 82576 Gigabit dual port, using the igb driver - tried e1000 and e1000e but they donât find any interfaces),
>> in 1Gbps mode, the interface starts flapping up and down and I canât get a connection at all. So my interface definition runs a script to use
>> ethtool to set the speed to 100Mbps, full duplex, no auto negotiation. Which âkindaâ works (for a while, hence my problems).
>>
>> Because the provided router works just fine, Iâm sure itâs something on my Linux box (Debian GNU/Linux Jessie) that does it.. Iâve tried running
>> it without any iptables, in both static and DHCP mode but same problem..
>>
>> Iâm not a complete beginner with Linux nor networks, but this is to âclose to the hardwareâ for me. Iâm at a loss to what else to try..
>>
>> This isnât a new machine, it have served me very well for five years give or take and Iâve never had any problems with it (not to say that it still
>> canât be hardware problems, but I find that somewhat unlikely at the moment).
>>
>>
>> Could anyone please advice to what I can try to try to pinpoint the problem (and/or possibly fix it)?

Attachment: signature.asc
Description: Message signed with OpenPGP