Description of problem: The netdump server uses a hard coded remote port when replying to netdump clients: netdumpclient.c: netdump_client_send_reboot () [...] addr.sin_port = htons(NETDUMP_PORT); addr.sin_addr.s_addr = htonl(reboot->ip); netdump_client_send_request () [...] addr.sin_port = htons(NETDUMP_PORT); addr.sin_addr.s_addr = htonl(client->ip); This prevents the server communicating with clients that have defined a non-default LOCALPORT in /etc/sysconfig/netdump. Version-Release number of selected component (if applicable): 0.7.16-14.EL How reproducible: 100% Steps to Reproduce: 1. Configure a netdump client with LOCALPORT!=6666 2. Force a crash on the client Actual results: Netdump server replies to port 6666, netdump handshake fails Expected results: Netdump server replies to the client's LOCALPORT Additional info:
Created attachment 311416 [details] use the client's local port when replying
fixed in -21.el5, thanks!
Cloned for el5 EPEL as bug 455265
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2009-0486.html