Page MenuHomeVyOS Platform
Create Task
Maniphest T20

duplicate address detection
Closed, InvalidPublicFEATURE REQUEST
Actions

Description

Hello,

it would be great to add duplicate address detection on commit

Details

Difficulty level
Easy (less than an hour)
Version
-
Is it a breaking change?
Unspecified (possibly destroys the router)
Issue type
Feature (new functionality)

Related Objects

Event Timeline

• kiv created this task.Mar 16 2016, 7:01 AM
syncer added projects: VyOS 1.1.x, VyOS 2.0.x.Mar 16 2016, 12:53 PM
syncer added a subscriber: VyOS 1.1.x.
EwaldvanGeffen added a subscriber: EwaldvanGeffen.EditedMar 19 2016, 2:40 PM

By duplicate address detection you mean (examples cases):

  1. eth0 address 192.168.1.1/24 and eth0 address 192.168.1.1/25
  2. as 1) but between eth0 and eth1
  3. duplicate IP address on connected segment of interface (you share an IP with another node)
  4. as 3) but with all connected-segments
  5. as 4) but additionally in connected routes unique
syncer triaged this task as Wishlist priority.Mar 31 2016, 7:40 PM
syncer added a subscriber: syncer.

@EwaldvanGeffen just wondering what will be the best option in terms of difficulty of implementation

syncer removed dmbaturin as the assignee of this task.Aug 21 2017, 1:09 AM
syncer changed the edit policy from "Public (No Login Required)" to "Custom Policy".
syncer edited projects, added VyOS 1.2 Crux; removed VyOS 2.0.x, VyOS 1.1.x.
syncer set Version to -.
syncer edited subscribers, added: Maintainers, dmbaturin; removed: syncer, VyOS 1.1.x.
syncer added subscribers: higebu, UnicronNL.

Moved this to 1.2

@UnicronNL @higebu @dmbaturin
Can we add easely such check (i think centos have it )

syncer assigned this task to c-po.Jun 10 2018, 3:28 AM
syncer updated the task description. (Show Details)
syncer edited subscribers, added: Active contributors; removed: UnicronNL, higebu, dmbaturin and 2 others.
syncer added a subscriber: c-po.

@c-po do you think it's something easy to implement?

c-po added a comment.Jun 10 2018, 8:56 AM

Hmm I'm wondering b/c I've seen a provider in germany (HETZNER) where they do NAT (not PAT) for their cloud customers. Every vServer has the same IP configuration with RFC1918 addresses and an outside router does the mapping. Implementing this would break such a szenario if it can't be disabled.

I see no "good" thing in this feature. A network admin should have a good address plan. What happens if VyOS is configured properly and someone on the segment assigns itself the same IP address as VyOS? Will VyOS complain, too?

syncer added a comment.Jun 10 2018, 12:03 PM

If you look on centos, it will not give you set ip (and up interface) with ip which exist on net
i agree that all should have address plan, but reality is a bitch

pasik added a subscriber: pasik.Oct 1 2018, 9:53 AM
syncer edited projects, added VyOS 1.3 Equuleus; removed VyOS 1.2 Crux.Oct 7 2018, 6:36 AM
syncer changed the subtype of this task from "Task" to "Feature Request".Oct 19 2018, 6:08 PM
c-po mentioned this in T1309: allow duplicate ip adresses on different interfaces.Mar 21 2019, 4:20 PM
c-po added a comment.EditedMar 21 2019, 5:22 PM

VyOS 1.2.0 currently has this enabled, closing.

image.png (466×724 px, 40 KB)

c-po closed this task as Invalid.Mar 21 2019, 5:22 PM
c-po moved this task from Need Triage to Finished on the VyOS 1.3 Equuleus board.
erkin set Is it a breaking change? to Unspecified (possibly destroys the router).Sep 1 2021, 10:56 AM
erkin set Issue type to Feature (new functionality).
dmbaturin edited projects, added VyOS 1.3 Equuleus (1.3.0-epa1); removed VyOS 1.3 Equuleus.Sep 10 2021, 5:54 AM