| View previous topic :: View next topic |
| Author |
Message |
erikderzweite
Tux's lil' helper
Joined: 25 Feb 2006
Posts: 143
|
 Posted: Wed Jul 16, 2008 5:37 am Post subject: fallback_eth0 fails: [solved] |
 |
|
I try to setup my wired interface to obtain static address if dhcp fails. Yet I get wrong static address. My /etc/conf.d/net snippet:
| Code: |
modules="!plug"
config_eth0=( "dhcp" )
dhcpcd_eth0="-t 10"
fallback_eth0=( "192.168.217.116 broadcast 192.168.217.255 netmask 255.255.255.0" )
fallback_route_eth0=( "default via 192.168.217.1" )
modules_wlan0=( "wpa_supplicant" )
wpa_supplicant_wlan0="-Dwext"
|
If I try to start net.eth0, I get:
| Code: | # /etc/init.d/net.eth0 restart --verbose
* Caching service dependencies ... [ ok ]
* Service net.eth0 stopping
* Stopping eth0
* Loading networking modules for eth0
* modules: apipa arping ccwgroup macchanger macnet rename netplugd iwconfig wpa_supplicant essidnet iptunnel ifconfig pppd system dhcpcd ip6to4
* Bringing down eth0
* Stopping dhcpcd on eth0 ... [ ok ]
* Stopping netplug on eth0 ... [ ok ]
* Shutting down eth0 ... [ ok ]
No resolv.conf for interface eth0
* Service net.eth0 stopped
* Service net.eth0 starting
* Starting eth0
* Loading networking modules for eth0
* modules: apipa arping ccwgroup macchanger macnet rename iwconfig essidnet iptunnel ifconfig pppd system dhcpcd ip6to4
* iwconfig provides wireless
* ifconfig provides interface
* pppd provides ppp
* dhcpcd provides dhcp
* Configuring eth0 for MAC address 0A:1B:0C:7D:FE:EF ... [ ok ]
* Wireless extensions not found for eth0
* Bringing up eth0
* dhcp
* Running dhcpcd ...
err, eth0: timed out
warn, eth0: using IPV4LL address 169.254.169.110 [ ok ]
* eth0 received address 169.254.169.110/16
* Service net.eth0 started
|
This happens on two computers. both of them have wlan0 interface, one as master, other uses wpa_supplicant. What could be the problem so eth0 ignores fallback values from /etc/conf.d/net? If I set static address, it starts correctly.
Last edited by erikderzweite on Wed Jul 16, 2008 2:03 pm; edited 1 time in total |
|
| Back to top |
|
 |
djanderson
Tux's lil' helper
Joined: 24 Mar 2004
Posts: 98
Location: Boulder, CO
|
| Posted: Wed Jul 16, 2008 6:54 am Post subject: |
|
|
From the dhcpcd.ebuild:
| Quote: | if use zeroconf; then
elog "You have installed dhcpcd with zeroconf support."
elog "This means that it will always obtain an IP address even if no"
elog "DHCP server can be contacted, which will break any existing"
elog "failover support you may have configured in your net configuration."
elog "This behaviour can be controlled with the -L flag."
elog "See the dhcpcd man page for more details." |
Hope that helps,
-Doug |
|
| Back to top |
|
|
erikderzweite
Tux's lil' helper
Joined: 25 Feb 2006
Posts: 143
|
| Posted: Wed Jul 16, 2008 1:20 pm Post subject: |
|
|
| djanderson wrote: | From the dhcpcd.ebuild:
| Quote: | if use zeroconf; then
elog "You have installed dhcpcd with zeroconf support."
elog "This means that it will always obtain an IP address even if no"
elog "DHCP server can be contacted, which will break any existing"
elog "failover support you may have configured in your net configuration."
elog "This behaviour can be controlled with the -L flag."
elog "See the dhcpcd man page for more details." |
Hope that helps,
-Doug |
That was the first thing I did. I have no problems with dhcpcd, it is the fallback that fails. |
|
| Back to top |
|
|
erikderzweite
Tux's lil' helper
Joined: 25 Feb 2006
Posts: 143
|
| Posted: Wed Jul 16, 2008 2:05 pm Post subject: |
|
|
Problem solved by setting
| Code: | | dhcpcd_eth0="-t 5 -L" |
Thanks for the advice. It is not clear, however, why this behavior is present, although I have compiled dhcpcd without zeroconf. |
|
| Back to top |
|
|
|
Networking & Security
