From: tglaser@b1-systems.de 
  
 >>>> (@all please keep me in Cc, d-devel is too high-volume to subscribe) 
  
 >With this, the interface does indeed come up, wait, and 
 >I get the expected IPv4 address€€€ but not the expected IPv6 
  
 Perhaps it makes sense to run dhcpcd per-interface with only 
 the expected address families enabled and convince upstream 
 that this is the necessary way forward for it to become viable. 
  
 It just cannot be that a DHCP client fucks up my IPv6 rtsol, 
 when not configured to touch IPv6 it should keep its hands 
 off it. And because we need to have the ability to use a 
 configuration where one interface has DHCP on IPv4 only but 
 the other on IPv6, a (one) global d€€mon with a global address 
 family setting cannot possibly work in a generic setting such 
 as a Debian network configuration integration. 
  
 Gru€€ 
 //Thorsten 
 -- 
 Thorsten Glaser 
 Linux / Unix Developer 
 Tel.: +49 160 91168501 
 E-Mail: tglaser@b1-systems.de 
  
 B1 Systems GmbH 
 Osterfeldstra€€e 7 / 85088 Vohburg / https://www.b1-systems.de/ 
 GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt, HRB 3537 
  
 --- SoupGate-Win32 v1.05 
  * Origin: you cannot sedate... all the things you hate (1:229/2)