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/windoze question
Cameron Matheson said: > First, his IP address is 'Obtained Automatically', does this mean i want > to use DHCP? Or does Windows have some proprietary method of > automatically obtaining IP addresses? that means DHCP.. > > If it is DHCP, i shouldn't need to know the default gw or nameservers > right? That would be a big relief too me... yeah. if this is a normal ethernet network you should have no problems. HOWEVER, if the DHCP server is a win32 box you may quite likely have DNS problems, as at least NT4 seems to add a line feed character or something at the end of the nameservers it reports, so check /etc/resolv.conf if your on such a network, you can modify the DHCP scripts to ignore resolv.conf and you can configure it manually if this is the case. if this is not a normal ethernet network(e.g. this is a computer with DSL over PPPoE or soemthing) then additional configuration may be required. nate -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dhcp/windoze question
nate wrote: >yeah. if this is a normal ethernet network you should have no problems. >HOWEVER, if the DHCP server is a win32 box you may quite likely have >DNS problems, as at least NT4 seems to add a line feed character or >something at the end of the nameservers it reports, so check /etc/resolv.conf >if your on such a network, you can modify the DHCP scripts to ignore >resolv.conf and you can configure it manually if this is the case. > How do i know which computer is the DHCP server? They are all just win98 boxen w/ the tcp/ip set to obtain IP address automatically. Or do i never need to know the ip address of the dhcp server (i thought that the deb installation asks you for that if you choose DHCP). >if this is not a normal ethernet network(e.g. this is a computer with >DSL over PPPoE or soemthing) then additional configuration may be >required. > Yeah, it's just normal ethernet (their is a DSL modem, but that will be shared by a windoze box. Thanks! Cam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dhcp/windoze question
Cameron Matheson said: > nate wrote: > > > How do i know which computer is the DHCP server? They are all just > win98 boxen w/ the tcp/ip set to obtain IP address automatically. Or do > i never need to know the ip address of the dhcp server (i thought that > the deb installation asks you for that if you choose DHCP). the logs on the debian machine should show what IP is the DHCP server. on win98 the command winipcfg should show the IP of the DHCP server, if its winnt or win2000 ipconfig /all should show. it's not really that important, just be aware if the /etc/resolv.conf is screwed up after switching to DHCP it could be because the DHCP server is running some flavor of win32. nate -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dhcp/windoze question
Hi On Tue, 10 Sep 2002, Cameron Matheson wrote: > Hey, > > I'm setting up a linux box for my friend (dual-booting actually), but > i'm going to have to set up the network setting and i was looking for > some advice first (because i can't change how the networking is done on > his entire network). > > First, his IP address is 'Obtained Automatically', does this mean i want > to use DHCP? Or does Windows have some proprietary method of > automatically obtaining IP addresses? > Yes, the windozebox will get his ip from dhcp, and if no dhcp can give him any adr, windoze will assign a APIPA ipadr. in the range 169.254.x.x. > If it is DHCP, i shouldn't need to know the default gw or nameservers > right? That would be a big relief too me... > Right, usually the windozebox get it all from dhcp. /ernst > Thanks, > Cameron Matheson > > > > -- > 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/windoze question
On Tue, 10 Sep 2002, Cameron Matheson wrote: > nate wrote: > > >yeah. if this is a normal ethernet network you should have no problems. > >HOWEVER, if the DHCP server is a win32 box you may quite likely have > >DNS problems, as at least NT4 seems to add a line feed character or > >something at the end of the nameservers it reports, so check /etc/resolv.conf > >if your on such a network, you can modify the DHCP scripts to ignore > >resolv.conf and you can configure it manually if this is the case. > > > > How do i know which computer is the DHCP server? They are all just > win98 boxen w/ the tcp/ip set to obtain IP address automatically. Or do > i never need to know the ip address of the dhcp server (i thought that > the deb installation asks you for that if you choose DHCP). > OK, then none of them are DHCP server. When a Windozebox is set up for DHCP, and there is no avilable, then windoze give itself an APIPA adr in the range : 169.254.x.x. If your box got an addres like this, then there is no DHCP in the net /ernst > >if this is not a normal ethernet network(e.g. this is a computer with > >DSL over PPPoE or soemthing) then additional configuration may be > >required. > > > > Yeah, it's just normal ethernet (their is a DSL modem, but that will be > shared by a windoze box. > > > Thanks! > Cam > > > > > -- > 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 server subnetting
Hi, Mike Egglestone écrivait : > Basically, is it OK networking practise to setup my eth1 as follows?: > Network 10.0.0.0 > IP address 10.0.0.1 > Netmask 255.255.254 > broadcast 10.0.1.255 You may like to know that 10.0.0.0 is a class A network, so you can legally use a netmask of 255.0.0.0 and a broadcast of 10.255.255.255 without any problem! For more information look for RFC 1918 (search Google), section 3. >From this, you'll be able to use a DHCP address range from 10.0.0.20 to 10.0.1.254 as well as from 10.100.0.0 to 10.100.255.255, assuming that your DHCP service is able to handle 65536 addresses! ;-) Regards, J.C. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dhcp server subnetting
On Sat, Sep 28, 2002 at 12:25:55AM +0700, Jean Christophe ANDR?? wrote: > Mike Egglestone ?crivait : > > Basically, is it OK networking practise to setup my eth1 as follows?: > > Network 10.0.0.0 > > IP address 10.0.0.1 > > Netmask 255.255.254 > > broadcast 10.0.1.255 > > You may like to know that 10.0.0.0 is a class A network, so you can legally > use a netmask of 255.0.0.0 and a broadcast of 10.255.255.255 without any > problem! For more information look for RFC 1918 (search Google), section 3. It's possible to do that, sure, but if you ever try to connect your machine to a VPN where other people are using RFC 1918 addresses then you'll run into problems if you've been excessively greedy. It's better practice to use a more reasonably-sized subnet. -- Colin Watson [[EMAIL PROTECTED]] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: dhcp server subnetting
> You may like to know that 10.0.0.0 is a class A network, so > you can legally > use a netmask of 255.0.0.0 and a broadcast of 10.255.255.255 > without any Nope, 10.0.0.0 is not a class A network anymore! 10.0.0.0 is just a single address out of for example 8.0.0.0/6. CIDR has been around since 1993. See RFC1519. 10.0.0.0/8 is one of the three CIDR blocks in RFC 1918 space. (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16) Clueful people around here, have silently agreed to say /8, /16 and /24 instead of class X, because classes do not only mean prefix length but also ip address range. For example "Class A address" once ment any ip addresses in the range from 1.0.0.0 to 126.255.255.255. "Class A network" ment any of the networks 1.0.0.0/8 to 126.0.0.0/8 with a mask of 255.0.0.0. Have fun, Boyan Krosnov, CCIE#8701 http://boyan.ludost.net/ Just another techie speaking for himself -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dhcp server subnetting
Colin Watson écrivait : > It's possible to do that, sure, but if you ever try to connect your > machine to a VPN where other people are using RFC 1918 addresses then > you'll run into problems if you've been excessively greedy. It's better > practice to use a more reasonably-sized subnet. You are totally right! We (at my agency) are using VPN, putting the country line number from ISO-3166 in the second byte, the organisation unit number in the third byte, and the computer number in the last one. We have many little local networks. :) We also have thought about reserving 10.0 as the backbone (still not used like this) and 10.255 as the mobile computers/networks... But our work is not finished yet, if you (or anybody else off course) have suggestion about good ways of using it, don't hesitate to tell me! :) Regards, J.C. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dhcp and dnat
This one time, at band camp, martin f krafft said: > hi there, > > my ISP allows me to use 4 IPs obtained with DHCP. I have a firewall > box connecting a DMZ and the LAN to upstream. In the DMZ, there are > two servers for which I would like to use a public IP assigned by > upstream's DHCP server and consequently DNATted (iptables) by the > firewall box. > > My thought was to let the firewall box be a proxy DHCP client (not > a relay), requesting multiple leases from the upstream DHCP server. > Once it obtained a lease it simply calls a custom script to set up > iptables DNAT and SNAT appropriately. > > However, I am unsure on how to do this. dhcp3-client works > wonderfully, but it requires the specification of an interface. As > I know of no way to configure proxy interfaces[1] I wonder how > I should use dhclient3 to accomplish what I want: obtain and maintain > a lease independently of the one for eth0 and simply make the obtained > IP available to a script. > > Do you know of a way to do this? > > 1. here's a cool idea for iptables: it provides interfaces like dnat0 > and dnat1 to be configure like so: > >ifconfig dnat0 up 212.113.54.167 for 192.168.1.13 > > and consequently, anything it receives on that interface is > DNATted and sent to 192.168.1.13. i guess SNAT would have to be > done transparently in the background for 192.168.1.13. How about virtual interfaces? IIRC eth0:1, etc. (check the syntax - I can't look it up right now). Each could have an interfaces entry, they could each be DHCP, and they could each be made to send the MAC address of the machine that they route for. Makes setting up routes easy too - all traffic on eth0:4 gets sent to box4, etc. Just a thought, Steve -- This will be a memorable month -- no matter how hard you try to forget it. msg05791/pgp0.pgp Description: PGP signature
Re: dhcp and dnat
Oops -- sent this directly to Stephen. Forwarding to list. Sorry Stephen. G Begin forwarded message: Date: Mon, 7 Oct 2002 14:25:45 -0500 From: Gerald Livingston <[EMAIL PROTECTED]> To: Stephen Gran <[EMAIL PROTECTED]> Subject: Re: dhcp and dnat On Sun, 6 Oct 2002 18:20:06 -0400 Stephen Gran <[EMAIL PROTECTED]> wrote: > This one time, at band camp, martin f krafft said: > > hi there, > > > > my ISP allows me to use 4 IPs obtained with DHCP. I have a firewall > > box connecting a DMZ and the LAN to upstream. In the DMZ, there are > > two servers for which I would like to use a public IP assigned by > > upstream's DHCP server and consequently DNATted (iptables) by the > > firewall box. > > > > My thought was to let the firewall box be a proxy DHCP client (not > > a relay), requesting multiple leases from the upstream DHCP server. > > Once it obtained a lease it simply calls a custom script to set up > > iptables DNAT and SNAT appropriately. > > > > However, I am unsure on how to do this. dhcp3-client works > > wonderfully, but it requires the specification of an interface. As > > I know of no way to configure proxy interfaces[1] I wonder how > > I should use dhclient3 to accomplish what I want: obtain and maintain > > a lease independently of the one for eth0 and simply make the obtained > > IP available to a script. > > > > Do you know of a way to do this? > > > > 1. here's a cool idea for iptables: it provides interfaces like dnat0 > > and dnat1 to be configure like so: > > > >ifconfig dnat0 up 212.113.54.167 for 192.168.1.13 > > > > and consequently, anything it receives on that interface is > > DNATted and sent to 192.168.1.13. i guess SNAT would have to be > > done transparently in the background for 192.168.1.13. > > How about virtual interfaces? IIRC eth0:1, etc. (check the syntax - I > can't look it up right now). Each could have an interfaces entry, they > could each be DHCP, and they could each be made to send the MAC address > of the machine that they route for. Makes setting up routes easy too - > all traffic on eth0:4 gets sent to box4, etc. > > Just a thought, > Steve > Where's the best documentation on setting up virtual interfaces? I'd like to be able to have my debian home machine talk to my debian laptop without installing another physical interface. The home box is getting it's primary IP from a cable modem through a hub -- my brother's Winbox is also plugged into the hub grabbing a second DHCP address. I want to be able to plug the laptop into the hub and talk to my home machine. G -- gvl2 (Gerald) AirBall the Rolling Basket Case (1969 Standard Beetle) LifeSaver (1974 Bay Window Bus) http://www.phorce1.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dhcp changed hostname!
martin f krafft said: > something just happened that i've never seen before. a client obtained a in my experience it is normal for a dhcp client to change it's hostname when recieving a dhcp address. it's been a long while since I used a debian system in a dynamic dhcp enviornment(most of my enviornments are statically assigned ips via MACs with DHCP just makes it easier and consistant), but in SuSE and redhat at least they by default change their hostnames to what the dhcp server says. though it is usually to a useful hostname that is the hostname of the IP in DNS, but I suppose a dhcp server could override what the hostname is sent out as. nate -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dhcp changed hostname!
This one time, at band camp, nate said: > martin f krafft said: > > something just happened that i've never seen before. a client obtained a > > > in my experience it is normal for a dhcp client to change it's > hostname when recieving a dhcp address. it's been a long while > since I used a debian system in a dynamic dhcp enviornment(most of > my enviornments are statically assigned ips via MACs with DHCP just > makes it easier and consistant), but in SuSE and redhat at least they > by default change their hostnames to what the dhcp server says. though > it is usually to a useful hostname that is the hostname of the IP in > DNS, but I suppose a dhcp server could override what the hostname > is sent out as. > > nate I've seen it change in the logs, but the hostname on the console always stayed the same. Odd. Steve -- BOFH excuse #142: new guy cross-connected phone lines with ac power bus. msg08527/pgp0.pgp Description: PGP signature
Re: dhcp changed hostname!
also sprach nate <[EMAIL PROTECTED]> [2002.10.23.0010 +0200]: > in my experience it is normal for a dhcp client to change it's > hostname when recieving a dhcp address. it's been a long while > since I used a debian system in a dynamic dhcp enviornment(most of > my enviornments are statically assigned ips via MACs with DHCP just > makes it easier and consistant), but in SuSE and redhat at least they > by default change their hostnames to what the dhcp server says. though > it is usually to a useful hostname that is the hostname of the IP in > DNS, but I suppose a dhcp server could override what the hostname > is sent out as. the point being: this didn't happen before on the same system, and doesn't happen on another system connected to the same IP. both are using dhcp3-client. -- .''`. martin f. krafft <[EMAIL PROTECTED]> : :' :proud Debian developer, admin, and user `. `'` `- Debian - when you have better things to do than to fix a system msg08529/pgp0.pgp Description: PGP signature
Re: DHCP dosen't work after kernel build
> "Paul" == Paul Lewis <[EMAIL PROTECTED]> writes: Paul> What have I missed out of my kernel build ? Under networking Paul> options I have dhcp, bootp and rarp support compiled in. ... Make sure the CONFIG_PACKET and CONFIG_FILTER options are enabled (and if they are modules, make sure they get loaded). Paul> My other kernels on the same machine work fine in this respect. BTW, the config options for Debian-built (and make-kpkg-built) kernels can be found in /boot/config* -- 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. msg07231/pgp0.pgp Description: PGP signature
