Actions
Bug #503
closedOrfeo: new IPv4
Start date:
2017-02-06
Due date:
% Done:
100%
Estimated time:
(Total: 0:00 h)
Patch Available:
Confirmed:
No
Branch:
Entity:
DuckCorp
Security:
No
Help Needed:
No
Description
New IPv4 has been added in /etc/network/interfaces.d/wan
(see admin
encrypted repository) but services/DNS doesn't use the new address. Services configurations need to updated replacing the old IPv4 by the new one.
IPv4 configuration:
# old IPv4 iface eth0 inet static address 193.17.192.211/28 gateway 193.17.192.222 # new IPv4 iface eth0 inet static address 193.200.43.105/29 gateway 193.200.43.110
The list of services ([X]
updated and applied, [/]
updated (see .new files) not applied, [ ]
TODO) :
orfeo.duckcorp.org¶
[X]
postfix (ansible not used)/etc/postfix/helo_overrides.cf
updated, modification applied using:postmap /etc/postfix/helo_overrides.cf
/etc/postfix/main.cf
updated, modification applied using:systemctl reload postfix
[X]
dspam (ansible not used)/etc/dspam/dspam.conf
updated, modification applied usingsystemctl reload dspam.service
[X]
ircd-ratbox (ansible not used)/etc/ircd-ratbox/common_exempts.conf
and/etc/ircd-ratbox/ircd.conf
updated, modification will be applied while rebooting (#502)
[X]
ratbox-services (ansible not used)/etc/ratbox-services/ratbox-services.conf
updated, modification will be applied while rebooting (#502)
[X]
bind/etc/bind/master/duckcorp.org.zone /etc/bind/master/hurdfr.org.zone /etc/bind/master/milkypond.org.zone /etc/bind/named.conf /etc/bind/tsig.conf
toushirou.duckcorp.org¶
[X]
fail2ban/etc/fail2ban/jail.conf
updated, modification applied using:systemctl restart fail2ban.service
[X]
postfix/etc/postfix/main.cf
updated, modification applied using:systemctl reload postfix
[X]
bind/etc/bind/named.conf
,/etc/bind/tsig.conf
and/etc/bind/slave_zones.conf
updated, modifications applied usingsystemctl reload bind9.service
jinta.duckcorp.org¶
[X]
ircd-ratbox (ansible not used)/etc/ircd-ratbox/common_exempts.conf
and/etc/ircd-ratbox/ircd.conf
updated, modification will be applied while rebooting (#502)
Configuration managed using Ansible¶
- fail2ban: configuration was up to date but not applied (see 8d89acefcc85733d1823e6719ad77094ce46fb5d), configuration is now applied on all hosts
/etc/resolv.conf
: branchorfeo_new_ipv4
reviewed and merged, needs to be applied
Updated by Pierre-Louis Bonicoli almost 8 years ago
- Description updated (diff)
- Status changed from New to In Progress
- Assignee set to Pierre-Louis Bonicoli
- % Done changed from 0 to 40
- Security set to No
- Help Needed set to No
Updated by Pierre-Louis Bonicoli almost 8 years ago
- Related to Bug #502: Reboot servers (orfeo, jinta, thorfinn, toushirou) added
Updated by Marc Dequènes almost 8 years ago
- Description updated (diff)
- % Done changed from 40 to 80
Some Ansible rules to propagate, and then wait a few days before closing this bug.
Updated by Marc Dequènes almost 8 years ago
I guess this is finished and could be closed?
Updated by Pierre-Louis Bonicoli almost 8 years ago
- Category set to System :: Network
- Status changed from In Progress to Resolved
Indeed \o/
I have informed Acontios :)
Actions