I'm trying to set up a WiFi connection, but the passwords don't seem to
be saved. I'm also getting a pop up message "Failed to get secrets
for... No agents were available for this request". Is this a new
"feature" that resulted from an update? I haven't had this problem before.
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org
I've already installed " openvpn-client-export". Is that the one you mean?
On 05/02/2017 03:11 PM, Chuck Payne wrote:
> There's a plug in that you should download on your pfSense that makes
> export you openvpn much easier, I have it and I only down the config
> zip that made setup on my opensuse much easier
>
> On May 2, 2017 14:39, "James Knott" <james.knott(a)rogers.com
> <mailto:james.knott@rogers.com>> wrote:
>
> I'm trying to set up an OpenVPN, from my notebook to pfSence firewall.
> I have exported the ovpn file and can import it into Network Manager.
> However, I am unable to connect. One thing I've noticed is it
> asks for
> a private key password as well as a user password. When the ovpm file
> is created, I am only asked for the user ID & password.
>
> Has anyone else set up OpenVPN to pfSense firewall?
>
> tnx jk
>
>
> --
> To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
> <mailto:opensuse%2Bunsubscribe@opensuse.org>
> To contact the owner, e-mail: opensuse+owner(a)opensuse.org
> <mailto:opensuse%2Bowner@opensuse.org>
>
>
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org
I'm trying to set up an OpenVPN, from my notebook to pfSence firewall.
I have exported the ovpn file and can import it into Network Manager.
However, I am unable to connect. One thing I've noticed is it asks for
a private key password as well as a user password. When the ovpm file
is created, I am only asked for the user ID & password.
Has anyone else set up OpenVPN to pfSense firewall?
tnx jk
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org
Hello,
I tested a new server install with three disks as raid 1. No problem so far.
But for reason not related to the hardware, I finally decided to don't
use this server as main as expected and so want to reclaim some disks.
I found various but not plain clues from the net, so I simply poweroff
the computer, remove the disk (easy as this one was external esata) and
reboot.
The reboot is happening without any warning, yast2 do not show any problem
as the removed disk is to be reformatted anyway, is there some other
thing I have to do to get a clean system in the server?
I only see this in the logs:
md/raid1:md127: active with 2 out of 3 mirrors
and
Started Activate md array even though degraded
may be I can reduce boot time in some way?
thanks
jdd
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org
We have a new computer system with a RealTek USB-based Ethernet chip.
There are 4 physical ports, each with PoE.
Mysteriously, only one port seems to show up. No idea why. We have
tried the original openSUSE r8152 driver, the one that came with the
computer (2.00.0) and the latest from RealTek (2.08.0). It makes no
difference.
This is on an openSUSE 13.1 system (kernel 3.11.6-4-desktop). Which is
what we want to run here.
Mysteriously, lsusb only lists one MAC address:
Bus 003 Device 002: ID 0bda:8152 Realtek Semiconductor Corp.
CDC Ethernet:
iMacAddress 3 00073240415B
That is the MAC address we see. But there should be 3 more!
What we do see is:
4: enp0s20u10: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc
pfifo_fast state UP qlen 1000
link/ether 00:07:32:40:41:5b brd ff:ff:ff:ff:ff:ff
inet6 fe80::207:32ff:fe40:415b/64 scope link
valid_lft forever preferred_lft forever
The BIOS is minimal. We do not see anything that seems to control this.
I'm not a fan of this type of Ethernet interface. It is part of a
fanless computer specially designed to run in cars and trains...
Has anyone else gotten such a RealTek Ethernet chipset to work to work?
--
Roger Oberholtzer
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org
Hi,
Using Leap 42.2 and Thunderbird 45.8...
I use lightning and Provider for Google Calendar add-ons to link my
thunderbird calendar to my google calendar. I was having a problem witha
reminder coming up, and not being able to dismiss the event. So I
decided to unsubscribe to all my calendars.
So I unsubscribed to all calendars, restarted TB, and then went to add a
new calendar from the File -> New -> Calendar sequence. It offers to add
a network calendar, and so I choose network, and then google calendar. I
have 2 separate gmail accounts.
Then I input my gmail address for that calendar, and when it gives me a
list of calendars to subscribe to, it populates the list of available
calendars from my other gmail account, not from my first gmail account.
I cannot get it to populate the list from my first gmail account.
I tried to shut down TB, delete the calendar-data directory, and delete
the storage.sdb directory, and then restart TB and run the sequence
again to try and add back this calendar. But it is the same thing.
It seems that tb is defaulting to some list of calendars in a
configuration file somewhere, and so it is only looking at that one
gmail account to get the list of calendars, and it is not looking at the
other account.
Anyone know how to reset it?
If not, is there a TB forum that anyone knows of that might be able to
offer more specific help on thunderbird?
--
George
Box: 42.2 | KDE Plasma 5.8 | AMD Phenom IIX4 | 64 | 32GB
Laptop #1: 42.2 | KDE Plasma 5.8 | Core i7-4710HQ | 64 | 16GB
Laptop #2: 42.2 | KDE Plasma 5.8 | Core i5 | 64 | 8GB
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org
All,
Kudos to the opensuse team for pushing the 4.4.62 update out. That said, the
sheer number of btrfs bug fixes included is both encouraging and troubling at
the same time. Especially fundamental issues like:
- btrfs: do not write corrupted metadata blocks to disk (bsc#1012452).
- btrfs: Fix block size returned to user space (bsc#1012452).
- btrfs: fix invalid reference in replace_path (bsc#1012452).
- btrfs: fix listxattrs not listing all xattrs packed in the same item
(bsc#1012452).
- btrfs: fix truncate_space_check (bsc#1012452).
- btrfs: make sure we stay inside the bvec during __btrfs_lookup_bio_sums
(bsc#1012452).
- btrfs: reada: Add missed segment checking in reada_find_zone
(bsc#1012452).
- btrfs: reada: Avoid many times of empty loop (bsc#1012452).
- btrfs: Reset IO error counters before start of device replacing
(bsc#1012452).
- btrfs: use proper type for failrec in extent_state (bsc#1012452).
([security-announce] openSUSE-SU-2017:1140-1: important: Security update for
the Linux Kernel)
Now granted, I don't begin to understand all the intricacies of the btrfs
code and many of the above may be benign, but writing corrupted metadata to
disk, fixing block sizes, invalid references, staying inside bounds, missing
segment checking, basic profiling issues, failing to reset counters, use of
improper types, etc.. just doesn't sound good.
I'm glad to see things progressing, and I'll continue to monitor the list
for BTRFS issues (with a continuing trickle of
"During the last month I had to reinstall _all_ of them.
All with broken / inconsitent / strange behaving root
Btrfs file systems."
type posts)
Keep up the good work.
--
David C. Rankin, J.D.,P.E.
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org