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

[ubuntu] Intel(R) Ethernet Connection I217-V - Ethernet not recognized - Ubuntu 18.04 LTS

$
0
0
Dear all,

I would like to abandon Windows for good and switch to linux once for all.

I am a total new comer to linux.

I have tried to install ubuntu 18.04 LTS a few months ago but, once the installation was complete, there were issues with the network card: I could not connect to my LAN. Since the computer is quite old I was pretty sure that the hardware should have been recognised easily, but apparently this was not the case.

My hardware is the following one:

Code:

Summary
        Operating System
            Windows 10 Pro 64-bit
        CPU
            Intel Core i5 4670 @ 3.40GHz    55 °C
            Haswell 22nm Technology
        RAM
            16,0GB Dual-Channel DDR3 @ 644MHz (9-9-9-24)
        Motherboard
            ASUSTeK COMPUTER INC. GRYPHON Z87 (SOCKET 1150)    34 °C
        Graphics
            Standard Monitor (1440x900@32Hz)
            2047MB NVIDIA GeForce RTX 2060 (Gigabyte)    68 °C
        Storage
            238GB Samsung SSD 840 PRO Series (SATA (SSD))    26 °C
            931GB Western Digital WDC WD10EFRX-68PJCN0 (SATA )    27 °C
        Optical Drives
            No optical disk drives detected
        Audio
            Realtek High Definition Audio

Here below please find some details about the networking hardware:

Code:

Adapters List
                Enabled
                        Broadcom 802.11ac Network Adapter
                       
                        Intel(R) Ethernet Connection I217-V

At the time, when I first tried to install ubuntu, I was stuck as I did not have any idea on how to install the correct driver for the I217-V controller. I also have a wireless card an Asus PCE-A56 (PCI-Ex1, 866mbit/s, 320 mbit/s) which uses a broadcom chip. From a quick search on the internet it appears that even this broadcom chip is not supported out of the box by ubuntu.

This is why I am now asking for help to install at least the ethernet controller driver. My idea is to download the drivers while windows is still on, transfer them to an usb stick and only then, install ubuntu. Once ubuntu is installed I should copy over the driver and proceed with the installation of the correct driver.

The first thing I looked for is the driver: link. Hopefully it is the correct one.

Is there anyone which could kindly illustrate me on how to proceed with the "manual" installation of the driver?

Thanks a lot.

andi

systemd-resolved.service is not loaded properly: Exec format error.

$
0
0
Hi!

I have a headless Ubuntu Server with some DNS trouble. After some troubeshooting to find out why it did not have an internet connection I found that starting systemd-resolved.service fixed the issue.
I didn't have time to figure out how to start it automatically at boot so I've been doing that manually via ssh for now.
This time it won't start the service;

Code:

$ sudo systemctl start systemd-resolved.service
Failed to start systemd-resolved.service: Unit systemd-resolved.service is not loaded properly: Exec format error.
See system logs and 'systemctl status systemd-resolved.service' for details.
$ systemctl status systemd-resolved.service
● systemd-resolved.service - dns
  Loaded: error (Reason: Exec format error)
  Active: inactive (dead)

Some advice on how to troubleshoot would be great!

System info:

Code:

$ uname -v
#74-Ubuntu SMP Tue Sep 17 17:06:04 UTC 2019
$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu 18.04.3 LTS"

HP Pavilion 590 with RTL8821CE or RT5392 PCIe doesn't see WiFi

$
0
0
Hi,
Recently I've bought an HP Pavilion 590-p0008nl at which I've mounted a NILOX wireless PCI express card [1] because I wasn't able to see my WiFi Network.

I'm using Ubuntu 18.04 with kernel 5.0.0-31-generic and this is the list of my network hardware:
Code:

sudo lshw -C network

 *-network               
      description: Wireless interface
      product: RT5392 PCIe Wireless Network Adapter
      vendor: Ralink corp.
      physical id: 0
      bus info: pci@0000:04:00.0
      logical name: wlp4s0
      version: 00
      serial: 78:44:76:c0:2b:b5
      width: 32 bits
      clock: 33MHz
      capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
      configuration: broadcast=yes driver=rt2800pci driverversion=5.0.0-31-generic firmware=0.40 latency=0 link=no multicast=yes wireless=IEEE 802.11
      resources: irq:57 memory:fe600000-fe60ffff
  *-network UNCLAIMED
      description: Network controller
      product: RTL8821CE 802.11ac PCIe Wireless Network Adapter
      vendor: Realtek Semiconductor Co., Ltd.
      physical id: 0
      bus info: pci@0000:17:00.0
      version: 00
      width: 64 bits
      clock: 33MHz
      capabilities: pm msi pciexpress cap_list
      configuration: latency=0
      resources: ioport:e000(size=256) memory:fe300000-fe30ffff
  *-network
      description: Ethernet interface
      product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
      vendor: Realtek Semiconductor Co., Ltd.
      physical id: 0
      bus info: pci@0000:1c:00.0
      logical name: enp28s0
      version: 15
      serial: c4:65:16:14:38:c7
      size: 10Mbit/s
      capacity: 1Gbit/s
      width: 64 bits
      clock: 33MHz
      capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
      configuration: autonegotiation=on broadcast=yes driver=r8169 duplex=half firmware=rtl8168h-2_0.0.2 02/26/15 latency=0 link=no multicast=yes port=MII speed=10Mbit/s
      resources: irq:48 ioport:d000(size=256) memory:fe504000-fe504fff memory:fe500000-fe503fff

I've tried to install the driver for RTL8821CE following the instructions described at https://github.com/tomaspinho/rtl8821ce and even disabling the SecureBoot I can't use my WiFi [2]. I think that procedure doesn't work properly with kernel 5.*.

Why I can't use my wireless PCI card? Do you think there is any kind of conflict between drivers?


[1] I used this PCI card with my previous PC under Ubuntu 16.04.
[2] The WiFi is seen only for a couple of seconds as soon as I turn on the PC.


Thanks.

10Ge SFP+ DAC link issues mlx4_en: enp5s0: Link Down - Link Up

$
0
0
Hello everyone. I have a strange networking issue. I've got a 'QNAP QSW-308-1C' 10Gbe sfp+ switch, a Mellanox MT26448 card, and a belkin 'F2CX036-10M' DAC cable.


I'm running Ubuntu 18.04.3 LTS, kernel 4.15.0-65-generic. The card is detected, the 'mlx4_en' module is loaded, and `ip link show` gives me the 'enp5s0' device. However `lshw -C network` shows 'link=no'. The indicator lights on the SPF+ port on the switch blink on and off. Link status light on the card came on briefly once. There is a repeating message in `dmsg`.

Code:

[21789.056195] mlx4_en: Mellanox ConnectX HCA Ethernet driver v4.0-0
[21789.056427] mlx4_en 0000:05:00.0: Activating port:1
[21789.056504] mlx4_en: 0000:05:00.0: Port 1: enabling only PFC DCB ops
[21789.058980] mlx4_en: 0000:05:00.0: Port 1: Using 8 TX rings
[21789.058981] mlx4_en: 0000:05:00.0: Port 1: Using 8 RX rings
[21789.059180] mlx4_en: 0000:05:00.0: Port 1: Initializing port
[21789.063402] mlx4_core 0000:05:00.0 enp5s0: renamed from eth1
[21789.110495] <mlx4_ib> mlx4_ib_add: mlx4_ib: Mellanox ConnectX InfiniBand driver v4.0-0
[21789.110864] <mlx4_ib> mlx4_ib_add: counter index 1 for port 1 allocated 1
[21802.388306] mlx4_en: enp5s0: Link Up
[21802.438230] mlx4_en: enp5s0: Link Down
[21821.670500] mlx4_en: enp5s0: Link Up
[21821.725437] mlx4_en: enp5s0: Link Down
[21943.956062] mlx4_en: enp5s0: Link Up
[21944.005986] mlx4_en: enp5s0: Link Down
[22058.549736] mlx4_en: enp5s0: Link Up
[22058.599698] mlx4_en: enp5s0: Link Down
[22089.342298] mlx4_en: enp5s0: Link Up
[22089.397239] mlx4_en: enp5s0: Link Down

Link Up / Link Down repeats forever unless I modprobe -r the driver. I'm fairly sure that the link led on the switch blinks in time to the dmesg notification.
Anyone have a clue where I should start troubleshooting?

More info below.
Code:

root@redacted:~# lspci |grep Mel;ip link show enp5s0;lsmod |grep mlx;echo -ne "dmseg link errors : ";dmesg |egrep "Up|Down"|wc -l
05:00.0 Ethernet controller: Mellanox Technologies MT26448 [ConnectX EN 10GigE, PCIe 2.0 5GT/s] (rev b0)
7: enp5s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
    link/ether 00:02:c9:51:a7:8e brd ff:ff:ff:ff:ff:ff
mlx4_ib              180224  0
ib_core              225280  1 mlx4_ib
mlx4_en              114688  0
mlx4_core            294912  2 mlx4_ib,mlx4_en
devlink                45056  3 mlx4_core,mlx4_ib,mlx4_en
ptp                    20480  1 mlx4_en
dmseg link errors : 698


:biggrin:And before anyone asks, yes, both ends of the cable are plugged in. :biggrin:

[ubuntu] Old IP comes back after every reboot

$
0
0
When I installed Ubuntu on my server I had set its IP addr static as 192.168.1.2.

Later I changed my subnet to 192.168.52.0 and set it to get its addr from DHCP server.

Normally everything works fine, but when I reboot my server its old IP addr comes back somehow. It's accessible from LAN and is able to connect to any device on LAN, using its DHCP addr, but oddly it can't connect to Internet.

See:

Code:

$ ifconfig
enp1s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.52.2  netmask 255.255.255.0  broadcast 192.168.52.255
        inet6 fdfa::e1b6:ea08:3491:5a56  prefixlen 64  scopeid 0x0<global>
        inet6 2804:xxx:xxx:5fed:a8d7:1a13:69a0:5dd1  prefixlen 64  scopeid 0x0<global>
        inet6 2804:yyy:yyy:dfb:635d:ac39:2ac4:448c  prefixlen 64  scopeid 0x0<global>
        inet6 fdfa::a8d7:1a13:69a0:5dd1  prefixlen 64  scopeid 0x0<global>
        inet6 2804:xxx:xxx:5fed:cf9d:4ca:68d4:7d7e  prefixlen 64  scopeid 0x0<global>
        inet6 2804:xxx:xxx:5fed::2  prefixlen 128  scopeid 0x0<global>
        inet6 2804:yyy:yyy:dfb::2  prefixlen 128  scopeid 0x0<global>
        inet6 2804:xxx:xxx:5fed:e1b6:ea08:3491:5a56  prefixlen 64  scopeid 0x0<global>
        inet6 fdfa::2  prefixlen 128  scopeid 0x0<global>
        inet6 2804:yyy:yyy:dfb:a8d7:1a13:69a0:5dd1  prefixlen 64  scopeid 0x0<global>
        inet6 fe80::b685:b26b:79a1:4011  prefixlen 64  scopeid 0x20<link>
        inet6 fdfa::87bb:2467:f949:2e0e  prefixlen 64  scopeid 0x0<global>
        ether e0:d5:5e:f2:64:5e  txqueuelen 1000  (Ethernet)
        RX packets 694695  bytes 104331390 (104.3 MB)
        RX errors 0  dropped 1  overruns 0  frame 0
        TX packets 705398  bytes 650543466 (650.5 MB)
        TX errors 0  dropped 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
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 1410944  bytes 298724888 (298.7 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1410944  bytes 298724888 (298.7 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

There's no reference to any 192.168.1, but when I try to reach Internet:

Code:

$ ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
From 192.168.1.2 icmp_seq=1 Destination Host Unreachable
From 192.168.1.2 icmp_seq=2 Destination Host Unreachable
From 192.168.1.2 icmp_seq=3 Destination Host Unreachable
From 192.168.1.2 icmp_seq=4 Destination Host Unreachable
From 192.168.1.2 icmp_seq=5 Destination Host Unreachable

How come that happens?

Then I use this command:

Code:

sudo ip addr del 192.168.1.2/24 dev enp1s0
And then it works again!

Code:

$ ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=52 time=31.0 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=52 time=31.9 ms
^C
--- 8.8.8.8 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1000ms
rtt min/avg/max/mdev = 31.076/31.491/31.907/0.451 ms

This seems like a ghost!

I could try to add a .sh to delete this addr during startup, but first I wanna try to figure out what's happening and fix it.

[ubuntu] SSH local port tunnel

$
0
0
Not deleting message in case someone else looking for similar answer.

I think the following works OK;

Code:

ssh -L port01:localhost:port01 -L port02:localhost:port02 user@remotehost
Folks,

I've often set up an ssh tunnel for a secure VNC connection but was wondering; is there a way to tunnel two ports for different services with the same connection or will it have to be two separate but concurrent connections?

Geffers

Trying to Compile Driver for Panda Wifi Adapter

$
0
0
Hi, apologies if this is the wrong forum. I'm getting the following errors when I compile for the Panda PAU05 wifi driver (why in the hell don't they just supply the driver?). Can someone tell me what is going wrong? I am running 16.04 LTS and using "make" command. I am by not stretch a linux pro but will understand if you tell me! Thanks!

Code:

/tftpboot/os/linux/../../sta/sta_cfg.c:4941:85: error: macro "__DATE__" might prevent reproducible builds [-Werror=date-time]
 intf(extra, size, "Driver version-%s, %s %s\n", STA_DRIVER_VERSION, __DATE__, _
                                                                    ^
/tftpboot/os/linux/../../sta/sta_cfg.c:4941:95: error: macro "__TIME__" might prevent reproducible builds [-Werror=date-time]
 , size, "Driver version-%s, %s %s\n", STA_DRIVER_VERSION, __DATE__, __TIME__ );
                                                                    ^
cc1: some warnings being treated as errors
scripts/Makefile.build:330: recipe for target '/tftpboot/os/linux/../../sta/sta_cfg.o' failed
make[2]: *** [/tftpboot/os/linux/../../sta/sta_cfg.o] Error 1
Makefile:1571: recipe for target '_module_/tftpboot/os/linux' failed
make[1]: *** [_module_/tftpboot/os/linux] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-4.15.0-65-generic'
Makefile:356: recipe for target 'LINUX' failed
make: *** [LINUX] Error 2

[ubuntu] DNS not working on ubuntu 19.04

$
0
0
I have a DNS problem that is bugging me for a long time.
Here is what happens:

1) First ping 8.8.8.8 works correctly but links www.slashdot.org does not. So, it is really a DNS problem.

2) accessing to the specific server works, that is nslookup yahoo.com 8.8.8.8 works correctly.

3) The DNS appears to work with
mathieu@kotohira:~$ journalctl -u systemd-resolved -f
-- Logs begin at Sat 2018-05-19 16:09:37 CEST. --
lis 21 10:50:23 kotohira systemd[1]: Stopping Network Name Resolution...
lis 21 10:50:23 kotohira systemd[1]: systemd-resolved.service: Succeeded.
lis 21 10:50:23 kotohira systemd[1]: Stopped Network Name Resolution.
-- Reboot --
lis 21 10:51:20 kotohira systemd[1]: Starting Network Name Resolution...
lis 21 10:51:21 kotohira systemd-resolved[857]: Positive Trust Anchors:
lis 21 10:51:21 kotohira systemd-resolved[857]: . IN DS 19036 8 2 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1 cdde32f24e8fb5
lis 21 10:51:21 kotohira systemd-resolved[857]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457 104237c7f8ec8d
lis 21 10:51:21 kotohira systemd-resolved[857]: Negative trust anchors: 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa 168.192.in-addr.arpa d.f.ip6.arpa corp home internal intranet lan local private test
lis 21 10:51:21 kotohira systemd-resolved[857]: Using system hostname 'kotohira'.
lis 21 10:51:21 kotohira systemd[1]: Started Network Name Resolution.

4) the result of systemd-resolve --status is

Global
LLMNR setting: no
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no
DNSSEC NTA: 10.in-addr.arpa
16.172.in-addr.arpa
168.192.in-addr.arpa
17.172.in-addr.arpa
18.172.in-addr.arpa
19.172.in-addr.arpa
20.172.in-addr.arpa
21.172.in-addr.arpa
22.172.in-addr.arpa
23.172.in-addr.arpa
24.172.in-addr.arpa
25.172.in-addr.arpa
26.172.in-addr.arpa
27.172.in-addr.arpa
28.172.in-addr.arpa
29.172.in-addr.arpa
30.172.in-addr.arpa
31.172.in-addr.arpa
corp
d.f.ip6.arpa
home
internal
intranet
lan
local
private
test
Link 4 (br-c20ac0e23c54)
Current Scopes: none
DefaultRoute setting: no
LLMNR setting: yes
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no
Link 3 (docker0)
Current Scopes: none
DefaultRoute setting: no
LLMNR setting: yes
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no
Link 2 (eno1)
Current Scopes: DNS
DefaultRoute setting: yes
LLMNR setting: yes
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no
Current DNS Server: 8.8.8.8
DNS Servers: 8.8.8.8
DNS Domain: ~.



Thus the server 8.8.8.8 is well indicated in the config.
Of course the DNS Domain is empty and this is a problem. But
a) I do not know what it is useful for.
b) I do not know how to set it as a google search returns plenty of bad hits.
c) It is not sure that setting it up would correct the problem

My questions:
1) How can I get detailed info on what goes wrong? nslookup -debug yahoo.com
does not show anything useful.
2) How to resolve the problem?
3) How to setup the DNS Domain? (I know what value it should be from another
computer on the same network that works correctly).

EAP-TLS & FreeRadius vs OpenVPN

$
0
0
At home I have a Unifi access point on a separate physical interface than trusted LAN. The AP is set up to operate on 2 subnets, 1 for IoT devices and a separate VLAN subnet intended for my trusted wireless laptops to gain access to the LAN for server administration. All this is local, at home, no remote access. My router is pfsense.

I’ve read that eap-tls with freeradius & firewall rules on the pfsense can be configured to allow only the laptop IPs via secure authentication & encryption. I’m curious which is best, eap-tls, or using OpenVPN? Thinking that later I may want to expand to allow remote VPN access. For now though, the goal is to hop from my wireless AP into LAN securely without allowing everyone in.

Samba Sharing a Mounted Partition in 18.04

$
0
0
After a bad 16.04 to 18.04 upgrade I've been trying to get my "server" (desktop version) back up and running.
One issue I'm still have is with network visibility and drive sharing.
I followed the guide below to setup up Samba:
https://linuxize.com/post/how-to-ins...-ubuntu-18-04/

I followed the steps, created users, and share folders. The user's share folders work, but the drive partitions do not.
There are two drives in a RAID 1 with two partitions created. Media for the Plex server, and Backup for backups. The partitions are mounted in Ubuntu as the OS is installed on a separate drive. After the bad upgrade was able to recreate the RAID and everything seems to be intact.

The Windows 10 network backup cannot use the Backup partition.
Windows discover does not see the server, but if I type in the IP address to map a partition it works.

Any help would be much appreciated! Thanks.

quick notes:
wins support is enabled and wins server = w.x.y.z is off.

[mark]
path = /samba/mark
browseable = no
read only = no
force create mode = 0660
force directory mode = 2770
valid users = mark @sadmin


[Backup]
path = /mnt/Backup
browseable = yes
read only = no
write list = @sambashare @sadmin
force create mode = 0660
force directory mode = 2770
valid users = @sambashare @sadmin


Here is my full smb.conf contents:

#======================= 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)

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable its WINS Server
wins support = yes

# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
# wins server = w.x.y.z

# This will prevent nmbd to search for NetBIOS names through DNS.
dns proxy = no

#### 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

# If you want Samba to only log through syslog then set the following
# parameter to 'yes'.
# syslog only = no

# We want Samba to log a minimum amount of information to syslog. Everything
# should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log
# through syslog you should set the following parameter to something higher.
syslog = 0

# 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 sever" 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

# If you are using encrypted passwords, Samba will need to know what
# password database type you are using.
passdb backend = tdbsam

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 = primary
# classic domain controller', 'server role = 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/adduser --quiet --disabled-password --gecos "" %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 uid = 10000-20000
; idmap gid = 10000-20000
; 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 (default) 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

[users]
path = /samba/users
browseable = yes
read only = no
force create mode = 0660
force directory mode = 2770
valid users = @sambashare @sadmin

[mark]
path = /samba/mark
browseable = no
read only = no
force create mode = 0660
force directory mode = 2770
valid users = mark @sadmin

[josh]
path = /samba/josh
browseable = no
read only = no
force create mode = 0660
force directory mode = 2770
valid users = josh @sadmin

[Media]
path = /mnt/Media
browseable = yes
read only = no
write list = @sambashare @sadmin
force create mode = 0660
force directory mode = 2770
valid users = @sambashare @sadmin

[Backup]
path = /mnt/Backup
browseable = yes
read only = no
write list = @sambashare @sadmin
force create mode = 0660
force directory mode = 2770
valid users = @sambashare @sadmin


[printers]
comment = All Printers
browseable = no
path = /var/spool/samba
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

[ubuntu] Long wait when booting

$
0
0
I am using Ubuntu 18.04 LTS Bionic Beaver on a Raspberry Pi3.

The onboard wifi chip has been disabled and instead I am using an external wifi dongle.

When the Pi is booted it waits for a long time (2mins?) before an error is produced and boot continues successfully. Wifi is then available.

The error states, "A start job is running for wait for network to be configured (1min 51s / no limit)" and continues with a "Failed to start................" I think it refers to the start job.

Networking is set up with Netplan 50-cloud-init.yaml as follows:

Code:

network:
    version: 2
    ethernets:
        eth0:
            dhcp4: true
            match:
                macaddress: b8:27:eb:81:46:0e
            set-name: eth0

network:
  version: 2
  renderer: networkd
  wifis:
    wlan0:
      dhcp4: no
      dhcp6: no
      addresses: [192.168.2.134/24]
      gateway4: 192.168.2.1
      nameservers:
        addresses: [192.168.2.1, 8.8.8.8]
      access-points:
        "xxxxxxxxxxxx_2.4GHz":
          password: "xxxxxxxxxxxxxxxxxxxxxxxxxxxxx"

Is such a long wait normal or are my wireless settings incorrect?

I have suffered a lot of settings resets due to failure to the onboard wifi chip not being usable and may have left a mess that has to be followed through by the system I suppose.

wireless-info.txt:

http://paste.ubuntu.com/p/KQrZrScNwZ/

[kubuntu] Kubuntu 19.10 not saving wifi password on boot up

$
0
0
Kubuntu 19.10 not saving wifi password on boot up. How do I correct this problem where the wifi password is saved so it does connect at boot up.
Thanks

[ubuntu] Ubuntu limiting the internet bandwith

$
0
0
Hello there!

Recently we have noticed that a few computers at work that use Ubuntu are having their internet speed limited.
We tried every troubleshooting method we could think of (more or less in this order):
- Restarted the affected computers,
- Changed the cables (including using a cable that provides the correct internet speed on other computers),
- Changed the switch settings for the affected computers,
- Changed the port in which the computer is connected to the switch,
- Changed most Ubuntu network settings

The only thing that changed the speed was using our office phone as a switch (connection became ISP -> Switch -> Phone -> Computer).

It's important to note that this issue affects just some of the computer running Ubuntu in the office. If the computer is running Windows it isn't affected.
Also important to note that only the download speed is affected, upload speeds are normal in all machines.

All connections are cabled. All machines running Ubuntu 19.04.

Attached to this post is a screenshot of an affected Ubuntu machine and another of a non-affected one, both taken almost at the same time with both machines running Chrome on Ubuntu 19.04.

[UbuntuGnome] help - Network Manager - adding usb modem - ethernet over usb.

$
0
0
I have some usb modems that support ethernet over usb(CDC NCM device) and as normal wireless AP. When in ethernet over usb mode, it presents itself as wwan0 and thru manual dhcpclient Ubuntu Desktop can connect to internet.

Is there any way to add this type of devices to Network Manager either thru cli or GUI ?.

I tried the documentation and could not find anything related to this.

Code:

Valid connection types: generic, 802-3-ethernet (ethernet), pppoe,
802-11-wireless (wifi), wimax, gsm, cdma, infiniband, adsl, bluetooth, vpn,
802-11-olpc-mesh (olpc-mesh), vlan, bond, team, bridge, bond-slave, team-slave,
bridge-slave, no-slave, tun, ip-tunnel, macvlan, vxlan

thanks in advance.

DNS PTR records

$
0
0
I'm finally beginning to add full IPv6 support to my networks and the first thing is to add PTR records for my mail servers.

My Public DNS records are held by my registrar Network Solutions, but my ISP provides the static IPV4 addresses. I use NAT 1 to 1 to translate incoming and outgoing traffic from a Private IPv4 to a Public IPv4.

I've read that the PTR record must be established by the ISP as "owner" of the IP addresses.

Can anyone tell me what do I need to do to get this set up properly?

19.10 on a Dell Inspiron 1521 no wifi.

$
0
0
I just installed Ubuntu 19.10 on an old Dell Inspiron 1521 but it did see the wifi card. I'm not sure what card is installed.
I had 14.04 on it before and it worked fine. Not sure what to do. I have it on a wire right now.
Any help would be great.

Get iface name with only pci location

$
0
0
I have an Dell E6400 running Kubuntu 18.10. This machine has an expresscard slot to which I currently have a wireless card connected. I know the "address" so to speak of the card. it is 0000:0e:00.0 The vendor ID is 168c:0024. I'm writing a script that tries to detect the presence of this card connected to the expresscard slot. if the device is connected the script is supposed to launch hostapd. I have not gooten tot eh hostapd portion of this little project so I will consider it out of scope for my question.

my question, therefore, is how do I find the interface name with just the "address", 0000:0e:00.0? I know systool -c net will list all iface names and their respective locations. but I want to list the one iface that's connected to address 0000:0e:00.0.

Does any body have any suggestions?

P.S. Let me know which is the best place for this thread, if posting to this division is inappropriate.

Thanks!

Super slow wifi connection

$
0
0
I have a HP250 laptop running Kubuntu 18.4 on it.
The laptop is about 5 yo, always running different version of Kubuntu and the wifi has always worked properly.
Since several weeks the wifi connection has become extremely slow. Most of the time it is impossible to charge any webpage (or download email etc). About every 5 minutes I get a few seconds of working connection and I can download and upload quite easily, until the connection goes back to useless again. This happens with all the wifi connections (at home, at work, in hotels etc)
A few things to be noted
- Ethernet connection works fine
- I feel like the wifi works better when, instead than connecting to the normal wifi networks, I connect to my phone mobile connection via tethering. I do not know if this makes any sense but I really feel the difference.
- I tried to use a live version of Kubuntu to understand if reinstalling the OS could have solved the issue. I only tried it for a few minutes, but the wifi connection seemed to be as slow and unreliable as always, so I have abandoned (so far) the idea of reinstalling the OS.
- Some weeks ago I had my laptop's back cover and hinges substituted, because they were in bad condition. I am not sure, but I wonder if this intervention could have damaged the wifi reception tool.


What do you think? Can you help me to understand if this is a software issue (and, in case, how I can solve it) or a hardware issue?

ubuntu server - start vpn client only for local resources

$
0
0
Good morning everybody,

I've a small home intranet with a local router with ZEROSHELL. I've set up a VPN server with ZS and my idea is to use it only to connect remotely and to reach the local PCs but not to be used as default gateway.

In the ubuntu 18.04 desktop, I can set up a VPN client selecting the "Use this connection only for the resources of its network". Perfect and done!

How do I achieve the same on an ubuntu 18.04 server?

In other terms:
I need to set up a VPN client on a web server ubuntu 18.04 which is used only for the resources of the intranet

At the moment when I connect the web server with vpn, the connection is fine but the web server uses it as default gateway...

Cheers

Not able to ping other IP

$
0
0
Code:

girish@girish-OptiPlex-3050:~$ lsb_release -a
No LSB modules are available.
Distributor ID:  Ubuntu
Description:      Ubuntu 16.04.3 LTS
Release:    16.04
Codename:  xenial


girish@girish-OptiPlex-3050:~$ uname -a
Linux girish-OptiPlex-3050 4.10.0-28-generic #32~16.04.2-Ubuntu SMP Thu Jul 20 10:19:48 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux


girish@girish-OptiPlex-3050:~$ route -n
Kernel IP routing table
Destination    Gateway        Genmask        Flags Metric Ref    Use Iface
0.0.0.0        192.168.0.1    0.0.0.0        UG    100    0        0 enp1s0
169.254.0.0    0.0.0.0        255.255.0.0    U    1000  0        0 enp1s0
192.168.0.0    0.0.0.0        255.255.255.0  U    100    0        0 enp1s0


girish@girish-OptiPlex-3050:~$ ifconfig -a
enp1s0    Link encap:Ethernet  HWaddr 54:bf:64:6c:fc:49
          inet addr:192.168.0.86  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::a980:f199:ad91:2f88/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:85510 errors:0 dropped:342 overruns:0 frame:0
          TX packets:3582 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:7170468 (7.1 MB)  TX bytes:257544 (257.5 KB)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:2459 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2459 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:211309 (211.3 KB)  TX bytes:211309 (211.3 KB)


girish@girish-OptiPlex-3050:~$ cat /etc/network/interfaces
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback

auto enp1s0
iface enp1s0 inet static
address 192.168.0.86
netmask 255.255.255.0
gateway 192.168.0.1
dns-nameservers 8.8.4.4 8.8.8.8


girish@girish-OptiPlex-3050:~$ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
#    DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 8.8.4.4
nameserver 8.8.8.8


girish@girish-OptiPlex-3050:~$ sudo lshw -class network
[sudo] password for girish:
  *-network             
      description: Ethernet interface
      product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
      vendor: Realtek Semiconductor Co., Ltd.
      physical id: 0
      bus info: pci@0000:01:00.0
      logical name: enp1s0
      version: 15
      serial: 54:bf:64:6c:fc:49
      size: 100Mbit/s
      capacity: 1Gbit/s
      width: 64 bits
      clock: 33MHz
      capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
      configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=full firmware=rtl8168h-2_0.0.2 02/26/15 ip=192.168.0.86 latency=0 link=yes multicast=yes port=MII speed=100Mbit/s
      resources: irq:125 ioport:e000(size=256) memory:f7004000-f7004fff memory:f7000000-f7003fff


girish@girish-OptiPlex-3050:~$ ping 192.168.0.86
PING 192.168.0.86 (192.168.0.86) 56(84) bytes of data.
64 bytes from 192.168.0.86: icmp_seq=1 ttl=64 time=0.059 ms
64 bytes from 192.168.0.86: icmp_seq=2 ttl=64 time=0.054 ms
64 bytes from 192.168.0.86: icmp_seq=3 ttl=64 time=0.061 ms
^C
--- 192.168.0.86 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2042ms
rtt min/avg/max/mdev = 0.054/0.058/0.061/0.003 ms



girish@girish-OptiPlex-3050:~$ ping 192.168.0.87
PING 192.168.0.87 (192.168.0.87) 56(84) bytes of data.
^C
--- 192.168.0.87 ping statistics ---
8 packets transmitted, 0 received, 100% packet loss, time 7130ms



girish@girish-OptiPlex-3050:~$ ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
From 192.168.0.86 icmp_seq=1 Destination Host Unreachable
From 192.168.0.86 icmp_seq=2 Destination Host Unreachable
From 192.168.0.86 icmp_seq=3 Destination Host Unreachable
^C
--- 192.168.0.1 ping statistics ---
7 packets transmitted, 0 received, +3 errors, 100% packet loss, time 6090ms
pipe 3

While I am able to access my local http://192.168.0.87:82/ in firefox.

Actually, I am going to add network printer which is shared on windows machine, but ubuntu is not finding it when I am trying to
configure it in ubuntu. So, post have two basic issues of :

1.Not able to ping other local IP and gateway.
2.Not finding the network printer which is shared on windows machine.

Kindly help me. I will try my best to provide you any other required info ASAP.

Thanks.
Viewing all 23300 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>