Quantcast
Channel: Ubuntu Forums - Networking & Wireless
Viewing all 23300 articles
Browse latest View live
↧

[ubuntu] Bluetooth problems with 20.04.06

August 11, 2024, 10:46 am
$
0
0
When I enter bluetooth the bluetooth tab to connect my earbuds (Galaxy Buds2), I can't see any devices because they all are named "Unknown" and says "Not Set Up", and I can't click on them.

I have a Broadcom BCM4352 wireless card, I tried running:
Code:
sudo apt install --reinstall bcmwl-kernel-source
but I couldn't fix the problem. What do you think I should do?
↧
Search

[ubuntu] No Internet Connection on Ubuntu server after kernel update.

August 13, 2024, 12:23 am
$
0
0
I have done an update via sudo apt get update && sudo apt upgrade. I upgraded to Ubuntu 22.04.4 LTS.
Also, I have upgraded the Kernel to GNU/Linux 6.5.0-1027-oracle aarch64.
After the update, I wasn't able to access the Instance via SSH. I can only access the instance via cloud console.
I don't know much about networking and have no idea how I can restore Internet access.
I have googled a bit and done these things:
ping 1.1.1.1
Code:
ping: connect: Network is unreachable
dig askubuntu.com @1.1.1.1
Code:
;; UDP setup with 1.1.1.1#53(1.1.1.1) for askubuntu.com failed: network unreachable.
;; no servers could be reached

;; UDP setup with 1.1.1.1#53(1.1.1.1) for askubuntu.com failed: network unreachable.
;; no servers could be reached

;; UDP setup with 1.1.1.1#53(1.1.1.1) for askubuntu.com failed: network unreachable.
;; no servers could be reached
ip addr gives me the following output:
Code:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
      valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
      valid_lft forever preferred_lft forever
2: enp0s3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 02:00:17:00:e1:21 brd ff:ff:ff:ff:ff:ff
3: tun0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 500
    link/none
    inet 10.8.0.1/24 scope global tun0
      valid_lft forever preferred_lft forever
    inet6 fe80::7e95:61d8:aa77:ad19/64 scope link stable-privacy
      valid_lft forever preferred_lft forever
4: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether 52:54:00:16:0b:c5 brd ff:ff:ff:ff:ff:ff
    inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
      valid_lft forever preferred_lft forever

The Output of cat /etc/netplan/*.yaml:
Code:
network:
version: 2
renderer: networkd
ethernets:
    enp0s3:
        dhcp4: true
# This file is generated from information provided by the datasource.  Changes
# to it will not persist across an instance reboot.  To disable cloud-init's
# network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
    version: 2
    ethernets:
        enp0s3:
            dhcp4: true
            match:
                macaddress: 02:00:17:00:e1:21
            set-name: enp0s3
sudo lshw -C network:
*-network               
      description: Ethernet controller
      product: Virtio network device
      vendor: Red Hat, Inc.
      physical id: 3
      bus info: pci@0000:00:03.0
      version: 01
      width: 64 bits
      clock: 33MHz
      capabilities: msix bus_master cap_list
      configuration: driver=virtio-pci latency=0
      resources: iomemory:800-7ff irq:48 memory:13001000-13001fff memory:8003008000-800300bfff
    *-virtio1 DISABLED
          description: Ethernet interface
          physical id: 0
          bus info: virtio@1
          logical name: enp0s3
          serial: 02:00:17:00:e1:21
          capabilities: ethernet physical
          configuration: autonegotiation=off broadcast=yes driver=virtio_net driverversion=1.0.0 link=no multicast=yes

sudo cat /etc/network/interfaces:
Code:
cat: /etc/network/interfaces: No such file or directory
Has anyone an idea what I could do? Tank you very much!
↧
↧

lacp not being sent on bond interfaces

August 13, 2024, 7:34 am
$
0
0
No LACP being sent out eno2 or eno3.
LACP IS being received from the other side.

LLDP is going out eno2 and eno3.

Not sure what I'm missing.

FWIW:
root@dl380rack1:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 24.04 LTS
Release: 24.04
Codename: noble




root@dl380rack1:~#cat /etc/netplan/50-cloud-init.yaml

network:
ethernets:
eno1:
dhcp4: true
eno2:
dhcp4: false
dhcp6: false
eno3:
dhcp4: false
dhcp6: false
eno4:
dhcp4: true
ens2f0np0:
dhcp4: true
ens2f1np1:
dhcp4: true
bonds:
bond0:
interfaces:
- eno2
- eno3
parameters:
mode: 802.3ad
lacp-rate: slow
mii-monitor-interval: 100
version: 2
~




root@dl380rack1:~# cat /proc/net/bonding/bond0
Ethernet Channel Bonding Driver: v6.8.0-39-generic


Bonding Mode: IEEE 802.3ad Dynamic link aggregation
Transmit Hash Policy: layer2 (0)
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 0
Down Delay (ms): 0
Peer Notification Delay (ms): 0


802.3ad info
LACP active: on
LACP rate: slow
Min links: 0
Aggregator selection policy (ad_select): stable
System priority: 65535
System MAC address: 02:5f:a1:a0:2d:01
Active Aggregator Info:
Aggregator ID: 1
Number of ports: 1
Actor Key: 9
Partner Key: 1
Partner Mac Address: 00:00:00:00:00:00


Slave Interface: eno2
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 98:f2:b3:e7:5e:bd
Slave queue ID: 0
Aggregator ID: 1
Actor Churn State: none
Partner Churn State: churned
Actor Churned Count: 0
Partner Churned Count: 1
details actor lacp pdu:
system priority: 65535
system mac address: 02:5f:a1:a0:2d:01
port key: 9
port priority: 255
port number: 1
port state: 77
details partner lacp pdu:
system priority: 65535
system mac address: 00:00:00:00:00:00
oper key: 1
port priority: 255
port number: 1
port state: 1


This doesn't look quite right:

root@dl380rack1:~# ethtool bond0
Settings for bond0:
Supported ports: [ ]
Supported link modes: Not reported
Supported pause frame use: No
Supports auto-negotiation: No
Supported FEC modes: Not reported
Advertised link modes: Not reported
Advertised pause frame use: No
Advertised auto-negotiation: No
Advertised FEC modes: Not reported
Speed: 1000Mb/s
Duplex: Full
Auto-negotiation: off
Port: Other
PHYAD: 0
Transceiver: internal
Link detected: yes
↧

Ubuntu Server cant Be Accessed Over IP or SHH But CloudFlare Tunnel Works Fine

August 14, 2024, 1:49 am
$
0
0
Hello All,

I am having this strange issue, after running for sometime, my Ubuntu server cant be accessed over local IP, cant SSH, cant reach any service like radarr, Jellyfin or so, unless i restart it.
But i am using Cloudflare tunnel so that if i am out of my home, so i can reach it, and it works fine even when i cant access services locally.
Means I cant reach Jellyfin from local IP but I can reach it via Cloudflare tunnel and it works perfectly fine, same goes with other services.
P.S. my server is over WiFi
↧

Fresh 24.04 install usb wifi antenna won't connect

August 14, 2024, 6:19 am
$
0
0
Fresh installed dual-boot windows/Ubuntu

Antenna model: TP-link AX1800 dual antenna high gain

Driver source: https://github.com/lwfinger/rtl8852au

Ubuntu recognizes the antenna, I'm able to search for the available networks, but it won't connect...

Here's the output of the wireless script: https://pastebin.com/UCdAR42m

Here's the journalctl output when trying to connect:

Code:
Aug 14 14:51:30 user-desktop NetworkManager[23303]: <info>  [1723639890.9570] device (wlx98254a6fcf41): Activation: (wifi) connection 'MY_NETWORK_NAME' has security, and secrets exist.  No new secrets needed.
Aug 14 14:51:30 user-desktop NetworkManager[23303]: <info>  [1723639890.9669] device (wlx98254a6fcf41): supplicant interface state: disconnected -> associating
Aug 14 14:51:37 user-desktop NetworkManager[23303]: <info>  [1723639897.7714] device (wlx98254a6fcf41): supplicant interface state: associating -> disconnected
Aug 14 14:51:37 user-desktop NetworkManager[23303]: <info>  [1723639897.8765] device (wlx98254a6fcf41): supplicant interface state: disconnected -> scanning
Aug 14 14:51:47 user-desktop NetworkManager[23303]: <info>  [1723639907.3879] device (wlx98254a6fcf41): supplicant interface state: scanning -> associating
Aug 14 14:51:48 user-desktop NetworkManager[23303]: <info>  [1723639908.6444] device (wlx98254a6fcf41): state change: config -> deactivating (reason 'new-activation', sys-iface-state: 'managed')
Aug 14 14:51:48 user-desktop NetworkManager[23303]: <info>  [1723639908.6449] device (wlx98254a6fcf41): disconnecting for new activation request.
Aug 14 14:51:50 user-desktop NetworkManager[23303]: <info>  [1723639910.1313] device (wlx98254a6fcf41): state change: deactivating -> disconnected (reason 'new-activation', sys-iface-state: 'managed')
Aug 14 14:51:50 user-desktop NetworkManager[23303]: <info>  [1723639910.1321] device (wlx98254a6fcf41): Activation: starting connection 'MY_NETWORK_NAME' (1134155a-503d-4ace-8ae3-9449da4d32db)
Aug 14 14:51:50 user-desktop NetworkManager[23303]: <info>  [1723639910.1324] device (wlx98254a6fcf41): supplicant interface state: associating -> disconnected
Aug 14 14:51:50 user-desktop NetworkManager[23303]: <info>  [1723639910.1326] device (wlx98254a6fcf41): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Aug 14 14:51:50 user-desktop NetworkManager[23303]: <info>  [1723639910.1329] device (wlx98254a6fcf41): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Aug 14 14:51:50 user-desktop NetworkManager[23303]: <info>  [1723639910.1330] device (wlx98254a6fcf41): Activation: (wifi) access point 'MY_NETWORK_NAME' has security, but secrets are required.
Aug 14 14:51:50 user-desktop NetworkManager[23303]: <info>  [1723639910.1330] device (wlx98254a6fcf41): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Aug 14 14:51:50 user-desktop NetworkManager[23303]: <info>  [1723639910.1331] sup-iface[808dc8d34ac3970d,1,wlx98254a6fcf41]: wps: type pbc start...
Aug 14 14:51:50 user-desktop NetworkManager[23303]: <info>  [1723639910.1337] device (wlx98254a6fcf41): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Aug 14 14:51:50 user-desktop NetworkManager[23303]: <info>  [1723639910.1338] device (wlx98254a6fcf41): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Aug 14 14:51:50 user-desktop NetworkManager[23303]: <info>  [1723639910.1340] device (wlx98254a6fcf41): Activation: (wifi) connection 'MY_NETWORK_NAME' has security, and secrets exist.  No new secrets needed.
Aug 14 14:51:50 user-desktop NetworkManager[23303]: <info>  [1723639910.8085] device (wlx98254a6fcf41): supplicant interface state: disconnected -> associating
Aug 14 14:51:59 user-desktop NetworkManager[23303]: <info>  [1723639919.7875] device (wlx98254a6fcf41): supplicant interface state: associating -> disconnected
Aug 14 14:52:00 user-desktop NetworkManager[23303]: <info>  [1723639920.2929] device (wlx98254a6fcf41): supplicant interface state: disconnected -> scanning
Aug 14 14:52:08 user-desktop NetworkManager[23303]: <info>  [1723639928.6503] device (wlx98254a6fcf41): supplicant interface state: scanning -> associating
Aug 14 14:52:15 user-desktop NetworkManager[23303]: <warn>  [1723639935.0220] device (wlx98254a6fcf41): Activation: (wifi) association took too long
Aug 14 14:52:15 user-desktop NetworkManager[23303]: <info>  [1723639935.0220] device (wlx98254a6fcf41): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Aug 14 14:52:15 user-desktop NetworkManager[23303]: <info>  [1723639935.0222] sup-iface[808dc8d34ac3970d,1,wlx98254a6fcf41]: wps: type pbc start...
Aug 14 14:52:15 user-desktop NetworkManager[23303]: <warn>  [1723639935.0223] device (wlx98254a6fcf41): Activation: (wifi) asking for new secrets
Aug 14 14:52:15 user-desktop NetworkManager[23303]: <info>  [1723639935.0227] device (wlx98254a6fcf41): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Aug 14 14:52:15 user-desktop NetworkManager[23303]: <info>  [1723639935.0229] device (wlx98254a6fcf41): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Aug 14 14:52:15 user-desktop NetworkManager[23303]: <info>  [1723639935.0231] device (wlx98254a6fcf41): Activation: (wifi) connection 'MY_NETWORK_NAME' has security, and secrets exist.  No new secrets needed.
Aug 14 14:52:15 user-desktop NetworkManager[23303]: <info>  [1723639935.3330] device (wlx98254a6fcf41): supplicant interface state: associating -> disconnected
Aug 14 14:52:15 user-desktop NetworkManager[23303]: <info>  [1723639935.3414] device (wlx98254a6fcf41): supplicant interface state: disconnected -> scanning
Aug 14 14:52:18 user-desktop NetworkManager[23303]: <info>  [1723639938.2194] device (wlx98254a6fcf41): supplicant interface state: scanning -> disconnected
Aug 14 14:52:27 user-desktop NetworkManager[23303]: <info>  [1723639947.2172] device (wlx98254a6fcf41): supplicant interface state: disconnected -> associating
Aug 14 14:52:27 user-desktop NetworkManager[23303]: <info>  [1723639947.2173] device (wlx98254a6fcf41): supplicant interface state: associating -> disconnected
Aug 14 14:52:30 user-desktop NetworkManager[23303]: <info>  [1723639950.2493] device (wlx98254a6fcf41): supplicant interface state: disconnected -> associating
Aug 14 14:52:36 user-desktop NetworkManager[23303]: <info>  [1723639956.6513] device (wlx98254a6fcf41): supplicant interface state: associating -> disconnected
Aug 14 14:52:41 user-desktop NetworkManager[23303]: <warn>  [1723639961.0249] device (wlx98254a6fcf41): Activation: (wifi) association took too long
Aug 14 14:52:41 user-desktop NetworkManager[23303]: <info>  [1723639961.0249] device (wlx98254a6fcf41): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Aug 14 14:52:41 user-desktop NetworkManager[23303]: <info>  [1723639961.0251] sup-iface[808dc8d34ac3970d,1,wlx98254a6fcf41]: wps: type pbc start...
Aug 14 14:52:41 user-desktop NetworkManager[23303]: <warn>  [1723639961.0252] device (wlx98254a6fcf41): Activation: (wifi) asking for new secrets
Aug 14 14:52:41 user-desktop NetworkManager[23303]: <info>  [1723639961.0258] device (wlx98254a6fcf41): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Aug 14 14:52:41 user-desktop NetworkManager[23303]: <info>  [1723639961.0260] device (wlx98254a6fcf41): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Aug 14 14:52:41 user-desktop NetworkManager[23303]: <info>  [1723639961.0262] device (wlx98254a6fcf41): Activation: (wifi) connection 'MY_NETWORK_NAME' has security, and secrets exist.  No new secrets needed.
Aug 14 14:52:41 user-desktop NetworkManager[23303]: <info>  [1723639961.0285] device (wlx98254a6fcf41): supplicant interface state: disconnected -> scanning
Aug 14 14:52:49 user-desktop NetworkManager[23303]: <info>  [1723639969.1016] device (wlx98254a6fcf41): supplicant interface state: scanning -> associating
Aug 14 14:52:56 user-desktop NetworkManager[23303]: <info>  [1723639976.1074] device (wlx98254a6fcf41): supplicant interface state: associating -> disconnected
Aug 14 14:53:06 user-desktop NetworkManager[23303]: <warn>  [1723639986.0230] device (wlx98254a6fcf41): Activation: (wifi) association took too long
Aug 14 14:53:06 user-desktop NetworkManager[23303]: <info>  [1723639986.0230] device (wlx98254a6fcf41): state change: config -> failed (reason 'no-secrets', sys-iface-state: 'managed')
Aug 14 14:53:06 user-desktop NetworkManager[23303]: <warn>  [1723639986.0233] device (wlx98254a6fcf41): Activation: failed for connection 'MY_NETWORK_NAME'
Aug 14 14:53:06 user-desktop NetworkManager[23303]: <info>  [1723639986.0234] device (wlx98254a6fcf41): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Aug 14 14:53:14 user-desktop NetworkManager[23303]: <info>  [1723639994.1193] device (wlx98254a6fcf41): supplicant interface state: disconnected -> inactive
i've been hitting against this wall for quite some time without solution...
↧
↧

[ubuntu] Ethernet won't connect

August 14, 2024, 6:34 pm
$
0
0
I'm using Ubuntu Server 22.04.4 LTS. Ethernet won't connect but when I added a WiFi card I can connect. I opened a terminal and type: "sudo lshw -C network"
This is what I got concerning my ethernet:
*-network DISABLED
description: Ethernet interface
product: AR8151 v2.0 Gigabit Ethernet
vendor: Qualcomm Atheros
physical id: 0
bus info: pci@0000:02:00.0
logical name: enp2s0
version: c0
serial: 90:2b:34:34:d0:db
capacity: 1Gbit/s
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress vpd bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=atl1c driverversion=5.15.0-117-generic latency=0 link=no multicast=yes port=twisted pair
resources: irq:18 memory:f7c00000-f7c3ffff ioport:d000(size=128)

How do I enable it? I checked the BIOS and it's enabled there.
Thanks
↧

Unable to generate a functional netplan yaml for my laptop

August 15, 2024, 9:40 am
$
0
0
Its a MS Surface laptop with a built in Marvell WiFI (w1p1s0) that works fine. The second device (enx00e04c681826) is a USB ethernet adapter with the RTL8153 firmware.

Drivers are install, devices show up, wifi works just fine on its own.

:/etc/network# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
2: enx00e04c681826: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 00:e0:4c:68:18:26 brd ff:ff:ff:ff:ff:ff
3: wwan0: <BROADCAST,MULTICAST,NOARP> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 4e:ba:8c:d4:d0:1d brd ff:ff:ff:ff:ff:ff
4: wlp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1492 qdisc mq state UP group default qlen 1000
link/ether 70:bc:10:5d:f6:52 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.161/24 metric 600 brd 192.168.1.255 scope global dynamic wlp1s0
valid_lft 68466sec preferred_lft 68466sec

Its a basic class C network with a single subnet. The wifi is fine being DHCP but I am trying to setup the ethernet with a static IP for external routing purposes.

Ive been digging through examples on the netplan github but I just cant seem to make it work. I have spent about 3 hours now attempting various things and none of it works. I have used online yaml checkers that verify syntax and spacing but every time I 'netplan try' my changes
I lose the IP on my wifi and have to physically console back in. Does anyone have any suggestions or maybe theres an online netplan yaml builder somewhere? Last time I setup anything like this in linux it still used /etc/network/interfaces and boy do I miss it. I would have it up in 5
minutes if this system wasnt depreciated. Netplan is a nightmare in comparison.
↧

aicsemi AIC8800 in kernel driver?

August 16, 2024, 10:06 pm
↧
Search

Ubuntu server 22 - missing /var/lib/dhcp/dhclient.xxx.leases

August 20, 2024, 5:06 am
$
0
0
Hello

on ubuntu 16 i have DHCP client lease file
/var/lib/dhcp/dhclient.eth0.leases

on ubuntu 22 this file does not exists, is it in a new path?
is there other lease file for ubuntu22 ?
↧
↧

IP4 to IP6

August 20, 2024, 8:23 am
$
0
0
Running Ubuntu server 24.04 on a Beelink mini PC. The mini pc lives in a ip4 world and I have a client that lives in the ip6 world. Is it possible to NAT, or some other method, from ip4 to ip6? If so how?

This is a demo type setting and I'm working on the proof of concept. My hope is that the mini pc can do the heavy lifting, but if there is hardware out there that can do it that might work also.
↧

[ubuntu] Wi-Fi Adapter Not Recognized on Ubuntu 22.04 - Qualcomm Atheros QCA6174

August 21, 2024, 11:22 am
$
0
0
Hi everyone,


I'm having a frustrating issue with my Ubuntu 22.04 system where my Wi-Fi adapter is not being recognized, and I can't connect to any Wi-Fi networks. Here's a summary of the problem:
System Information:


  • OS: Ubuntu 22.04
  • Wi-Fi Adapter: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter
  • Driver: ath10k_pci
  • Current Firmware: WLAN.RM.4.4.1-00157-QCARMSWPZ-1

Problem Description:


  • The Wi-Fi adapter appears as DISABLED when I check using lshw -C network.
  • The device status shows unmanaged in nmcli device status.
  • When I try to scan for Wi-Fi networks using nmcli device wifi rescan, I get the error: "Error: Scanning not allowed while unavailable."
  • I've tried using rfkill to unblock Wi-Fi, but it doesn't solve the issue. rfkill list shows that Wi-Fi is not blocked.
  • The adapter was previously working when I was setting up a Wi-Fi hotspot using hostapd. After that, I couldn't connect to any Wi-Fi network.

Steps I've Tried:


  1. Reinstalling NetworkManager: Ensured NetworkManager is installed and up to date.
  2. Reloading the driver: Tried modprobe -r ath10k_pci and modprobe ath10k_pci to reload the Wi-Fi driver.



I'm out of ideas at this point. Has anyone encountered a similar issue or could suggest further troubleshooting steps? Any help would be greatly appreciated!


Thanks in advance!
↧

why is my ip-address changing?

August 22, 2024, 3:20 am
$
0
0
Yesterday my ip-address in my local wlan network was 192.168.2.219, today it is 192.168.2.211.
In the mean time the host was NOT rebooted (but sleeping) and also the router has not been touched.
Who is responsible for these spontaneous changes?
↧

Ubuntu 24.04 LTS - SAMBA Issue: smbd.service failed to start

August 22, 2024, 5:52 am
$
0
0
Hi all,

I have just installed Ubuntu 24.04 and am trying to share a folder through SMB with my network.
However I am unable to as samba fails to start every single time. The goal is to share the content located in /mnt/12TB/ServerFolders

In my most recent attempt I performed the following steps:
1. Followed the official ubuntu tutorial

2. The command whereis samba gives me the following:
Code:
samba: /usr/sbin/samba /usr/lib/x86_64-linux-gnu/samba /etc/samba /usr/libexec/samba /usr/share/samba /usr/share/man/man7/samba.7.gz /usr/share/man/man8/samba.8.gz
3. My etc/samba/smb.conf file:
Code:
#
# Sample configuration file for the Samba suite for Debian GNU/Linux.
#
#
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options most of which
# are not shown in this example
#
# Some options that are often worth tuning have been included as
# commented-out examples in this file.
#  - When such options are commented with ";", the proposed setting
#    differs from the default Samba behaviour
#  - When commented with "#", the proposed setting is the default
#    behaviour of Samba but the option is considered important
#    enough to be mentioned here
#
# NOTE: Whenever you modify this file you should run the command
# "testparm" to check that you have not made any basic syntactic
# errors.

#======================= Global Settings =======================

[global]

## Browsing/Identification ###

# Change this to the workgroup/NT-domain name your Samba server will part of
  workgroup = WORKGROUP

# server string is the equivalent of the NT Description field
  server string = %h server (Samba, Ubuntu)

#### Networking ####

# The specific set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names are normally preferred
;  interfaces = 127.0.0.0/8 eth0

# Only bind to the named interfaces and/or networks; you must use the
# 'interfaces' option above to use this.
# It is recommended that you enable this feature if your Samba machine is
# not protected by a firewall or is a firewall itself.  However, this
# option cannot handle dynamic or non-broadcast interfaces correctly.
;  bind interfaces only = yes



#### Debugging/Accounting ####

# This tells Samba to use a separate log file for each machine
# that connects
  log file = /var/log/samba/log.%m

# Cap the size of the individual log files (in KiB).
  max log size = 1000

# We want Samba to only log to /var/log/samba/log.{smbd,nmbd}.
# Append syslog@1 if you want important messages to be sent to syslog too.
  logging = file

# Do something sensible when Samba crashes: mail the admin a backtrace
  panic action = /usr/share/samba/panic-action %d


####### Authentication #######

# Server role. Defines in which mode Samba will operate. Possible
# values are "standalone server", "member server", "classic primary
# domain controller", "classic backup domain controller", "active
# directory domain controller".
#
# Most people will want "standalone server" or "member server".
# Running as "active directory domain controller" will require first
# running "samba-tool domain provision" to wipe databases and create a
# new domain.
  server role = standalone server

  obey pam restrictions = yes

# This boolean parameter controls whether Samba attempts to sync the Unix
# password with the SMB password when the encrypted SMB password in the
# passdb is changed.
  unix password sync = yes

# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Ian Kahan <<kahan@informatik.tu-muenchen.de> for
# sending the correct chat script for the passwd program in Debian Sarge).
  passwd program = /usr/bin/passwd %u
  passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .

# This boolean controls whether PAM will be used for password changes
# when requested by an SMB client instead of the program listed in
# 'passwd program'. The default is 'no'.
  pam password change = yes

# This option controls how unsuccessful authentication attempts are mapped
# to anonymous connections
  map to guest = bad user

########## Domains ###########

#
# The following settings only takes effect if 'server role = classic
# primary domain controller', 'server role = classic backup domain controller'
# or 'domain logons' is set
#

# It specifies the location of the user's
# profile directory from the client point of view) The following
# required a [profiles] share to be setup on the samba server (see
# below)
;  logon path = \\%N\profiles\%U
# Another common choice is storing the profile in the user's home directory
# (this is Samba's default)
#  logon path = \\%N\%U\profile

# The following setting only takes effect if 'domain logons' is set
# It specifies the location of a user's home directory (from the client
# point of view)
;  logon drive = H:
#  logon home = \\%N\%U

# The following setting only takes effect if 'domain logons' is set
# It specifies the script to run during logon. The script must be stored
# in the [netlogon] share
# NOTE: Must be store in 'DOS' file format convention
;  logon script = logon.cmd

# This allows Unix users to be created on the domain controller via the SAMR
# RPC pipe.  The example command creates a user account with a disabled Unix
# password; please adapt to your needs
; add user script = /usr/sbin/useradd --create-home %u

# This allows machine accounts to be created on the domain controller via the
# SAMR RPC pipe. 
# The following assumes a "machines" group exists on the system
; add machine script  = /usr/sbin/useradd -g machines -c "%u machine account" -d /var/lib/samba -s /bin/false %u

# This allows Unix groups to be created on the domain controller via the SAMR
# RPC pipe. 
; add group script = /usr/sbin/addgroup --force-badname %g

############ Misc ############

# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting
;  include = /home/samba/etc/smb.conf.%m

# Some defaults for winbind (make sure you're not using the ranges
# for something else.)
;  idmap config * :              backend = tdb
;  idmap config * :              range  = 3000-7999
;  idmap config YOURDOMAINHERE : backend = tdb
;  idmap config YOURDOMAINHERE : range  = 100000-999999
;  template shell = /bin/bash

# Setup usershare options to enable non-root users to share folders
# with the net usershare command.

# Maximum number of usershare. 0 means that usershare is disabled.
#  usershare max shares = 100

# Allow users who've been granted usershare privileges to create
# public shares, not just authenticated ones
  usershare allow guests = yes

#======================= Share Definitions =======================

# Un-comment the following (and tweak the other settings below to suit)
# to enable the default home directory shares. This will share each
# user's home directory as \\server\username
;[homes]
;  comment = Home Directories
;  browseable = no

# By default, the home directories are exported read-only. Change the
# next parameter to 'no' if you want to be able to write to them.
;  read only = yes

# File creation mask is set to 0700 for security reasons. If you want to
# create files with group=rw permissions, set next parameter to 0775.
;  create mask = 0700

# Directory creation mask is set to 0700 for security reasons. If you want to
# create dirs. with group=rw permissions, set next parameter to 0775.
;  directory mask = 0700

# By default, \\server\username shares can be connected to by anyone
# with access to the samba server.
# Un-comment the following parameter to make sure that only "username"
# can connect to \\server\username
# This might need tweaking when using external authentication schemes
;  valid users = %S

# Un-comment the following and create the netlogon directory for Domain Logons
# (you need to configure Samba to act as a domain controller too.)
;[netlogon]
;  comment = Network Logon Service
;  path = /home/samba/netlogon
;  guest ok = yes
;  read only = yes

# Un-comment the following and create the profiles directory to store
# users profiles (see the "logon path" option above)
# (you need to configure Samba to act as a domain controller too.)
# The path below should be writable by all users so that their
# profile directory may be created the first time they log on
;[profiles]
;  comment = Users profiles
;  path = /home/samba/profiles
;  guest ok = no
;  browseable = no
;  create mask = 0600
;  directory mask = 0700

[printers]
  comment = All Printers
  browseable = no
  path = /var/tmp
  printable = yes
  guest ok = no
  read only = yes
  create mask = 0700

# Windows clients look for this share name as a source of downloadable
# printer drivers
[print$]
  comment = Printer Drivers
  path = /var/lib/samba/printers
  browseable = yes
  read only = yes
  guest ok = no
# Uncomment to allow remote administration of Windows print drivers.
# You may need to replace 'lpadmin' with the name of the group your
# admin users are members of.
# Please note that you also need to set appropriate Unix permissions
# to the drivers directory for these users to have write rights in it
;  write list = root, @lpadmin

[sambashare]
    comment = Samba on Ubuntu
    path = /mnt/12TB/ServerFolders
    read only = yes
    browsable = yes
4. I check the conf file with testparm:
Code:
Load smb config files from /etc/samba/smb.conf
Loaded services file OK.
Weak crypto is allowed by GnuTLS (e.g. NTLM as a compatibility fallback)

Server role: ROLE_STANDALONE

Press enter to see a dump of your service definitions

# Global parameters
[global]
    log file = /var/log/samba/log.%m
    logging = file
    map to guest = Bad User
    max log size = 1000
    obey pam restrictions = Yes
    pam password change = Yes
    panic action = /usr/share/samba/panic-action %d
    passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
    passwd program = /usr/bin/passwd %u
    server role = standalone server
    server string = %h server (Samba, Ubuntu)
    unix password sync = Yes
    usershare allow guests = Yes
    idmap config * : backend = tdb


[printers]
    browseable = No
    comment = All Printers
    create mask = 0700
    path = /var/tmp
    printable = Yes


[print$]
    comment = Printer Drivers
    path = /var/lib/samba/printers


[sambashare]
    comment = Samba on Ubuntu
    path = /mnt/12TB/ServerFolders
5. Seems good too. However when I start the service with "sudo service smbd restart" I receive the following error:
Code:
Job for smbd.service failed because a fatal signal was delivered causing the control process to dump core.
See "systemctl status smbd.service" and "journalctl -xeu smbd.service" for details.
6. Output of "systemctl status smbd.service"
Code:
systemctl status smbd.service
× smbd.service - Samba SMB Daemon
    Loaded: loaded (/usr/lib/systemd/system/smbd.service; enabled; preset: enabled)
    Active: failed (Result: core-dump) since Thu 2024-08-22 14:25:23 CEST; 8s ago
      Docs: man:smbd(8)
            man:samba(7)
            man:smb.conf(5)
    Process: 96495 ExecCondition=/usr/share/samba/is-configured smb (code=exited, status=0/SUCCESS)
    Process: 96498 ExecStart=/usr/sbin/smbd --foreground --no-process-group $SMBDOPTIONS (code=dumped, signal=SEGV)
  Main PID: 96498 (code=dumped, signal=SEGV)
        CPU: 35ms

Aug 22 14:25:22 Microserver systemd[1]: Starting smbd.service - Samba SMB Daemon...
Aug 22 14:25:22 Microserver (smbd)[96498]: smbd.service: Referenced but unset environment variable evaluates to an empty string>
Aug 22 14:25:23 Microserver systemd[1]: smbd.service: Main process exited, code=dumped, status=11/SEGV
Aug 22 14:25:23 Microserver systemd[1]: smbd.service: Failed with result 'core-dump'.
Aug 22 14:25:23 Microserver systemd[1]: Failed to start smbd.service - Samba SMB Daemon.
7. Lastly the output of "sudo service samba status"
Code:
[sudo] password for microserver:
○ samba-ad-dc.service - Samba AD Daemon
    Loaded: loaded (/usr/lib/systemd/system/samba-ad-dc.service; enabled; preset: enabled)
    Active: inactive (dead) (Result: exec-condition) since Thu 2024-08-22 13:51:25 CEST; 28min ago
  Condition: start condition unmet at Thu 2024-08-22 13:51:25 CEST; 28min ago
      Docs: man:samba(8)
            man:samba(7)
            man:smb.conf(5)
    Process: 89812 ExecCondition=/usr/share/samba/is-configured samba (code=exited, status=1/FAILURE)
        CPU: 34ms

Aug 22 13:51:25 Microserver systemd[1]: Starting samba-ad-dc.service - Samba AD Daemon...
Aug 22 13:51:25 Microserver systemd[1]: samba-ad-dc.service: Skipped due to 'exec-condition'.
Aug 22 13:51:25 Microserver systemd[1]: Condition check resulted in samba-ad-dc.service - Samba AD Daemon being skipped.
I have spent over 5 hours getting it to work and lost count in the amount of reinstalls. My result is this. Can anyone help me get this SMB share running?

Thanks in advance
↧
↧

[ubuntu] why my ens33 interface at ubuntu 23.10 is not enabled as boot

August 22, 2024, 6:12 am
$
0
0
hello,
why my ens33 interface at ubuntu 23.10 boot and as kernel: 6.9.9-060909-generic
is not enabled on my vmware 16.x machine with vmware wokstation 17.x? :
Code:
ens33: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST>  mtu 1500
        inet 192.168.1.48 netmask 255.255.255.0 diffusion 192.168.1.255
        ether 00:0c:29:8b:91:22 txqueuelen 1000  (Ethernet)
        RX 1188539 bytes 1620041574 (1.6 GB) Packages
        RX errors 0 overruns of 1580 deleted 0 frame 0
        TX Packages 28792 bytes 3494784 (3.4 MB)
        Errors TX 0 Fall 0 Overruns 0 Carrier 0 Collisions 0

ens37: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  1500 mtu
        inet 192.168.1.36 netmask 255.255.255.0 broadcast 192.168.1.255
        ether 00:0c:29:8b:91:2c txqueuelen 1000  (Ethernet)
        RX 137316 bytes 148649057 (148.6 Mo) packages
        RX errors 0 overruns of 976 deleted 0 frame 0
        TX Packages 37846 bytes 16826331 (16.8 MB)
        Errors TX 0 Fall 0 Overruns 0 Carrier 0 Collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1 netmask 255.0.0.0.0
        inet6::1 prefixlen 128 scopeid 0x10<host>
        loop txqueuelen 1000  (local loop)
        Packages RX 88316 bytes 11370208 (11.3 MB)
        Errors RX 0 Drop 0 Overshoot 0 Frame 0
        Packages TX 88316 bytes 11370208 (11.3 MB)
        Errors TX 0 Fall 0 Overruns 0 Carrier 0 Collisions 0

Code:
alexandre@alexandre-developpeur:/opt/Qt$ nmcli --version
outil nmcli, version 1.44.2
alexandre@alexandre-developpeur:/opt/Qt$ NetworkManager --version
1.44.2
alexandre@alexandre-developpeur:/opt/Qt$
Regards
↧

[ubuntu] My USB Dongle (Archer T2U Plus) only scans for networks and displays an empty list.

August 23, 2024, 5:36 am
$
0
0
I was doing port forwarding in my vscode project the last time I used ubuntu. The next time I used ubuntu, my wifi dongle didn't even show up. After a day of troubleshooting, I was able to get the interface recognised by the hardware (it was showing unclaimed earlier). However, now I can't connect to any network because none show up.
Note: The same USB Dongle works just fine on windows, which is how I'm posting this thread as well.

Thank You
↧
Search

Realtek b851 WiFi Card doesn't work in Ubuntu

August 24, 2024, 12:30 am
$
0
0
Hello,

My wife recently bought a new computer (ASUS X1504VAP-NJ815W) and I tried to install Kubuntu LTS on it. Originally after installation the computer would go to a blank screen after reboots, however I fixed this fault by updating to the latest packages using a USB to Ethernet adapter. I am now trying to get the inbuilt WiFi card up and running but am running into issues. lspci reports the card as:

0000:01:00.0 Network controller: Realtek Semiconductor Co., Ltd. Device b851

I then googled this b851 and it seems that it should be part of the rtw89 driver found here:

https://github.com/lwfinger/rtw89

So I followed the installation instructions. However, when I run "make" as recommended in the readme, I get the following error:

/home/XXXX/rtw89/core.c: In function ‘rtw89_core_register_hw’:
/home/XXXX/rtw89/core.c:4678:37:error: ‘WIPHY_FLAG_DISABLE_WEXT’ undeclared (first use in this function)
4678 | hw->wiphy->flags |= WIPHY_FLAG_DISABLE_WEXT;
| ^~~~~~~~~~~~~~~~~~~~~~~
/home/XXXX/rtw89/core.c:4678:37:note: each undeclared identifier is reported only once for each function it
appears in
make[3]: *** [scripts/Makefile.build:243: /home/XXXX/rtw89/core.o] Error 1
make[2]: *** [/usr/src/linux-headers-6.8.0-31-generic/Makefile:1926: /home/XXXX/rtw89] Error 2
make[1]: *** [Makefile:240: __sub-make] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-6.8.0-31-generic'
make: *** [Makefile:104: all] Error 2

Any help would be greatly appreciated.

Cheers.
↧

Intel 8265/8275 drops connection every few seconds - Ubuntu 24.04 LTS

August 25, 2024, 4:47 am
$
0
0
As per pinned instructions:

https://dpaste.com/48MLK59T8

Pinging the default route shows the disconnection:

Code:
64 bytes from 192.168.1.1: icmp_seq=12 ttl=64 time=3.81 ms
64 bytes from 192.168.1.1: icmp_seq=13 ttl=64 time=3.31 ms
64 bytes from 192.168.1.1: icmp_seq=14 ttl=64 time=12.5 ms
64 bytes from 192.168.1.1: icmp_seq=15 ttl=64 time=1.70 ms
64 bytes from 192.168.1.1: icmp_seq=16 ttl=64 time=3.19 ms
64 bytes from 192.168.1.1: icmp_seq=17 ttl=64 time=4.91 ms
64 bytes from 192.168.1.1: icmp_seq=18 ttl=64 time=4.36 ms
64 bytes from 192.168.1.1: icmp_seq=19 ttl=64 time=13.2 ms
64 bytes from 192.168.1.1: icmp_seq=20 ttl=64 time=4.59 ms
64 bytes from 192.168.1.1: icmp_seq=21 ttl=64 time=2.67 ms
64 bytes from 192.168.1.1: icmp_seq=22 ttl=64 time=4.17 ms
64 bytes from 192.168.1.1: icmp_seq=23 ttl=64 time=4.15 ms
From 192.168.1.221 icmp_seq=24 Destination Host Unreachable
From 192.168.1.221 icmp_seq=25 Destination Host Unreachable
From 192.168.1.221 icmp_seq=26 Destination Host Unreachable
64 bytes from 192.168.1.1: icmp_seq=27 ttl=64 time=201 ms
From 192.168.1.221 icmp_seq=28 Destination Host Unreachable
From 192.168.1.221 icmp_seq=29 Destination Host Unreachable
From 192.168.1.221 icmp_seq=30 Destination Host Unreachable
64 bytes from 192.168.1.1: icmp_seq=31 ttl=64 time=9.95 ms
64 bytes from 192.168.1.1: icmp_seq=32 ttl=64 time=9.92 ms
64 bytes from 192.168.1.1: icmp_seq=33 ttl=64 time=7.59 ms
64 bytes from 192.168.1.1: icmp_seq=34 ttl=64 time=2.37 ms
64 bytes from 192.168.1.1: icmp_seq=35 ttl=64 time=3.58 ms
I had presumed it was a h/w problem since it is quite hot here this summer, but I see a lot of references to similar, so maybe it isn't.

Any ideas?
↧
↧

[SOLVED] Intermittent Wireless Drops

August 25, 2024, 7:18 am
↧

[ubuntu] wireless - iwlist scan - what are cell

August 25, 2024, 7:21 am
$
0
0
I using the 'iwlist' tool to get details about the wifi landscape at my location; however, I noticed items called 'cell'. Some of these cells have bogus mac addresses, and do not show SSIDs. Are these cells the radios from my router? For example: My ssid shows up as 'cell 01'; however, 'cell 02' and 'cell 03' are on the same channel as my SSID and signal strength and SNR are the same, but there is not listed SSID.

Just not sure how to read the iwlist output. Thank you
↧

Intermittent Wireless Drops

August 25, 2024, 7:34 am
$
0
0
Hello,

wirelessinfo.txt: https://paste.ubuntu.com/p/DWXpRm5RNn/

I'm trying to use an Ubuntu 24.04 LTS laptop as a mini home server. The laptop intermittently stops accepting incoming connections (ports 443, 8080, 32400 - SSH, Web, Plex). The server will work well for some short amount of time but will then stop working. The issue occurs regardless of the client used (Macbook, iPad, etc.), leading me to believe it is an issue with the server or the Starlink router. Rebooting the server or the client will restore connectivity for a short amount of time (several seconds to several hours). 127.0.0.1 always works.

Steps I've tried to troubleshoot:
1. Ensured Powermode is set to 'Performance'
2. Ensured the server is always on power, never just battery
3. Tried with NordVPN on and off on both the server and client (local network is whitelisted) -- VPN seems to have no effect on the issue
4. Set ../default-wifi-powersave-on.conf to 'wifi.powersave = 2'
5. Ensured the server has good wireless access to the router (never more than 20' with no obstructions)

Thank you for the help.
↧
Viewing all 23300 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>