2
All settings in the modem / router are correct, and you can ssh from internally to your host meaning that your ssh / dropbear is working. The issue is not your internal network or modem. Unfortunately, your ISP has a hardened firewall not allowing forwarding traffic into your network making it so you cannot access your host externally.
2
Please make sure that you still have samba-client package installed:
sudo apt install samba-client
1
Connect via Ethernet and install wpasupplicant and net-tools.
sudo apt update
sudo apt install wpasupplicant net-tools
Use this .yaml file... use the EXACT same spacing, indentation, and no tabs...
network:
version: 2
renderer: networkd
ethernets:
enp1s0:
dhcp4: true
optional: true
wifis:
wlo1:
dhcp4: true
access-...
1
You can use something more powerful like kill -9.
First find out PID number like so:
pgrep openconnect
12345
After that, kill the process with: sudo kill -9 12345.
1
I suggest that it is Network Manager that is interfering. I also don't think that sudo ifconfig device_name on is correct. Please try:
sudo service NetworkManager stop
sudo ifconfig wlp0s20f3 down
sudo iwconfig wlp0s20f3 mode monitor
sudo ifconfig wlp0s20f3 up
Start wireshark and see if there is any improvement.
1
It's because Canonical has disabled SMB1 for security reasons. SMB2/SMB3 still works.
smbtree command also no longer works.
Either...
Use //server/pathname or //IP/pathname when using the Connect to Server, or in your /etc/fstab
or
Edit /etc/samba/smb.conf, and add this to the Network section, and restart smbd and nmbd...
# allow SMB1
client min protocol = ...
1
Modify the line in your /etc/dhcpcd.conf file of static ip_address=10.0.0.14/24 to static ip_address=10.0.0.10/24 so that it no longer tries to set the 10.0.0.14 IP address.
1
This message generally indicates that you try to remove a route from a routing table, but such a route does not exist in the table.
When bringing the interface down, ifdown is trying to remove any routes that are associated with a given interface. This message appears when ifdown "thinks" it has to remove a route (because it appears somewhere in ...
1
I had the same problem with the network being offline after an update on Ubuntu 20.x.
I found this bug report: https://bugs.launchpad.net/netplan/+bug/1922898
Here is how I was able to fix my Ubuntu 20.x servers:
Download latest netplan.io_0.102:
cd /tmp
wget http://security.ubuntu.com/ubuntu/pool/main/n/netplan.io/netplan.io_0.102-0ubuntu1~20.04.1_amd64....
Only top voted, non community-wiki answers of a minimum length are eligible
