8

Both of your server's network cards are connected to your home network. When you create a bridge between them you are creating a loop, which can indeed take down the network. If you're looking to build in some form of redundancy so that either NIC can stop and the server's connectivity will continue, look up "bonding" instead of a bridging. Once ...


3

Given that there is no working IPv6 configuration and the output of the second image shows the routing table before you start assigning random IP addresses, your chance that you'll be able is about 253 / 4294967296 (0.00000005890615284442) or less. The address in your first image won't work. The problem is that your computer needs a gateway to access the ...


3

Wifi adapters often require firmware to be uploaded to the adapter by the operating system, and some distributions don’t include that firmware in their default installation images because it isn’t free software (i.e., succinctly, it isn’t provided with source code in a form that’s modifiable by the user, with an appropriate license). This means that the wifi ...


3

The problem is that your internet router does not know about the network 192.168.2.0/24. The openSUSE machine knows that network and therefore answers even when accessed with the other address. If you have access to the internet router and the address 192.168.1.51 is a fixed DHCP lease, you could add a route at the internet router pointing to 192.168.2.0/24 ...


2

This is compatible with a Duplicate Selective Acknowledgement as described in RFC 2883 which adds DSACK to the SACK mechanism described in RFC 2018. Here's an example from the RFC: Because several ACK packets are lost, the data sender retransmits packet 3000-3499, and the data receiver subsequently receives a duplicate segment with sequence numbers 3000-...


2

pcap is a packet-capture library; it provides a common interface for packet capture across a number of different operating systems. tcpdump is implemented using pcap. rpcapd is a remote packet-capture dæmon, also implemented using pcap; it allows packets to be captured on one host controlled by another. pcap can connect to rpcapd, and use it to capture ...


2

I only ever used remmina binary from the repository and haven't had any performence issues. Since you're using the snap package, it might be tied to this. Maybe try using the binary from the repository and compare the performence. sudo apt install remmina Hope this helps.


2

Not sure I follow but this? # netstat -rn Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 enp0s25 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 wlp3s0 172.17.0.0 0.0.0.0 255.255.0.0 U ...


2

You will get Warning: remote port forwarding failed for listen port when there is already something listening on the specified port. You can use sudo netstat -lnp | grep 13333 if this happens again to check if something is still listening on that port. The p flag on netstat should show you the pid of whatever is listening on that port. Chances are that your ...


2

It looks as though you might need to enable keepalive functionality. Something like the following in your .ssh/config might work: Host * ServerAliveInterval 300 ServerAliveCountMax 2


2

In netstat, you won't see PIDs if it is a kernel process. Also, like @Mathias Weidner was suggesting, you won't see the PID if the user invoking netstat isn't privileged enough.


1

Using nmcli: nmcli device show |grep 'GENERAL.DEVICE:\|GENERAL.TYPE:\|IP4.ADDRESS' Including IPV6: nmcli device show |grep 'GENERAL.DEVICE:\|GENERAL.TYPE:\|IP4.ADDRESS\|IP6.ADDRESS'


1

ip -details gives addtional information like the interface kind (see later). For real parsability, choose the JSON output and a JSON parser: jq. Here's what is a one-liner but that I choose to display split over multiple lines for readability. Requires the jq utility that should be packaged in most distributions, to parse ip -json's output. jq's language isn'...


1

Based on information I've found in this blog post from Red Hat, I think I understand the purpose. (I'm not a Linux networking expert, so if anyone more knowledgeable sees any mistakes, feel free to correct me in the comments or post your own answer.) First, some background: A sit device is a type of virtual network device that takes your IPv6 traffic, ...


1

By default, systemd and its systemd-fstab-generator will treat all local disks listed in /etc/fstab as essential, and if one of those cannot be mounted at boot time, the system will drop into emergency mode. If some of your local disks are non-essential, you should consider explicitly marking them as such, by using the nofail mount option. You said "...


1

I marked @GAD3R answer as accepted because it seems to be the modern way to handle this. However, eventually I stuck to the old setup and simply added a enp3s0f0 file to /etc/network/interfaces.d with the following config for my static IPs : auto enp3s0f0:1 iface enp3s0f0:1 inet static address aaa.bb.cc.232/29 auto enp3s0f0:2 iface enp3s0f0:2 inet static ...


1

In your /etc/network/interfaces keep only: #source-directory /etc/network/interfaces.d auto lo iface lo inet loopback See 5.3. The modern network configuration without GUI to configure a static or DHCP network configuration. E,g: /etc/systemd/network/10-dhcp-enp3s0f0.network: [Match] Name=enp3s0f0 [Network] DHCP=yes /etc/systemd/network/10-static-eth0-0....


1

I'm a genius. WOL from Microsoft Store works because it knows my IP and stuff. The wakeonlan uses default broadcast port 255.255.255.255 which is incorrect since I'm on a 192.168.1.*/24. I changed command to wakeonlan -i 192.168.1.255 -p 9 <HW Mac here> and it worked. Usage wakeonlan [-h] [-v] [-i IP_address] [-p port] [-f file] [[hardware_address] ...


1

Both the sites have the same local network (192.168.1.0/24). This is a problem -- if you have 192.168.1.2 (say Device A1) in Site A wanting to connect to 192.168.1.3 (say Device B1) in Site B, 192.168.1.2 will think 192.168.1.3 is on its own local network and can connect to it directly (whereas it actually needs to route through the WireGuard servers). You ...


1

There isn't a simple, easy answer for why Ethernet drivers tend to be more reliable on Linux than Wi-Fi drivers, but there are a couple of reasons. Many servers use Ethernet cards and Linux servers are much more common than Linux desktops and laptops. Large companies would refuse to buy servers with Brand A Ethernet adapters if Brand A had shoddy drivers ...


1

InfiniBand (at least the Mellanox hardware) uses CPU offloading and can achieve very high throughput without significant CPU load. The raw speed can be well tested using the InfiniBand verbs performance tests in the perftest package, e.g. ib_write_bw. The measured data rate is usually >95 % of the specified connection rate. The iperf tool uses by default ...


1

You still need to provide device when using -netdev (ie. -netdev ... and -device is extended syntax on -nic .... See https://qemu.readthedocs.io/en/latest/system/invocation.html#hxtool-5 Thus you need something like this: qemu-system-x86_64 -hda linux.img -boot n -device e1000,netdev=n1 \ -netdev user,id=n1,tftp=/path/to/tftp/files,bootfile=/pxelinux.0 And.....


1

There is default file in the dir /etc/nginx/sites-enabled/ which hosts the default page when you hit server's IP in the browser. If you have single web app which you wish to access with server's IP then remove the default host file by running below command unlink /etc/nginx/sites-enabled/default (the filename may be 00-default or default) If you have ...


Only top voted, non community-wiki answers of a minimum length are eligible