Please be advised that we have just published a brand new, 1st edition report
reviewing the UK Pump Market in 2012 with forecasts to 2016 and would like to
extend an offer for you to receive a copy at 20% discount off the usual price
for a limited time. The report is the most detailed
On Tue, 08 Feb 2011 09:12:09 +, Tixy wrote:
>> > ;; ANSWER SECTION:
>> > maroon. 0 IN A 127.0.0.1
>> >
>> > ;; Query time: 0 msec
>> > ;; SERVER: 192.168.0.100#53(192.168.0.100) ;; WHEN: Sun Feb 6
>> > 23:20:41 2011
>> > ;; MSG SIZE rcvd: 40
>>
>> This is t
On Tue, 2011-02-08 at 04:44 +, T o n g wrote:
> On Mon, 07 Feb 2011 04:27:06 +, T o n g wrote:
>
> > $ dig maroon @maroon
> >
> > ; <<>> DiG 9.7.1-P2 <<>> maroon @maroon ;; global options: +cmd
> > ;; Got answer:
> > ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 53975 ;; flags: qr
>
On Mon, 07 Feb 2011 11:12:37 +, Tixy wrote:
> I also had another thought, Is kvm1 a virtual machine? If so, does it
> even get to talk directly to the dnsmasq server or is the host doing NAT
> and it's own configuration for the guest?
See my blog,
http://sfxpt.wordpress.com/2011/02/06/provi
On Mon, 2011-02-07 at 10:58 +, T o n g wrote:
> On Mon, 07 Feb 2011 07:23:33 +, Tixy wrote:
>
> > Had kvm1 got it's ip address by DHCP at this point? Dnsmasq doesn't
> > return results for machines until after its served out an address. . .
>
> Ahh... no wonder.
> Thanks -- what a good r
On Mon, 2011-02-07 at 03:15 +, T o n g wrote:
> On second though, if I dedicate a box for dnsmasq as both dhcp and dns ow
> this could be arranged.
> server, can I use a dhcp client on the very box to obtain the fixed IP
> address configured in dnsmasq?
>
> I know this is kind of chicken-egg
On Mon, 2011-02-07 at 04:27 +, T o n g wrote:
> On Sat, 05 Feb 2011 20:19:43 +, Tixy wrote:
>
> > . . . adding a dhcp-host line in dnsmasq.conf for each NIC. E.g. the
> > entry for the machine I'm typing on is
> >
> > dhcp-host=00:28:58:3A:EB:A1,192.168.2.20,computer2,infinite
> >
On Sat, 05 Feb 2011 20:19:43 +, Tixy wrote:
> . . . adding a dhcp-host line in dnsmasq.conf for each NIC. E.g. the
> entry for the machine I'm typing on is
>
> dhcp-host=00:28:58:3A:EB:A1,192.168.2.20,computer2,infinite
> ^ ^^ ^ MAC
On Sun, 2011-02-06 at 04:07 +, T o n g wrote:
> In that case, I assume that the dnsmasq server need to be configured to
> be on a static IP, correct? Any I need to manually set up everything
> else, like route, etc, correct?
Yes, in /etc/network/interfaces I have:
allow-hotplug eth0
ifa
On Sat, 05 Feb 2011 20:19:43 +, Tixy wrote:
> You'll have to disable DHCP on your router so only your new box responds
> to DHCP requests. . .
Thanks for your answer, Tixy.
In that case, I assume that the dnsmasq server need to be configured to
be on a static IP, correct? Any I need to man
On Sat, 2011-02-05 at 15:34 +, T o n g wrote:
[...]
> - The dnsmasq can be used as both dhchp and dns server. This is
> ideal for a home network. My question is, my router is
> currently acting as both dhchp and dns server for the moment,
> if I dedicate a box for dnsmasq as both dhchp an
Hi,
Some questions around pump, dhchp, dns and dnsmasq,
- Some dhcp server *requires* that hostnames be sent. I've found
document on how to send hostnames with other dhchp clients
except pump. Now, how can I configure pump to send hostnames
when making dhchp requests?
- The dnsmas
godo schreef:
On 10/27/2010 10:53 PM, Henrique de Moraes Holschuh wrote:
On Wed, 27 Oct 2010, steef wrote:
when i do on the evo n115: $lynx www.knmi.nl it ens up bij telling
me something like:
i cannot get into *file://localhost/home/steef/www.knmi.nl*:
something seems to be not exactly how i
On 10/27/2010 10:53 PM, Henrique de Moraes Holschuh wrote:
On Wed, 27 Oct 2010, steef wrote:
when i do on the evo n115: $lynx www.knmi.nl it ens up bij telling
me something like:
i cannot get into *file://localhost/home/steef/www.knmi.nl*:
something seems to be not exactly how i should want it
On Wed, 27 Oct 2010, steef wrote:
> when i do on the evo n115: $lynx www.knmi.nl it ens up bij telling
> me something like:
> i cannot get into *file://localhost/home/steef/www.knmi.nl*:
> something seems to be not exactly how i should want it.
The "http://"; part of the URL is likely not option
neighbourhood. sudo ifconfig wlan0 up tells me
that firmware version b43-phy0 is loaded but that link is not ready:
*ADDCONF (NETDEV_UP): wlan0: link is not ready*. sudo pump -i wlan0
tells: operation failed and a small program like wifi-radar cannot find
(in a test with consent of one of my neighbours) an IP
gusti <[EMAIL PROTECTED]>:
>
> I have all the packages up-to-date, I'm using official kernel 2.6.18
> for debian stable. I already tried 'dhclient' from the packages
> 'dhcp-client' and 'dhcp3-client' and 'pump' from the pack
Hello
My network die after few minutes all the time.
I have all the packages up-to-date, I'm using official kernel 2.6.18
for debian stable. I already tried 'dhclient' from the packages
'dhcp-client' and 'dhcp3-client' and 'pump' from the package &
On 2007-07-10 15:09:25 -0600, Bob Proulx wrote:
> > > but I think that maybe you simply need to remove all of the 'auto'
> > > and 'allow-hotplug' lines from the file. Then it won't be started
> > > automatically.
> >
> > But I want it to be started automatically on some networks. This is
> > very
Vincent Lefevre wrote:
> Bob Proulx wrote:
> > That bug may still be open but I have never seen it in any
> > configuration. I think that bug may no longer be there but no one has
> > verified it to root cause and so it has not been closed. There is no
> > discussion after the first report. Is a
ngs. The new debian-installer will set things up with
> allow-hotplug. Then machines such as laptops with a pcmcia slot or
> usb device can have network devices go online and offline in a nice
> hotplug fashion. Same for any other hotpluggable device.
There seems to be a difference. Wh
here are still networks
without DHCP.
> The Etch default is to use network-manager to bring network devices
> online. See /usr/share/doc/network-manager/README.Debian for full
> details.
I don't want something graphical.
> > because on another machine (a laptop) I use netenv a
is to use network-manager to bring network devices
online. See /usr/share/doc/network-manager/README.Debian for full
details.
> because on another machine (a laptop) I use netenv and DHCP is not
> used on some networks (BTW, I've already have a "killall pump" in
> my nete
but I don't know how at this moment.
> But on the other machine (on which I have the problem I mentioned at
> the beginning of this thread), when I type "pump -i eth1" (again, the
> device exists but is down and not connected), I also get the error
> message "Operati
assume that something specific to
> your system is messed up. You will need to debug it. Sorry but that
> is the best advice I can give.
OK, I confirm that this is a problem with pump (its man page sucks and
I didn't know how it should have behaved) on this particular machine.
egins the process again when it wakes
> up. This behavior seems to be exactly what you need; unfortunately, I
> don't know anything about pump.
The problem with dhclient is that it disconfigures the loopback
interface under some conditions. A bug is still open after 7 years!
ht
debug it. Sorry but that
is the best advice I can give.
> > > How can I make pump (the DHCP client I'm using) to try again
> > > periodically?
> >
> > I think it should already be trying again periodically.
>
> It doesn't, even with 'allow-hotpl
t; network isn't available yet. In this case, I can no longer ssh to
> it. And I can't reboot it remotely.
>
> How can I make pump (the DHCP client I'm using) to try again
> periodically? I think I can write a script that tests if pump
> is running (with the "ps&q
On 2007-06-29 12:50:14 +0200, Vincent Lefevre wrote:
> On 2007-06-28 15:17:45 -0600, Bob Proulx wrote:
> > Change the 'auto eth0' line to 'allow-hotplug eth0' instead. That
> > triggers the dhcp to happen when the device becomes available. That
> > will probably workaround whatever problem you ar
ow-hotplug is now the default in Etch.
This doesn't work. Probably a kernel problem then. I've reported
the bug.
> > How can I make pump (the DHCP client I'm using) to try again
> > periodically?
>
> I think it should already be trying again periodically.
It doesn&
ble. That
will probably workaround whatever problem you are experiencing. The
allow-hotplug is now the default in Etch.
> How can I make pump (the DHCP client I'm using) to try again
> periodically?
I think it should already be trying again periodically. Perhaps the
timeout is very long.
On a machine in a local network, I have in my /etc/network/interfaces
file:
auto eth0
iface eth0 inet dhcp
But after a power outage, my machine sometimes restarts while the
network isn't available yet. In this case, I can no longer ssh to
it. And I can't reboot it remotely.
How can I
Under 2.4.17.x I was using "pump -i eth0" to put my NIC in dhcp mode and all
was well.
I have now upgraded to "testing", i.e. [2.6.17-2-k7] and now pump won't
function. In fact it
puts the network down, which I bring back up with "networking restart" and
after w
* John Graves <[EMAIL PROTECTED]> [2004 Aug 10 14:24 -0500]:
> I added the above and rebootedvoila. I came up on the LAN.
> Thanks Nate.
Glad to hear it.
> Onto Samba..
Sorry, I have zero experience with that, so someone else will have to
step in. :-)
- Nate >>
--
Wireless | Am
Nate Bargmann wrote:
Mine is blank. Should I add what you have??
Yes!
Here is a sample interfaces file that should work with pump:
---
# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)
# The loopback interface
auto lo
* John Graves <[EMAIL PROTECTED]> [2004 Aug 10 13:17 -0500]:
> 846 ? Ss 0.00 pump
> 42.42 pts/1 S+ grep pump
That's good. Pump is being run.
> yes /etc/inet.d/networking does exist
That means the netbase
p eth0) doesn't work at all.
2. Pump when called the first time, says it can't start and that there
may be another instance of pump running. But when I check with
ifconfig, I now have eth0 up and running with an ip address.
What does the command 'ps ax | grep "pump
; 1. ifup (or ifup eth0) doesn't work at all.
> >
> > 2. Pump when called the first time, says it can't start and that there
> > may be another instance of pump running. But when I check with
> > ifconfig, I now have eth0 up and running with an ip address.
What do
On Tue, 10 Aug 2004 23:52, John Graves wrote:
> I have installed the Debian Sarge Distro. After some adventure, I am
> able to create a network connection. However several oddities occur.
>
> 1. ifup (or ifup eth0) doesn't work at all.
>
> 2. Pump when called the fi
I have installed the Debian Sarge Distro. After some adventure, I am
able to create a network connection. However several oddities occur.
1. ifup (or ifup eth0) doesn't work at all.
2. Pump when called the first time, says it can't start and that there
may be another instan
My DSL connection with iface eth0 inet dhcp works fine but every time I
reboot the system I have to run pump to set the gateway. Something I
read seemed to indicate that pump was needed with kernel-2.2.? but not
with kernel-2.4.18.
My system is Woody with kernel-2.4.18 so perhaps there is
Problem was:
"cottmain" == cottmain writes: ..snip ..
new kernel: fails to get ip at boot, works after'pump'
Solution from Shyamal:
If you built your own kernel be sure to set CONFIG_PACKET and
CONFIG_NETFILTER otherwise dhpcd will not work.
Resolution:
It worked perfectly. Th
"cottmain" == cottmain writes:
cottmain> Hello All, Debian woody 3.0r0 upgraded and new kernel
cottmain> -old kernel: obtained an ip address on boot perfectly,
cottmain> -new kernel: fails to get one at boot, only gets one
cottmain> after 'pump&#x
Hello All,
Debian woody 3.0r0 upgraded and new kernel
-old kernel: obtained an ip address on boot perfectly,
-new kernel: fails to get one at boot, only gets one after 'pump'
it's probably a classic mistake.
Any solutions greatly appreciated.
Thanks,
Daniel.
--
hello,
i've got a problem with Debian woody. When i boot via dhcp (pump), my
debian client doesn't set the hostname it should get via the "option
host-name" i put on server-side. I can't understand why, it sets up the
right gateway, ip, dnsserver ip but not the hostn
I believe I've discovered a minor bug, but I don't know which
package I should submit a bug report for. Some guidance would be
appreciated.
When I boot, /etc/init.d/networking calls /sbin/ifup, which in turn
starts the pump daemon when it brings eth0 with a DHCP assigned
address.
Late
On Mon, Mar 18, 2002 at 09:11:54PM +1100, Herbert Xu wrote:
> Sean 'Shaleh' Perry <[EMAIL PROTECTED]> wrote:
>
> > pump does not obey the RFC and has been known to not work on all networks.
> > Debian is moving away from it.
>
> This is no longer the cas
Sean 'Shaleh' Perry <[EMAIL PROTECTED]> wrote:
> pump does not obey the RFC and has been known to not work on all networks.
> Debian is moving away from it.
This is no longer the case. pump is now useing AF_PACKET to send discover
packets.
--
Debian GNU/Li
On Wed, Mar 13, 2002 at 03:12:04PM -0600, Elizabeth Barham wrote:
>
> In /etc/init.d/networking, you'll see:
>
>
> if ! [ -x /sbin/ifup ]; then
> exit 0
> fi
>
> -x == -x FILETrue if the file is executable by you.
>
> The file must exist and whoever
Martin Wuertele posts :
> modify /etc/network/interfaces and add the auto line
This is already there in my /etc/network/interfaces file. It fails to
work. Only if I run udhcpc as root, does the eth0 device come up. How
does one bring up the eth0 interface automatically upon boot ?
--
/(__ _
"Sridhar M.A." <[EMAIL PROTECTED]> writes:
> All these are there [/etc/networking/interfaces]. But, when I give
> the command:
>
> /etc/init.d/networking start|restart
>
> nothing happens.
~~~ ~~~
In /etc/init.d/networking, you'll see:
if ! [ -x /sbin/ifup ]; then
exit 0
fi
-
On Wed, Mar 13, 2002 at 10:23:48AM +0100, Martin Wuertele wrote:
>
> modify /etc/network/interfaces and add the auto line:
>
> eg
> auto eth0
>
> will when booting fire up eth0. and if your configuration is something
> like
> eth0 inet dhcp
> it will when booting a
Hi Raghavendra!
On Wed, 13 Mar 2002, Raghavendra Bhat wrote:
> I start udhcpc manually. What is the best way to start udhcpc while
> booting up ? Is it OK to create a symlink farm using update-rc.d ? How
> are you doing this ?
modify /etc/network/interfaces and add the auto line:
eg
auto
Adam Majer posts :
> like udhcpc since it is very small and seems to work quite reliably.
I start udhcpc manually. What is the best way to start udhcpc while
booting up ? Is it OK to create a symlink farm using update-rc.d ? How
are you doing this ?
TIA.
--
/(__ __|\ ragOO, VU2RGU<->h
o eth0
iface lo inet loopback
iface eth0 inet dhcp
and here I just use udhcpc - the tiny dhcp client... no config there.
I thought I was using dhcp-client (which I was) - but I just changed to
the tiny version. It works perfectly..
I found pump to be the most buggy dhcp client available - it wo
.33.137.200;
Adam Majer wrote:
On Tue, Mar 12, 2002 at 10:27:24AM -0600, hanasaki wrote:
I have both installed.
- is there a way to tell ifup/down which to use?
dhclient seems to need entries for each interface, that will get a
lease, in /etc/dhclient.conf. Pump is nice in that
On Tue, Mar 12, 2002 at 10:27:24AM -0600, hanasaki wrote:
> I have both installed.
> - is there a way to tell ifup/down which to use?
> dhclient seems to need entries for each interface, that will get a
> lease, in /etc/dhclient.conf. Pump is nice in that it only requireds on
On 12-Mar-2002 hanasaki wrote:
> I have both installed.
> - is there a way to tell ifup/down which to use?
> dhclient seems to need entries for each interface, that will get a
> lease, in /etc/dhclient.conf. Pump is nice in that it only requireds on
> place to specifiy tha
I have both installed.
- is there a way to tell ifup/down which to use?
dhclient seems to need entries for each interface, that will get a
lease, in /etc/dhclient.conf. Pump is nice in that it only requireds on
place to specifiy that the interface will be dhcp
(/etc/network
if you
switch to 'dhcp-client' instead of 'pump'.
--
ragOO, VU2RGU http://gnuhead.net.dhis.org/ GPG: 1024D/F1624A6E
Helping to keep the Air-Waves FREE Amateur Radio
Helping to keep your Software FREE the GNU Project
Helping to keep the W W W FREE Debian GNU/${kernel}
Hello:
I use a '386 (successfully) as a firewall, with Debian 2.2 on it. It
is connected to an ADSL modem and runs quite well. Its been up for 63
days, passing packets back and forth.
Lately, "pump", when asked for "status" (i.e. pump --status) on the
default device
I seem to have a problem with pump
On my laptop, when ever I pump an IP, it seems to fork a child process, and
while the parent eventually quits (when I get the IP) the child keeps on
pumping away, eventually causing me to loose the IP (as it seems to either
confuse the DHCP server, or it just
/etc/pump.conf:
domainsearch "demon.nl"
retries 3
timeout 60
device eth1 {
}
when I run ifup eth1 I get the following error in /var/log/syslog:
Oct 4 12:52:41 cumulus pumpd[5098]: HOSTNAME: requesting
MYNAME.demon.nl
Oct 4 12:52:41 cumulus pumpd[5098]: PUMP: sending discover
ge in /var/log/syslog:
> Oct 4 12:52:41 cumulus pumpd[5098]: HOSTNAME: requesting
> MYNAME.demon.nl
> Oct 4 12:52:41 cumulus pumpd[5098]: PUMP: sending discover
> Oct 4 12:52:41 cumulus pumpd[5098]: breq: opcode: 1
> Oct 4 12:52:41 cumulus pumpd[5098]: breq: hw: 1
> Oct 4 12:5
:
domainsearch "demon.nl"
retries 3
timeout 60
device eth1 {
}
when I run ifup eth1 I get the following message in /var/log/syslog:
Oct 4 12:52:41 cumulus pumpd[5098]: HOSTNAME: requesting
MYNAME.demon.nl
Oct 4 12:52:41 cumulus pumpd[5098]: PUMP: sending discover
Oct 4 12:52:
"demon.nl"
retries 3
timeout 60
device eth1 {
}
when I run ifup eth1 I get the following error in /var/log/syslog:
Oct 4 12:52:41 cumulus pumpd[5098]: HOSTNAME: requesting
MYNAME.demon.nl
Oct 4 12:52:41 cumulus pumpd[5098]: PUMP: sending discover
Oct 4 12:52:41 cumulus
I take it that is your own network? Try and have the dhcp server supply
the proper domain to your clients. That may or may not clean this up.
I'm not sure about how pump cleans and restores the resolv.conf or why
you get a zombie.
--mike
On 08 Aug 2001 20:07:47 +0200, Daniel Wagner
27;m not sure otherwise what would do that. What does the
> syslog say about pump lines? Can you run pump -i eth0 --status for me?
i've no idea what's this process is good for, that's why i asked.
|[EMAIL PROTECTED]:~# pump -i eth0 --status
|Device eth0
|IP: 1
about pump lines? Can you run pump -i eth0 --status for me?
--mike
On 08 Aug 2001 19:32:02 +0200, Daniel Wagner wrote:
> Michael Heldebrant <[EMAIL PROTECTED]> writes:
>
> > What kernel version and what is your /etc/pump.conf look like?
>
> the kernel i currently use is 2.4.7
What kernel version and what is your /etc/pump.conf look like?
--mike
> On 08 Aug 2001 18:30:14 +0200, Daniel Wagner wrote:
> hi,
>
> i've got a strange behavior of pump here on my box. when i use it to
> configure my interaces, i get strange kernelthreads:
>
> |10562
hi,
i've got a strange behavior of pump here on my box. when i use it to
configure my interaces, i get strange kernelthreads:
|10562 pts/2S 0:00 pump -i eth0
|10563 pts/2Z 0:00 [eth0 ]
|10564 pts/2SW 0:00 [eth0]
i've tried the dhcp-client package, no zomb
What's the proper way to get pump working with [EMAIL PROTECTED] cable modems.
They require the hostname to be seen. I have been able to get my debian
system up using Dhcpcd, but never with pump.
--
Lance Peterson
[EMAIL PROTECTED] - email
(817) 289-2800 x1142 - voicemai
>>>>> "Bill" == Bill Vinson <[EMAIL PROTECTED]> writes:
Bill> I determined what my problem was. I was using vinson.home as my
Bill> domain as I don't own a real one. When I switched it to
Bill> vinson.com it started working. It seems pump requires a r
I determined what my problem was. I was using vinson.home as my domain
as I don't own a real one. When I switched it to vinson.com it started
working. It seems pump requires a real dns name.
Bill
On Mon, 30 Jul 2001, Ron Golan wrote:
> On Mon, Jul 30, 2001 at 09:26:42PM +0200, G
On Mon, Jul 30, 2001 at 09:26:42PM +0200, Guy Geens wrote:
> >>>>> "Bill" == Bill Vinson <[EMAIL PROTECTED]> writes:
>
> Bill> I am having problems with dhcpd and pump. I run dhcpd on another
> Bill> system to manage my home net's IPs, but I c
>>>>> "Bill" == Bill Vinson <[EMAIL PROTECTED]> writes:
Bill> I am having problems with dhcpd and pump. I run dhcpd on another
Bill> system to manage my home net's IPs, but I can't get the
Bill> domainsearch list to be populated in /etc/reso
Greetings, all.
I'm running 2.2r3, and I'm having some difficulties setting my FQDN. My IP
address is assigned via DHCP from a server here at work; I'm using pump.
The DHCP server is set up such that when it assigns an IP address, it
automatically updates the DNS tables on that s
I am having problems with dhcpd and pump. I run dhcpd on another system
to manage my home net's IPs, but I can't get the domainsearch list to be
populated in /etc/resolv.conf.
When I obtain a lease with pump, it changes /etc/resolv.conf to include
my DNS servers, but it also blanks out
Once a week my ATT cablemodem lease expires. Pump has never auto-released.
I have a cronjob that runs monday at 5:00am, and thursday also. This covers
the spread incase a cable outage actually drops my line and isn't on the sunday
list for some reason.
It's not just you Carl, I hv
Guy Geens <[EMAIL PROTECTED]> writes:
> Alan> Hmmm... it shouldn't happen every week, but if your IP changes,
> Alan> pump will _not_ try to get a new lease...
>
> It might be an ISP policy.
It's not. I have the same ISP. 8^) They do renumber on o
Alan> Hmmm... it shouldn't happen every week, but if your IP changes,
Alan> pump will _not_ try to get a new lease...
It might be an ISP policy.
Some ISPs will force a new address on all users from time to time, to
make it difficult for people to run servers. (I know a DSL provider
who
Just wondering if this is a bug worth reporting or unique to me:
periodically (perhaps every other week) my Internet connection via
Optimum Online (Cablevision) freezes, and I have to kill and restart
pump in order to get everything freed up. Yes, kill, pump -R does
not work.
I'm connecti
Carl Fink <[EMAIL PROTECTED]> writes:
> periodically (perhaps every other week) my Internet connection via
> Optimum Online (Cablevision) freezes, and I have to kill and restart
> pump in order to get everything freed up. Yes, kill, pump -R does
> not work.
Hmmm... it shou
Hi,
I have a problem with pump. Generally, it works fine, but it doesn't
write the search directive in resolv.conf correctely. I get:
aphrodite:/home/matthias# pump -s
Device eth0
IP: 192.168.128.150
Netmask: 255.255.255.0
Broadcast: 192.168.128.255
Ne
put that on yet. I just don't quite understand how
kernel-package works, and can't find docs for it.
3. Promiscuos Mode
I use a notebook computer with a Xircom CardBus Ethernet 10/100 CBE2-100
PCMCIA nic, and I use DHCP to get my LAN IP from the router. When I boot
up, the card is reco
On Sat, Jan 20, 2001 at 06:32:47AM +, Jim Breton wrote:
> In /var/log/daemon.log I see the following:
>
> cardmgr[163]: + /sbin/pump -i eth0 > /dev/null
> cardmgr[163]: + pump: no extra parameters are expected
> cardmgr[163]: start cmd exited with status 1
Well... I fou
Please ignore, I was unaware of the debian-laptop list until just now;
will re-post there. Thanks.
I've got potato 2.2r2 running on a Quantex laptop.
Whenever I insert my ethernet card (Linksys PCMPC100), the drivers for
it load successfully but pump fails to configure it.
In /var/log/daemon.log I see the following:
cardmgr[163]: + /sbin/pump -i eth0 > /dev/null
cardmgr[163]: +
h0
> > at boot time. pump is already installed, but it doesn't seem to be doing
> > anything. I tried installing dhcpcd, but it conflicted with pump. Any
> > ideas? Thanks!
>
> Um, remove pump and install dhcpcd?
Pump should work fine after you edit /etc/net
On Fri, Jan 12, 2001 at 01:30:27AM -0600, Benjamin Pharr wrote:
> I finally found the right kernel options for my ethernet card, so now the
> kernel recognizes it, but I need to setup dhcp support to configure eth0
> at boot time. pump is already installed, but it doesn't se
I finally found the right kernel options for my ethernet card, so now the
kernel recognizes it, but I need to setup dhcp support to configure eth0
at boot time. pump is already installed, but it doesn't seem to be doing
anything. I tried installing dhcpcd, but it conflicted with pump.
Quoting Nathan E Norman <[EMAIL PROTECTED]>:
> On Thu, Jan 04, 2001 at 05:04:41PM -0600, Bill Bell wrote:
> > Hello all,
> >
> > I have a box which is using mostly woody and I have a quesiton
> > about using pump as a DHCP client. Documentation for pu
On Thu, Jan 04, 2001 at 05:04:41PM -0600, Bill Bell wrote:
> Hello all,
>
> I have a box which is using mostly woody and I have a quesiton about using
> pump
> as a DHCP client. Documentation for pump is scarce, perhaps because
> functionality is limited.
>
> How do
Hello all,
I have a box which is using mostly woody and I have a quesiton about using pump
as a DHCP client. Documentation for pump is scarce, perhaps because
functionality is limited.
How do I run a script each time pump refreshes it's information?
I would like to continue using pump,(
e ok.
>
> When I start 'pump', it tries to get dynamic ip from server using
> dhcp, but fails everytime. When 'pump' is trying to get the ip,
> 'ifconfig' shows this:
>
>
> eth0 Link encap:Ethernet HWaddr 00:00:C0:57:6D:DE
> UP
Hi List!
I have a problem configuring my debian potato to use dhcp. I'm
connected to the Internet via cable modem. The network card is
configured to irq=10 and io=0x300. The module is smc-ultra. The card
should be ok.
When I start 'pump', it tries to get dynamic ip from server
"Sean 'Shaleh' Perry" <[EMAIL PROTECTED]> writes:
> >
> > Why was pump made the default DHCP client ? I have been unable to get
> > pump working with my @Home setup. dhcp-client, however, works very
> > well.
> >
>
> dunno, appare
>
> Why was pump made the default DHCP client ? I have been unable to get
> pump working with my @Home setup. dhcp-client, however, works very
> well.
>
dunno, apparently it was small or something. Plus if it worked for Red Hat
..
> -Original Message-
> From: Bryan K. Walton [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, September 13, 2000 6:23 PM
> To: Debian-User Mailing List
> Subject: pump replacing dhcpcd?
>
>
> When I go to the debian web site and look up info on the pump
> package,
On 13-Sep-2000 Bryan K. Walton wrote:
> When I go to the debian web site and look up info on the pump package, one of
> the things that the page tells me is:
>
> "This is the DHCP/BOOTP client written by RedHat. This replaces the dhcpcd
> package."
>
> I take this
1 - 100 of 111 matches
Mail list logo
