On 04/11/2014 02:49 PM, Sean Darcy wrote:
On 04/11/2014 02:46 PM, Sean Darcy wrote:
> I've just upgraded to 20. I have a multihomed machine, two interfaces -
> "external" and "internal". external uses dhcp, internal has a
static
> address. But NM doesn't honor the static address, and uses dhcp on
> internal. The same setup worked in 19.
>
> cat ifcfg-internal
> # Please read /usr/share/doc/initscripts-*/sysconfig.txt
> # for the documentation of these parameters.
> BOOTPROTO=none
> DEVICE=internal
> TYPE=Ethernet
> IPV6INIT=no
> ONBOOT=yes
> USERCTL=no
> IPADDR=10.10.11.251
> PREFIX=24
> DEFROUTE=no
> IPV4_FAILURE_FATAL=no
> NAME="System CableMatters_USB_2(internal)"
>
> NM reads the file:
>
> NetworkManager[2355]: ifcfg-rh: parsing
> /etc/sysconfig/network-scripts/ifcfg-internal ...
> NetworkManager[2355]: ifcfg-rh: read connection 'System
> CableMatters_USB_2(internal)'
>
> but still calls dhclient:
>
> NetworkManager: DHCPDISCOVER on internal to 255.255.255.255 port 67
> interval 3 (xid=0x360c001)
> dhclient[2647]: DHCPDISCOVER on internal to 255.255.255.255 port 67
> interval 8 (xid=0x360c001)
>
> I've now disabled NM, and set it up manually.
>
> What's changed in 20 that breaks this?
>
> sean
>
>
Googling suggest I need to disable NM altogether:
http://danielgibbs.co.uk/2014/01/fedora-20-set-static-ip-address/
Is this correct? Can't NM handle static addresses?
sean
Changed the name of the connection to "internal" , same as the device.
Again, NM treated it as dynamic.
But someplace it has the correct info.
nmcli -a -p connection show configured internal
connection.id: internal
connection.uuid: ef5b0746-2604-b21f-c03e-00556aef68fc
connection.interface-name: internal
connection.type: 802-3-ethernet
connection.autoconnect: yes
connection.timestamp: 0
.....
ipv4.method: manual
ipv4.dns:
ipv4.dns-search:
ipv4.addresses: { ip = 10.10.11.251/24, gw =
0.0.0.0 }
ipv4.routes: { dst = 192.168.0.0/24, nh =
10.10.11.251, mt = 0 }
ipv4.ignore-auto-routes: no
ipv4.ignore-auto-dns: no
ipv4.dhcp-client-id: --
ipv4.dhcp-send-hostname: yes
ipv4.dhcp-hostname: --
ipv4.never-default: yes
ipv4.may-fail: yes
.........
Even stranger.
nmcli connection up internal
worked!
Really weird.
sean