Re: Updated info about disabling tracker related processes?
On Mon, May 21, 2018 at 3:03 PM, Dario Lesca wrote: > Il giorno lun, 21/05/2018 alle 10.57 +0200, Gianluca Cecchi ha scritto: > > Just a confirmation: the last command is needed only to purge old > generated files/databases for that connected user, correct? > > > Yes > > So in case of multiple users you need to run it for every one who has > logged in before to purge all? > > > Yes > > Thank! > > > -- > > Dario Lesca > (inviato dal mio Linux Fedora 28 Workstation) > > ___ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/users@lists. > fedoraproject.org/message/PEIQ27QVWNDH4P4KVAKRKTYB2PSCY6Z2/ > > today updates seemed to get in again tracker... seemed a weak dependency So after accepting and rebooting, again hog my cpu and I rexecuted the steps described by Dario that went this way [g.cecchi@ope46 ~]$ sudo -E dnf -y -C remove tracker-miners [sudo] password for g.cecchi: Dependencies resolved. PackageArch Version RepositorySize Removing: tracker-miners x86_64 2.0.5-1.fc28 @updates 3.6 M Removing unused dependencies: libgrssx86_64 0.7.0-6.fc28 @fedora 171 k Transaction Summary Remove 2 Packages strange... donna why tracker-miners came again and then I could remove without dependencies... Just to inform in case other guys update and don't notice Gianluca ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/I2VBCFOJY32TBSB5BZYAUCCNTMINJ3OG/
[389-users] Re: Expected Write/Read Behavior in a Supplier/Consumer scenario...
Hello David, Hello Mark, thank you very much for your answers! Today I also tried 'LDAP Sync refreshAndPersist' with the related protocol extensions. It works with the r/o (consumer) / r/w (supplier) topology and the corresponding 389 plugins. However, I came to the conclusion that I have to rethink my approach how to model the LDAP DIT with respect of 'eventual consistency' vs. my wrong ACID assumptions... Best, Artur :-) ___ 389-users mailing list -- 389-users@lists.fedoraproject.org To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org/message/DCHEV2IWMUQOOEQJRUW6MM5OED25F2VC/
Re: Cannot establish a L2TP/IPSec VPN connection
On Wed, Jul 4, 2018 at 7:21 AM, Gordon Messmer wrote: >>> >>> "915d709a-49b3-4928-8d5e-0f7e7a4de99a" #1: ignoring informational >>> payload NO_PROPOSAL_CHOSEN, msgid=, length=12 >>> Jul 03 18:50:10 xhost NetworkManager[900]: 003 >>> "915d709a-49b3-4928-8d5e-0f7e7a4de99a" #1: received and ignored >>> informational message >> >> >> This seems like a message that shouldn't be ignored or else the other end >> is labelling it incorrectly. According to that, it appears that your VPN >> client side isn't offering a connection setup that the server accepts. Make >> sure you have the right configuration. > > > Specifically, I think it means that either the phase 1 and phase 2 > algorithms proposed weren't accepted by the server, or the routes specified > in your configuration aren't acceptable. > > For an ipsec/l2tp connection, you don't need to add routes to the ipsec > connection, or use it as the default route. The routing will be > handled/specified in the l2tp layer. Thanks, Gordon. I think you were right: it seems that default phase 1 and phase 2 algorithms were not accepted by the server. I changed the algorithms, but still not able to establish the connection. The logs are below. Paul - Jul 04 11:12:41 xhost NetworkManager[911]: [1530699161.9279] audit: op="connection-activate" uuid="915d709a-49b3-4928-8d5e-0f7e7a4de99a" name="FEP VPN 3" pid=1564 uid=1000 result="success" Jul 04 11:12:41 xhost NetworkManager[911]: [1530699161.9371] vpn-connection[0x56336f4382e0,915d709a-49b3-4928-8d5e-0f7e7a4de99a,"FEP VPN 3",0]: Started the VPN service, PID 9514 Jul 04 11:12:41 xhost NetworkManager[911]: [1530699161.9473] vpn-connection[0x56336f4382e0,915d709a-49b3-4928-8d5e-0f7e7a4de99a,"FEP VPN 3",0]: Saw the service appear; activating connection Jul 04 11:12:42 xhost NetworkManager[911]: [1530699162.0548] vpn-connection[0x56336f4382e0,915d709a-49b3-4928-8d5e-0f7e7a4de99a,"FEP VPN 3",0]: VPN connection: (ConnectInteractive) reply received Jul 04 11:12:42 xhost nm-l2tp-service[9514]: Check port 1701 Jul 04 11:12:42 xhost NetworkManager[911]: Redirecting to: systemctl stop ipsec.service Jul 04 11:12:42 xhost NetworkManager[911]: warning: could not open include filename: '/etc/ipsec.d/*.conf' Jul 04 11:12:42 xhost libipsecconf[9544]: warning: could not open include filename: '/etc/ipsec.d/*.conf' Jul 04 11:12:42 xhost NetworkManager[911]: warning: could not open include filename: '/etc/ipsec.d/*.conf' Jul 04 11:12:42 xhost libipsecconf[9549]: warning: could not open include filename: '/etc/ipsec.d/*.conf' Jul 04 11:12:42 xhost NetworkManager[911]: warning: could not open include filename: '/etc/ipsec.d/*.conf' Jul 04 11:12:42 xhost libipsecconf[9562]: warning: could not open include filename: '/etc/ipsec.d/*.conf' Jul 04 11:12:42 xhost NetworkManager[911]: warning: could not open include filename: '/etc/ipsec.d/*.conf' Jul 04 11:12:42 xhost libipsecconf[9567]: warning: could not open include filename: '/etc/ipsec.d/*.conf' Jul 04 11:12:42 xhost NetworkManager[911]: Redirecting to: systemctl start ipsec.service Jul 04 11:12:43 xhost NetworkManager[911]: 002 listening for IKE messages Jul 04 11:12:43 xhost NetworkManager[911]: 002 adding interface enp3s0/enp3s0 192.168.1.4:500 Jul 04 11:12:43 xhost NetworkManager[911]: 002 adding interface enp3s0/enp3s0 192.168.1.4:4500 Jul 04 11:12:43 xhost NetworkManager[911]: 002 adding interface lo/lo 127.0.0.1:500 Jul 04 11:12:43 xhost NetworkManager[911]: 002 adding interface lo/lo 127.0.0.1:4500 Jul 04 11:12:43 xhost NetworkManager[911]: 002 adding interface lo/lo ::1:500 Jul 04 11:12:43 xhost NetworkManager[911]: 002 loading secrets from "/etc/ipsec.secrets" Jul 04 11:12:43 xhost NetworkManager[911]: 002 loading secrets from "/etc/ipsec.d/nm-l2tp-ipsec-06788735-e3e9-4051-a515-c7d9ed14aee7.secrets" Jul 04 11:12:43 xhost NetworkManager[911]: 003 WARNING: using a weak secret (PSK) Jul 04 11:12:43 xhost NetworkManager[911]: 002 loading secrets from "/etc/ipsec.d/nm-l2tp-ipsec-915d709a-49b3-4928-8d5e-0f7e7a4de99a.secrets" Jul 04 11:12:43 xhost NetworkManager[911]: 002 loading secrets from "/etc/ipsec.d/nm-l2tp-ipsec-abea2bcd-c2b7-46a8-993d-0f44aa7d6075.secrets" Jul 04 11:12:43 xhost NetworkManager[911]: 002 loading secrets from "/etc/ipsec.d/nm-l2tp-ipsec-eea9d5c0-b3b5-4a28-83a1-13b0ced7f080.secrets" Jul 04 11:12:44 xhost NetworkManager[911]: 002 listening for IKE messages Jul 04 11:12:44 xhost NetworkManager[911]: 002 forgetting secrets Jul 04 11:12:44 xhost NetworkManager[911]: 002 loading secrets from "/etc/ipsec.secrets" Jul 04 11:12:44 xhost NetworkManager[911]: 002 loading secrets from "/etc/ipsec.d/nm-l2tp-ipsec-06788735-e3e9-4051-a515-c7d9ed14aee7.secrets" Jul 04 11:12:44 xhost NetworkManager[911]: 003 WARNING: using a weak secret (PSK) Jul 04 11:12:44 xhost NetworkManager[911]: 002 loading secrets from "/etc/ipsec.d/nm-l2tp-ipsec-915d709a-49b3-4928-8d5e-0f7e7a4de99a.secrets" Jul 04 11:12:44 xhost NetworkManager[911]: 002 loading
DHCPv6 with qemu/kvm
Hi, I've used virsh to edit my networking configuration as so... default b53f97fd-1d87-4352-9da1-bbbf0a9419cf When the host system is booted I get the following for virbr0 virbr0: flags=4163 mtu 1500 inet 192.168.122.1 netmask 255.255.255.0 broadcast 192.168.122.255 inet6 2001:b030:112f:ff5b::::2 prefixlen 112 scopeid 0x0 inet6 fe80::5054:ff:fe9a:e849 prefixlen 64 scopeid 0x20 ether 52:54:00:9a:e8:49 txqueuelen 1000 (Ethernet) But on the guest system I see only. ens3: flags=4163 mtu 1500 inet 192.168.122.75 netmask 255.255.255.0 broadcast 192.168.122.255 inet6 fe80::e5c3:139f:1d2c:d126 prefixlen 64 scopeid 0x20 ether 52:54:00:e9:37:ee txqueuelen 1000 (Ethernet) Using wireshark on the host system I do see the following coming in 94 60.503493233 fe80::e5c3:139f:1d2c:d126 ff02::1:2 DHCPv6 147 Solicit XID: 0x8265dd CID: 0004094110c9abc2d4b95bf6d1c6c0300065 But there is no response for the request. Any ideas of what I may have missed? -- Conjecture is just a conclusion based on incomplete information. It isn't a fact. signature.asc Description: OpenPGP digital signature ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/2CKUFWSH6HXI565TZD3KGLT3GHC43YBY/
Re: Cannot establish a L2TP/IPSec VPN connection
On 07/03/2018 11:39 AM, Samuel Sieb wrote: On 07/03/2018 10:55 AM, Paul Smith wrote: "915d709a-49b3-4928-8d5e-0f7e7a4de99a" #1: ignoring informational payload NO_PROPOSAL_CHOSEN, msgid=, length=12 Jul 03 18:50:10 xhost NetworkManager[900]: 003 "915d709a-49b3-4928-8d5e-0f7e7a4de99a" #1: received and ignored informational message This seems like a message that shouldn't be ignored or else the other end is labelling it incorrectly. According to that, it appears that your VPN client side isn't offering a connection setup that the server accepts. Make sure you have the right configuration. Specifically, I think it means that either the phase 1 and phase 2 algorithms proposed weren't accepted by the server, or the routes specified in your configuration aren't acceptable. For an ipsec/l2tp connection, you don't need to add routes to the ipsec connection, or use it as the default route. The routing will be handled/specified in the l2tp layer. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/TZV6IHDTJQ3JABILRQ6LIIKEWUAYG5LU/
