On Wed, Mar 1, 2017 at 6:14 PM poma wrote:
> On 01.03.2017 17:11, Thomas Haller wrote:
> > On Wed, 2017-03-01 at 08:07 +0100, poma wrote:
> >> From 28b7713cda1deba1b54bd9e52b0d62716e356b66 Mon Sep 17 00:00:00
> >> 2001
> >> From: poma
> >> Date: Wed, 1 Mar 2017 07:05:40 +0100
> >> Subject: [PATC
On Mon, Nov 28, 2016 at 7:05 PM poma wrote:
>
> fg/c-e-ethernet-link2
>
> # egrep duplex\|speed /etc/NetworkManager/system-connections/enp3s0
> duplex=half
> speed=1000
>
> # nmcli -f 802-3-ethernet.duplex,802-3-ethernet.speed connection show
> enp3s0
> 802-3-ethernet.duplex: hal
Compile time checks for SELinux presence/status are simply wrong.
On Thu, Sep 29, 2016 at 3:11 PM Guido Trentalancia
wrote:
> When SELinux is enabled, do not create a symbolic link to a "resolv.conf"
> file outside /etc (e.g. in /var/run/NetworkManager), but instead create a
> regular file in /
Hi,
This actually works :)
Thanks
Jeka
On Wed, Aug 17, 2016 at 10:42 PM Thomas Haller wrote:
> On Wed, 2016-08-17 at 19:27 +0000, Jetchko Jekov wrote:
> > Hi Tomas,
> >
> > Unfortunately this doesn't work either. Maybe because 1st VPN server
> > pushes
0.0/8 and 10.x.x.x/32 (route to 2nd VPN server), still this second
route is ignored by NM
Just for the record: 1st VPN connection is managed by openconnect plugin.
Br,
Jeka
On Tue, Aug 16, 2016 at 11:48 PM Thomas Haller wrote:
> On Mon, 2016-08-15 at 21:51 +, Jetchko Jekov wrote
IP address in manual routes
specification.
And in my case I cant know this in advance (this is corporate VPN and I can
land on any of dozens entry points).
Jeka
On Mon, Aug 15, 2016 at 7:46 PM Thomas Haller wrote:
> On Sun, 2016-08-14 at 17:44 +, Jetchko Jekov wrote:
> > Hi guys,
>
Hi guys,
I have following problem:
I am trying to setup openvpn connection to VPN server accessible not via
default gateway.
Wnen NM configures vpn connection it sets the route to VPN server's IP
address wrongly via default gateway.
Here is an example:
- before activating VPN connection my routin
Ops, forgot to attach the file :/
On Wed, Nov 18, 2015 at 10:06 AM Jetchko Jekov
wrote:
> OK, I checked /usr/lib/udev/rules.d/85-nm-unmanaged.rules.
> I extended it for my purposes (why there aren't rules by default for
> libvirt and docker bridges btw?)
> I am including u
On Tue, Nov 17, 2015 at 11:45 PM Dan Williams wrote:
> On Tue, 2015-11-17 at 13:30 +0000, Jetchko Jekov wrote:
> > Hi,
> > Here it is.
>
> NM will always detect all kernel interfaces and expose them through its
> APIs, but it will *not* necessarily actively manage t
Hi,
Here it is.
Jeka
On Tue, Nov 17, 2015 at 2:25 PM Thomas Haller wrote:
> On Mon, 2015-11-16 at 21:58 +0000, Jetchko Jekov wrote:
> > OK, I spent some time with filtering of NM log. I removed the debug
> > lines related to WiFi connections management (they contain way too
>
such "huge" file here? Or shall I gzip (bzip2/xz ) it first?
Jeka
On Mon, Nov 16, 2015 at 4:57 PM Jetchko Jekov
wrote:
> I am not comfortable sending full NM log (even partially filtered) on
> public mailing list. is there a way to do it privately?
>
> Br,
> Jeka
>
&g
I am not comfortable sending full NM log (even partially filtered) on
public mailing list. is there a way to do it privately?
Br,
Jeka
On Mon, Nov 16, 2015 at 4:29 PM Thomas Haller wrote:
> On Mon, 2015-11-16 at 15:05 +0000, Jetchko Jekov wrote:
> > Hello,
> >
> > I am
Hello,
I am pretty sure that this question was raised several times already on
this list as I found some references when searching. But somehow none of
proposed settings work for me.
In general, I want to tell NM to ignore all virtual interfaces which are
not explicitly created with it. For examp
13 matches
Mail list logo
