Re: DHCP Problem
On Mon, 4 Dec 2023 05:55:50 +0100 wrote: > Wait a sec: before the clients get an answer from the DHCP server, > they don't have any route (at least not for the network in question), > so it doesn't make sense poking at them with ip route and things. > They send their request to the local network's segment broadcast > address. As I understand things, that's true of the first request a client makes, say, at boot. After that, the client knows which machine it got its last lease from and can query directly. -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
Re: DHCP Problem
On Sun, Dec 03, 2023 at 12:30:53PM -0700, Charles Curley wrote: > I am installing a new router which seems to work well so far. > > I have changed the DHCP server to use the new router's address, and shut > the server down and restarted it. Existing clients insist on using the > old router anyway. Is there any way to goose clients into using the new > one short of manually using the ip route command? Wait a sec: before the clients get an answer from the DHCP server, they don't have any route (at least not for the network in question), so it doesn't make sense poking at them with ip route and things. They send their request to the local network's segment broadcast address. What's possibly happening is that your old DCHP server is still up and running and faster than your new one, so its answers come in first. Cheers -- t signature.asc Description: PGP signature
Re: DHCP Problem, but where
On Sun, 3 Dec 2023 22:32:59 -0500 Jeffrey Walton wrote: > The "restart your dhcp clients" may have a sharp edge. Sometimes the > clients have a touch of resiliency or hardening added so they contact > their original dhcp server, and not a [possibly] rogue server setup by > an unknowing developer or attacker. In the past, you used to have to > reboot Microsoft clients to get them to use the new dhcp server. I > don't know Linux behavior. > > But if the problem is, dhcp clients are using the old dhcp server or > old dhcp lease info, then I would try to reboot a client if the > service restart did not help. I think the ISC dhclient (which is what I use here) does try to return to its original server. Rather than reboot anything, I simply stopped the DHCP server on that machine. Apparently clients then started back at the beginning. Shortening the lease time accelerates that process. -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
Re: DHCP Problem
On Sun, 3 Dec 2023 12:30:53 -0700 Charles Curley wrote: > I am installing a new router which seems to work well so far. > > I have changed the DHCP server to use the new router's address, and > shut the server down and restarted it. Existing clients insist on > using the old router anyway. Is there any way to goose clients into > using the new one short of manually using the ip route command? > > OK, stupid mistake of the week. The frustrating problem was that the clients kept getting the old router's IP address. This was for the simple reason that I had managed to not change the value of the "option routers" entry for the subnet. Doh! I have fixed that. Never be afraid to recheck your own work. I did shorten the lease times and that has accelerated the changeover. I didn't need to restart all the client's leases. Two days hence I'll change them back. -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
Re: DHCP Problem, but where
On Sun, Dec 3, 2023 at 9:57 PM jeremy ardley wrote: > > > On 4/12/23 05:18, Geert Stappers wrote: > > That triggered me to ask "Has the DHCP server been restarted?" > > > The default behaviour of most dhcp clients when they can't connect to a > dhcp server is to maintain the settings from any previous lease. > > A second default behaviour is for clients to not request new dhcp until > their existing dhcp lease has expired. > > To make sure a new dhcp setting is taken by all clients you need to > > - reconfigure your dhcp server > > - restart your dhcp server > > - check your dhcp server logs for any problems > > - restart your dhcp clients > > - check your client dhcp logs to see if the new lease info has been taken. > > There can be problems where a client with a specific MAC address > requests a specific ip address based on a previous lease but the server > is unwilling or unable to allocate that address to that MAC. This can be > checked in the server and client logs. It may also require flushing the > server lease tables and client configs so they can both start out > completely fresh. The "restart your dhcp clients" may have a sharp edge. Sometimes the clients have a touch of resiliency or hardening added so they contact their original dhcp server, and not a [possibly] rogue server setup by an unknowing developer or attacker. In the past, you used to have to reboot Microsoft clients to get them to use the new dhcp server. I don't know Linux behavior. But if the problem is, dhcp clients are using the old dhcp server or old dhcp lease info, then I would try to reboot a client if the service restart did not help. (I saw a similar attack happen as an undergrad at the University of Maryland. Someone in the CS department setup a Linux server with Kerberos running. Workstations got answers from the rogue server and got [useless] tickets granted, and the [useless] tickets could not be used for authenticating to other services on the UMBC network. It was an intermittent problem, and it took a couple of weeks to straighten it out). Jeff
Re: DHCP Problem, but where
On Sun, 3 Dec 2023 22:18:22 +0100 Geert Stappers wrote: > Has the DHCP server been restarted? Yes. -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
Re: DHCP Problem, but where
On 4/12/23 05:18, Geert Stappers wrote: That triggered me to ask "Has the DHCP server been restarted?" The default behaviour of most dhcp clients when they can't connect to a dhcp server is to maintain the settings from any previous lease. A second default behaviour is for clients to not request new dhcp until their existing dhcp lease has expired. To make sure a new dhcp setting is taken by all clients you need to - reconfigure your dhcp server - restart your dhcp server - check your dhcp server logs for any problems - restart your dhcp clients - check your client dhcp logs to see if the new lease info has been taken. There can be problems where a client with a specific MAC address requests a specific ip address based on a previous lease but the server is unwilling or unable to allocate that address to that MAC. This can be checked in the server and client logs. It may also require flushing the server lease tables and client configs so they can both start out completely fresh.
Re: DHCP Problem
On Sun, 3 Dec 2023 20:56:20 +0100 Marco Moock wrote: > Did you check with a sniffer that the answer from the DHCP includes > the new router address? Not with a sniffer, but I did check the lease file. Neither the router address nor the various lease times changed. -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
Re: DHCP Problem, but where
On Sun, Dec 03, 2023 at 04:03:39PM -0500, Henning Follmann wrote: > > On Dec 3, 2023, at 14:31, Charles Curley wrote: > > > > I am installing a new router which seems to work well so far. > > > > I have changed the DHCP server to use the new router's address, and shut > > the server down and restarted it. Existing clients insist on using the > > old router anyway. Is there any way to goose clients into using the new > > one short of manually using the ip route command? > > > > > > Did you flush the old leases from /var/lib/dhcpd ? > Just changing the config is not enough. That triggered me to ask "Has the DHCP server been restarted?" Groeten Geert Stappers -- Silence is hard to parse
Re: DHCP Problem
> On Dec 3, 2023, at 14:31, Charles Curley > wrote: > > I am installing a new router which seems to work well so far. > > I have changed the DHCP server to use the new router's address, and shut > the server down and restarted it. Existing clients insist on using the > old router anyway. Is there any way to goose clients into using the new > one short of manually using the ip route command? > > Did you flush the old leases from /var/lib/dhcpd ? Just changing the config is not enough. -H
Re: DHCP Problem
Am 03.12.2023 um 12:30:53 Uhr schrieb Charles Curley: > I have changed the DHCP server to use the new router's address, and > shut the server down and restarted it. Existing clients insist on > using the old router anyway. Is there any way to goose clients into > using the new one short of manually using the ip route command? Did you check with a sniffer that the answer from the DHCP includes the new router address? As long as the lease time of the old lease the route may stay in the routing table.
Re: Dhcp problem...what is the msitake?
On Wed, Nov 26, 2008 at 11:16:50PM +0100, Jesus arteche wrote: hardware ethernet xx:xx:xx:xx:xx:50; hardware ethernet xx:xx:xx:xx:xx:51; hardware ethernet xx:xx:xx:xx:xx:54; hardware ethernet xx:xx:xx:xx:xx:55; You actually have addresses ending with 50--55 like that? What you specify there must be the same as in the request you find in the logfile. Which addresses are issued to the clients? Do they get addresses in the subnets they are supposed to be in and just not the fixed ones they should get, or do they get totally different addresses? -- Don't let them, daddy. Don't let the stars run down. http://adin.dyndns.org/adin/TheLastQ.htm -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Dhcp problem...what is the msitake?
2008/11/27 Jesus arteche [EMAIL PROTECTED]:
hey,
I've implemented a dhcp server, I want to cretae several subnets inside the
same subnet using net mask, at teh same time i want to give the ip by mac.
The problem is that when the server get the mac dont give the correct ip to
the client, its like i didnt define it in conf file. The syslog shows how
the petition arrives but later the server dont give it the correct ip. Thats
my conf, can someone help me?:
What do you want to achieve with your separate subnets? At the moment
your group statements may be confusing things as you aren't using any
group features.
You don't need to specify domain name servers inside each host
declaration unless you want it to be different from the globally
defined setting above.
Below I have attached my dhcpd.conf file for you to look at, I have a
range of ip's 192.168.32 - 192.168.0.64 allocated automatically (for
visitors) and everything else is statically defined.
Also like Lee said, check your mac addresses, they need to match the
actual hardware. Unless you bought a box of nics then they aren't
going to be sequential (possibly even in a box they might not be
sequential).
Adrian
# dhcpd.conf
#
# Sample configuration file for ISC dhcpd
#
# option definitions common to all supported networks...
option domain-name lefty;
option domain-name-servers 192.168.0.5, 192.168.0.1;
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.0.255;
option routers 192.168.0.1;
server-name caprica.lefty;
default-lease-time 43200;
max-lease-time 86400;
subnet 192.168.0.0 netmask 255.255.255.0 {
range 192.168.0.32 192.168.0.64;
}
subnet 192.168.100.0 netmask 255.255.255.0 {
not authoritative;
}
#subnet 192.5.5.0 netmask 255.255.255.224 {
# range 192.5.5.26 192.5.5.30;
# option domain-name-servers bb.home.vix.com, gw.home.vix.com;
# option domain-name vix.com;
# option routers 192.5.5.1;
# option subnet-mask 255.255.255.224;
# option broadcast-address 192.5.5.31;
# default-lease-time 600;
# max-lease-time 7200;
#}
# Fixed IP addresses can also be specified for hosts. These addresses
# should not also be listed as being available for dynamic assignment.
# Hosts for which fixed IP addresses have been specified can boot using
# BOOTP or DHCP. Hosts for which no fixed address is specified can only
# be booted with DHCP, unless there is an address range on the subnet
# to which a BOOTP client is connected which has the dynamic-bootp flag
# set.
#host caprica {
# hardware ethernet 00:40:CA:19:1F:44;
# option domain-name lefty;
# fixed-address 192.168.0.1;
#}host starbuck {
#On board lan card (suspect)
#hardware ethernet 00:40:CA:19:0B:84;
hardware ethernet 00:E0:29:9D:BF:13;
option domain-name qld.optushome.com.au lefty;
fixed-address starbuck.lefty;
}
host bruce {
hardware ethernet 00:02:E3:0E:5F:8B;
option domain-name qld.optushome.com.au lefty;
fixed-address bruce.lefty;
}
host brucelaptop {
hardware ethernet 00:C0:9F:B4:3C:91;
option domain-name qld.optushome.com.au lefty;
fixed-address brucelaptop.lefty;
}
host ibm {
hardware ethernet 00:A0:24:AC:47:BF;
option domain-name lefty;
fixed-address ibm.lefty;
}
host earth {
hardware ethernet 00:11:95:66:17:73;
option domain-name qld.optushome.com.au lefty;
fixed-address earth.lefty;
}
host gallactica {
hardware ethernet 00:40:F4:05:10:58;
option domain-name qld.optushome.com.au lefty;
fixed-address gallactica.lefty;
}
host Brother-MFC {
hardware ethernet 00:80:77:8E:05:A4;
fixed-address brother-mfc.lefty;
}
host Netgear-FS526T {
hardware ethernet 00:09:5B:62:14:D7;
fixed-address switch.lefty;
}
host xbox {
hardware ethernet 00:0d:3a:53:27:fa;
fixed-address xbox.lefty;
}
host n95 {
hardware ethernet 00:1e:3a:92:fd:fc;
fixed-address n95.lefty;
}
host cloud9 {
hardware ethernet 00:1B:24:F7:C4:1D;
hardware ethernet 00:1D:E0:30:1F:D5;
fixed-address cloud9.lefty;
}
host WRT54GL-lan {
hardware ethernet 00:21:29:9D:B2:A1;
fixed-address wrt54gl-lan.lefty;
}
host WRT54GL-wan {
hardware ethernet 00:21:29:9D:B2:A2;
fixed-address wrt54gl-wan.lefty;
}
host WRT54GL-wir {
hardware ethernet 00:21:29:9D:B2:A3;
fixed-address wrt54gl-air.lefty;
}
host gemini.lefty {
hardware ethernet 00:A0:CC:D6:38:DE;}
}
# If a DHCP or BOOTP client is mobile and might be connected to a variety
# of networks, more than one fixed address for that host can be specified.
# Hosts can have fixed addresses on some networks, but receive dynamically
# allocated address on other subnets; in order to support this, a host
# declaration for that client must be given which does not have a fixed
# address. If a client should get different parameters depending on
# what subnet it boots on, host declarations for each such network should
# be given. Finally, if a domain name is given for a host's fixed address
# and that domain name evaluates to more than one address, the address
# corresponding to the network to which
Re: dhcp problem
I had a similar problem. The file /etc/dhcp3/dhclient.conf is the file that controls resolv.conf (at least on this system). You can specify which DNS is used first by using prepend domain-name-servers xxx.xxx.xxx.xxx; replacing of course the x's with the ip address of the DNS. This line is already present using 127.0.0.1 but is commented out. I have tried it, and it works. Yea, it's working, thanks. Joe - -- Registerd Linux user #443289 at http://counter.li.org/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGC+tsiXBCVWpc5J4RArQdAKDO10MEfaW4p/3oBrJbWO3NplhEtQCghLNz GZiR4zMqeuWw4Qy33w6LmjY= =3+HX -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- S. M. Ibrahim (Lavlu) Web Application Developer somewherein... Home page: http://lavluda.tripod.com Blog: http://lavluda.tk Yahoo!! ID: lavluda MSN ID: lavluda Skype : lavluda
Re: dhcp problem
On Thu, 29 Mar 2007 20:54:34 +0600 S. M. Ibrahim (Lavlu) [EMAIL PROTECTED] wrote: My isp is providing me the ip using DHCP. everything fine. But they are sending 3 nameserver. And first DNS server is not responding. SO it take time to switch to the secound dns. So, it's making problem (slow down). I want to keep fix (will not updated or replace by dhcp) the /etc/resolv.conf with only 2 nameserver (that are working). Any idea, how to do this ? From 'man dhclient': The supersede statement supersede [ option declaration ] ; If for some option the client should always use a locally-configured value or values rather than whatever is supplied by the server, these values can be defined in the supersede statement. So if you're using dhclient you could try something like: supersede domain-name-servers a.b.c d.e.f Also from the manpage: The request statement request [ option ] [, ... option ]; The request statement causes the client to request that any server responding to the client send the client its values for the specified options.Only the option names should be specified in the request statement - not option parameters.By default, the DHCP server requests the subnet-mask, broadcast-address, time-offset, routers, domain-name, domain-name-servers and host-name options. So you could write a request line and omit 'domain-name-servers'. I have not tried any of this. HTH, Celejar -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dhcp problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Celejar wrote: On Thu, 29 Mar 2007 20:54:34 +0600 S. M. Ibrahim (Lavlu) [EMAIL PROTECTED] wrote: My isp is providing me the ip using DHCP. everything fine. But they are sending 3 nameserver. And first DNS server is not responding. SO it take time to switch to the secound dns. So, it's making problem (slow down). I want to keep fix (will not updated or replace by dhcp) the /etc/resolv.conf with only 2 nameserver (that are working). Any idea, how to do this ? From 'man dhclient': The supersede statement supersede [ option declaration ] ; If for some option the client should always use a locally-configured value or values rather than whatever is supplied by the server, these values can be defined in the supersede statement. So if you're using dhclient you could try something like: supersede domain-name-servers a.b.c d.e.f Also from the manpage: The request statement request [ option ] [, ... option ]; The request statement causes the client to request that any server responding to the client send the client its values for the specified options.Only the option names should be specified in the request statement - not option parameters.By default, the DHCP server requests the subnet-mask, broadcast-address, time-offset, routers, domain-name, domain-name-servers and host-name options. So you could write a request line and omit 'domain-name-servers'. I have not tried any of this. HTH, Celejar I had a similar problem. The file /etc/dhcp3/dhclient.conf is the file that controls resolv.conf (at least on this system). You can specify which DNS is used first by using prepend domain-name-servers xxx.xxx.xxx.xxx; replacing of course the x's with the ip address of the DNS. This line is already present using 127.0.0.1 but is commented out. I have tried it, and it works. Joe - -- Registerd Linux user #443289 at http://counter.li.org/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGC+tsiXBCVWpc5J4RArQdAKDO10MEfaW4p/3oBrJbWO3NplhEtQCghLNz GZiR4zMqeuWw4Qy33w6LmjY= =3+HX -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: DHCP problem following Etch upgrade
On Sat, 18 Feb 2006 23:43:06 + John Halton [EMAIL PROTECTED] wrote: John Halton wrote: This is the same problem as in my previous thread (Hanging during boot-up following dbus upgrade) but a response on that thread has enabled me to narrow it down a bit. dhcp-client (I assume) is pausing indefinitely at the bound to 80.x.xxx.x -- renewal in 56953 seconds message. This applies during boot-up and also if I run ifup eth0. Hitting Ctrl+C gets past the problem and the IP address appears to be bound correctly despite this pause - at least, I'm not having any difficulty connecting to the internet. The problem has only started arising since a recent upgrade in which I replaced dbus-1 with dbus, on my Etch installation. Also, while we're on the subject of dhcp-client, is there any reason/benefit to installing dhcp3-client instead of, or as well as, dhcp-client? At the moment I only have dhcp-client installed, it's not been a problem to date, and am not quite sure what the difference is. As a follow-up, I've tried replacing dhcp-client with dhcp3-client, and the same problem is still arising. have you tried the dhcpcd package? -- Shawn Lamson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: DHCP problem following Etch upgrade
On 2/21/06, Shawn Lamson [EMAIL PROTECTED] wrote: On Sat, 18 Feb 2006 23:43:06 + have you tried the dhcpcd package? I've had an off-list email suggesting that the problem is due to a bug in zeroconf, and that purging zeroconf will solve it. (See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=349340) I've not had chance to try this yet but I'm guessing it should work, especially since I'd already noticed zeroconf running when I looked at what processes were running during these pauses in activity.
Re: DHCP problem following Etch upgrade
John Halton wrote: This is the same problem as in my previous thread (Hanging during boot-up following dbus upgrade) but a response on that thread has enabled me to narrow it down a bit. dhcp-client (I assume) is pausing indefinitely at the bound to 80.x.xxx.x -- renewal in 56953 seconds message. This applies during boot-up and also if I run ifup eth0. Hitting Ctrl+C gets past the problem and the IP address appears to be bound correctly despite this pause - at least, I'm not having any difficulty connecting to the internet. The problem has only started arising since a recent upgrade in which I replaced dbus-1 with dbus, on my Etch installation. Also, while we're on the subject of dhcp-client, is there any reason/benefit to installing dhcp3-client instead of, or as well as, dhcp-client? At the moment I only have dhcp-client installed, it's not been a problem to date, and am not quite sure what the difference is. As a follow-up, I've tried replacing dhcp-client with dhcp3-client, and the same problem is still arising. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dhcp problem
On Monday 18 July 2005 05:26, [EMAIL PROTECTED] wrote: I got my broadband setup and my provider uses DHCP and I have a intelligent router (modem). I installed dhcpcd as dhcp client and it works fine except that it couldnt get right nameservers and hence resolving host name takes lot of time. If I put nameservers (I got it from my provider) in /etc/resolv.conf, it works fine. But the problem is when I login as different user, it shows different nameserver in networking. Do I have to configure nameserver for every user on my system? If you are using a combined solution, using both DHCP and static configuration, I suggest hacking your /etc/network/interfaces to echo the static DNS-settings to /etc/resolv.conf. Something like this: iface eth0 inet dhcp post-up echo -e 'search\nnameserver ip.of.pri.dns\nnameserver ip.of.sec.dns' /etc/resolv.conf This isn't the best advise, I'm sure. But I *guess* it does the trick. However, it should be noted that I never tested it with dhcpcd; only dhclient. Regards, Anders Breindahl. pgpwvPmCSn7ui.pgp Description: PGP signature
Re: DHCP problem where ip address is assigned to wrong NIC on reboot
On Tue, Jun 21, 2005 at 10:44:05PM -0400, Derrick Hudson wrote:
On Tue, Jun 21, 2005 at 05:32:01PM -0700, Xeno Campanoli wrote:
| I got a real whacky one. This old machine I've got has two NICs, and during
| install I assign eth1 to be the one used, and it gets the ip address from
| DHCP. Well, after the reboot, that same IP address is assigned to eth0, and
| I get no network. I've solved this by switching the cable over and
rebooting,
| but it sounds like a bug, so I thought I'd mention it. The machine I'm
running
| is an old thing with 92 meg of memory, but presumably it's not the memory
that
| is confusing DHCP, but just the two NICS. Perhaps nobody has two NICs
anymore?
I have two NICs in several machines. The only time I've seen anything
similar is when the system doesn't detect the cards in the same order
each time it boots and so the cards are assigned the labels 'eth0' and
'eth1' different.
In that case, the solution is simple: install the 'ifrename' package,
read the documentation, and create a suitable /etc/iftab file. Using
this approach you can assign the NICs meaningful names (ie 'lan' or
'wan' or whatever) based on the MAC address (or base I/O for ISA
cards). This ensures that the cards are identified properly,
regardless of how many you have and which one(s) are available at boot
time and what order the kernel loads the driver(s) for them. Then you
use this meaningful name in all your configuration files and can be
assured the correct NIC will be used.
Is PnP disabled in bios?
\begin{humor}
Disclaimer:
If I receive a message from you, you are agreeing that:
1. I am by definition, the intended recipient
2. All information in the email is mine to do with as I see fit and make
such financial profit, political mileage, or good joke as it lends
itself to. In particular, I may quote it on USENET or the WWW.
3. I may take the contents as representing the views of your company.
4. This overrides any disclaimer or statement of confidentiality that may
be included on your message
\end{humor}
www: http://dman13.dyndns.org/~dman/jabber: [EMAIL PROTECTED]
lol nice sig
--
Chris.
--
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: DHCP problem where ip address is assigned to wrong NIC on reboot
On Tue, 21 Jun 2005, Xeno Campanoli wrote: I got a real whacky one. This old machine I've got has two NICs, and during install I assign eth1 to be the one used, and it gets the ip address from DHCP. Well, after the reboot, that same IP address is assigned to eth0, and I get no network. I've solved this by switching the cable over and rebooting, but it sounds like a bug, so I thought I'd mention it. The machine I'm running is an old thing with 92 meg of memory, but presumably it's not the memory that is confusing DHCP, but just the two NICS. Perhaps nobody has two NICs anymore? You know, this is odd because I have a Sun Ultra V and had the same problem with my 3.1 installation. One NIC could get DHCP during the initial install then upon reboot, Debian only saw the Linksys NIC and on the onboard SUN nic. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: DHCP problem where ip address is assigned to wrong NIC on reboot
Xeno Campanoli wrote: I got a real whacky one. This old machine I've got has two NICs, and during install I assign eth1 to be the one used, and it gets the ip address from DHCP. Well, after the reboot, that same IP address is assigned to eth0, and I get no network. I've solved this by switching the cable over and rebooting, but it sounds like a bug, so I thought I'd mention it. The machine I'm running is an old thing with 92 meg of memory, but presumably it's not the memory that is confusing DHCP, but just the two NICS. Perhaps nobody has two NICs anymore? xc http://www.tldp.org/HOWTO/Ethernet-HOWTO-2.html#ss2.4 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: DHCP problem where ip address is assigned to wrong NIC on reboot
On Tue, Jun 21, 2005 at 05:32:01PM -0700, Xeno Campanoli wrote:
| I got a real whacky one. This old machine I've got has two NICs, and during
| install I assign eth1 to be the one used, and it gets the ip address from
| DHCP. Well, after the reboot, that same IP address is assigned to eth0, and
| I get no network. I've solved this by switching the cable over and rebooting,
| but it sounds like a bug, so I thought I'd mention it. The machine I'm
running
| is an old thing with 92 meg of memory, but presumably it's not the memory that
| is confusing DHCP, but just the two NICS. Perhaps nobody has two NICs
anymore?
I have two NICs in several machines. The only time I've seen anything
similar is when the system doesn't detect the cards in the same order
each time it boots and so the cards are assigned the labels 'eth0' and
'eth1' different.
In that case, the solution is simple: install the 'ifrename' package,
read the documentation, and create a suitable /etc/iftab file. Using
this approach you can assign the NICs meaningful names (ie 'lan' or
'wan' or whatever) based on the MAC address (or base I/O for ISA
cards). This ensures that the cards are identified properly,
regardless of how many you have and which one(s) are available at boot
time and what order the kernel loads the driver(s) for them. Then you
use this meaningful name in all your configuration files and can be
assured the correct NIC will be used.
HTH,
-D
--
\begin{humor}
Disclaimer:
If I receive a message from you, you are agreeing that:
1. I am by definition, the intended recipient
2. All information in the email is mine to do with as I see fit and make
such financial profit, political mileage, or good joke as it lends
itself to. In particular, I may quote it on USENET or the WWW.
3. I may take the contents as representing the views of your company.
4. This overrides any disclaimer or statement of confidentiality that may
be included on your message
\end{humor}
www: http://dman13.dyndns.org/~dman/jabber: [EMAIL PROTECTED]
signature.asc
Description: Digital signature
Re: DHCP problem
On Sat, Aug 07, 2004 at 09:59:30AM -0400, [EMAIL PROTECTED] wrote: Hello. I am a relatively new user of Debian and I couldn't figure this one out. I have 2 machines running Sarge, both configured to use DHCP. At boot time both for some reason acquire the same address (192.168.102.100) from my router. Is there a way to force at least one of them to get a different address? Are you sure that the router actually gives that address to both? It would help if you posted the relevant bits of /var/log/syslog on each machine... -- Karl E. Jørgensen [EMAIL PROTECTED] http://karl.jorgensen.com Today's fortune: Hold the MAYO pass the COSMIC AWARENESS ... signature.asc Description: Digital signature
Re: DHCP problem
On Sat, 2004-08-07 at 08:59, [EMAIL PROTECTED] wrote: Hello. I am a relatively new user of Debian and I couldn't figure this one out. I have 2 machines running Sarge, both configured to use DHCP. At boot time both for some reason acquire the same address (192.168.102.100) from my router. Is there a way to force at least one of them to get a different address? it probably depends on your router. i imagine you could set up one or both of your boxes to have static ip's. just take all the information you'd get from dhcp (dns servers from /etc/resolv.conf, gateway information from the route command, etc) and assign them manually. -matt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: DHCP problem
On Saturday 07 August 2004 14:59, [EMAIL PROTECTED] wrote: Hello. I am a relatively new user of Debian and I couldn't figure this one out. I have 2 machines running Sarge, both configured to use DHCP. At boot time both for some reason acquire the same address (192.168.102.100) from my router. Is there a way to force at least one of them to get a different address? This seems like an issue with the server. Once it has offered one machine the address, and it has accepted it, it should offer it to the other. Can you give more details of your router which is supposidly offering these addresses. Also, each client machine should have indication of the exchange with the dhcp server in /var/log/syslog. Can you post it. -- Alan Chandler [EMAIL PROTECTED] First they ignore you, then they laugh at you, then they fight you, then you win. --Gandhi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dhcp problem
Cristi Banciu dijo: I know I could simply solve the problem by bonding ip with mac, but I don't want to do that. I need dinamicaly assigned address, not static. you'll always get differents ip's if you don't assign a determinate ip address to an MAC address. The rest of your pool of ip addresses will be assigned dinamicaly. cheers! diego PD. my english is so poor! :) sorry! -- [Diego Martínez Castañeda] ,''`. [Técnico de sistemas Linux] : :' : [dmartinez @ keekorok . com] `. `' [ GPG: ] `-[ 8A17 037F 2975 825F 9F2A ] debian [ 0F86 0130 8326 70B4 3B14 ] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dhcp problem
On Wed, 2004-06-09 at 12:37, Diego Martnez Castaeda wrote: you'll always get differents ip's if you don't assign a determinate ip address to an MAC address. The rest of your pool of ip addresses will be assigned dinamicaly. so , you wanna tell me that I have no choice but to assign ip static based on mac ? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dhcp problem
Cristi Banciu dijo: On Wed, 2004-06-09 at 12:37, Diego MartÃnez Castañeda wrote: you'll always get differents ip's if you don't assign a determinate ip address to an MAC address. The rest of your pool of ip addresses will be assigned dinamicaly. so , you wanna tell me that I have no choice but to assign ip static based on mac ? if you wanna the same ip address in one machine, independently from operating system you use, yes. using this method, you aren't assigning static ip address from your hosts, because you are using automatic assign in DHCP. Via DHCP you can assign ip address with three methods: - automatic: assign an ip to a host until host deny this. - dinamic: assign an ip to a host, changing everytime it reconnect. - manual: you assign an ip to a host, staticaly. cheers! diego -- [Diego Martínez Castañeda] ,''`. [Técnico de sistemas Linux] : :' : [dmartinez @ keekorok . com] `. `' [ GPG: ] `-[ 8A17 037F 2975 825F 9F2A ] debian [ 0F86 0130 8326 70B4 3B14 ] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dhcp problem [SOLVED]
On Wed, 2004-06-09 at 12:21, Cristi Banciu wrote: Hi, I have a network with computers with dual boot (linux and windows). They get ip from a debian dhcp3 server. When a client boot the machine in windows he gets ip A, and when the same client boots the machine in linux gets ip A+1. How could I make it receive the same ip, no matter what OS the machine boots. In linux I edited /etc/dhclient-eth0.conf and I put send client-host-name and send dhcp-client-identifier. I know I could simply solve the problem by bonding ip with mac, but I don't want to do that. I need dinamicaly assigned address, not static. Using dhcpcd instead of dhclient will solve the problem. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: DHCP Problem nach Kernel Update (dhclient)
Walter Wiedmann [EMAIL PROTECTED] wrote: Moin Walter, ich habe da ein kleines Problem mit dem dhclient. Ich habe zwei Kernelversioen. Bei der 2.4.18 funktioniert der dhclient ganz normal, und ich bekomme eine IP-Adresse zugewissen. Bei der Version 2.4.21 funktioniert der dhclient nicht mehr. Das Programm beendet sich mir Exit - Code 1. Exit - Code habe ich durch manuellen Aufruf von dhclient -e eth0 und anschliesendem echo $? abgefragt. [...] funktioniert es aber ohne Problem. Kann es sein, dass ein bestimmtes Modul(modules) noch geladen werden muss, damit dhclient wieder funktioniert, bzw. muss ein bestimmter Kerneltreiber eingeschaltet sein? Der einzige Unterschied bei der Sache ist ja nur :-)) der Kernel. Hast du Packet socket und Socket Filtering im Kernel aktiviert? beides findest Du unter Networking options. Oder CONFIG_PACKET und CONFIG_FILTER in .config Sonst kannst du auch den udhcpc nehmen, der kommt ohne Socket Filtering aus. Gruss, Serge -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: DHCP Problem nach Kernel Update (dhclient)
Serge Gebhardt wrote: Walter Wiedmann [EMAIL PROTECTED] wrote: Moin Walter, ich habe da ein kleines Problem mit dem dhclient. Ich habe zwei Kernelversioen. Bei der 2.4.18 funktioniert der dhclient ganz normal, und ich bekomme eine IP-Adresse zugewissen. Bei der Version 2.4.21 funktioniert der dhclient nicht mehr. Das Programm beendet sich mir Exit - Code 1. Exit - Code habe ich durch manuellen Aufruf von dhclient -e eth0 und anschliesendem echo $? abgefragt. [...] funktioniert es aber ohne Problem. Kann es sein, dass ein bestimmtes Modul(modules) noch geladen werden muss, damit dhclient wieder funktioniert, bzw. muss ein bestimmter Kerneltreiber eingeschaltet sein? Der einzige Unterschied bei der Sache ist ja nur :-)) der Kernel. Hast du Packet socket und Socket Filtering im Kernel aktiviert? beides findest Du unter Networking options. Oder CONFIG_PACKET und CONFIG_FILTER in .config Sonst kannst du auch den udhcpc nehmen, der kommt ohne Socket Filtering aus. Gruss, Serge Hallo, in der .config steht: CONFIG_PACKET=y #CONFIG_FILTER is not set Somit ist CONFIG_FILTER nicht aktiv? Brauch ich CONFIG_FILTER für dhclient? Hab ich ausgeschaltet, weil die Empfehlung N war. Ich hab da aber gleich noch eine andere Frage. Weiss jemand, wo ich die .config vom Standard - Kernel 2.4.21 von Debian herbekommen kann. Ich wollte nämlich eigentlich nur einen Treiber einschalten, und musste dann aber die komplete Configuration manchen. Danke Walter -- Walter Wiedmann Homepage: http://walter-wiedmann.gmxhome.de -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: DHCP Problem nach Kernel Update (dhclient)
* Walter Wiedmann [EMAIL PROTECTED] wrote: [ ... ] Ich hab da aber gleich noch eine andere Frage. Weiss jemand, wo ich die .config vom Standard - Kernel 2.4.21 von Debian herbekommen kann. Ich wollte nämlich eigentlich nur einen Treiber einschalten, und musste dann aber die komplete Configuration manchen. Einfach aus /boot/config-2.4.21 in dein Kernelsource verzeichnis als .config kopieren. und dann ein make oldconfig oder mit make-kpkg --config oldconfig ... HTH, tim -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: DHCP Problem nach Kernel Update (dhclient)
Walter Wiedmann schrieb: Serge Gebhardt wrote: Hast du Packet socket und Socket Filtering im Kernel aktiviert? beides findest Du unter Networking options. Oder CONFIG_PACKET und CONFIG_FILTER in .config Sonst kannst du auch den udhcpc nehmen, der kommt ohne Socket Filtering aus. Hallo, in der .config steht: CONFIG_PACKET=y #CONFIG_FILTER is not set Somit ist CONFIG_FILTER nicht aktiv? Brauch ich CONFIG_FILTER für dhclient? Hab ich ausgeschaltet, weil die Empfehlung N war. Ich hab da aber gleich noch eine andere Frage. Weiss jemand, wo ich die .config vom Standard - Kernel 2.4.21 von Debian herbekommen kann. Ich wollte nämlich eigentlich nur einen Treiber einschalten, und musste dann aber die komplete Configuration manchen. Danke Walter Hallo, warum fragst du das mit CONFIG_FILTER nochmal ? Das hat Serge dir doch schon erklärt. Die config-Datei solltest du gewöhnlich in /boot finden. 'cp /boot/config-2.4.21 /usr/src/linux/.config' Gruß Jörg -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: DHCP Problem nach Kernel Update (dhclient)
Walter Wiedmann [EMAIL PROTECTED] wrote: Serge Gebhardt wrote: Walter Wiedmann [EMAIL PROTECTED] wrote: ich habe da ein kleines Problem mit dem dhclient. Ich habe zwei Kernelversioen. Bei der 2.4.18 funktioniert der dhclient ganz normal, und ich bekomme eine IP-Adresse zugewissen. Bei der Version 2.4.21 funktioniert der dhclient nicht mehr. Das Programm beendet sich mir Exit - Code 1. Exit - Code habe ich durch manuellen Aufruf von dhclient -e eth0 und anschliesendem echo $? abgefragt. [...] funktioniert es aber ohne Problem. Kann es sein, dass ein bestimmtes Modul(modules) noch geladen werden muss, damit dhclient wieder funktioniert, bzw. muss ein bestimmter Kerneltreiber eingeschaltet sein? Der einzige Unterschied bei der Sache ist ja nur :-)) der Kernel. Hast du Packet socket und Socket Filtering im Kernel aktiviert? beides findest Du unter Networking options. Oder CONFIG_PACKET undCONFIG_FILTER in .config Sonst kannst du auch den udhcpc nehmen, der kommt ohne Socket Filtering aus. in der .config steht: CONFIG_PACKET=y #CONFIG_FILTER is not set Somit ist CONFIG_FILTER nicht aktiv? genau Brauch ich CONFIG_FILTER für dhclient? Hab ich ausgeschaltet, weil die Empfehlung N war. ja, das brauchst Du für dhclient. Oder wie oben schon erwähnt, du benutzt udhcpc, das kommt ohne CONFIG_FILTER aus. Ich hab da aber gleich noch eine andere Frage. Weiss jemand, wo ich die.config vom Standard - Kernel 2.4.21 von Debian herbekommen kann. Ich wollte nämlich eigentlich nur einen Treiber einschalten, und musste dann aber die komplete Configuration manchen. wenn er installiert ist, dann unter /boot/config-2.4.21 oder ähnlich. Gruss, Serge -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: DHCP Problem nach Kernel Update (dhclient)
Ok, dass war die Lösung! Danke -- Walter Wiedmann Homepage: http://walter-wiedmann.gmxhome.de -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: dhcp problem after recompiling kernel
Ok, tried it again (recompiling the kernel with both variables set) and now dhclient works. Hence, you were right, thanks for your help. :-) I must have overlooked something earlier. Auke On Sun, 2002-10-27 at 13:48, Colin Watson wrote: On Sun, Oct 27, 2002 at 01:26:31PM +0100, Auke Jilderda wrote: Yup, that did the trick! Thanks a lot, I started to get a serious headache from hitting the wall for hours. ;-) Makes me wonder though: Why the heck does Woody default come with dhclient if it doesn't even work with kernel 2.4? I'd suspect this is a problem more people will run into. woody's dhclient does work with 2.4. You did remember to include both CONFIG_PACKET and CONFIG_FILTER in your locally-built kernel, didn't you? -- Colin Watson [[EMAIL PROTECTED]] -- PGP: 0x4A34DD6D, http://bunny.sourceforge.net/ signature.asc Description: This is a digitally signed message part
Re: dhcp problem after recompiling kernel
On Sun, Oct 27, 2002 at 01:26:31PM +0100, Auke Jilderda wrote: Yup, that did the trick! Thanks a lot, I started to get a serious headache from hitting the wall for hours. ;-) Makes me wonder though: Why the heck does Woody default come with dhclient if it doesn't even work with kernel 2.4? I'd suspect this is a problem more people will run into. woody's dhclient does work with 2.4. You did remember to include both CONFIG_PACKET and CONFIG_FILTER in your locally-built kernel, didn't you? -- Colin Watson [[EMAIL PROTECTED]] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dhcp problem after recompiling kernel
Ofcourse I included CONFIG_PACKET and I tried both with and without CONFIG_FILTER. None worked. Why would CONFIG_FILTER be required? It seems unrelated to DHCP to me. Auke On Sun, 2002-10-27 at 13:48, Colin Watson wrote: woody's dhclient does work with 2.4. You did remember to include both CONFIG_PACKET and CONFIG_FILTER in your locally-built kernel, didn't you? -- Colin Watson [[EMAIL PROTECTED]] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- PGP: 0x4A34DD6D, http://bunny.sourceforge.net/ signature.asc Description: This is a digitally signed message part
Re: dhcp problem after recompiling kernel
Auke == Auke Jilderda [EMAIL PROTECTED] writes: Auke Makes me wonder though: Why the heck does Woody default come Auke with dhclient if it doesn't even work with kernel 2.4? I'd Auke suspect this is a problem more people will run into. Uh? It dhclient works great for me with the default 2.4 kernel in Woody. What makes you suggest this? Your problem was with a custom kernel, right? Cheers! Shyamal -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dhcp problem after recompiling kernel
For most users dhclient works perfectly with kernel 2.4, IMHO. There seems to be something interesting in Auke's case. Qian On 27 Oct 2002, Shyamal Prasad wrote: Auke == Auke Jilderda [EMAIL PROTECTED] writes: Auke Makes me wonder though: Why the heck does Woody default come Auke with dhclient if it doesn't even work with kernel 2.4? I'd Auke suspect this is a problem more people will run into. Uh? It dhclient works great for me with the default 2.4 kernel in Woody. What makes you suggest this? Your problem was with a custom kernel, right? Cheers! Shyamal -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dhcp problem after recompiling kernel
Hi fellow Eindhovenaar, (judging from the emailadress :-)), I also posted my question on the debian-laptop list (because it seemed to fit their better on second thought) and here's a clue to the issue at hand: | Auke == Auke Jilderda [EMAIL PROTECTED] writes: | | Auke Why do I need the CONFIG_FILTER for DHCP? Seems unrelated to | Auke me. | | Me too. From what I can tell (from | /usr/share/doc/dhcp3-client/dhcp-on-linux.txt), it seems Linux doesn't | allow network interfaces to be bound to 0.0.0.0, which is required for | dhcp. So dhclient needs to use CONFIG_FILTER to work around it. How | pump does it, I don't know. | | -- | Hubert Chan [EMAIL PROTECTED] - http://www.uhoreg.ca/ | PGP/GnuPG key: 1024D/124B61FA | Fingerprint: 96C5 012F 5F74 A5F7 1FF7 5291 AF29 C719 124B 61FA | Key available at wwwkeys.pgp.net. Encrypted e-mail preferred. Seems like there is some strange thing going on in the IP setup. I think I'll double-check tomorrow whether it works for me with CONFIG_FILTER enabled. (Thought I did that already but now I'm not so sure anymore.) Auke On Sun, 2002-10-27 at 22:29, Q. Gong wrote: For most users dhclient works perfectly with kernel 2.4, IMHO. There seems to be something interesting in Auke's case. Qian -- PGP: 0x4A34DD6D, http://bunny.sourceforge.net/ signature.asc Description: This is a digitally signed message part
Re: dhcp problem after recompiling kernel
Yup, that did the trick! Thanks a lot, I started to get a serious headache from hitting the wall for hours. ;-) Makes me wonder though: Why the heck does Woody default come with dhclient if it doesn't even work with kernel 2.4? I'd suspect this is a problem more people will run into. Anyway, thanks a lot! Auke On Sun, 2002-10-27 at 13:03, Jose M. Gomez wrote: On Sunday 27 October 2002 12:17, Auke Jilderda wrote: I'm running kernel 2.4.18 with dhclient as dhcp client. Any suggestion on what the problem might be? Hi, have you tried pump instead of dhclient?. I have a 2.4.18 as well and everything was working fine with the network card at home, but for some reason I couln't use dhcp in university. After a couple of days of hitting my head agaisnt the wall (and use a stolen fixed ip address) I tried pump and it worked without problems. So you could try to remove dhclient and install pump. By the way, in the manpage or in the package description, cannot remember now, it said something like it is for 2.2.x, so probably that is why it doesn't work with 2.4.x, at least for me. Could that be because woody shipped with a default 2.2.x? (has that changed?). Hope it helps -- PGP: 0x4A34DD6D, http://bunny.sourceforge.net/ signature.asc Description: This is a digitally signed message part
Re: DHCP problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday 26 September 2002 04:56 pm, lorac wrote: I can not seem to get DHCP to work on its own, except with the stock kernel that came with Debian. It sees the card, but just does not pull an IP. I can get it to pull an IP if I manually run pump /sbin/pump -i eth0. I have no problems using a static ip, or getting an ip in Windows. I have enabled kernel level auto configuration as well w\ dhcp. I'm not sure what other information i can give, but if someone could help me it would be appreciated. lorac - Violence is the last refuge of the incompetent. - Salvor Hardin Great sig .. I completely concur ^ Iorac: What do you have in your /etc/network/interfaces file? Look at it and also read the man page on interfaces. Here's a paste of part of mine: auto lo iface lo inet loopback auto eth0 iface eth0 inet dhcp This should give you a good start. gl - -- Jaye Inabnit\ARS ke6sls\/A GNU-Debian linux user\/ http://www.qsl.net/ke6sls If it's stupid, but works, it ain't stupid. I SHOUT JUST FOR FUN. Free software, in a free world, for a free spirit. Please Support freedom! -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE9k7yBZHBxKsta6kMRAh4RAKCHti68YwhX56lnp0hcURUObG/ChwCfXXdm m8/hwY60GaebxAZ660OlJuE= =P7h0 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
re: dhcp-problem
Nix, jag har ingen brandvägg körandes. Så problemet borde vara något annat. eller är de portarna stängda på något annat sätt?
Re: dhcp-problem
Jag gissar på att du har en brandvägg som sätter lite käppar i hjulet. Jag hade samma problem vilket jag löste med att öppna portar 67 (bootps) och 68 (bootpc) enligt följande: Chain OUTPUT (policy DROP) target prot opt source destination ACCEPT udp -- 0.0.0.0 255.255.255.255udp spt:bootpc dpt:bootps Chain INPUT (policy DROP) target prot opt source destination ACCEPT udp -- 0.0.0.0 255.255.255.255udp spt:bootpc dpt:bootps ACCEPT udp -- ip för dhcp servern 255.255.255.255udp spt:bootps dpt:bootpc Detta är med iptables och testing. Sätt in ip-adressen för din DHCP server ovan (eller 0.0.0.0 om du inte vet adressen). Du kan hitta mer info i en tråd som var här på listan för inte så länge sedan. Tråden gick under namnet ADSL-problem. Lycka till, /petter On Mon, 2002-01-21 at 13:10, amentia at hotpop wrote: Min debianburk (unstable) är ansluten till gavlenet, ett för gävle lokalt fibernät, som delar ut ip-adresser med dhcp. Jag har aldrig fått dhcp att fungera med debian. När jag gick över från RedHat till debian för ett halvår sedan löste jag det genom att boota windows (som jag inte längre har installerat) och satte alla uppgifter win fick från dhcp-servern som static i debian. (Jag visste att de dynamiska IP-adressrna så gott som aldrig ändrades). Detta fungerade perfekt tills för några dagar sedan då nätet gick ner ett antal timmar. När det kom upp igen observerade jag att min flickväns dator fått en ny ip-adress och märkte sålunda att min egen burk inte längre hade någon kontakt med nätet. Efter lite strulande med dhclient och pump fick jag det att fungera (med hjälp av pump, tror jag) utan att pilla i några konfigurationsfiler. Allt verkade vara frid och fröjd ända tills jag kom hem från jobbet den dagen. Ingen kontakt med nätet igen. Efter lite letande på nätet (och misslyckande med pump) bestämde jag mig för att koncentrera mig på dhclient. Trixade en massa med dhclient.conf och /etc/network/interfaces. Ingen framgång. Upptäckte att jag inte konfigurerat config_packet och config_filter i kärnan. Fixade det, men lyckas ändå inte. /var/log/syslog säger: dhclient-2.2.x: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 1 dhclient-2.2.x: No DHCPOFFERS received. dhclient-2.2.x: No working leases in persistent database. dhclient-2.2.x: Sleeping. notera att dhclient pratar om 255.255.255.255 trots att nätmasken borde vara 255.255.255.0. Jag har satt subnet-mask till detta i /etc/dhclient.conf, vilket verkar hjälpa föga. Hjälp! Jag vet inte längre vad jag ska göra och jag börjar tröttna på att behöva snylta på en ickig w98-maskin. Med hopp om hjälp Mattias Östergren -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: DHCP problem....
I would add: if you want to be able to ping the machine just like you can windows boxes then you'll need the Linux version of the software which makes this mechanism (Lan Manager a.k.a. Windows Networking) work. This package is called samba and is available as a couple different debian packages. Doing 'apt-get install samba' should get you there. Note that you may need a script which will update /etc/hosts. I'm not sure if the current dhcp package will do this and samba will not work otherwise. Phil Brutsche wrote: A long time ago, in a galaxy far, far way, someone said... I just installed DHCP client on Debian slink machine. It works almost fine it just does not pick up the host name :(. It is seen on the network by its IP address only. If I ping it by the name from the local console it responds that the host name is not known (I removed its static IP entry from the hosts file). Any suggestions will be appreciated :) This is how I read your message: 1) A computer running slink called elvis (for example) uses DHCP to get it's IP# and related information. 2) Someone else on the network tries to ping elvis, and fails 3) Someone on elvis tries to ping elvis, and fails If this is the case, welcome to DHCP :) The reason #2 and #3 fails is because there is no way for another system to find out elvis' IP#, either because the name 'elvis' wasn't found in /etc/hosts (or the equivalent), or in DNS, as you found out. Your solutions are: 1) convince the local system administrator(s) to use Dynamic DNS. This allows the DHCP server to update the DNS server's IP# database 2) convince the local system administrator(s) to give you a static IP# somehow, either through DHCP by MAC address or an outright static IP# (no DHCP involved) 3) use one of the free dynamic hosting services available on the internet; an example is www.dhs.org -- -- Phil Brutsche [EMAIL PROTECTED] There are two things that are infinite; Human stupidity and the universe. And I'm not sure about the universe. - Albert Einstein -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null -- Jens B. Jorgensen [EMAIL PROTECTED]
RE: DHCP problem....
Hello Phil, I am not that much worried about the other machines on the network, since they are Win systems and I am installing Samba on my machine but.. my machine does not even know itself :(. If I put some sort of static IP address into hosts file this IP address is used when I try to ping say, elvis and the error message that network is unreachable shows on my screen. If I ping the IP address which I pick up from running ifconfig for example, everything works fine. I can force network admin to give me a static address but this is besides the point lol... now the matter of pride is to solve the problem if you know what I mean :))). Jens Jorgensen mentiond about a script updating hosts file automatically... would you have any idea it should look like? :) Best regards and thank you for help :) Jersey -- From: Phil Brutsche[SMTP:[EMAIL PROTECTED] Sent: Wednesday, October 13, 1999 12:36 AM To: [EMAIL PROTECTED] Cc: Debian-User Subject:Re: DHCP problem A long time ago, in a galaxy far, far way, someone said... I just installed DHCP client on Debian slink machine. It works almost fine it just does not pick up the host name :(. It is seen on the network by its IP address only. If I ping it by the name from the local console it responds that the host name is not known (I removed its static IP entry from the hosts file). Any suggestions will be appreciated :) This is how I read your message: 1) A computer running slink called elvis (for example) uses DHCP to get it's IP# and related information. 2) Someone else on the network tries to ping elvis, and fails 3) Someone on elvis tries to ping elvis, and fails If this is the case, welcome to DHCP :) The reason #2 and #3 fails is because there is no way for another system to find out elvis' IP#, either because the name 'elvis' wasn't found in /etc/hosts (or the equivalent), or in DNS, as you found out. Your solutions are: 1) convince the local system administrator(s) to use Dynamic DNS. This allows the DHCP server to update the DNS server's IP# database 2) convince the local system administrator(s) to give you a static IP# somehow, either through DHCP by MAC address or an outright static IP# (no DHCP involved) 3) use one of the free dynamic hosting services available on the internet; an example is www.dhs.org -- -- Phil Brutsche [EMAIL PROTECTED] There are two things that are infinite; Human stupidity and the universe. And I'm not sure about the universe. - Albert Einstein
Re: DHCP problem....
sounds like a DNS issue, run a reverse lookup on the IP and see what comes out. you can also add this line to your /etc/resolv.conf domain yourdomain.com that will cause the system to search the local domain when you ping a hostname. for me if i pinged the host galactica, resolv.conf would automatically try galactica.firetrail.com but it looks more to be a DNS thing. the hostname may not be a valid (Domain Name) host. that can be checked by trying to resolve the full host.domain.com. if it resolves the problem is on the client machine(the /etc/resolv.conf shit) nate [mailto:[EMAIL PROTECTED] ]-- Linux System Administrator http://www.firetrail.com/ Firetrail Internet Services Limited http://www.aphroland.org/ Everett, WA 425-348-7336http://www.linuxpowered.net/ Powered By:http://comedy.aphroland.org/ Debian 2.1 Linux 2.0.36 SMPhttp://yahoo.aphroland.org/ -[mailto:[EMAIL PROTECTED] ]-- On Wed, 13 Oct 1999, J.M. Jersey Miszczyk wrote: Hi there :), I just installed DHCP client on Debian slink machine. It works almost fine it just does not pick up the host name :(. It is seen on the network by its IP address only. If I ping it by the name from the local console it responds that the host name is not known (I removed its static IP entry from the hosts file). Any suggestions will be appreciated :) Best regards Jersey -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: DHCP problem....
Yes, ok. Well the first thing is you want to use the newer client,
(dhcp-client-beta if you're running slink, dhcp-client if you're running
potato). Using the newer client is necessary because this client does not go
into the background until it gets an address (or times out, but let's
hope/assume that doesn't happen). The older client did go into the background
with the unfortunate result that samba and other network daemons that want to
know what your address is and want to look it up by host name would be started
right away before the dhcp client had time to get an address.
The next thing is to modify /etc/dhclient-script. This script is run at various
times by the dhcp client daemon in order to accomplish certain things like
setting up routes. We need to add code to it so that when dhcp acquires an IP
address it will update the /etc/hosts file to make the machine's host name
resolve to it's IP address properly. I've included my /etc/dhclient-script
which you can copy from.
J.M. \Jersey\ Miszczyk wrote:
Hello Phil,
I am not that much worried about the other machines on the network, since
they are Win systems and I am installing Samba on my machine but.. my
machine does not even know itself :(. If I put some sort of static IP
address into hosts file this IP address is used when I try to ping say,
elvis and the error message that network is unreachable shows on my
screen. If I ping the IP address which I pick up from running ifconfig
for example, everything works fine.
I can force network admin to give me a static address but this is
besides the point lol... now the matter of pride is to solve the
problem if you know what I mean :))).
Jens Jorgensen mentiond about a script updating hosts file
automatically... would you have any idea it should look like? :)
Best regards and thank you for help :)
Jersey
--
From: Phil Brutsche[SMTP:[EMAIL PROTECTED]
Sent: Wednesday, October 13, 1999 12:36 AM
To: [EMAIL PROTECTED]
Cc: Debian-User
Subject:Re: DHCP problem
A long time ago, in a galaxy far, far way, someone said...
I just installed DHCP client on Debian slink machine. It works almost
fine it just does not pick up the host name :(. It is seen on the
network by its IP address only. If I ping it by the name from the local
console it responds that the host name is not known (I removed its static
IP entry from the hosts file).
Any suggestions will be appreciated :)
This is how I read your message:
1) A computer running slink called elvis (for example) uses DHCP to get
it's IP# and related information.
2) Someone else on the network tries to ping elvis, and fails
3) Someone on elvis tries to ping elvis, and fails
If this is the case, welcome to DHCP :) The reason #2 and #3 fails is
because there is no way for another system to find out elvis' IP#, either
because the name 'elvis' wasn't found in /etc/hosts (or the equivalent),
or in DNS, as you found out. Your solutions are:
1) convince the local system administrator(s) to use Dynamic DNS. This
allows the DHCP server to update the DNS server's IP# database
2) convince the local system administrator(s) to give you a static IP#
somehow, either through DHCP by MAC address or an outright static IP#
(no DHCP involved)
3) use one of the free dynamic hosting services available on the internet;
an example is www.dhs.org
--
--
Phil Brutsche [EMAIL PROTECTED]
There are two things that are infinite; Human stupidity and the
universe. And I'm not sure about the universe. - Albert Einstein
--
Jens B. Jorgensen
[EMAIL PROTECTED]
#!/bin/sh
# dhclient-script for Linux. Dan Halbert, March, 1997.
# Updated for Linux 2.[12] by Brian J. Murrell, January 1999.
# No guarantees about this. I'm a novice at the details of Linux
# networking.
# Notes:
# 0. This script is based on the netbsd script supplied with dhcp-970306.
# 1. ifconfig down apparently deletes all relevant routes and flushes
# the arp cache, so this doesn't need to be done explicitly.
# 2. The alias address handling here has not been tested AT ALL.
# I'm just going by the doc of modern Linux ip aliasing, which uses
# notations like eth0:0, eth0:1, for each alias.
# 3. I have to calculate the network address, and calculate the broadcast
# address if it is not supplied. This might be much more easily done
# by the dhclient C code, and passed on.
# 4. TIMEOUT not tested. ping has a flag I don't know, and I'm suspicious
# of the $1 in its args.
update_hosts () {
if sed -e
'/^[0-9]\{1,3\}\.[0-9]\{1,3\}\.[0-9]\{1,3\}\.[0-9]\{1,3\}[[:space:]]\+.*'$(/bin/hostname)'.*/
s/^[0-9]\{1,3\}\.[0-9]\{1,3\}\.[0-9]\{1,3\}\.[0-9]\{1,3\}/'$1'/' /etc/hosts
/etc/hosts.new.$$
then
/bin/cp /etc/hosts /etc/hosts.old
mv /etc/hosts.new.$$ /etc/hosts
else
rm /etc/hosts.new
Re: DHCP problem....
A long time ago, in a galaxy far, far way, someone said... I just installed DHCP client on Debian slink machine. It works almost fine it just does not pick up the host name :(. It is seen on the network by its IP address only. If I ping it by the name from the local console it responds that the host name is not known (I removed its static IP entry from the hosts file). Any suggestions will be appreciated :) This is how I read your message: 1) A computer running slink called elvis (for example) uses DHCP to get it's IP# and related information. 2) Someone else on the network tries to ping elvis, and fails 3) Someone on elvis tries to ping elvis, and fails If this is the case, welcome to DHCP :) The reason #2 and #3 fails is because there is no way for another system to find out elvis' IP#, either because the name 'elvis' wasn't found in /etc/hosts (or the equivalent), or in DNS, as you found out. Your solutions are: 1) convince the local system administrator(s) to use Dynamic DNS. This allows the DHCP server to update the DNS server's IP# database 2) convince the local system administrator(s) to give you a static IP# somehow, either through DHCP by MAC address or an outright static IP# (no DHCP involved) 3) use one of the free dynamic hosting services available on the internet; an example is www.dhs.org -- -- Phil Brutsche [EMAIL PROTECTED] There are two things that are infinite; Human stupidity and the universe. And I'm not sure about the universe. - Albert Einstein
Re: dhcp problem
I don't think the problem is the package. I think the problem is in the configuration. Looking at the trace you can quickly see that dhcpcd is trying to set the interface's IP address *and* broadcast address to 191.255.252.220. I don't think it's legal to set an interface's IP address and broadcast address to the same thing. It would appear that the broadcast address is not correct, so I would check your config files. sam wrote: Hi, I just can not use DHCP on my Linux box. My kernel is 2.2.9 I get the following error: dhcpcd[1158]: ioctl SIOCSIFBRDADDR (ifConfig): Cannot assign requested address since it was giving me this, I tried option -r, does not work either... As an example, strace dhcpcd -r -d gives me this: socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 3 ioctl(3, SIOCGIFHWADDR, 0xbcdc) = 0 ioctl(3, SIOCSIFADDR, 0xbcdc) = 0 ioctl(3, SIOCSIFBRDADDR, 0xbcdc)= -1 EADDRNOTAVAIL (Cannot assign requested address) write(2, ioctl SIOCSIFBRDADDR (ifConfig):..., 65ioctl SIOCSIFBRDADDR (ifConfig): Cannot assign requested address ) = 65 BTW, my network card works fine, I can do networking with a computer on the same hub if I set the IP address by hand using ifconfig ... Bu it put the mess on the rest of the network sometimes since it can bring ip conflicts, and other computers can not access mine. I tried the dhcp package from slink, and then from potato The last package I tested is dhcpcd 1.3.17pl2-1 (potato) I tried both packages (slink,potato), with or without option -r on kernel 2.0.36 and 2.2.9. I read the DHCPD mini-HOWTO and had a look to /usr/doc/dhcpcd, ... nothing helped I did a 'man ioctl_list' to see if I could get a clue (what is SIOCSIFBRDADDR about ?), and I did not. So, I am kind of desperate... Can some one help me please ? I really need to use the network, and for the moment, I have to switch back to windoze to do so. Please, CC me in the answer, since I am not on this list. Cheers, vdb -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null -- Jens B. Jorgensen [EMAIL PROTECTED]
