Qippur's questions

We successfully mounted on a linux server a folder shared by an old (XP) windows panel PC.

# mount.cifs //192.168.X.Y/folder /mnt/folder

Once we inspected the folder on client machine, we noticed that all files showed the same name

# ls /mnt/folder/

Conca_0C Conca_0C Conca_0C Conca_0C Conca_0C Conca_0C Conca_0C Conca_0C Conca_0C

As we know the real names of the folders, we tried to list the contents of one of the folders accessing it by its real name.

The problem persists also in subfolders.

# ls /mnt/folder/Conca_01/

22D012322D01 22D012322D01

We tried setting and unsetting some mount.cifs parameters:

• iocharset
• mapchars
• mapposix
• vers (SMB version)
• posix
• unix
• linux
• posixpaths

all without success.

The only way we found it to work is via gio mount (gvfs), but we need this filesystem to be mounted at boot via fstab, and we found no way to use gio mount in fstab.

Unfortunately we do not have another windows machine in the same network to test a mount between machines with the same OS.

Any ideas?

Good day,

I am trying to set up a 3-node DRBD9 cluster

• 2 nodes actually have a disk
• the 2 nodes with disk have a direct link via a cross cable and a switch connection with third node
• third node is diskless and acts as a tie breaker

on all three nodes configuration is quite simple:

global_common.conf

global {
  usage-count yes;
}
common {
  net {
    protocol C;
        allow-two-primaries yes;
        transport "tcp";
  }
}

alice-bob.res:

resource alice-bob {
    volume 0 {
       device           minor 0;
       disk             /dev/zd0;
       meta-disk        internal;
    }

    on alice {
       node-id 0;
    }

    on bob {
       node-id 1;
    }

    on charlie {
       node-id 2;
       volume 0 {
           disk         none;
       }
    }

        connection {
        host alice      address 10.0.0.1:7001;
        host bob        address 10.0.0.2:7011;
        }
        connection {
        host alice      address 172.16.0.1:7002;
        host charlie    address 172.16.0.3:7021;
        }
        connection {
        host bob        address 172.16.0.2:7012;
        host charlie    address 172.16.0.3:7021;
        }
}

If DRBD is started on diskless node before the other two everything is fine. If it is started after them, it is shown as standalone.

relevant messages in kern.log on alice:

Apr 18 14:54:04 alice kernel: drbd alice-bob: Declined by peer bob (id: 1), see the kernel log there

on bob:

Apr 18 14:54:04 bob kernel: drbd alice-bob alice: Preparing remote state change 1639412379
Apr 18 14:54:04 bob kernel: drbd alice-bob alice: Aborting remote state change 1639412379

kernel module:

description:    drbd - Distributed Replicated Block Device v9.0.28-1

What am I missing here? Thanks in advance

I had a SSH key which I imported without problems in my GPG keyring as auth key using pem2openpgp from monkeysphere. The imported key works fine. I removed its SSH version from ~/.ssh and switched from ssh-agent to gnupg-agent with SSH support. The problem came when I purchased a Yubikey 4 and tried to move sign, encrypt and auth keys into it. All keys are 4k RSA. Sign and encrypt keys, created inside gpg, can be moved wihout issues, while the imported auth key is refused. I always get an "Invalid value" error message. If I create a new auth key - 4k RSA as the imported key, it can be moved without issues. I also tried to export and reimport my auth key from and to gpg keyring, without results. Yubikey support dismissed the case some time ago because a non-imported key works. Replacing my current key would be a lot of work, as I manage many servers. I would prefer avoiding it.

This is the debug log from scdaemon.

2020-03-03 22:39:26 scdaemon[4493] writing new key
2020-03-03 22:39:26 scdaemon[4493] RSA modulus size is 4096 bits
2020-03-03 22:39:26 scdaemon[4493] DBG: send apdu: c=00 i=DB p1=3F p2=FF lc=539 le=-1 em=-254
2020-03-03 22:39:26 scdaemon[4493] DBG:   PCSC_data: ...
2020-03-03 22:39:26 scdaemon[4493] DBG:   PCSC_data: ...
2020-03-03 22:39:26 scdaemon[4493] DBG:  response: sw=6A80  datalen=0
2020-03-03 22:39:26 scdaemon[4493] failed to store the key: Invalid value
2020-03-03 22:39:26 scdaemon[4493] operation writekey result: Invalid value
2020-03-03 22:39:26 scdaemon[4493] DBG: chan_7 -> ERR 100663351 Invalid value <SCD>

Any hint would be appreciated. Thanks in advance.

I created an organization (o=otherorg,dc=example,dc=com) inside my OpenLDAP server running on Debian stretch. Now I want to remove it, but no tool I tried allows me to. Below is a chunk of slapcat output I would like to remove the "dn: o=otherorg,dc=example,dc=com" entry I tried with:

ldapdelete -x -W -D "cn=admin,dc=example,dc=com" "o=otherorg,dc=example,dc=com"

I created a file named delete.ldif containing:

dn: o=otherorg,dc=example,dc=com
changetype: delete

and ran:

 ldapmodify -Y EXTERNAL -H ldapi:/// -f /path/to/delete.ldiff

All without success

dn: dc=example,dc=com
objectClass: top
objectClass: dcObject
objectClass: organization
o: example.com
dc: example
structuralObjectClass: organization
entryUUID: 99585550-02ab-1038-9dc9-000000000000
creatorsName: cn=admin,dc=example,dc=com
createTimestamp: 19700101164420Z
entryCSN: 19700101164420.615825Z#000000#000#000000
modifiersName: cn=admin,dc=example,dc=com
modifyTimestamp: 19700101164420Z
contextCSN: 19700101173944.872394Z#000000#000#000000
contextCSN: 19700101173733.720551Z#000000#001#000000

dn: cn=admin,dc=example,dc=com
objectClass: simpleSecurityObject
objectClass: organizationalRole
cn: admin
description: LDAP administrator
structuralObjectClass: organizationalRole
creatorsName: cn=admin,dc=example,dc=com
userPassword:: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX=
entryUUID: 995956ee-02ab-1038-9dca-000000000000
createTimestamp: 19700101164420Z
entryCSN: 19700101164420.622825Z#000000#000#000000
modifiersName: cn=admin,dc=example,dc=com
modifyTimestamp: 19700101164420Z

dn: o=otherorg,dc=example,dc=com
entryUUID: 7a6cd5be-02b3-1038-8346-000000000000
creatorsName: cn=admin,dc=example,dc=com
createTimestamp: 19700101173944Z
entryCSN: 19700101173944.872394Z#000000#000#000000
objectClass: top
objectClass: glue
structuralObjectClass: glue
modifiersName: cn=admin,dc=example,dc=com
modifyTimestamp: 19700101173944Z

We inherited the management of an ASA 5520 running IOS 8.2(3) from a previous company, and now we are switching the connectivity to a VPN from a LAN link directly connected to one of ASA interfaces.

Our skills on IOS are not very high.

While traffic through mainstream protocols (ssh, ftp, http...) flow seamlessly through the tunnel, all other traffic (e.g. rsync, NGINX on port 82...) is blocked. Needless to say, using LAN link there are no issues.

We set a permit ip any for the traffic coming from the VPN.

Looking at documentation, we made a test and ran:

Asa(config)# sysopt connection permit-vpn

This allowed all traffic to flow, but as we have different customers connecting via VPN, we cannot keep this option active.

We checked all ASA logs, which are stored in a log server, but we could find no hints in them.

We tried to find a solution via online documentation from Cisco and we browsed user groups, with no luck.

We believe the solution is so trivial that no one ever experienced the problem without solving it in a snap.

Any hints about what to check are warmly welcome. Our running-config is huge, and we believe it is not useful to post it all, but we can post suggested chunks if asked.