[SOLVED] Intel NIC e1000e hardware unit hang

[gctwnl]

Same here. I ran an update yesterday. But I suspect an earlier PVE update already triggered this already as a guest VM on that NUC runs one of my DNS servers and it seems that one is preferred by many clients. As a result, I notice all kinds of networking issues on my clients which in the end are DNS issues, that are fixed after a while. So, I suspect I have had this issue for a while now. The issue became much worse after the last PVE update until the point that the system became unreachable and I had to go to the console. I have now added the post-up, and configured clients on the network only to use the other DNS for now. But this is such an issue that if not resolved I have to drop the whole setup.

 

[TErxleben]

Same here. I ran an update yesterday. But I suspect an earlier PVE update already triggered this already as a guest VM on that NUC runs one of my DNS servers and it seems that one is preferred by many clients. As a result, I notice all kinds of networking issues on my clients which in the end are DNS issues, that are fixed after a while. So, I suspect I have had this issue for a while now. The issue became much worse after the last PVE update until the point that the system became unreachable and I had to go to the console. I have now added the post-up, and configured clients on the network only to use the other DNS for now. But this is such an issue that if not resolved I have to drop the whole setup.

Aside from the fact that the root cause is still present after more than three years, you should reconsider your DNS setup. With DNS failover configured, the issue shouldn't affect any clients.

 

[gctwnl]

Aside from the fact that the root cause is still present after more than three years, you should reconsider your DNS setup. With DNS failover configured, the issue shouldn't affect any clients.

How would DNS failover help me with clients on the local network getting their DNS server config from DHCP? The only thing I can think of is DNS in a HA setup, a la HAproxy, but the latter only does TCP/HTTP, not UDP.

My issue is that I have two DNS servers running on my LAN with two different LAN IP addresses. I have to provide both to the clients (phones, computers) with DHCP. If the clients are stuck on trying to use the one they have been using so far even if it is unreachable, that client is stuck. What I would need is a HA way to run my (unbound) resolvers.

 

[TErxleben]

How would DNS failover help me with clients on the local network getting their DNS server config from DHCP? The only thing I can think of is DNS in a HA setup, a la HAproxy, but the latter only does TCP/HTTP, not UDP.

My issue is that I have two DNS servers running on my LAN with two different LAN IP addresses. I have to provide both to the clients (phones, computers) with DHCP. If the clients are stuck on trying to use the one they have been using so far even if it is unreachable, that client is stuck. What I would need is a HA way to run my (unbound) resolvers.

The two IP addresses are exactly your problem. This can be easily solved by "hiding" multiple DHCP/DNS servers behind one IP address.

First, search the internet for something like "pihole failover." You'll find plenty of suggestions there.

HA is by no means necessary.

 

[gctwnl]

The two IP addresses are exactly your problem. This can be easily solved by "hiding" multiple DHCP/DNS servers behind one IP address.

First, search the internet for something like "pihole failover." You'll find plenty of suggestions there.

HA is by no means necessary.

Yes I understand that. I am looking into setting up a virtual IP on my OPNsense router. Creates a SPOF, but if the router dies nothing much works anyway.

 

[TErxleben]

Yes I understand that. I am looking into setting up a virtual IP on my OPNsense router. Creates a SPOF, but if the router dies nothing much works anyway.

You'll never get rid of SPOFs. However, these problems can be easily reduced to a minimum. DHCP/DNS is quite easy to handle. In my opinion, DHCP/DNS is the most important service in a network.