-
Notifications
You must be signed in to change notification settings - Fork 6
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #1 from anthonyguella/develop
Fix dhcpcd bug
- Loading branch information
Showing
4 changed files
with
119 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,56 @@ | ||
# A sample configuration for dhcpcd. | ||
# See dhcpcd.conf(5) for details. | ||
|
||
# Allow users of this group to interact with dhcpcd via the control socket. | ||
#controlgroup wheel | ||
|
||
# Inform the DHCP server of our hostname for DDNS. | ||
hostname | ||
|
||
# Use the hardware address of the interface for the Client ID. | ||
clientid | ||
# or | ||
# Use the same DUID + IAID as set in DHCPv6 for DHCPv4 ClientID as per RFC4361. | ||
# Some non-RFC compliant DHCP servers do not reply with this set. | ||
# In this case, comment out duid and enable clientid above. | ||
#duid | ||
|
||
# Persist interface configuration when dhcpcd exits. | ||
persistent | ||
|
||
# Rapid commit support. | ||
# Safe to enable by default because it requires the equivalent option set | ||
# on the server to actually work. | ||
option rapid_commit | ||
|
||
# A list of options to request from the DHCP server. | ||
option domain_name_servers, domain_name, domain_search, host_name | ||
option classless_static_routes | ||
# Most distributions have NTP support. | ||
option ntp_servers | ||
# Respect the network MTU. This is applied to DHCP routes. | ||
option interface_mtu | ||
|
||
# A ServerID is required by RFC2131. | ||
require dhcp_server_identifier | ||
|
||
# Generate Stable Private IPv6 Addresses instead of hardware based ones | ||
slaac private | ||
|
||
# Example static IP configuration: | ||
#interface eth0 | ||
#static ip_address=192.168.0.10/24 | ||
#static ip6_address=fd51:42f8:caae:d92e::ff/64 | ||
#static routers=192.168.0.1 | ||
#static domain_name_servers=192.168.0.1 8.8.8.8 fd51:42f8:caae:d92e::1 | ||
|
||
# It is possible to fall back to a static IP if DHCP fails: | ||
# define static profile | ||
#profile static_eth0 | ||
#static ip_address=192.168.1.23/24 | ||
#static routers=192.168.1.1 | ||
#static domain_name_servers=192.168.1.1 | ||
|
||
# fallback to static profile on eth0 | ||
#interface eth0 | ||
#fallback static_eth0 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,57 @@ | ||
# A sample configuration for dhcpcd. | ||
# See dhcpcd.conf(5) for details. | ||
|
||
# Allow users of this group to interact with dhcpcd via the control socket. | ||
#controlgroup wheel | ||
|
||
# Inform the DHCP server of our hostname for DDNS. | ||
hostname | ||
|
||
# Use the hardware address of the interface for the Client ID. | ||
clientid | ||
# or | ||
# Use the same DUID + IAID as set in DHCPv6 for DHCPv4 ClientID as per RFC4361. | ||
# Some non-RFC compliant DHCP servers do not reply with this set. | ||
# In this case, comment out duid and enable clientid above. | ||
#duid | ||
|
||
# Persist interface configuration when dhcpcd exits. | ||
persistent | ||
|
||
# Rapid commit support. | ||
# Safe to enable by default because it requires the equivalent option set | ||
# on the server to actually work. | ||
option rapid_commit | ||
|
||
# A list of options to request from the DHCP server. | ||
option domain_name_servers, domain_name, domain_search, host_name | ||
option classless_static_routes | ||
# Most distributions have NTP support. | ||
option ntp_servers | ||
# Respect the network MTU. This is applied to DHCP routes. | ||
option interface_mtu | ||
|
||
# A ServerID is required by RFC2131. | ||
require dhcp_server_identifier | ||
|
||
# Generate Stable Private IPv6 Addresses instead of hardware based ones | ||
slaac private | ||
|
||
# Example static IP configuration: | ||
#interface eth0 | ||
#static ip_address=192.168.0.10/24 | ||
#static ip6_address=fd51:42f8:caae:d92e::ff/64 | ||
#static routers=192.168.0.1 | ||
#static domain_name_servers=192.168.0.1 8.8.8.8 fd51:42f8:caae:d92e::1 | ||
|
||
# It is possible to fall back to a static IP if DHCP fails: | ||
# define static profile | ||
#profile static_eth0 | ||
#static ip_address=192.168.1.23/24 | ||
#static routers=192.168.1.1 | ||
#static domain_name_servers=192.168.1.1 | ||
|
||
# fallback to static profile on eth0 | ||
#interface eth0 | ||
#fallback static_eth0 | ||
nohook wpa_supplicant |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters