Re: Marvell 88E80856 switching from static to dhcp configuration all on its own
On Thu, Jul 17, 2008 at 06:53:25PM -0700, Freddy Freeloader wrote: ... > > These troubleshooting suggestions really don't help explain to me why > dhclient would override the settings in /etc/network/interfaces for one > NIC and not the other though. And why would it override manual > settings? Isn't there some process watching the settings in > /etc/network/interfaces to stop just such a thing from happening, or > doesn't the driver and device itself record its state so that dhclient > wouldn't even attempt this unless there is some type of user override, > i.e. ifdown/ifup, /etc/init.d/networking restart, etc... ? so far as I know, interfaces is only read once, when it's needed, at the time the interface is upped. Once it's up, that file's not read. You can test this by upping an interface, commenting it out of interfaces and then trying to down the interface (ifdown). It will fail because it can't find the interface in the file. At least that's how I remember it. > > There's something going on that I really don't understand here, and just > troubleshooting it at the level shown here doesn't seem to me that it > will answer my base questions. Can anyone point me to documentation on > how this works, because I must be missing something. > > Why wouldn't restarting networking not have killed dhclient after > /etc/network/interfaces was read, the NIC's configured, and all NIC's > were configured with a static IP address? dhclient doesn't care about /etc/network/interfaces at all. It just tries to get dhcp lease over the specified interfaces. Why only the one interface? because something is specifying that interface to dhclient. WHy doesn't the process get killed? because the rest of the networking system doesn't know about it. When you start networking, or do an ifup, those scripts keep track of the dhclient that it starts by pid. If dhclient is started by some other process, those scripts don't know about it. At least, again, that's how I understand it. That comes from just using them a lot, playing with it to see what it does. The canonical answer is to be found in the code. best A signature.asc Description: Digital signature
Re: Marvell 88E80856 switching from static to dhcp configuration all on its own
Thomas Preud'homme wrote: The Friday 18 July 2008 00:24:04 Andrew Sackville-West, you wrote : On Thu, Jul 17, 2008 at 02:30:42PM -0700, Freddy Freeloader wrote: Andrew Sackville-West wrote: On Thu, Jul 17, 2008 at 01:36:43PM -0700, Freddy Freeloader wrote: Andrew Sackville-West wrote: On Thu, Jul 17, 2008 at 11:14:25AM -0700, Freddy Freeloader wrote: [...] I have two NICs. The onboard Marvell and a 3Com 3c905b. The 3Com handles dhcp and dns requests. Both are configured for statically configured IP addresses in /etc/network/interfaces. However, the Marvell will, after some unknown amount of time--less than 12 hours--drop its static IP address and request a dhcp address from the 3Com adapter. [...] probably a killall dhclient will sort it out. [...] [I] will give that a try and see if the behavior changes. [...] perhaps some other package is starting dhclient? Basically, if you have both interfaces using static ip, dhclient shouldn't even be started. care to post /etc/network/interfaces? [...] For some reason dhclient WAS running, but I don't know why. if it reappears, try a `ps aux`, maybe there will be a clue there as to where it's coming from. And after a reboot, run watch grep dhclient /var/log/syslog or some equivalent and watch for it to show up. You wouldn't happen to have any guesses on the second problem I listed would you? :) nope, sorry. A You could also look with a pstree or recompile dhclient with a getppid at the beginning in order to see which process launch dhclient. I'll try pstree. I hadn't thought of that. These troubleshooting suggestions really don't help explain to me why dhclient would override the settings in /etc/network/interfaces for one NIC and not the other though. And why would it override manual settings? Isn't there some process watching the settings in /etc/network/interfaces to stop just such a thing from happening, or doesn't the driver and device itself record its state so that dhclient wouldn't even attempt this unless there is some type of user override, i.e. ifdown/ifup, /etc/init.d/networking restart, etc... ? There's something going on that I really don't understand here, and just troubleshooting it at the level shown here doesn't seem to me that it will answer my base questions. Can anyone point me to documentation on how this works, because I must be missing something. Why wouldn't restarting networking not have killed dhclient after /etc/network/interfaces was read, the NIC's configured, and all NIC's were configured with a static IP address? Also, I still think there is a driver issue with this as eth1 sent out dhcp requests probably a dozen times (cycles of 6 dhcprequests), received no answers, and then was answered with multiple offers before it finally accepted one of those offers and bound to that address? It seems to me if there were no driver issues involved eth1 would have gotten its dhcp address on the first attempt if this was all related to JUST dhclient. One of the problems with this module in the 2.6.24 kernel was the interface would come up, accept an IP address from /etc/network/interfaces, but it couldn't send or receive anything. This seems to be an extension of that problem. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Marvell 88E80856 switching from static to dhcp configuration all on its own
The Friday 18 July 2008 00:24:04 Andrew Sackville-West, you wrote : > On Thu, Jul 17, 2008 at 02:30:42PM -0700, Freddy Freeloader wrote: > > Andrew Sackville-West wrote: > >> On Thu, Jul 17, 2008 at 01:36:43PM -0700, Freddy Freeloader wrote: > >>> Andrew Sackville-West wrote: > On Thu, Jul 17, 2008 at 11:14:25AM -0700, Freddy Freeloader wrote: > > [...] > > > I have two NICs. The onboard Marvell and a 3Com 3c905b. The > > 3Com handles dhcp and dns requests. Both are configured for > > statically configured IP addresses in /etc/network/interfaces. > > However, the Marvell will, after some unknown amount of > > time--less than 12 hours--drop its static IP address and > > request a dhcp address from the 3Com adapter. > > [...] > > probably a killall dhclient will sort it out. > > [...] > > >>> [I] will give that a try and see if the behavior changes. > > [...] > > >> perhaps some other package is starting dhclient? Basically, if you > >> have both interfaces using static ip, dhclient shouldn't even be > >> started. care to post /etc/network/interfaces? > > [...] > > > For some reason dhclient WAS running, but I don't know why. > > if it reappears, try a `ps aux`, maybe there will be a clue there as > to where it's coming from. And after a reboot, run > > watch grep dhclient /var/log/syslog > > or some equivalent and watch for it to show up. > > > You wouldn't happen to have any guesses on the second problem I listed > > would you? :) > > nope, sorry. > > A You could also look with a pstree or recompile dhclient with a getppid at the beginning in order to see which process launch dhclient. -- Thomas Preud'homme Why debian : http://www.debian.org/intro/why_debian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Marvell 88E80856 switching from static to dhcp configuration all on its own
On Thu, Jul 17, 2008 at 02:30:42PM -0700, Freddy Freeloader wrote: > Andrew Sackville-West wrote: >> On Thu, Jul 17, 2008 at 01:36:43PM -0700, Freddy Freeloader wrote: >>> Andrew Sackville-West wrote: On Thu, Jul 17, 2008 at 11:14:25AM -0700, Freddy Freeloader wrote: [...] > I have two NICs. The onboard Marvell and a 3Com 3c905b. The > 3Com handles dhcp and dns requests. Both are configured for > statically configured IP addresses in /etc/network/interfaces. > However, the Marvell will, after some unknown amount of > time--less than 12 hours--drop its static IP address and > request a dhcp address from the 3Com adapter. [...] probably a killall dhclient will sort it out. [...] >>> [I] will give that a try and see if the behavior changes. [...] >> >> perhaps some other package is starting dhclient? Basically, if you >> have both interfaces using static ip, dhclient shouldn't even be >> started. care to post /etc/network/interfaces? [...] > For some reason dhclient WAS running, but I don't know why. if it reappears, try a `ps aux`, maybe there will be a clue there as to where it's coming from. And after a reboot, run watch grep dhclient /var/log/syslog or some equivalent and watch for it to show up. > You wouldn't happen to have any guesses on the second problem I listed > would you? :) nope, sorry. A signature.asc Description: Digital signature
Re: Marvell 88E80856 switching from static to dhcp configuration all on its own
Andrew Sackville-West wrote: On Thu, Jul 17, 2008 at 01:36:43PM -0700, Freddy Freeloader wrote: Andrew Sackville-West wrote: On Thu, Jul 17, 2008 at 11:14:25AM -0700, Freddy Freeloader wrote: Hi All, I'm having a strange problem with a Marvell 88E8056 - 10/100/1000 Controller on a Biostar TA 770 A2+ motherboard. This is an Etch AMD64 install, but I have added the 2.6.25-amd64 kernel as I could not get the Marvell controller to work at all with the 2.6.18 kernel. ... I have two NICs. The onboard Marvell and a 3Com 3c905b. The 3Com handles dhcp and dns requests. Both are configured for statically configured IP addresses in /etc/network/interfaces. However, the Marvell will, after some unknown amount of time--less than 12 hours--drop its static IP address and request a dhcp address from the 3Com adapter. ... I'm assuming this is a bug in the sky2 module, but don't know enough about things in this area to do more than assume. I bet it's not a driver problem but simply that you have inadvertently started a dhclient. It picks up a lease from somewhere, but then you restart networking which reverts the interface to a static address. Then when the dhclient thinks the lease has expired, it goes and gets another one. I've seen this happen on my laptop when I've been monkeying around with getting a connection at a new location. I'll forget that I manually started dhclient and then some time later... maybe days, I'll connect somewhere where I get static ip (like home) and then all of the sudden the dhclient will wake up and go looking for a new address... probably a killall dhclient will sort it out. I wondered about it, but it didn't make sense in that the networking system is completely ignoring its own configuration. Plus, this behavior has survived several reboots of the system. However, I will give that a try and see if the behavior changes. do you have network-mangler^Wmanager installed? perhaps some other package is starting dhclient? Basically, if you have both interfaces using static ip, dhclient shouldn't even be started. care to post /etc/network/interfaces? A For some reason dhclient WAS running, but I don't know why. Especially on that interface as it was not chosen as the default interface during install, and that's the only interface I've had configured to use dhcp at any time. As I said, both interfaces specify "static" in /etc/network/interfaces. It's working now as it's had long enough to repeat its behavior based on the time frame of how long things took to happen last time so I'm assuming it's fixed. And, if dhclient was getting a new IP address for that interface, why not for the other NIC too? What makes the Marvell interface the interface that keeps getting reconfigured and the 3Com interface stay stable? I've never seen this kind of thing happen before and I've switched interfaces between static and dhcp many times. I've never had to manually kill dhclient before to keep it from reconfiguring a working, manually configured, interface. To me that says there is possibly something wrong with the driver for the NIC itself and it's crashing and losing its state or something. Nothing shows up in syslog or kern.log, but I still wonder about it. And, no, network-mangler isn't running or installed. It's one of the first things I get rid of in a desktop install. IIRC, n-m only comes with a gui, and I have no gui installed. Plus, it doesn't show up using dpkg -l | grep network so I know it's not there This is just a base install with the server packages I need to run for use in my lab. Nothing else. You wouldn't happen to have any guesses on the second problem I listed would you? :) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Marvell 88E80856 switching from static to dhcp configuration all on its own
On Thu, Jul 17, 2008 at 01:36:43PM -0700, Freddy Freeloader wrote: > Andrew Sackville-West wrote: >> On Thu, Jul 17, 2008 at 11:14:25AM -0700, Freddy Freeloader wrote: >> >>> Hi All, >>> >>> I'm having a strange problem with a Marvell 88E8056 - 10/100/1000 >>> Controller on a Biostar TA 770 A2+ motherboard. This is an Etch >>> AMD64 install, but I have added the 2.6.25-amd64 kernel as I could >>> not get the Marvell controller to work at all with the 2.6.18 >>> kernel. >> >> ... >> >> >>> I have two NICs. The onboard Marvell and a 3Com 3c905b. The 3Com >>> handles dhcp and dns requests. Both are configured for statically >>> configured IP addresses in /etc/network/interfaces. However, the >>> Marvell will, after some unknown amount of time--less than 12 >>> hours--drop its static IP address and request a dhcp address from the >>> 3Com adapter. >>> >> >> ... >> >>> I'm assuming this is a bug in the sky2 module, but don't know enough >>> about things in this area to do more than assume. >> >> I bet it's not a driver problem but simply that you have inadvertently >> started a dhclient. It picks up a lease from somewhere, but then you >> restart networking which reverts the interface to a static >> address. Then when the dhclient thinks the lease has expired, it goes >> and gets another one. >> >> I've seen this happen on my laptop when I've been monkeying around >> with getting a connection at a new location. I'll forget that I >> manually started dhclient and then some time later... maybe days, I'll >> connect somewhere where I get static ip (like home) and then all of >> the sudden the dhclient will wake up and go looking for a new >> address... >> >> probably a killall dhclient will sort it out. >> > > I wondered about it, but it didn't make sense in that the networking > system is completely ignoring its own configuration. Plus, this > behavior has survived several reboots of the system. However, I will > give that a try and see if the behavior changes. do you have network-mangler^Wmanager installed? perhaps some other package is starting dhclient? Basically, if you have both interfaces using static ip, dhclient shouldn't even be started. care to post /etc/network/interfaces? A signature.asc Description: Digital signature
Re: Marvell 88E80856 switching from static to dhcp configuration all on its own
Andrew Sackville-West wrote: On Thu, Jul 17, 2008 at 11:14:25AM -0700, Freddy Freeloader wrote: Hi All, I'm having a strange problem with a Marvell 88E8056 - 10/100/1000 Controller on a Biostar TA 770 A2+ motherboard. This is an Etch AMD64 install, but I have added the 2.6.25-amd64 kernel as I could not get the Marvell controller to work at all with the 2.6.18 kernel. ... I have two NICs. The onboard Marvell and a 3Com 3c905b. The 3Com handles dhcp and dns requests. Both are configured for statically configured IP addresses in /etc/network/interfaces. However, the Marvell will, after some unknown amount of time--less than 12 hours--drop its static IP address and request a dhcp address from the 3Com adapter. ... I'm assuming this is a bug in the sky2 module, but don't know enough about things in this area to do more than assume. I bet it's not a driver problem but simply that you have inadvertently started a dhclient. It picks up a lease from somewhere, but then you restart networking which reverts the interface to a static address. Then when the dhclient thinks the lease has expired, it goes and gets another one. I've seen this happen on my laptop when I've been monkeying around with getting a connection at a new location. I'll forget that I manually started dhclient and then some time later... maybe days, I'll connect somewhere where I get static ip (like home) and then all of the sudden the dhclient will wake up and go looking for a new address... probably a killall dhclient will sort it out. A I wondered about it, but it didn't make sense in that the networking system is completely ignoring its own configuration. Plus, this behavior has survived several reboots of the system. However, I will give that a try and see if the behavior changes. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Marvell 88E80856 switching from static to dhcp configuration all on its own
On Thu, Jul 17, 2008 at 11:14:25AM -0700, Freddy Freeloader wrote: > Hi All, > > I'm having a strange problem with a Marvell 88E8056 - 10/100/1000 > Controller on a Biostar TA 770 A2+ motherboard. This is an Etch AMD64 > install, but I have added the 2.6.25-amd64 kernel as I could not get the > Marvell controller to work at all with the 2.6.18 kernel. ... > I have two NICs. The onboard Marvell and a 3Com 3c905b. The 3Com > handles dhcp and dns requests. Both are configured for statically > configured IP addresses in /etc/network/interfaces. However, the > Marvell will, after some unknown amount of time--less than 12 > hours--drop its static IP address and request a dhcp address from the > 3Com adapter. ... > > I'm assuming this is a bug in the sky2 module, but don't know enough > about things in this area to do more than assume. I bet it's not a driver problem but simply that you have inadvertently started a dhclient. It picks up a lease from somewhere, but then you restart networking which reverts the interface to a static address. Then when the dhclient thinks the lease has expired, it goes and gets another one. I've seen this happen on my laptop when I've been monkeying around with getting a connection at a new location. I'll forget that I manually started dhclient and then some time later... maybe days, I'll connect somewhere where I get static ip (like home) and then all of the sudden the dhclient will wake up and go looking for a new address... probably a killall dhclient will sort it out. A signature.asc Description: Digital signature
Marvell 88E80856 switching from static to dhcp configuration all on its own
Hi All, I'm having a strange problem with a Marvell 88E8056 - 10/100/1000 Controller on a Biostar TA 770 A2+ motherboard. This is an Etch AMD64 install, but I have added the 2.6.25-amd64 kernel as I could not get the Marvell controller to work at all with the 2.6.18 kernel. Other than that this is pretty much a minimal install. No gui, just a basic system running dns, dhcp3, mysql 5.0, postgresql 8.1and Apache2 in my test lab. This system has no contact with the internet other than as a dns forwarder. I have two NICs. The onboard Marvell and a 3Com 3c905b. The 3Com handles dhcp and dns requests. Both are configured for statically configured IP addresses in /etc/network/interfaces. However, the Marvell will, after some unknown amount of time--less than 12 hours--drop its static IP address and request a dhcp address from the 3Com adapter. If I do an ifconfig -a it shows the dhcp address, and if I run nmap against the network--how I found this originally as there was an unknown IP address showing up and a known good one missing--the dhcp address shows up. However, if I look at /etc/network/interfaces the Marvell interface is still set to static, and if I restart networking ( /etc/init.d/networking restart ) the Marvell NIC picks up its static IP address again. Below is the output from lscpi -vv concerning the NIC in question. 03:00.0 Ethernet controller: Marvell Technology Group Ltd. Unknown device 4364 (rev 13) Subsystem: Biostar Microtech Int'l Corp Unknown device 2700 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Latency: 0, Cache Line Size: 32 bytes Interrupt: pin A routed to IRQ 1276 Region 0: Memory at fddfc000 (64-bit, non-prefetchable) [size=16K] Region 2: I/O ports at de00 [size=256] [virtual] Expansion ROM at fdc0 [disabled] [size=128K] Capabilities: [48] Power Management version 3 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=1 PME- Capabilities: [50] Vital Product Data Capabilities: [5c] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable+ Address: fee0300c Data: 4191 Capabilities: [e0] Express Legacy Endpoint IRQ 0 Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag- Device: Latency L0s unlimited, L1 unlimited Device: AtnBtn- AtnInd- PwrInd- Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported- Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- Device: MaxPayload 128 bytes, MaxReadReq 512 bytes Link: Supported Speed 2.5Gb/s, Width x1, ASPM L0s L1, Port 3 Link: Latency L0s <256ns, L1 unlimited Link: ASPM Disabled RCB 128 bytes CommClk+ ExtSynch- Link: Speed 2.5Gb/s, Width x1 Capabilities: [100] Advanced Error Reporting Hmmm It's been 45 minutes since I restarted networking and the Marvell has already dropped its static IP address and picked up a dhcp address. Below is the relevant information from syslog after restarting networking. Jul 17 09:45:56 lab kernel: [81245.173294] eth0: no IPv6 routers present Jul 17 09:46:01 lab kernel: [81249.915550] eth1: no IPv6 routers present Jul 17 09:46:26 lab dhcpd: receive_packet failed on eth0: Network is down Jul 17 09:46:26 lab kernel: [81275.403919] sky2 eth1: disabling interface Jul 17 09:46:26 lab dhclient: receive_packet failed on eth1: Network is down Jul 17 09:46:26 lab kernel: [81275.414464] eth0: setting full-duplex. Jul 17 09:46:26 lab kernel: [81275.449493] sky2 eth1: enabling interface Jul 17 09:46:26 lab kernel: [81275.451945] ADDRCONF(NETDEV_UP): eth1: link is not ready Jul 17 09:46:29 lab kernel: [81278.425075] sky2 eth1: Link is up at 1000 Mbps, full duplex, flow control both Jul 17 09:46:29 lab kernel: [81278.427530] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready Jul 17 09:46:36 lab kernel: [81285.424608] eth0: no IPv6 routers present Jul 17 09:46:39 lab kernel: [81288.428601] eth1: no IPv6 routers present Jul 17 09:55:19 lab dhclient: DHCPREQUEST on eth1 to 192.168.1.28 port 67 Jul 17 09:55:33 lab last message repeated 3 times Jul 17 09:55:41 lab dhclient: DHCPREQUEST on eth1 to 192.168.1.28 port 67 Jul 17 09:56:18 lab last message repeated 3 times Jul 17 09:57:38 lab last message repeated 4 times Jul 17 09:58:39 lab last message repeated 4 times Jul 17 09:59:29 lab last message repeated 3 times Jul 17 10:00:28 lab last message repeated 4 times This repeats a few more times and then: Jul 17 10:04:39 lab dhcpd: Wrote 0 deleted host decls to leases file. Jul 17 10:04:39 lab dhcpd: Wrote 0 new dynamic host decls to leases file. Jul 17 10:04:39 lab dhcpd: Wrote 7 leases to lease
dhcp configuration issues
I have a dsl gateway that can't seem to give out proper dns
information. So I configured it to pass different dns servers in its
dhcp leases. When I cat /var/lib/dhcp/dhclient.leases it looks like
this:
lease {
interface "eth0"
fixed-address 192.168.0.2;
option subnet-mask 255.255.255.0;
option routers 192.168.0.1;
option domain-name-servers 205.171.2.65,205.171.3.65;
option domain-name "domain.actdsltmp";
option dhcp-lease-time 86400;
option dhcp-message-type 5;
option dhcp-server-identifier 192.168.0.1;
renew 4 2005/8/18 04:15:22;
rebind 4 2005/8/18 13:15:22;
expire 4 2005/8/18 16:15:22;
}
Which is what I would expect, but then looking at /etc/resolv.conf I
still have 192.168.0.1 as my primary name server. How do I go about
chaning this? I know I can use supersede and append but I don't want
to use these servers on every network I connect to.
I'm sure I'm missing something simple.
Thanks in advance.
Dave
Re: dhcp configuration
On Mon, 20 Aug 2001, dman wrote: > On Tue, Aug 21, 2001 at 07:16:29AM +1000, Serge Rey wrote: > > | for the benefit of future users who may run into the same issue you did, > | could you tell us what did you uninstall and reinstall? > > # apt-get remove --purge > # apt-get install > This is basically what I did, except using dselect. Not sure why it fixed my problem though. Maybe I screwed up one of my config files the first time around. Oh well, all is happy now, and I got LiVid to work nicely so it's time to try out some DVDs. :-) Titus Barik ([EMAIL PROTECTED]) AIM: TBarik ICQ: 1604453
Re: dhcp configuration
On Tue, Aug 21, 2001 at 07:16:29AM +1000, Serge Rey wrote: | for the benefit of future users who may run into the same issue you did, | could you tell us what did you uninstall and reinstall? # apt-get remove --purge # apt-get install (in his case, was "pump") -D
Re: dhcp configuration
On Mon, Aug 20, 2001 at 03:33:10PM -0400, Titus Barik wrote: > On 20 Aug 2001, Michael Heldebrant wrote: > > > What does your /etc/pump.conf file look like? > > > > --mike > > Hmm, it works now. I simply uninstalled (with purge) and reinstalled and > everything seems to be okay. I guess that's what I get for running > testing. > titus, for the benefit of future users who may run into the same issue you did, could you tell us what did you uninstall and reinstall? thanks -- Sergio J. Rey http://typhoon.sdsu.edu/rey.html Probability does not exist. - B. de Finetti Chances are. - J. Mathis
Re: dhcp configuration
On 20 Aug 2001, Michael Heldebrant wrote: > What does your /etc/pump.conf file look like? > > --mike Hmm, it works now. I simply uninstalled (with purge) and reinstalled and everything seems to be okay. I guess that's what I get for running testing. Thanks for all your help. Titus Barik ([EMAIL PROTECTED]) AIM: TBarik ICQ: 1604453
Re: dhcp configuration
On 20 Aug 2001 14:33:20 -0400, Titus Barik wrote: > On Mon, 20 Aug 2001, dman wrote: > > > | Debian. Can someone tell me what the preferred (and hopefully best) way > > | to setup DHCP is? I also notice that there is another dhcp client that > > | one can choose from (dhcpcd). > > > > What network interface is configured by DHCP? eth0? What does your > > /etc/network/interfaces look like? > > > > auto eth1 > > iface eth1 inet dhcp > > ifconfig tells me that my ethernet card is on eth0. Thus, I added the > lines: > > auto eth0 > iface eth0 inet dhcp > > to my /etc/network interfaces file. > > I then rebooted, but ethernet doesn't work. I can still type "pump", and > then use the ethernet. I have a feeling that I'm missing some simple > step. What does your /etc/pump.conf file look like? --mike
Re: dhcp configuration
On Mon, 20 Aug 2001, dman wrote: > | Debian. Can someone tell me what the preferred (and hopefully best) way > | to setup DHCP is? I also notice that there is another dhcp client that > | one can choose from (dhcpcd). > > What network interface is configured by DHCP? eth0? What does your > /etc/network/interfaces look like? > > auto eth1 > iface eth1 inet dhcp ifconfig tells me that my ethernet card is on eth0. Thus, I added the lines: auto eth0 iface eth0 inet dhcp to my /etc/network interfaces file. I then rebooted, but ethernet doesn't work. I can still type "pump", and then use the ethernet. I have a feeling that I'm missing some simple step. Titus Barik ([EMAIL PROTECTED]) AIM: TBarik ICQ: 1604453
Re: dhcp configuration
On Mon, Aug 20, 2001 at 01:55:29PM -0400, Titus Barik wrote: | | Hi, I'm a newbie to Debian, and I'm not sure what the proper way to | configure DHCP is. Right now, I simply type 'pump' after the computer is | restarted. I initially thought that I should put this in init.d, but I | am not exactly sure what the proper way to do this would be in | Debian. Can someone tell me what the preferred (and hopefully best) way | to setup DHCP is? I also notice that there is another dhcp client that | one can choose from (dhcpcd). What network interface is configured by DHCP? eth0? What does your /etc/network/interfaces look like? My DHCP configured interface is eth1 so my /etc/network/interfaces file has auto eth1 iface eth1 inet dhcp in it. I also specified some options below that so a certain command is run whenever the interface is brought up. HTH, -D
dhcp configuration
Hi, I'm a newbie to Debian, and I'm not sure what the proper way to configure DHCP is. Right now, I simply type 'pump' after the computer is restarted. I initially thought that I should put this in init.d, but I am not exactly sure what the proper way to do this would be in Debian. Can someone tell me what the preferred (and hopefully best) way to setup DHCP is? I also notice that there is another dhcp client that one can choose from (dhcpcd). Thanks in advance. It is much appreciated. Titus Barik ([EMAIL PROTECTED]) AIM: TBarik ICQ: 1604453
Network DHCP Configuration
Hi, I put Internet at my home with cable 24 hours by day. There is now a server at my building and I have to get an IP number with DCHP and I installed dhcp client but it doesnt work. There is an error now. ifconfig eth0 eth0 Link encap:Ethernet HWaddr 08:00:31:00:1F:F8 inet addr:10.200.0.187 Bcast:10.255.255.255 Mask:255.0.0.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:252 dropped:0 overruns:0 frame:0 TX packets:5 errors:0 dropped:0 overruns:0 carrier:0 Collisions:0 Interrupt:10 Base address:0xd000 And when I try any net service there is an error: TIMEOUT WAITING FOT TX RDC What is RDC? Leonardo Gresta Paulino Murta COPPE/UFRJ - M.Sc. student (Software Engineering) http://www.cos.ufrj.br/~murta [EMAIL PROTECTED] - End forwarded message - -- Abraços,PH Paulo Henrique Baptista de Oliveira -- [EMAIL PROTECTED] Information Technology Consultant Linux Solutions -- http://www.linuxsolutions.com.br Av. Presidente Vargas, 509/4o andar - 852-4564 - Rio de Janeiro - RJ Brazil
