Bug 81239
| Summary: | cipe interface preventing route from going into kernel | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Ted Kaczmarek <tedkaz> |
| Component: | cipe | Assignee: | Nalin Dahyabhai <nalin> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | David Lawrence <dkl> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 8.0 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | athlon | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2003-02-24 02:20:00 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
*** Bug 81241 has been marked as a duplicate of this bug. *** This problem does not occur with 2.4.18-24.8.0, no point in leaving this open. |
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: Always Steps to Reproduce: 1.Bring up cipe inteface on HOST A with ip of 192.168.200.1 and HOST B peer of 192.168.200.2 2.Have bgp peer HOST A send 192.168.0.0/16 route to HOST B 3.Confirm route in bgp table, not in kernel routing table Actual Results: Route of 192.168.0.0/16 is not put in kernel routing table. Expected Results: Route of 192.168.0.0/16 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 issue. Will attach a diagram as well.