Thanks for the reply Dan.
My primary use case is:
1)If wireless connection is available, always IPv4 routing should happen
through this interface though other wired interfaces exist.
2)If wireless connection is not available, then the existing behavior of
network manager should apply.
Also sa
* Dan Williams
> I poked at this today, using this config and your openvpn-2.4.0 RPMs:
>
> [...]
>
> but got no response from the server. Is it still up and configured?
> I've at least verified that the NM-openvpn IPv6 changes don't cause
> problems for my existing openvpn configurations, so th
On Wed, 2013-12-18 at 01:04 +0100, Tore Anderson wrote:
> * Tore Anderson
>
> > I'm working on setting up a test VPN server where I can reproduce it and
> > generate a backtrace to share (I don't dare to do that towards my
> > employer's VPN server).
>
> Ok, so now I have a dual-stacked OpenVPN t
On Mon, 2014-01-06 at 17:35 +, Robert Horovitz wrote:
> Hi Dan,
>
> thanks for your reply.
>
> > Ah, sorry. That block is for the connection files
> > in /etc/NetworkManager/system-connections, if that's where the
> > connection is stored.
> >
> > If the connection is instead stored in an i
On Mon, 2014-01-06 at 08:01 -0800, Scott Shambarger wrote:
> When NetworkManager initiates a expire->preinit->bound dhcp4 state
> change, the
> dispatcher scripts are given stale DHCP4_* values.
>
> Tracked the problem down to nm-device.c... when the dhcp configuration
> is
> updated, the dispat
On 01/06/2014 04:52 PM, Dan Williams wrote:
> Sorry about that, I was unclear. You'd actually want:
>
> dev disconnect
> reload
> con up
>
> the reload has to happen before the connection is brought up, since it's
> brought up with the values NM knows about, and those aren't updated
> until 'rel
On Mon, 2014-01-06 at 14:34 -0400, Jorge Fábregas wrote:
> On 01/06/2014 12:54 PM, Dan Williams wrote:
> > Manually modifying ifcfg files is definitely supported, though by
> > default you'll need to use "nmcli con reload" to tell NetworkManager
> > that you've made a change directly. (Alternative
On 01/06/2014 12:59 PM, Dan Williams wrote:
> As I alluded to in my other mail, at the moment NM doesn't implement
> direct changing of the interface's addresses/routes with immediate
> effect.
Understood. Thanks.
> In the future we will add the ability to change addresses/routes and
> other
On 01/06/2014 12:54 PM, Dan Williams wrote:
> Manually modifying ifcfg files is definitely supported, though by
> default you'll need to use "nmcli con reload" to tell NetworkManager
> that you've made a change directly. (Alternatively, NM can
> automatically notice changes if you set "monitor-con
Hi Dan,
thanks for your reply.
> Ah, sorry. That block is for the connection files
> in /etc/NetworkManager/system-connections, if that's where the
> connection is stored.
>
> If the connection is instead stored in an ifcfg file on Fedora or RHEL,
> then you'll want to use "DHCP_SEND_HOSTNAME=n
On Sat, 2014-01-04 at 20:41 -0700, Michael Butash wrote:
> Greetings,
>
> I installed kubuntu 13.10 tonight, and was trying to connect my vpn to
> work, but it seems that it won't start without having a managed ethernet
> adapter. Because of using likewise-open and kerberos for AD auth on
> lo
When NetworkManager initiates a expire->preinit->bound dhcp4 state
change, the
dispatcher scripts are given stale DHCP4_* values.
Tracked the problem down to nm-device.c... when the dhcp configuration
is
updated, the dispatcher is triggered before the dhcp4 state has been
updated.
I've attache
On Fri, 2014-01-03 at 18:52 -0400, Jorge Fábregas wrote:
> Hi everyone,
>
> Fedora 20 here. I'm learning my way through nmcli and I'm having a hard
> time trying to change an existing ip address (non-interactive way):
>
> nmcli con mod my-con-em1 ipv4.addresses 192.168.200.101/24 192.168.101.1
>
On Sat, 2014-01-04 at 14:01 -0400, Jorge Fábregas wrote:
> Hello again,
>
> I created a connection with this:
>
> nmcli con add con-name my-new-em1 ifname em1 type ethernet ip4
> 192.168.69.101/24 gw4 192.168.69.1
>
> Then I opened the Network Manager GUI and changed to that connection. I
> dou
On Fri, 2014-01-03 at 22:59 +, Robert Horovitz wrote:
> Hi Dan,
>
> thanks for your reply.
>
> > If you're using 'keyfile' configuration files, you can add the line
> > "dhcp-send-hostname=false" to the [ipv4] block to prevent sending the
> > hostname to the DHCP server. I don't believe it's
15 matches
Mail list logo
