cannot access my network and NAS.
I have tried with Manjaro in Live environment and there it works.
Could it have something to do with the firewall. I have not changed anything there.
Is Noob on this with networking
cannot access my network and NAS.
You're going to have to provide more information - noone here has any knowledge about how your network is arranged.
To rule the firewall out
First stop it
systemctl stop firewalld
Then if this allows you to connect to nas
Then you will have to try different zones in firewalld
For ex see if trusted zone works
sudo firewall-cmd --set-default-zone=trusted
You should post your system specs. I realize you posted them on your prior wifi help request. You marked the thread solved, but I have an inkling it wasn't corrected fully.
Do not have Android phone tethering connected when you run any network diagnostic commands:
Please post again:
I also asked you to post these outputs on your prior help request (but you never did).
We will also need far more information on your NAS setup to have any idea what the problem is.
Hi here is some more information.
I use Lan cable and it works fine against the internet.
But I can not access my NAS.
I installed Manjaro in dual boot. There it works to access the NAS.
System: Kernel: 5.9.1-zen2-1-zen x86_64 bits: 64 compiler: N/A parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen root=UUID=ffb1225b-58ce-4f89-9a97-86cff3dc2b96 rw [email protected] quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0 systemd.unified_cgroup_hierarchy=1 resume=UUID=f1649338-0c72-40ea-bca5-f957036ab3b6 loglevel=3 Desktop: KDE Plasma 5.20.1 tk: Qt 5.15.1 info: latte-dock wm: kwin_x11 dm: SDDM Distro: Garuda Linux Machine: Type: Laptop System: Hewlett-Packard product: HP Pavilion 15 Notebook PC v: 0975100000405F10000620180 serial: <filter> Chassis: type: 10 serial: <filter> Mobo: Hewlett-Packard model: 2281 v: 77.35 serial: <filter> UEFI [Legacy]: Insyde v: F.42 date: 03/18/2015 Battery: ID-1: BAT0 charge: 33.6 Wh condition: 33.6/33.6 Wh (100%) volts: 16.8/14.8 model: Hewlett-Packard Primary type: Li-ion serial: N/A status: Full Device-1: hidpp_battery_0 model: Logitech M705 serial: <filter> charge: 30% rechargeable: yes status: Discharging CPU: Info: Dual Core model: Intel Core i5-4210U bits: 64 type: MT MCP arch: Haswell family: 6 model-id: 45 (69) stepping: 1 microcode: 26 L2 cache: 3072 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19154 Speed: 1696 MHz min/max: 800/2700 MHz Core speeds (MHz): 1: 1696 2: 1696 3: 1696 4: 1684 Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable Type: mds mitigation: Clear CPU buffers; SMT vulnerable Type: meltdown mitigation: PTI Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl and seccomp Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, STIBP: conditional, RSB filling Type: srbds mitigation: Microcode Type: tsx_async_abort status: Not affected Graphics: Device-1: Intel Haswell-ULT Integrated Graphics vendor: Hewlett-Packard driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0a16 Device-2: NVIDIA GM108M [GeForce 840M] vendor: Hewlett-Packard driver: N/A alternate: nouveau, nvidia_drm, nvidia bus ID: 0a:00.0 chip ID: 10de:1341 Device-3: Suyin type: USB driver: uvcvideo bus ID: 1-1.3:3 chip ID: 064e:c341 serial: <filter> Display: x11 server: X.Org 1.20.9 compositor: kwin_x11 driver: modesetting display ID: :0 screens: 1 Screen-1: 0 s-res: 3286x1080 s-dpi: 96 s-size: 869x285mm (34.2x11.2") s-diag: 915mm (36") Monitor-1: eDP-1 res: 1366x768 hz: 60 dpi: 101 size: 344x193mm (13.5x7.6") diag: 394mm (15.5") Monitor-2: HDMI-1 res: 1920x1080 hz: 60 dpi: 82 size: 598x336mm (23.5x13.2") diag: 686mm (27") OpenGL: renderer: Mesa DRI Intel HD Graphics 4400 (HSW GT2) v: 4.5 Mesa 20.2.1 compat-v: 3.0 direct render: Yes Audio: Device-1: Intel Haswell-ULT HD Audio vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus ID: 00:03.0 chip ID: 8086:0a0c Device-2: Intel 8 Series HD Audio vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:9c20 Sound Server: ALSA v: k5.9.1-zen2-1-zen Network: Device-1: Broadcom and subsidiaries BCM43142 802.11b/g/n vendor: Hewlett-Packard driver: wl v: kernel port: 6040 bus ID: 08:00.0 chip ID: 14e4:4365 IF: wlo1 state: dormant mac: <filter> Device-2: Realtek RTL810xE PCI Express Fast Ethernet vendor: Hewlett-Packard driver: r8169 v: kernel port: 4000 bus ID: 09:00.0 chip ID: 10ec:8136 IF: eno1 state: up speed: 100 Mbps duplex: full mac: <filter> Drives: Local Storage: total: 465.76 GiB used: 65.71 GiB (14.1%) SMART Message: Unable to run smartctl. Root privileges required. ID-1: /dev/sda vendor: HGST (Hitachi) model: HTS545050A7E680 size: 465.76 GiB block size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s rotation: 5400 rpm serial: <filter> rev: AH10 scheme: MBR Partition: ID-1: / raw size: 228.48 GiB size: 228.48 GiB (100.00%) used: 65.71 GiB (28.8%) fs: btrfs dev: /dev/sda1 ID-2: /home raw size: 228.48 GiB size: 228.48 GiB (100.00%) used: 65.71 GiB (28.8%) fs: btrfs dev: /dev/sda1 ID-3: /var/log raw size: 228.48 GiB size: 228.48 GiB (100.00%) used: 65.71 GiB (28.8%) fs: btrfs dev: /dev/sda1 ID-4: /var/tmp raw size: 228.48 GiB size: 228.48 GiB (100.00%) used: 65.71 GiB (28.8%) fs: btrfs dev: /dev/sda1 Swap: Kernel: swappiness: 10 (default 60) cache pressure: 75 (default 100) ID-1: swap-1 type: partition size: 8.80 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sda2 ID-2: swap-2 type: zram size: 493.2 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram0 ID-3: swap-3 type: zram size: 493.2 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram1 ID-4: swap-4 type: zram size: 493.2 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram2 ID-5: swap-5 type: zram size: 493.2 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram3 Sensors: System Temperatures: cpu: 53.0 C mobo: N/A Fan Speeds (RPM): N/A Info: Processes: 245 Uptime: 4m Memory: 7.71 GiB used: 1.99 GiB (25.9%) Init: systemd v: 246 Compilers: gcc: 10.2.0 Packages: pacman: 1309 lib: 279 Shell: Zsh v: 5.8 running in~~~ ~~~❯ ping -c5 126.96.36.199 100% ─╯ PING 188.8.131.52 (184.108.40.206) 56(84) bytes of data. 64 bytes from 220.127.116.11: icmp_seq=1 ttl=114 time=11.1 ms 64 bytes from 18.104.22.168: icmp_seq=2 ttl=114 time=11.1 ms 64 bytes from 22.214.171.124: icmp_seq=3 ttl=114 time=11.1 ms 64 bytes from 126.96.36.199: icmp_seq=4 ttl=114 time=11.1 ms 64 bytes from 188.8.131.52: icmp_seq=5 ttl=114 time=11.0 ms --- 184.108.40.206 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4004ms rtt min/avg/max/mdev = 10.987/11.069/11.146/0.050 ms~~~ ~~~❯ ping -c5 google.com 100% ─╯ PING google.com (220.127.116.11) 56(84) bytes of data. 64 bytes from muc03s13-in-f14.1e100.net (18.104.22.168): icmp_seq=1 ttl=116 time=10.8 ms 64 bytes from arn09s20-in-f14.1e100.net (22.214.171.124): icmp_seq=2 ttl=116 time=10.9 ms 64 bytes from arn09s20-in-f14.1e100.net (126.96.36.199): icmp_seq=3 ttl=116 time=10.8 ms 64 bytes from arn09s20-in-f14.1e100.net (188.8.131.52): icmp_seq=4 ttl=116 time=10.9 ms 64 bytes from arn09s20-in-f14.1e100.net (184.108.40.206): icmp_seq=5 ttl=116 time=10.9 ms --- google.com ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4005ms rtt min/avg/max/mdev = 10.796/10.881/10.937/0.058 ms~~~
PING 220.127.116.11 (18.104.22.168) 56(84) bytes of data. 64 bytes from 22.214.171.124: icmp_seq=1 ttl=114 time=11.1 ms 64 bytes from 126.96.36.199: icmp_seq=2 ttl=114 time=11.1 ms 64 bytes from 188.8.131.52: icmp_seq=3 ttl=114 time=11.1 ms 64 bytes from 184.108.40.206: icmp_seq=4 ttl=114 time=11.1 ms 64 bytes from 220.127.116.11: icmp_seq=5 ttl=114 time=11.0 ms --- 18.104.22.168 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4004ms rtt min/avg/max/mdev = 10.987/11.069/11.146/0.050 ms~~~
You don't need to keep posting your ping statistics.
Please post the methods that you have tried to access your NAS.
# See resolvconf.conf(5) for details resolv_conf=/etc/resolv.conf # If you run a local name server, you should uncomment the below line and # configure your subscribers configuration files below. #name_servers=127.0.0.1~~~ I have tried with Dolphin, Nemo and Krusader.
# See resolvconf.conf(5) for details resolv_conf=/etc/resolv.conf # If you run a local name server, you should uncomment the below line and # configure your subscribers configuration files below. #name_servers=127.0.0.1~~~
Did you stop/disable your firewall as @librewish suggested. It would be best to disable the firewall temporarily until you have fixed all your networking issues. Otherwise you will need to stop the firewall after every reboot (unless you create the proper firewall rules).
From looking at your inxi output I'd guess you never really got your wifi issue resolved as your wifi adapter is reporting as dormant. If you are using your laptop via your Ethernet to connect to your NAS (and it's not used to roam) I guess that's not such a big priority.
You never told us what type of NAS you were running or which protocol you were using to connect. I assume you are trying to use Samba to connect to your NAS. Samba is often a pain to get working properly on Arch based distro's. Generally I try to refrain from giving advice on Samba as I feel it is too unreliable and I use NFS.
KDE often does not connect to network shares that well OOTB using Dolphin. Often the best way to access and play media files over your network is by mounting your shares.
I'm getting the feeling your not familiar with this stuff (and it's a ton to understand all at once). Any one of these topics alone could be the subject of a full chapter in a book as they all take a fair bit grasp. I'm thinking you're going to have to do some research and read/watch some tutorials to get an idea how all this stuff works. Here are some links to start you off:
I can confirm that after I set up my NAS using nfs in stead of samba, the Garada KDE installation works OOTB after adding one simple line to fstab to make the NAS available to the KDE cliënt, including Dolphin file browser.
As you write, you are right. I do not know much about setting up networks. What I use is WD Mybook live.
Have not had to bother with this before as it has only worked.
But as you write, it has not worked with Dolphin.
I have then used Nemo without any problems.
Tested with Arco linux with kde as environment and there it works well with Nemo.
Do not know what it may be that makes it not work in Karuda?
kio-extras for remote filesystems. This should already be installed as a dependency.
gvfs-smb for remote Samba shares.
Also, do you have samba installed and active on your client pc? Look for samba in Garuda Welcome app, settings tab. WD mybook is presumably samba server configured.
Even when Samba is installed properly and all the services are running it is often super finicky on having the configuration just right to actually work. I hate configuring samba. You go to all the effort of getting it just right, and then some update from upstream totally breaks it.
NFS seems far more straightforward to me to configure. Although, I do not know if his NAS is compatible with NFS. Sorry for all these new confusing terms to learn, but in the end you'll have much better performance if you learn how to do things the Linux way.
For help on possibly setting up nfs on WD nas, maybe refer to community.wd.com. From the web interface to the server you need to enable ssh to the server. After that you might be able to setup the device as an nfs server in stead of the default samba server.
I have to thank you for all the help I have received. But I'm running Arco Linux again now. There works. I have to access my Wd where my pictures are. (Works as a photographer)
Also noticed that KDE connect did not work for me Today. I will certainly come back to test again. Mvh Pata
You have to enable to port in the firewall, its blocked by default. Have a look at this topic
I'll be back for sure. As a whole, I think Garuda is one of the best Arch.
You in the development team have done a great job