(FWD)linux, cable modem, and RCN

[John Chambers]

Derek Atkins <warlord at MIT.EDU> wrote:
| As I said, pump _just worked_ for me with RCN.  The installers come,
| plug everything in, and then they turn the stuff on.  They wait a
| couple minutes for everything to sync up.  They may call back to the
| home office to make sure stuff is turned on.  Then you plug-in, "turn
| on your machine" (e.g.  run pump), and you should be on the net.  Just
| do this part yourself and ask them what they want to test.  Generally
| you can prove you're on the net by going to some web page (or pinging
| something).

Well, the RCN guy came plugged it all in, the lights came on, so I ran
   pump -i eth0

It instantly responded with "Operation failed."

| Also, pump logs to daemon.* so you probably want to put this in
| syslog.conf:
|
| daemon.debug		/var/log/debug.log

Yup; did that, and had "tail -f"  running  on  /var/log/messages  and
/var/log/debug.log  files.   When  I  ran the above pump command, the
messages file got the two messages:

Feb 21 11:59:17 kendy kernel: Packet log: out REJECT eth0 PROTO=17 0.0.0.0:68 255.255.255.255:67 L=328 S=0x00 I=25251 F=0x0000 T=64 (#6)
Feb 21 11:59:17 kendy kernel: Packet log: out REJECT eth0 PROTO=17 0.0.0.0:68 255.255.255.255:67 L=328 S=0x00 I=25252 F=0x0000 T=64 (#6)

The /var/log/debug.log file got the messages:

Feb 21 11:59:17 kendy pumpd[2511]: starting at Wed Feb 21 11:59:17 2001
Feb 21 11:59:17 kendy pumpd[2511]: PUMP: sending discover
Feb 21 11:59:17 kendy pumpd[2511]: breq: opcode: 1
Feb 21 11:59:17 kendy pumpd[2511]: breq: hw: 1
Feb 21 11:59:17 kendy pumpd[2511]: breq: hwlength: 6
Feb 21 11:59:17 kendy pumpd[2511]: breq: hopcount: 0
Feb 21 11:59:17 kendy pumpd[2511]: breq: id: 0x734b7729
Feb 21 11:59:17 kendy pumpd[2511]: breq: secs: 0
Feb 21 11:59:17 kendy pumpd[2511]: breq: flags: 0x   0
Feb 21 11:59:17 kendy pumpd[2511]: breq: ciaddr: 0.0.0.0
Feb 21 11:59:17 kendy pumpd[2511]: breq: yiaddr: 0.0.0.0
Feb 21 11:59:17 kendy pumpd[2511]: breq: server_ip: 0.0.0.0
Feb 21 11:59:17 kendy pumpd[2511]: breq: bootp_gw_ip: 0.0.0.0
Feb 21 11:59:17 kendy pumpd[2511]: breq: hwaddr:
Feb 21 11:59:17 kendy pumpd[2511]: breq: servername:
Feb 21 11:59:17 kendy pumpd[2511]: breq: bootfile:
Feb 21 11:59:17 kendy pumpd[2511]: breq: vendor: 0x63 0x53 0x82 0x63
Feb 21 11:59:17 kendy pumpd[2511]: breq: vendor:  53   1 0x 1
Feb 21 11:59:17 kendy pumpd[2511]: breq: vendor: 0xff
Feb 21 11:59:17 kendy pumpd[2511]: PUMP: sending discover
Feb 21 11:59:17 kendy pumpd[2511]: breq: opcode: 1
Feb 21 11:59:17 kendy pumpd[2511]: breq: hw: 1
Feb 21 11:59:17 kendy pumpd[2511]: breq: hwlength: 6
Feb 21 11:59:17 kendy pumpd[2511]: breq: hopcount: 0
Feb 21 11:59:17 kendy pumpd[2511]: breq: id: 0x734b7729
Feb 21 11:59:17 kendy pumpd[2511]: breq: secs: 0
Feb 21 11:59:17 kendy pumpd[2511]: breq: flags: 0x   0
Feb 21 11:59:17 kendy pumpd[2511]: breq: ciaddr: 0.0.0.0
Feb 21 11:59:17 kendy pumpd[2511]: breq: yiaddr: 0.0.0.0
Feb 21 11:59:17 kendy pumpd[2511]: breq: server_ip: 0.0.0.0
Feb 21 11:59:17 kendy pumpd[2511]: breq: bootp_gw_ip: 0.0.0.0
Feb 21 11:59:17 kendy pumpd[2511]: breq: hwaddr:
Feb 21 11:59:17 kendy pumpd[2511]: breq: servername:
Feb 21 11:59:17 kendy pumpd[2511]: breq: bootfile:
Feb 21 11:59:17 kendy pumpd[2511]: breq: vendor: 0x63 0x53 0x82 0x63
Feb 21 11:59:17 kendy pumpd[2511]: breq: vendor:  53   1 0x 1
Feb 21 11:59:17 kendy pumpd[2511]: breq: vendor: 0xff

Also, before this, eth0 was up and had an address (192.168.0.17), and
pinging  it  worked fine.  When I ran pump, etho disappeared from the
list that "ifconfig" returns.  "ifconfig -a' says that eth0  is  down
and no longer has an IP address.

I notice that there's  a  "pump  -i  eth0"  process  running  in  the
background,  and  it  periodically repeats the above two lines to the
messages file, but the debug.log file doesn't grow.

The installer guy doesn't have any clue about the  above  errors,  of
course.  Any idea what might be wrong here?

-
Subcription/unsubscription/info requests: send e-mail with
"subscribe", "unsubscribe", or "info" on the first line of the
message body to discuss-request at blu.org (Subject line is ignored).