networking – Ubuntu 16.04: WiFi connection unavailable after shutdown (Network Unclaimed)

After restarting the machine, WiFi became unavailable.

I ran lshw -c network, and here is the output:

*-network UNCLAIMED
description: Ethernet controller
product: Ethernet Connection (7) I219-V
vendor: Intel Corporation
physical id: 1f.6
bus info: pci@0000:00:1f.6
version: 10
width: 32 bits
clock: 33MHz
capabilities: pm msi bus_master cap_list
configuration: latency=0
resources: memory:a1100000-a111ffff

I also ran lspci:

  • 00:00.0 Host bridge: Intel Corporation 8th Gen Core Processor Host
    Bridge/DRAM Registers (rev 07)
  • 00:02.0 VGA compatible controller: Intel Corporation Device 3e92
  • 00:12.0 Signal processing controller: Intel Corporation Cannon Lake
    PCH Thermal Controller (rev 10)
  • 00:14.0 USB controller: Intel Corporation Cannon Lake PCH USB 3.1
    xHCI Host Controller (rev 10)
  • 00:14.2 RAM memory: Intel Corporation Cannon Lake PCH Shared SRAM
    (rev 10)
  • 00:16.0 Communication controller: Intel Corporation Cannon Lake PCH
    HECI Controller (rev 10)
  • 00:17.0 SATA controller: Intel Corporation Cannon Lake PCH SATA AHCI
    Controller (rev 10)
  • 00:1f.0 ISA bridge: Intel Corporation Device a308 (rev 10)
  • 00:1f.3 Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10)
  • 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller
    (rev 10)
  • 00:1f.5 Serial bus controller (0c80): Intel Corporation Cannon Lake
    PCH SPI Controller (rev 10)
  • 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection
    (7) I219-V (rev 10)

My machine is running on Ubuntu 16.04:

  • LSB
    Version: core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch
  • Distributor ID: Ubuntu
  • Description: Ubuntu 16.04.6 LTS
  • Release: 16.04
  • Codename: xenial

Any help would be much appreciated.

Thank you very much

networking – Intermittent connection failures to Kubernetes service on GKE

I’ve been trying to diagnose this issue for several days and have a pretty good picture what is happening, but still no idea why.

The symptom is requests to different Services with failing TCP network connection (EHOSTUNREACH, ECONNREFUSED, Connection reset by peer, No route to host, Connection refused, Connection timed out, etc) from other Pods. I’ve gone through logs in detail around one incident and for some reason no request was sent downstream to any of the Pods in the ReplicaSet backing the Service for 9 seconds.

I couldn’t find any obvious signs why traffic to Pods stopped or restarted and this what I’d need some help with, not really sure where else to look or what to try.

There are a few more things which might be relevant:

  • Readiness probe requests went through and responded to successfully every second – these were the only requests reaching Pods
  • DNS resolution seems to be working as some Pods logged being unable to connect to the Service’s resolved IP
  • Cluster logs showing io.k8s.core.v1.endpoints.update API calls around the outage, but Node IPs were in addresses (not notReadyAddresses) list
  • We’re running Kubernetes 1.15 and 1.16 on GKE, unfortunately not VPC-native (alias IP) as the clusters were created a few years ago
  • We don’t have Istio or any other service mesh running, but I’m very tempted now

Thanks in advance for any suggestions!

networking – Updated to 20.04 Epson L6170 Networked Printer Not Working

I updated to 20.04 a week back, and I can no longer print to our network printer. The printer shows up in settings, but any time I try to print something, it fails. I have tried printing from Chrome, Document Viewer, and Libre Office. In Chrome, the printer does not even appear. In the latter two, the name shows up, but printing fails.

I have removed the printer and added it again. I have uninstalled ippusbxd and tried re-adding the printer. I have installed the Epson Linux drivers. Every time, the printer is detected, but something fails in the process of adding it and I still cannot print.

It was working perfectly in 18.04 for a year. There is a lot of information on fixing HP printers in 20.04 lying around, but none for Epson. The only thing I have not tried that I saw suggested is installing 20.04 from scratch because that seems rather extreme for a printing problem. Thank you for any help you can offer.

networking – How do you prevent a Windows Server 2019 network connection profile with no default gateway from reverting to “Public”

I am bringing up a new site and installing dual homed Windows 2019 RAS/Web servers. The interfaces on the DMZ must have a default gateway defined or they simply don’t work. The “internal” interfaces do not have a default gateway defined and this is fine once systems are attached to a domain controller

But while these systems are stand-alone, rebooting reverts the internal NICs profile to “public”. I, of course, change it back with Set-NetConnectionProfile. But next reboot and we are back where we started.

It is pretty darn annoying since I can no longer RDP to them! I am wondering if anyone has found a simple solution to this behavior.

Not interested in anything convoluted; no registry hacks or the like. As I say, once my domain controllers are up, this will take care of itself. But I deal with this incredibly moronic behavior (hope you are listening, Microsoft) every time I bring up a Windows site.

networking – How to route 2 interfaces to the same destination IP address

I have a RPi with two different interfaces (wwan0, wwan1) each one with one IP provided by two different wireless network operators.

The RPi has to communicate with a server for the correct fucntioning of the system. The problem is that the two interfaces have to connect with the server, that is, with the same IP address. Therefore it is difficult to get the goal as the RPi will have the output route to get the server just to one interface (wwan0 or wwan1).

As the type of traffic that I want to send is different, could it exist any special routing to do it? I want to send ftp* traffic through wwan0 and the rest of the traffic trhough wwan1. Is it possible?

*The FTP traffic is started by the server (RPi <—–FTP req— Server).

Thanks in advance

networking – Connect from OVH SSH server in sftp

I have a website hosted with OVH. I want to use the ssh server to connect to an other server to send a file in SFTP.
But when I do the sftp command the answer is:

ssh: connect to host b2b-sftp.clip.engie.com port 22: Connection refused
Couldn’t read packet: Connection reset by peer

And when I try a simple curl command: curl ifconfig.me I have the answer:

curl: (7) Failed to connect to ifconfig.me port 80: Connection refused

wireless networking – Windows 10 machine periodically shows Wi-Fi as “no internet available”, even though other devices work fine. How to debug?

I’m using a brand new Dell laptop with Windows 10, connected to a WiFi network. Periodically the machine indicates the Wifi connection as “no Internet available”, at which point I cannot even log into the router’s admin page. Reconnecting to the Wifi usually helps restore connectivity. All other devices are working fine.

How do I debug this issue to figure out what’s wrong?

networking – Wireless and Wired networks don’t work

I have this issue with my Ubuntu budgie 20.04 which both wired and wireless networks don’t work any more. I had this problem with wireless before and I reinstalled the os to fix it! It worked fine for a month but slowly the wireless network got disabled in middle of work and now after many restarts and shutdowns, it may work for 1 minute! today the same is happening with the wired connection but The odd thing is that the problem is only with the Ethernet cable connection and when I use usb and my mobile usb tethering option, my laptops internet works fine! I don’t know whether it is software or hardware and after many searches and command I couldn’t figure out the problem. Please help!

farzin@farzin-X541UVK:~$ lsb_release  -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 20.04.1 LTS
Release:    20.04
Codename:   focal

networking – SSH connection refused on no-ip but allowed on local

Hello I am quite recent to the linux server enviroment and I’ve been trying to set an old laptop as a webserver with nginx

I followed this tutorial for securing my server:
tutorial for securing the ssh access

Then I proceeded to portforward my router to allow remote ssh and also opened up port 80 to test if I could connect the server as a subdomain to a domain I already own.
After that I enabled No-Ip on my router and set up a dynamic DNS for my IP, so that I could ssh from that dns from anywhere

However now I am facing the following problems:

  • I cannot ssh via my dynamic dns from No-ip but I can ssh via the local IP of the ‘server’
  • If I try to run $ ssh -p MYPORT user@no-ip-address, I get this in return:
    • ssh: connect to host no-ip-address port MYPORT: Connection refused.

I have checked if my no-ip dns has the port open in here and it tells me that the port I want to use to ssh into the server is open.

I also linked this server as a subdomain of a domain I already own with nginx and whilst the server is connected to that subdomain, if I try to telnet that subdomain it is linked to my routers public IP as expected but I also get the Connection refused error that I get when trying to ssh to the server.

Thanks in advance!

EDIT: I am using Ubuntu Server 20.04 LTS

networking – Docker: Converting an existing legacy system to Dockerized form while maintaining original network scheme

I’m in the midst of a project that made to convert an existing VOIP legacy system into a dockerized form. The existing system consists of 5 different Linux machines, each machine is having 2 different network interfaces – one exposed to the public WAN, and the other is a private Lan network. I plan on creating a docker compose file for setting up the orchestration.

The network roughly looks like this:

Server #1 Eth0: IP 192.168.0.200/24 Eth1: IP X.X.X.65/27

Server #2 Eth0: IP 192.168.0.201/24 Eth1: IP X.X.X.66/27

Server #3 Eth0: IP 192.168.0.202/24 Eth1: IP X.X.X.87/27

Server #4 Eth0: IP 192.168.0.203/24 Eth1: IP Y.Y.Y.240/27

Server #5 Eth0: IP 192.168.0.204/24 Eth1: IP Y.Y.Y.241/27

Servers 1-3 are part of the same subnet, so are servers 4-5.

I am trying to find the best way to convert this network setup into docker networks, I want every container to preserve his public IP (the one on Eth1, meaning that traffic generated from the container will keep the same public IP it had on the original server), but also to be able to communicate with every other docker container on the same private net, while also keeping it easily managable and having the least overhead possible.

Would it be possible to mix between a Bridge network and connect every docker container to it, while also having a Macvlan network for each docker container which will bind to a different network interface on host level?

Can I create only 2 network interfaces for the host machine, each for a different subnet, while maintaining the different IP addresses on them (one network interface will consist of 2 IPs, the other one of 3, and each interface will have a corresponding Macvlan docker network)?

Is there a better way to make this work?