Re: [arch-general] manually configure network

2017-07-12 Thread Mrrob 

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
bridgemobile_ppp  vlan-staticwireless-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@.serviceenabled
httpd.service enabled
lxdm.service  enabled
nmbd.service  enabled
openntpd.service  enabled
org.cups.cupsd.serviceenabled
postgresql.serviceenabled
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
---

Re: [arch-general] manually configure network

2017-07-12 Thread Rich 



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
bridgemobile_ppp  vlan-staticwireless-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@.serviceenabled
httpd.service enabled
lxdm.service  enabled
nmbd.service  enabled
openntpd.service  enabled
org.cups.cupsd.serviceenabled
postgresql.serviceenabled
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

Re: [arch-general] manually configure network

2017-07-12 Thread mick howe via arch-general 
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

Re: [arch-general] manually configure network

2017-07-12 Thread mick howe via arch-general 
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-dhcptuntapwireless-wpa-config
>> ​​
>> bonding  macvlan-static   vlan-dhcp
>> wireless-wpa-configsection
>> bridge   mobile_ppp   vlan-staticwireless-wpa-static
>> ethernet-custom  openvswitch  wireless-open
>> ethernet-dhcppppoewireless-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
>

Re: [arch-general] manually configure network

2017-07-12 Thread mick howe via arch-general 
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
> bridgemobile_ppp  vlan-staticwireless-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@.serviceenabled
httpd.service enabled
lxdm.service  enabled
nmbd.service  enabled
openntpd.service  enabled
org.cups.cupsd.serviceenabled
postgresql.serviceenabled
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?

Re: [arch-general] manually configure network

2017-07-12 Thread Rich 



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-dhcptuntapwireless-wpa-config
​​
bonding  macvlan-static   vlan-dhcp  wireless-wpa-configsection
bridge   mobile_ppp   vlan-staticwireless-wpa-static
ethernet-custom  openvswitch  wireless-open
ethernet-dhcppppoewireless-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

Re: [arch-general] manually configure network

2017-07-12 Thread mick howe via arch-general 
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-dhcptuntapwireless-wpa-config
​​
bonding  macvlan-static   vlan-dhcp  wireless-wpa-configsection
bridge   mobile_ppp   vlan-staticwireless-wpa-static
ethernet-custom  openvswitch  wireless-open
ethernet-dhcppppoewireless-wep

/etc/netctl/hooks:
.  ..

/etc/netctl/interfaces:
.  ..

>
> and
>
> $ systemctl list-unit-files --state=enabled
>
> ---
> mrrob
> ---
>

Re: [arch-general] manually configure network

2017-07-12 Thread Mrrob 

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.

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.


Look in /etc/netctl

and

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

---
mrrob
---

Re: [arch-general] [arch-dev-public] Changing compilation flags

2017-07-12 Thread Alex Xu via arch-general 
spec file? only supported by gcc, but that seems to be kinda the point
here. I think this is what most distros do (and possibly also how
--enable-default-* works).

[arch-general] manually configure network

2017-07-12 Thread mick howe via arch-general 
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.

Re: [arch-general] Changing compilation flags

2017-07-12 Thread Jordan Glover via arch-general 
I testes some rebuilded binaries and BINDNOW isn't always enabled:
checksec -f /usr/bin/unrar
RELRO
Partial RELRO
checksec -f /usr/bin/qml (qt5-declarative)
RELRO
Partial RELRO
I don't know if -fno-plt was correctly passed but it's possible that build 
process doesn't work as intended. Maybe we need to patch binutils to enable 
z,now by default as Daniel advised?
On Wed Jul 5 16:51:55 UTC 2017, Daniel Micay wrote:
>There"s no loss of compatibility from only some code using it. The only
>issue with it is that immediate binding *must* be used to support it, so
>if CFLAGS is respected then LDFLAGS *must* be respected, or immediate
>binding needs to be set as the default in the linker(s).
On Wed Jul 5 19:04:51 UTC 2017 , Daniel Micay wrote:
>So I think it would be a good idea to flip the default to -z,now in the linker
>if we're going to use -fno-plt. I think they'd take a patch for that upstream.
>Clang issue could be avoided with a 1 line patch adding another no-op flag
>and they'd take that upstream. It's harmless to use the slower lazy linking
>calling convention when -fno-plt is passed. -fno-plt code is fully compatible
>with non -fno-plt code, the only requirement is that -fno-plt code is linked
>with -Wl,-z,now which works fine for non -fno-plt code too and is desirable
>for security either way.

Re: [arch-general] tmux/systemd: tmux user service exits on detach/logout

2017-07-12 Thread David Runge 
Hey again,

On 2017-07-07 15:24:39 (+0200), David Runge wrote:
> I got a very strange behavior with tmux and systemd on my server and
> maybe someone knows a way around it.
> 
> The way I start tmux is as follows:
> Setting TMUX_TMPDIR to my user's XDG_RUNTIME_DIR and starting tmux in a
> systemd user service [1]. I do the same for other things, such as
> weechat [2]. They both use the same tmux.conf [3].
> Lingering is activated for my user, so the enabled user services will
> start with the system and stay running, even when it's disconnected...
> in theory (and this used to work very well, without a problem for
> years).
> 
> With some changes in systemd however, this seems to fail now, and I
> can't seem to find the reason why. Tmux just exits with "server lost"
> once I do a detach.
> At first I could only observe this behavior when I had a shared ssh
> session to the server (so I thought), that I then quit, or when I
> attached and detached the tmux session quickly.
> Now I'm getting this nearly every time I detach from the tmux session!
> 
> I tried several things by now, and it doesn't seem to make any
> difference:
> - using legacy cgroups [4], because of maybe being affected by this [5]
> - switching to single connections instead of shared connections for ssh
>   (lowered the amount of random tmux quits!)
> - using hardened kernel (just to try another one)
> - logging a tmux session, without getting any output, that would
>   explain, why this happens
> - crossing fingers (actually helps, because the bug seems completely
>   random ;/ )
> - using a system scope unit (tmux@username) [6], getting the same results
> - downgrading tmux to >=2.3 (no difference)
> - downgrading systemd to <=233-7 (seems to happen less frequently)
After a week of testing: tmux - in above mentioned setup - works much
more reliable with systemd 233-7.

Maybe any of the package maintainers can comment on it?

> For some awkward reason, it seems to have worked again for a short time,
> when Arch first switched to systemd 233 a few days back [6], but ever
> since it moved to systemd-stable [7], the problem is back (and even
> worse than before). Me thinking that might only be due to a "less
> frequent occurence" though.
So, in conclusion, the issue is most likely related to some changes
applied to the 233 branch in systemd-stable.

> [1] https://git.sleepmap.de/software/uenv.git/tree/user/tmux.service
> [2] https://git.sleepmap.de/software/uenv.git/tree/user/weechat.service
> [3] https://git.sleepmap.de/config/dotfiles.git/tree/.tmux.conf
> [4] 
> https://www.freedesktop.org/software/systemd/man/systemd.html#systemd.legacy_systemd_cgroup_controller
> [5] https://github.com/systemd/systemd/issues/3388
> [6] https://wiki.archlinux.org/index.php/Tmux#Autostart_with_systemd
> [7] 
> https://git.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/systemd=e0ee38b0c90d0a0da7baad4f472f38dd451326a6
> [8] https://github.com/systemd/systemd-stable

Best,
David


-- 
https://sleepmap.de


signature.asc
Description: PGP signature