Bug 53263 - PEER=0.0.0.0 doesn't work anymore
PEER=0.0.0.0 doesn't work anymore
Status: CLOSED WONTFIX
Product: Red Hat Linux
Classification: Retired
Component: cipe (Show other bugs)
7.3
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Nalin Dahyabhai
David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-09-05 15:08 EDT by Trond Eivind Glomsrxd
Modified: 2007-04-18 12:36 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-06-04 18:37:39 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Trond Eivind Glomsrxd 2001-09-05 15:08:22 EDT
cipe-1.4.5-6, RC2 (still a problem 2001-09-05)

Setting "PEER=0.0.0.0" in /etc/sysconfig/network-scripts/ifcfg-cipcb0
doesn't work - redhat-config-network creates a valid setup for two nodes
connecting when specifying both endpoints. Setting this to automatic, or
manually changing the PEER value to 0.0.0.0 on one of the endpoints does
not work.

These messages appear on the end you've specified 0.0.0.0:

Sep  5 15:16:27 halden kernel: cipcb0: cipe_recvmsg
Sep  5 15:16:27 halden kernel: cipcb0: cipe_recvmsg
Sep  5 15:16:28 halden ciped-cb[6003]: kxchg: recv: Connection refused
Sep  5 15:16:28 halden kernel: cipcb0: cipe_recvmsg

Nothing on the remote end.
Comment 1 Trond Eivind Glomsrxd 2001-10-30 12:09:30 EST
This was shipped broken. Any progress?
Comment 2 Daniel Roesen 2005-06-04 18:37:39 EDT
cipe is gone from RHEL and Fedora... Dead horse.

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