[Bug 176671] [epair] MAC address for epair device not unique

2018-07-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=176671

Eugene Grosbein  changed:

   What|Removed |Added

   See Also||https://bugs.freebsd.org/bu
   ||gzilla/show_bug.cgi?id=2299
   ||57

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


[Bug 176671] [epair] MAC address for epair device not unique

2018-05-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=176671

Luca Pizzamiglio  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|In Progress |Closed

--- Comment #11 from Luca Pizzamiglio  ---


*** This bug has been marked as a duplicate of bug 184149 ***

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


[Bug 176671] [epair] MAC address for epair device not unique

2018-05-07 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=176671

--- Comment #10 from Kubilay Kocak  ---
If bug 184149 is a duplicate of this bug, please close it (marked duplicate of
this issue id) and CC hrs (current assignee on bug 184149) here.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


[Bug 176671] [epair] MAC address for epair device not unique

2018-05-07 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=176671

Kubilay Kocak  changed:

   What|Removed |Added

   See Also||https://reviews.freebsd.org
   ||/D1858,
   ||https://github.com/freebsd/
   ||freebsd/pull/92,
   ||https://bugs.freebsd.org/bu
   ||gzilla/show_bug.cgi?id=1841
   ||49
  Flags||mfc-stable10?,
   ||mfc-stable11?
   Keywords||needs-qa
 CC||i...@freebsd.org

--- Comment #9 from Kubilay Kocak  ---
CC original committer of base r314471

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


[Bug 176671] [epair] MAC address for epair device not unique

2018-05-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=176671

Luca Pizzamiglio  changed:

   What|Removed |Added

URL||https://reviews.freebsd.org
   ||/D15329

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


[Bug 176671] [epair] MAC address for epair device not unique

2018-05-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=176671

Luca Pizzamiglio  changed:

   What|Removed |Added

 CC||pizza...@freebsd.org

--- Comment #8 from Luca Pizzamiglio  ---
Created attachment 193115
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=193115&action=edit
Another fix

This patch fix the issue, reusing the epair a if_index also for epair b.

Moreover, I've added hostid bits in the MAC to avoid that multiple servers that
shares the same configuration (failover), will have the same epair MAC address,
as pointed out by Olivier.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


[Bug 176671] [epair] MAC address for epair device not unique

2018-02-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=176671

O. Hartmann  changed:

   What|Removed |Added

 CC||ohartm...@walstatt.org

--- Comment #7 from O. Hartmann  ---
I have faced this problem on recent CURRENT (FreeBSD 12.0-CURRENT #36 r329150:
Mon Feb 12 06:30:47 CET 2018 amd64, VIMAGE kernel). Creating a bunch of epairs
attached to bridges render the VIMAGE-based virtual network unusable as long as
the MAC addresses is not setup manually:

dmesg output, watch out the MAC=02:ce:d0:00:07:0a, which seems to occur
multiple times.

All bridges and epairs are created/destroyed/attached from /etc/jail.conf.

[...]
bridge0: Ethernet address: 02:09:e6:72:3b:00
bridge1: Ethernet address: 02:09:e6:72:3b:01
bridge2: Ethernet address: 02:09:e6:72:3b:02
epair4000a: Ethernet address: 02:ce:d0:00:07:0a
epair4000b: Ethernet address: 02:ce:d0:00:08:0b
epair4000a: link state changed to UP
epair4000b: link state changed to UP
epair4001a: Ethernet address: 02:ce:d0:00:09:0a
epair4001b: Ethernet address: 02:ce:d0:00:0a:0b
epair4001a: link state changed to UP
epair4001b: link state changed to UP
epair4002a: Ethernet address: 02:ce:d0:00:0b:0a
epair4002b: Ethernet address: 02:ce:d0:00:0c:0b
epair4002a: link state changed to UP
epair4002b: link state changed to UP
epair4000b: promiscuous mode enabled
bridge0: link state changed to UP
epair4001b: promiscuous mode enabled
bridge1: link state changed to UP
bce1: promiscuous mode enabled
epair4002b: promiscuous mode enabled
bridge2: link state changed to UP
ng_ether_ifnet_arrival_event: can't re-name node epair4000a
ng_ether_ifnet_arrival_event: can't re-name node epair4001a
ng_ether_ifnet_arrival_event: can't re-name node epair4002a
epair4a: Ethernet address: 02:ce:d0:00:07:0a
epair4b: Ethernet address: 02:ce:d0:00:09:0b
epair4a: link state changed to UP
epair4b: link state changed to UP
epair4b: promiscuous mode enabled
ng_ether_ifnet_arrival_event: can't re-name node epair4a
epair2a: Ethernet address: 02:ce:d0:00:07:0a
epair2b: Ethernet address: 02:ce:d0:00:0b:0b
epair2a: link state changed to UP
epair2b: link state changed to UP
epair2b: promiscuous mode enabled
ng_ether_ifnet_arrival_event: can't re-name node epair2a
bridge0: state changed to forwarding on epair4000b
bridge1: state changed to forwarding on epair4001b
bridge2: state changed to forwarding on epair4002b
epair235a: Ethernet address: 02:ce:d0:00:07:0a
epair235b: Ethernet address: 02:ce:d0:00:0d:0b
epair235a: link state changed to UP
epair235b: link state changed to UP
epair235b: promiscuous mode enabled
ng_ether_ifnet_arrival_event: can't re-name node epair235a
epair237a: Ethernet address: 02:ce:d0:00:07:0a
epair237b: Ethernet address: 02:ce:d0:00:0e:0b
epair237a: link state changed to UP
epair237b: link state changed to UP
epair237b: promiscuous mode enabled
ng_ether_ifnet_arrival_event: can't re-name node epair237a
epair251a: Ethernet address: 02:ce:d0:00:07:0a
epair251b: Ethernet address: 02:ce:d0:00:0f:0b
epair251a: link state changed to UP
epair251b: link state changed to UP
epair251b: promiscuous mode enabled
ng_ether_ifnet_arrival_event: can't re-name node epair251a
epair238a: Ethernet address: 02:ce:d0:00:07:0a
epair238b: Ethernet address: 02:ce:d0:00:10:0b
epair238a: link state changed to UP
epair238b: link state changed to UP
epair238b: promiscuous mode enabled
ng_ether_ifnet_arrival_event: can't re-name node epair238a
epair10238a: Ethernet address: 02:ce:d0:00:07:0a
epair10238b: Ethernet address: 02:ce:d0:00:11:0b
epair10238a: link state changed to UP
epair10238b: link state changed to UP
epair10238b: promiscuous mode enabled
ng_ether_ifnet_arrival_event: can't re-name node epair10238a
epair10250a: Ethernet address: 02:ce:d0:00:07:0a
epair10250b: Ethernet address: 02:ce:d0:00:12:0b
epair10250a: link state changed to UP
epair10250b: link state changed to UP
epair10250b: promiscuous mode enabled
ng_ether_ifnet_arrival_event: can't re-name node epair10250a
epair20128a: Ethernet address: 02:ce:d0:00:07:0a
epair20128b: Ethernet address: 02:ce:d0:00:13:0b
epair20128a: link state changed to UP
epair20128b: link state changed to UP
epair20128b: promiscuous mode enabled
ng_ether_ifnet_arrival_event: can't re-name node epair20128a
epair20129a: Ethernet address: 02:ce:d0:00:07:0a
epair20129b: Ethernet address: 02:ce:d0:00:14:0b
epair20129a: link state changed to UP
epair20129b: link state changed to UP
epair20129b: promiscuous mode enabled

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


[Bug 176671] [epair] MAC address for epair device not unique

2017-07-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=176671

--- Comment #6 from Olivier Cochard  ---
I've reach to reproduce a setup when this localy-unique epair create conflict
on a LAN:

 ++   +---+
 | ServerA|   |serverB|
 |  bridge0 - em0 |- LAN -| em0 - bridge0 |
 ||   |   | | |
 |  epair1a   |   |   epair1a |
 |  epair1b   |   |   epair1b |
 ||   |   | | |
 |  vnetjail1 |   | vnetjail2 |
 ++   +---+

MAC addresses of epair1 are the same on both jail, then they can't communicate
each others:

[root@jail1]~# ifconfig epair1b ether
epair1b: flags=8943 metric 0
mtu 1500
options=8
ether 02:ff:70:00:0f:0b
hwaddr 02:ff:70:00:0f:0b


[root@jail2]~# ifconfig epair1b ether
epair1b: flags=8943 metric 0
mtu 1500
options=8
ether 02:ff:70:00:0f:0b
hwaddr 02:ff:70:00:0f:0b

We could perhaps generate a MAC field "eaddr[1]" (in if_epair.c) from the
hostid  for mitigate this conflict (like the net/if_bridge.c code) ?
But if we take code from if_bridge, we should create a common function for
being available to if_bridge and if_epair.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


[Bug 176671] [epair] MAC address for epair device not unique

2017-07-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=176671

--- Comment #5 from Olivier Cochard  ---
Oops, it was reverted later:

https://svnweb.freebsd.org/base?view=revision&revision=314480

But I've generated a bunch of epair interface (on -head, 11-stable), and didn't
reach to have MAC conflict. if_index is used for the MAC generation, and it
can't have same if_index.

...
epair253a: Ethernet address: 02:ff:b0:02:05:0a
epair253b: Ethernet address: 02:ff:00:02:06:0b
epair254a: Ethernet address: 02:ff:b0:02:07:0a
epair254b: Ethernet address: 02:ff:00:02:08:0b
epair255a: Ethernet address: 02:ff:b0:02:09:0a
epair255b: Ethernet address: 02:ff:00:02:0a:0b
epair256a: Ethernet address: 02:ff:b0:02:0b:0a
epair256b: Ethernet address: 02:ff:00:02:0c:0b
epair257a: Ethernet address: 02:ff:b0:02:0d:0a
epair257b: Ethernet address: 02:ff:00:02:0e:0b
epair258a: Ethernet address: 02:ff:b0:02:0f:0a
...
epair594a: Ethernet address: 02:ff:b0:04:af:0a
epair594b: Ethernet address: 02:00:00:04:b0:0b
epair595a: Ethernet address: 02:ff:b0:04:b1:0a
epair595b: Ethernet address: 02:ff:00:04:b2:0b
epair596a: Ethernet address: 02:ff:b0:04:b3:0a
epair596b: Ethernet address: 02:00:00:04:b4:0b
epair597a: Ethernet address: 02:ff:b0:04:b5:0a
epair597b: Ethernet address: 02:ff:00:04:b6:0b
epair598a: Ethernet address: 02:ff:b0:04:b7:0a
epair598b: Ethernet address: 02:ff:00:04:b8:0b
epair599a: Ethernet address: 02:ff:b0:04:b9:0a
epair599b: Ethernet address: 02:ff:00:04:ba:0b
...
epair896a: Ethernet address: 02:ff:b0:07:0b:0a
epair896b: Ethernet address: 02:ff:00:07:0c:0b
epair897a: Ethernet address: 02:ff:b0:07:0d:0a
epair897b: Ethernet address: 02:ff:00:07:0e:0b
epair898a: Ethernet address: 02:ff:b0:07:0f:0a
epair898b: Ethernet address: 02:ff:00:07:10:0b
epair899a: Ethernet address: 02:ff:b0:07:11:0a
epair899b: Ethernet address: 02:ff:00:07:12:0b

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


[Bug 176671] [epair] MAC address for epair device not unique

2017-07-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=176671

Olivier Cochard  changed:

   What|Removed |Added

 CC||oliv...@freebsd.org

--- Comment #4 from Olivier Cochard  ---
I believe this PR can be closed, because a fix was committed here (Wed Aug 17
20:21:33 2016) :

https://svnweb.freebsd.org/base/head/sys/net/if_epair.c?r1=314471&r2=314470&pathrev=314471

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


[Bug 176671] [epair] MAC address for epair device not unique

2014-07-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=176671

Shuto.Imai  changed:

   What|Removed |Added

 CC||dev.shutin...@gmail.com

--- Comment #3 from Shuto.Imai  ---
About this problem, is there any progress?

Thankyou

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"