Hey Everyone,

Well, someone on this list mentioned that if Cox takes over the ailing 
@home service that they are going to go DHCP all the way.

I have never been successful getting DHCP to work on my boxen and have 
always just hardcoded the IP they gave me.  My setup is the following:

*486 running Debian stable acting as a firewall
*two ethernet cards
*the Trinity OS firewall script
*pump dhcp client on eth0
*eth1 acting as a 192.168.0.* internal network

Whenever I try to start pump like this:

  $ pump -h cx1211543-a

it fails.  Here is the output in syslog:


Nov 30 16:58:17 cx1211543-a pumpd[15189]: PUMP: sending discover Nov 30 
16:58:17 cx1211543-a pumpd[15189]: breq: opcode: 1
Nov 30 16:58:17 cx1211543-a pumpd[15189]: breq: hw: 1
Nov 30 16:58:17 cx1211543-a pumpd[15189]: breq: hwlength: 6
Nov 30 16:58:17 cx1211543-a pumpd[15189]: breq: hopcount: 0
Nov 30 16:58:17 cx1211543-a pumpd[15189]: breq: id: 0xd47be056
Nov 30 16:58:17 cx1211543-a pumpd[15189]: breq: secs: 0
Nov 30 16:58:17 cx1211543-a pumpd[15189]: breq: flags: 0x   0
Nov 30 16:58:17 cx1211543-a pumpd[15189]: breq: ciaddr: 0.0.0.0
Nov 30 16:58:17 cx1211543-a pumpd[15189]: breq: yiaddr: 0.0.0.0
Nov 30 16:58:17 cx1211543-a pumpd[15189]: breq: server_ip: 0.0.0.0
Nov 30 16:58:17 cx1211543-a pumpd[15189]: breq: bootp_gw_ip: 0.0.0.0
Nov 30 16:58:17 cx1211543-a pumpd[15189]: breq: hwaddr: Nov 30 16:58:17 
cx1211543-a pumpd[15189]: breq: servername: Nov 30 16:58:17 cx1211543-a 
pumpd[15189]: breq: bootfile: Nov 30 16:58:17 cx1211543-a pumpd[15189]: 
breq: vendor: 0x63 0x53 0x82 0x63
Nov 30 16:58:17 cx1211543-a pumpd[15189]: breq: vendor:  53   1 0x 1
Nov 30 16:58:17 cx1211543-a pumpd[15189]: breq: vendor: 0xff
Nov 30 16:58:17 cx1211543-a kernel: eth0: Setting Rx mode to 0 addresses.
Nov 30 16:58:17 cx1211543-a kernel: eth0: Setting Rx mode to 1 addresses.
Nov 30 16:58:17 cx1211543-a kernel: Packet log: input REJECT eth0 PROTO=17 
192.168.0.1:68 255.255.255.255:67 L=328 S=0x00 I=14163 F=0x0000 T=64 (#12)
Nov 30 16:58:17 cx1211543-a kernel: Packet log: input REJECT eth0 PROTO=2 
192.168.100.1:65535 224.0.0.1:65535 L=28 S=0xC0 I=0 F=0x0000 T=1 (#15)
Nov 30 16:58:20 cx1211543-a kernel: Packet log: input REJECT eth0 PROTO=17 
192.168.0.1:68 255.255.255.255:67 L=328 S=0x00 I=14166 F=0x0000 T=64 (#12)
Nov 30 16:58:26 cx1211543-a kernel: Packet log: input REJECT eth0 PROTO=17 
192.168.0.1:68 255.255.255.255:67 L=328 S=0x00 I=14168 F=0x0000 T=64 (#12)
Nov 30 16:58:37 cx1211543-a kernel: Packet log: input REJECT eth0 PROTO=17 
192.168.0.1:68 255.255.255.255:67 L=328 S=0x00 I=14170 F=0x0000 T=64 (#12)

Obviously, the REJECTed packets make me suspicious of the firewall, but I 
am far from being a firewall expert.

Any help is appreciated.

julian


-- 
mail : julian @ catchen.org         | ( topeka )
www  : http://catchen.org/topeka/   |  phx, az
sent : Fri Nov 30, 2001 04:53PM MST | 
The state continues to kill its victims, not so much to defend society 
against
then -- for it could do that equally well by imprisonment -- but to appease
the mob's emotions of hatred and revenge.
                       --Clarence S. Darrow, "The Futility of the Death 
Penalty",
                         Forum, September 1928