Project

General

Profile

Anomalie #8434

Distribution EOLE - Anomalie #8429: Bastion: problème d’application des règles au démarrage et reconfigure

Redémarrer bastion sur les événements DHCP et PPPOE

Added by Daniel Dehennin almost 6 years ago. Updated over 5 years ago.

Status:
Fermé
Priority:
Normal
Assigned To:
Category:
-
Start date:
06/23/2014
Due date:
07/04/2014
% Done:

100%

Estimated time:
6.00 h
Spent time:
Distribution:
EOLE 2.4

Description

Si un changement d’adresse IP intervient sur une renégociation DHCP ou PPPOE, il faut redémarrer bastion (CreoleService bastion restart).

Associated revisions

Revision 60cd1098 (diff)
Added by Daniel Dehennin almost 6 years ago

Redémarrer bastion sur les événements DHCP et PPPOE

  • network-scripts/dhclient/bastion: Redémarrer bastion si un paramètre
    IP change lors d’un « BOUND » DHCP.
  • network-scripts/pppoe/bastion: Redémarrer bastion après une
    négociation PPPOE.
  • eole-common.mk: Installer les nouveaux scripts.

Fixes: #8434 @2h

Revision 1269a1a6 (diff)
Added by Daniel Dehennin almost 6 years ago

Installation des scripts DHCP et PPPOE

Ref: #8434 @10m

History

#1 Updated by Daniel Dehennin almost 6 years ago

  • Target version set to Eole 2.4.0.1
  • Estimated time set to 6.00 h

#2 Updated by Daniel Dehennin almost 6 years ago

  • Status changed from Nouveau to Accepté
  • Assigned To set to Daniel Dehennin

#3 Updated by Daniel Dehennin almost 6 years ago

Pour le DHCP cela semble être assez facile, en activant le mode debug des scripts /etc/dhcp/dhclient-enter-hooks.d/debug et /etc/dhcp/dhclient-exit-hooks.d/debug on obtient la liste des variables utilisables :

Wed Jun 25 12:18:21 CEST 2014: entering dhclient-enter-hooks.d, dumping variables.
reason='BOUND'
interface='eth0'
new_ip_address='192.168.230.168'
new_network_number='192.168.230.0'
new_subnet_mask='255.255.255.0'
new_broadcast_address='192.168.230.0'
new_routers='192.168.230.254'
new_domain_name='eole.lan'
new_domain_name_servers='192.168.232.2'
new_netbios_name_servers='192.168.232.5'
new_ntp_servers='192.168.232.2'
old_ip_address='192.168.230.168'
old_network_number='192.168.230.0'
old_subnet_mask='255.255.255.0'
old_broadcast_address='192.168.230.0'
old_routers='192.168.230.254'
old_domain_name='eole.lan'
old_domain_name_servers='192.168.232.2'
old_netbios_name_servers='192.168.232.5'
old_ntp_servers='192.168.232.2'
--------------------------
Wed Jun 25 12:18:21 CEST 2014: entering dhclient-exit-hooks.d, dumping variables.
reason='BOUND'
interface='eth0'
new_ip_address='192.168.230.168'
new_network_number='192.168.230.0'
new_subnet_mask='255.255.255.0'
new_broadcast_address='192.168.230.0'
new_routers='192.168.230.254'
new_domain_name='eole.lan'
new_domain_name_servers='192.168.232.2'
new_netbios_name_servers='192.168.232.5'
new_ntp_servers='192.168.232.2'
old_ip_address='192.168.230.168'
old_network_number='192.168.230.0'
old_subnet_mask='255.255.255.0'
old_broadcast_address='192.168.230.0'
old_routers='192.168.230.254'
old_domain_name='eole.lan'
old_domain_name_servers='192.168.232.2'
old_netbios_name_servers='192.168.232.5'
old_ntp_servers='192.168.232.2'
--------------------------

#4 Updated by Daniel Dehennin almost 6 years ago

  • Status changed from Accepté to Résolu
  • % Done changed from 0 to 100

#5 Updated by Daniel Dehennin almost 6 years ago

  • Project changed from Distribution EOLE to eole-common

#6 Updated by Benjamin Bohard over 5 years ago

  • Status changed from Résolu to Fermé

Also available in: Atom PDF