Same-subnet traffic is forwarded to the default gateway and directly connected routes are ignored
Bug #1794371 reported by
Dmitrii Shcherbakov
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| charm-policy-routing |
Fix Released
|
Undecided
|
Dmitrii Shcherbakov | ||
Bug Description
Communication within the same subnet is affected by the ip rule added by the charm because directly connected routes in the main routing table are not present in the secondary routing table. As a result even same-subnet (same broadcast domain) traffic is forwarded to the default gateway.
Related branches
~dmitriis/charm-policy-routing:1794371-fix-direct-routes
Merged
into
~canonical-bootstack/charm-policy-routing:master
at
revision 1d54a531a7df5445b9b30e9ee13295f0b3e4d0b9
- Nicolas Pochet (community): Approve
- Drew Freiberger: Pending requested
- Alvaro Uria: Pending requested
-
Diff: 14 lines (+2/-1)1 file modifiedtemplates/service.j2 (+2/-1)
| Changed in charm-policy-routing: | |
| status: | New → In Progress |
| assignee: | nobody → Dmitrii Shcherbakov (dmitriis) |
Revision history for this message
| Drew Freiberger (afreiberger) wrote | #1 |
| Changed in charm-policy-routing: | |
| status: | In Progress → Fix Released |
To post a comment you must log in.
Fix merged. released as cs:~canonical-