Hot answers tagged

3

ss uses the AF_NETLINK socket layer to talk to the kernel. This is a lower level protocol but allows for data to be transferred very quickly and in large chunks. A quick strace on CentOS 7 shows it sets the transfer window to be 1Mb.


2

Sshd doesn't care where the connection is coming from, if it's configured to do a reverse DNS lookup, it does.


2

Unfortunately, that's just not going to work well—not because of the IP being on both interfaces, but because the subnet is. If your device needs to talk to 192.168.1.2, which interface should it send that traffic on? Maybe that's the customer's device trying to talk to your device, maybe it's your device trying to talk to one of your other devices. The ...


1

try; swap all cables in the route with new isolate linux and aix as only two machines on a single switch (reduce the test environment) cross over patch with static settings (if possible- reducing again) in case its the switch at fault, test with second switch get onto the switch itself and check for flapping or errors on the ports run wireshark on the ...


1

At home a I have a Lamobo R1 (ARM with 5 gigabit ethernet ports) with Jessie Debian; I have an IPsec VPN configured with StrongSwan. The server acts as router and firewalls too, with iptables. All accesses from the outside have to come via the VPN, including ssh. In addition, the IPsec VPN is configured as such to be compatible with the native VPN ...


1

You can set the option UseDNS no in the file /etc/ssh/sshd_config on your server to tell sshd(8) not to do DNS lookups.



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