Bug 81239 - cipe interface preventing route from going into kernel
cipe interface preventing route from going into kernel
Product: Red Hat Linux
Classification: Retired
Component: cipe (Show other bugs)
athlon Linux
medium Severity medium
: ---
: ---
Assigned To: Nalin Dahyabhai
David Lawrence
: 81241 (view as bug list)
Depends On:
  Show dependency treegraph
Reported: 2003-01-06 18:34 EST by Ted Kaczmarek
Modified: 2007-04-18 12:49 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-02-23 21:20:00 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Ted Kaczmarek 2003-01-06 18:34:44 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3b) Gecko/20030104

Description of problem:
Route will not install if cipe interface ip is in same address space.

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

How reproducible:

Steps to Reproduce:
1.Bring up cipe inteface on HOST A with ip of and HOST B peer of
2.Have bgp peer HOST A send route to HOST B
3.Confirm route in bgp table, not in kernel routing table

Actual Results:  Route of is not put in kernel routing table.

Expected Results:  Route of is put into kernel routing table.

Additional info:

As a test instead of sending the /16 which overlaps the cipe interface, I sent
it as a /17, that route does get put into the kernel routing table. Wasn't sure
if this is kernel or cipe, but it is definelty cipe related. I even advertised
the same route from another peer (Router C)across the ethernet0 and saw the same

Will attach a diagram as well.
Comment 1 Ted Kaczmarek 2003-01-06 18:50:39 EST
*** Bug 81241 has been marked as a duplicate of this bug. ***
Comment 2 Ted Kaczmarek 2003-02-23 21:20:00 EST
This problem does not occur with 2.4.18-24.8.0, no point in leaving this open.

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