On 13 July 2017 at 01:17, Mrrob wrote:

On 13/07/17 07:09, mick howe via arch-general wrote:

...

I've just changed ISP and I can't get the changed configuration to stick.

I'm using 'static IP address - manual assignment' from Network configuration wiki page.

I need to change my address from 192.168.1.0/24 to 192.168.20.1/24.

using iproute2 tools as per wiki I can get everything working UNTIL I reboot, at which time some of the settings show the old values and others the new.

I've been manually configuring these settings without problems since I started using linux in 1994.

I assume that (as well as changing ISPs) you have changed your router and it has a different internal range to the old one.

​Correct​

If you have an IP address automatically after booting then something is bringing up the network automatically. Assuming your Arch install is newer than 2013 then I would expect you've configured netctl to manage the interface.

​About april 2013​ ​, can't remember details of what I did then but I would have used what was most like the ​the original method.

Look in /etc/netctl

[mick@cave ~]$ ls -aR /etc/netctl /etc/netctl: . .. examples hooks interfaces /etc/netctl/examples: . ethernet-static tunnel wireless-wpa .. macvlan-dhcp tuntap wireless-wpa-config ​​ bonding macvlan-static vlan-dhcp wireless-wpa-configsection bridge mobile_ppp vlan-static wireless-wpa-static ethernet-custom openvswitch wireless-open ethernet-dhcp pppoe wireless-wep /etc/netctl/hooks: . .. /etc/netctl/interfaces: . ..

and

$ systemctl list-unit-files --state=enabled

--- mrrob ---

On 13 July 2017 at 03:14, Rich wrote:

On 07/12/2017 09:58 PM, mick howe via arch-general wrote:

...

On 13 July 2017 at 01:17, Mrrob wrote:

On 13/07/17 07:09, mick howe via arch-general wrote:

...

I've just changed ISP and I can't get the changed configuration to stick.

...

I'm using 'static IP address - manual assignment' from Network configuration wiki page.

I need to change my address from 192.168.1.0/24 to 192.168.20.1/24.

using iproute2 tools as per wiki I can get everything working UNTIL I reboot, at which time some of the settings show the old values and others the new.

I've been manually configuring these settings without problems since I started using linux in 1994.

I assume that (as well as changing ISPs) you have changed your router

and it has a different internal range to the old one.

​Correct​

...

If you have an IP address automatically after booting then something is bringing up the network automatically. Assuming your Arch install is newer than 2013 then I would expect you've configured netctl to manage the interface.

​About april 2013​ ​, can't remember details of what I did then but I would have used what was most like the ​the original method.

...

Look in /etc/netctl

[mick@cave ~]$ ls -aR /etc/netctl /etc/netctl: . .. examples hooks interfaces

/etc/netctl/examples: . ethernet-static tunnel wireless-wpa .. macvlan-dhcp tuntap wireless-wpa-config ​​ bonding macvlan-static vlan-dhcp wireless-wpa-configsection bridge mobile_ppp vlan-static wireless-wpa-static ethernet-custom openvswitch wireless-open ethernet-dhcp pppoe wireless-wep

/etc/netctl/hooks: . ..

/etc/netctl/interfaces: . ..

...

and

$ systemctl list-unit-files --state=enabled

--- mrrob ---

You are probably using dhcpcd. This is what is installed when initially setting up the OS. Depending on exactly what settings are being reverted to default it may be normal behavior. What you need to do is find out exactly which network manager you are using and exactly what settings are not sticking across a reboot. The fix is probably not difficult but need more info to be able to make intelligent suggestions. I had a problem with dhcpcd reverting my DNS servers to the ISP defaults on every restart.

--Rich

On 07/12/2017 10:37 PM, mick howe via arch-general wrote:

On 13 July 2017 at 03:14, Rich wrote:

...

You are probably using dhcpcd. This is what is installed when initially setting up the OS. Depending on exactly what settings are being reverted to default it may be normal behavior. What you need to do is find out exactly which network manager you are using and exactly what settings are not sticking across a reboot. The fix is probably not difficult but need more info to be able to make intelligent suggestions. I had a problem with dhcpcd reverting my DNS servers to the ISP defaults on every restart.

--Rich

​I tried it when I first started with linux in 1994​ and now avoid it like the plague, I'd rather do it manually. It was simple until somebody decided I need a string of cascading daemons to do everything.

mick stressed out and frustrated in frozen glen innes

There was a simple elegance in rc.conf, e.g.: interface=eth0 address=192.168.1.17 netmask=255.255.255.0 broadcast=192.168.1.255 gateway=192.168.1.11 But with netctl, (https://wiki.archlinux.org/index.php/Netctl) it's not that much different. Instead of rc.conf, find your network interface with `ip addr` (enp0s10 below), create a profile in /etc/netctl (say /etc/netctl/mystaticip). You can pull an example of a static setup from /etc/netctl/examples. A minimal example (for ipv4) a static IP is something like: Description='A basic static ethernet connection' Interface=enp0s10 Connection=ethernet IP=static Address=('192.168.1.16/24') #Routes=('192.168.0.0/24 via 192.168.1.2') ## I don't use Gateway='192.168.1.13' DNS=('192.168.1.16') Then (after testing with e.g. 'netctl start mystaticip'), all you need to do to have it set each time you boot is issue the command # netctl enable mystaticip which will essentially create the hook required to activate your connection in /etc/systemd/system. Hopefully that will relieve some stress and frustration. -- David C. Rankin, J.D.,P.E.

On 07/12/2017 10:29 PM, mick howe via arch-general wrote:

On 13 July 2017 at 01:17, Mrrob wrote:

...

On 13/07/17 07:09, mick howe via arch-general wrote:

...

I've just changed ISP and I can't get the changed configuration to stick.

I'm using 'static IP address - manual assignment' from Network configuration wiki page.

I need to change my address from 192.168.1.0/24 to 192.168.20.1/24.

using iproute2 tools as per wiki I can get everything working UNTIL I reboot, at which time some of the settings show the old values and others the new.

I've been manually configuring these settings without problems since I started using linux in 1994.

I assume that (as well as changing ISPs) you have changed your router and it has a different internal range to the old one.

​Correct, and the ISP failed to include modem password in the box.

...

If you have an IP address automatically after booting then something is bringing up the network automatically. Assuming your Arch install is newer than 2013 then I would expect you've configured netctl to manage the interface.

​I had to reinstal when I moved in April 2013, would have used the simplest manual method ​

...

Look in /etc/netctl

[mick@cave ~]$ ls -aR /etc/netctl/etc/netctl: . .. examples hooks interfaces

...

/etc/netctl/examples: . ethernet-static tunnel wireless-wpa .. macvlan-dhcp tuntap wireless-wpa-config bonding macvlan-static vlan-dhcp wireless-wpa-configsection bridge mobile_ppp vlan-static wireless-wpa-static ethernet-custom openvswitch wireless-open ethernet-dhcp ​ ​ pppoe ​ ​ wireless-wep

/etc/netctl/hooks: . ..

/etc/netctl/interfaces: . ..

...

and

$ systemctl list-unit-files --state=enabled

[mick@cave ~]$ systemctl list-unit-files --state=enabled UNIT FILE STATE org.cups.cupsd.path enabled autovt@.service enabled dbus-org.freedesktop.network1.service enabled dbus-org.freedesktop.resolve1.service enabled display-manager.service enabled getty@.service enabled httpd.service enabled lxdm.service enabled nmbd.service enabled openntpd.service enabled org.cups.cupsd.service enabled postgresql.service enabled smbd.service enabled systemd-networkd.service enabled systemd-resolved.service enabled org.cups.cupsd.socket enabled systemd-networkd.socket enabled remote-fs.target enabled

18 unit files listed. lines 1-21 ​is blahbluhblah​network1.service the guilty party or is it systemd-networkd.service?

what am I looking for in these?

This is the wiki page for the network manager you are using: systemd-networkd https://wiki.archlinux.org/index.php/Systemd-networkd --Rich

On 13/07/17 11:29, mick howe via arch-general wrote:

On 13 July 2017 at 01:17, Mrrob wrote:

...

On 13/07/17 07:09, mick howe via arch-general wrote:

...

I've just changed ISP and I can't get the changed configuration to stick.

I'm using 'static IP address - manual assignment' from Network configuration wiki page.

I need to change my address from 192.168.1.0/24 to 192.168.20.1/24.

using iproute2 tools as per wiki I can get everything working UNTIL I reboot, at which time some of the settings show the old values and others the new.

I've been manually configuring these settings without problems since I started using linux in 1994.

I assume that (as well as changing ISPs) you have changed your router and it has a different internal range to the old one.

​Correct, and the ISP failed to include modem password in the box.

...

If you have an IP address automatically after booting then something is bringing up the network automatically. Assuming your Arch install is newer than 2013 then I would expect you've configured netctl to manage the interface.

​I had to reinstal when I moved in April 2013, would have used the simplest manual method ​

...

Look in /etc/netctl

[mick@cave ~]$ ls -aR /etc/netctl/etc/netctl: . .. examples hooks interfaces

...

/etc/netctl/examples: . ethernet-static tunnel wireless-wpa .. macvlan-dhcp tuntap wireless-wpa-config bonding macvlan-static vlan-dhcp wireless-wpa-configsection bridge mobile_ppp vlan-static wireless-wpa-static ethernet-custom openvswitch wireless-open ethernet-dhcp ​ ​ pppoe ​ ​ wireless-wep

/etc/netctl/hooks: . ..

/etc/netctl/interfaces: . ..

...

and

$ systemctl list-unit-files --state=enabled

[mick@cave ~]$ systemctl list-unit-files --state=enabled UNIT FILE STATE org.cups.cupsd.path enabled autovt@.service enabled dbus-org.freedesktop.network1.service enabled dbus-org.freedesktop.resolve1.service enabled display-manager.service enabled getty@.service enabled httpd.service enabled lxdm.service enabled nmbd.service enabled openntpd.service enabled org.cups.cupsd.service enabled postgresql.service enabled smbd.service enabled systemd-networkd.service enabled systemd-resolved.service enabled org.cups.cupsd.socket enabled systemd-networkd.socket enabled remote-fs.target enabled

18 unit files listed. lines 1-21 ​is blahbluhblah​network1.service the guilty party or is it systemd-networkd.service?

what am I looking for in these?

_They_ announced the change from netcfg to netctl on the 10th of April 2013. This isn't entirely relevant to the problem but may give insight into how you originally set it up. [0] If you want you can look at the old versions of the wiki page for netcfg. It looks like systemd-networkd.service is responsible [1]. I suggest you look to reconfigure that perhaps by looking for foo.network configs in /etc/systemd/network/ or using networkctl. [0] https://www.archlinux.org/news/netctl-is-now-in-core/ [1] https://wiki.archlinux.org/index.php/systemd-networkd --- mrrob ---