Bug 55090 - portmap replies from wrong IP address
Summary: portmap replies from wrong IP address
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: portmap
Version: 6.2
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Trond Eivind Glomsrxd
QA Contact: Aaron Brown
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-10-25 12:56 UTC by Peter J. Holzer
Modified: 2007-04-18 16:37 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2001-10-30 17:18:39 UTC
Embargoed:


Attachments (Terms of Use)

Description Peter J. Holzer 2001-10-25 12:56:15 UTC
Description of Problem:

When a machine has virtual interfaces, the reply from portmap will
not come from the IP address to which the request was sent, but
from the IP address of the "base interface".

If there is a stateful firewall between the client and the server or
if the client is paranoid, the request will fail.


Version-Release number of selected component (if applicable):

portmap-4.0-19

How Reproducible:


Steps to Reproduce:
1. Use a machine (in this example wsrgeh) with at least one
   virtual IP address (here wsrcom)
2. start tcpdump 
3. on a different machine, invoke "showmount -e wsrcom"
4. Observe the packets

Actual Results:

14:26:27.968144 < titan.wsr.ac.at.55629 > wsrcom.wsr.ac.at.sunrpc: udp 56 (DF)
14:26:27.968486 > wsrgeh.wsr.ac.at.sunrpc > titan.wsr.ac.at.55629: udp 28


Expected Results:

14:26:27.968144 < titan.wsr.ac.at.55629 > wsrcom.wsr.ac.at.sunrpc: udp 56 (DF)
14:26:27.968486 > wsrcom.wsr.ac.at.sunrpc > titan.wsr.ac.at.55629: udp 28



Additional Information:
	

In my testcase titan and wsrcom/wsrgeh are actually in different networks
separated by a firewall (iptables with ip_conntrack). I don't think this is
necessary to reproduce the problem, though.

Comment 1 Trond Eivind Glomsrxd 2001-10-30 17:11:59 UTC
Waiting for an extra IP from IS to check...

Comment 2 Trond Eivind Glomsrxd 2001-10-30 19:11:11 UTC
RHL 7.2 replies from queried interface.


Note You need to log in before you can comment on or make changes to this bug.