Re: [gentoo-user] eth0 fallback configuration is ignored
On 10/29/07, Mick [EMAIL PROTECTED] wrote:
On Sunday 28 October 2007, Dan Farrell wrote:
On Sun, 28 Oct 2007 12:19:13 +
Mick [EMAIL PROTECTED] wrote:
On Saturday 27 October 2007, Dan Farrell wrote:
On Sat, 27 Oct 2007 21:58:11 +0930
Iain Buchanan [EMAIL PROTECTED] wrote:
This behaviour is called APIPA (Automatic PRivate IP Addressing)
(from /etc/conf.d/net.example):
# APIPA is a module that tries to find a free address in the range
# Automatic Private IP Addressing (APIPA)
# use APIPA to find a free address in the range
# 169.254.0.0-169.254.255.255
It provides DHCP-like functionality without a DHCP server. Pretty
useless, unless you use it to configure all your IPs or a route for
that subnet.
Even worse, if your DHCP server comes up later, your PC will still
hold on to APIPA - not sure how this feature can be of any use to be
honest, but most devices these days from MS Windows to PDAs tend to
behave like this.
Let me correct myself here: my Gentoo boxen behave like this. A WinXP
that I
tested for this purpose does not. It comes up with the APIPA address and
when a router becomes available in the network later on, it readily
obtains a
dhcp address and drops the APIPA. Any idea how to configure Gentoo to do
the
same?
I think ifplugd does this.
eix ifplugd
* sys-apps/ifplugd
Available versions: 0.28-r7 ~0.28-r8 {doc}
Homepage:http://0pointer.de/lennart/projects/ifplugd/
Description: Brings up/down ethernet ports automatically with
cable detection
--
- Mark Shields
Re: [gentoo-user] eth0 fallback configuration is ignored
On Tuesday 30 October 2007, Mark Shields wrote: On 10/29/07, Mick [EMAIL PROTECTED] wrote: On Sunday 28 October 2007, Dan Farrell wrote: On Sun, 28 Oct 2007 12:19:13 + Mick [EMAIL PROTECTED] wrote: On Saturday 27 October 2007, Dan Farrell wrote: On Sat, 27 Oct 2007 21:58:11 +0930 Iain Buchanan [EMAIL PROTECTED] wrote: This behaviour is called APIPA (Automatic PRivate IP Addressing) (from /etc/conf.d/net.example): # APIPA is a module that tries to find a free address in the range # Automatic Private IP Addressing (APIPA) # use APIPA to find a free address in the range # 169.254.0.0-169.254.255.255 It provides DHCP-like functionality without a DHCP server. Pretty useless, unless you use it to configure all your IPs or a route for that subnet. Even worse, if your DHCP server comes up later, your PC will still hold on to APIPA - not sure how this feature can be of any use to be honest, but most devices these days from MS Windows to PDAs tend to behave like this. Let me correct myself here: my Gentoo boxen behave like this. A WinXP that I tested for this purpose does not. It comes up with the APIPA address and when a router becomes available in the network later on, it readily obtains a dhcp address and drops the APIPA. Any idea how to configure Gentoo to do the same? I think ifplugd does this. Not on my laptop . . . :( -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] eth0 fallback configuration is ignored
On Sunday 28 October 2007, Dan Farrell wrote: On Sun, 28 Oct 2007 12:19:13 + Mick [EMAIL PROTECTED] wrote: On Saturday 27 October 2007, Dan Farrell wrote: On Sat, 27 Oct 2007 21:58:11 +0930 Iain Buchanan [EMAIL PROTECTED] wrote: This behaviour is called APIPA (Automatic PRivate IP Addressing) (from /etc/conf.d/net.example): # APIPA is a module that tries to find a free address in the range # Automatic Private IP Addressing (APIPA) # use APIPA to find a free address in the range # 169.254.0.0-169.254.255.255 It provides DHCP-like functionality without a DHCP server. Pretty useless, unless you use it to configure all your IPs or a route for that subnet. Even worse, if your DHCP server comes up later, your PC will still hold on to APIPA - not sure how this feature can be of any use to be honest, but most devices these days from MS Windows to PDAs tend to behave like this. Let me correct myself here: my Gentoo boxen behave like this. A WinXP that I tested for this purpose does not. It comes up with the APIPA address and when a router becomes available in the network later on, it readily obtains a dhcp address and drops the APIPA. Any idea how to configure Gentoo to do the same? I was also wondering what kind of useful purpose this would serve. I am guessing that it would be enough for a network on one broadcast domain, if there is no need for any routing information. I am guessing that it is a way of getting two computers talking to each other when they find themselves connected, but without a router? -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] eth0 fallback configuration is ignored
On Mon, 29 Oct 2007 07:51:52 + Mick [EMAIL PROTECTED] wrote: Let me correct myself here: my Gentoo boxen behave like this. A WinXP that I tested for this purpose does not. It comes up with the APIPA address and when a router becomes available in the network later on, it readily obtains a dhcp address and drops the APIPA. Any idea how to configure Gentoo to do the same? I don't know, but as soon as you find out, let me know, OK? You could probably also set up a cron job to check every few seconds if the IP address is an APIPA address, and if it is, send out some sort of query to see if DHCP will work. I was also wondering what kind of useful purpose this would serve. I am guessing that it would be enough for a network on one broadcast domain, if there is no need for any routing information. I am guessing that it is a way of getting two computers talking to each other when they find themselves connected, but without a router? -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] eth0 fallback configuration is ignored
On Saturday 27 October 2007, Dan Farrell wrote: On Sat, 27 Oct 2007 21:58:11 +0930 Iain Buchanan [EMAIL PROTECTED] wrote: is it by any chance assigning you a 169... address? Did you recently upgrade dhcpcd to ... around ... 3.1.6 I think? Anyway, it now tries zeroconf or whatever it's called, to give you an address when there's no server around. Personally I don't like it, but you can decide :) This behaviour is called APIPA (Automatic PRivate IP Addressing) (from /etc/conf.d/net.example): # APIPA is a module that tries to find a free address in the range # Automatic Private IP Addressing (APIPA) # use APIPA to find a free address in the range # 169.254.0.0-169.254.255.255 It provides DHCP-like functionality without a DHCP server. Pretty useless, unless you use it to configure all your IPs or a route for that subnet. Even worse, if your DHCP server comes up later, your PC will still hold on to APIPA - not sure how this feature can be of any use to be honest, but most devices these days from MS Windows to PDAs tend to behave like this. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] eth0 fallback configuration is ignored
On Sun, 28 Oct 2007 12:19:13 + Mick [EMAIL PROTECTED] wrote: On Saturday 27 October 2007, Dan Farrell wrote: On Sat, 27 Oct 2007 21:58:11 +0930 Iain Buchanan [EMAIL PROTECTED] wrote: is it by any chance assigning you a 169... address? Did you recently upgrade dhcpcd to ... around ... 3.1.6 I think? Anyway, it now tries zeroconf or whatever it's called, to give you an address when there's no server around. Personally I don't like it, but you can decide :) This behaviour is called APIPA (Automatic PRivate IP Addressing) (from /etc/conf.d/net.example): # APIPA is a module that tries to find a free address in the range # Automatic Private IP Addressing (APIPA) # use APIPA to find a free address in the range # 169.254.0.0-169.254.255.255 It provides DHCP-like functionality without a DHCP server. Pretty useless, unless you use it to configure all your IPs or a route for that subnet. Even worse, if your DHCP server comes up later, your PC will still hold on to APIPA - not sure how this feature can be of any use to be honest, but most devices these days from MS Windows to PDAs tend to behave like this. I was also wondering what kind of useful purpose this would serve. I am guessing that it would be enough for a network on one broadcast domain, if there is no need for any routing information. -- [EMAIL PROTECTED] mailing list
[gentoo-user] eth0 fallback configuration is ignored
Hi, My /etc/conf.d/net says: config_eth0=( dhcp ) fallback_eth0=( 192.168.3.3/24 ) fallback_route_eth0=( default via 192.168.3.1 ) But dhcpcd is ignoring this. Instead it is using /var/lib/dhcpcd/dhcpcd-eth0.info to set eth0. This looks like the '-E' option is used, but where? How can I make my fallback configuration effective? Thanks, jules -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] eth0 fallback configuration is ignored
On Sat, 2007-10-27 at 13:48 +0200, Jules Colding wrote: Hi, My /etc/conf.d/net says: config_eth0=( dhcp ) fallback_eth0=( 192.168.3.3/24 ) fallback_route_eth0=( default via 192.168.3.1 ) But dhcpcd is ignoring this. Instead it is using /var/lib/dhcpcd/dhcpcd-eth0.info to set eth0. This looks like the '-E' option is used, but where? How can I make my fallback configuration effective? is it by any chance assigning you a 169... address? Did you recently upgrade dhcpcd to ... around ... 3.1.6 I think? Anyway, it now tries zeroconf or whatever it's called, to give you an address when there's no server around. Personally I don't like it, but you can decide :) If you read your elog messages you would have seen: You have installed dhcpcd with zeroconf support. This means that it will always obtain an IP address even if no DHCP server can be contacted, which will break any existing failover support you may have configured in your net configuration. This behaviour can be controlled with the -L flag. See the dhcpcd man page for more details. get rid of the zeroconf use flag or use -L. HTH, -- Iain Buchanan iaindb at netspace dot net dot au In ancient China there is a legend that one day a child will be born from a dragon, grow to be a man, and vanquish evil from the land. That man is not Chuck Norris, because Chuck Norris killed that man. -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] eth0 fallback configuration is ignored
Hi Iain,. On Sat, 2007-10-27 at 21:58 +0930, Iain Buchanan wrote: On Sat, 2007-10-27 at 13:48 +0200, Jules Colding wrote: Hi, My /etc/conf.d/net says: config_eth0=( dhcp ) fallback_eth0=( 192.168.3.3/24 ) fallback_route_eth0=( default via 192.168.3.1 ) But dhcpcd is ignoring this. Instead it is using /var/lib/dhcpcd/dhcpcd-eth0.info to set eth0. This looks like the '-E' option is used, but where? How can I make my fallback configuration effective? is it by any chance assigning you a 169... address? Yes, indeed it is. Did you recently upgrade dhcpcd to ... around ... 3.1.6 I think? 3.1.5-r1 actually. Anyway, it now tries zeroconf or whatever it's called, to give you an address when there's no server around. Personally I don't like it, but you can decide :) If you read your elog messages you would have seen: You have installed dhcpcd with zeroconf support. This means that it will always obtain an IP address even if no DHCP server can be contacted, which will break any existing failover support you may have configured in your net configuration. This behaviour can be controlled with the -L flag. See the dhcpcd man page for more details. get rid of the zeroconf use flag or use -L. Thanks a lot, will do. I didn't catch that message. Thanks, jules -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] eth0 fallback configuration is ignored
On Sat, 27 Oct 2007 21:58:11 +0930 Iain Buchanan [EMAIL PROTECTED] wrote: is it by any chance assigning you a 169... address? Did you recently upgrade dhcpcd to ... around ... 3.1.6 I think? Anyway, it now tries zeroconf or whatever it's called, to give you an address when there's no server around. Personally I don't like it, but you can decide :) This behaviour is called APIPA (Automatic PRivate IP Addressing) (from /etc/conf.d/net.example): # APIPA is a module that tries to find a free address in the range # Automatic Private IP Addressing (APIPA) # use APIPA to find a free address in the range # 169.254.0.0-169.254.255.255 It provides DHCP-like functionality without a DHCP server. Pretty useless, unless you use it to configure all your IPs or a route for that subnet. -- [EMAIL PROTECTED] mailing list
