Help with weird portmapper problem

Help with weird portmapper problem

Post by Jay Mayna » Fri, 22 May 1998 04:00:00

I'm trying to use my Debian 1.31 box as a boot server for a VAX to work on
a NetBSD/VAX port. When I try to use bootparamd for the purpose, the VAX
never gets a reply to the "whoami" request, after successfully using RARP
to get its IP address. epan shows the RPC portmap request arriving on the
Linux box, but portmap never gets the packet (or at least debug mode never
shows the request coming in). I've gone so far as to rcompile portmap from
the source code. My hosts.allow has ALL:ALL (the LAN's behind a firewall).
ifconfig eth0 shows:

eth0      Link encap:10Mbps Ethernet  HWaddr 00:C0:26:38:EB:1F
          inet addr:  Bcast:  Mask:
          RX packets:56023 errors:0 dropped:0 overruns:0
          TX packets:19194 errors:0 dropped:0 overruns:0
          Interrupt:9 Base address:0x360
I've read all the doc I could find, and it all said, basically, "if
portmapper's running, you're done." This is driving me nute. Help!
Jay Maynard, EMT/P, K5ZC, PP-ASEL | Never ascribe to malice that which can

    "I'm just a cute little don't cross me." -- Dot Warner


1. Weird Ping, weird FTP, weird Telnet... HELP!!!

Can anyone diagnose this for me?

I'm in the process of building up a firewall but at some stage I musta
messed up and am now getting really weird results.

This is the results of a ping from to (the box
which will become the fireawall).

PING ( from : 56(84) bytes of
64 bytes from icmp_seq=0 ttl=225 time=0.7ms
64 bytes from icmp_seq=1 ttl=225 time=80001.0ms
64 bytes from icmp_seq=2 ttl=225 time=160000.9ms
64 bytes from icmp_seq=3 ttl=225 time=240000.8ms
64 bytes from icmp_seq=4 ttl=225 time=320000.8ms
64 bytes from icmp_seq=5 ttl=225 time=400000.7ms
64 bytes from icmp_seq=6 ttl=225 time=480000.7ms


--- ping statistics ---
509 packets transmitted, 8 packets received, 98% packet loss
round-trip min/avg/max = 0.7/280000.7/560000.6 ms

This also happens when I do it from other machines behind the firewall
but I was very surprised when it did it when pinging itself.

Theres a pattern of 80000ms increments between successful pings...
Can't figure out whats wrong though.

If I try to telnet or FTP, I have to wait for an eternity b4 the login
prompt appears after the initial "connected" msg. But once I login
there is no problem using the console or transferring files. Same
thing for other machines to So the network is "working"
but its waiting for something.

Has anyone had this happen to them b4 and manage to solve it?

Any help appreciated


2. remotely tar files on a backup tape from another machine

3. Weird, weird, weird issue ....

4. Need help with Sendmail optimization

5. Help with Portmapper

6. Problem with COW (Netrek) port

7. Help! with digital portmapper

8. rpc.statd

9. Help-portmapper not responding

10. help with portmapper message

11. portmapper problem

12. problems with portmapper / library upgrade (?)

13. RPC Portmapper problems