Opened 4 years ago
Closed 3 years ago
#1267 closed Bug / Defect (worksforme)
Multicast error
| Reported by: | ulfper | Owned by: | tct |
|---|---|---|---|
| Priority: | major | Milestone: | release 2.4.11 |
| Component: | Networking | Version: | OpenVPN 2.4.8 (Community Ed) |
| Severity: | Not set (select this one, unless your'e a OpenVPN developer) | Keywords: | multicast Windows TAP |
| Cc: |
Description
We have come upon a strange multicast behaviour. We run OpenVPN on Windows 7 and use the TAP setting. When a OpenVPN server sends a multicast packet over TAP it seems that only one client gets a correct multicast packet (the same as on the server). The rest of the clients get a corrupted first octet for the destination MAC address (00 is replaced by FB).
This have been observered on OpenVPN 2.4.3, OpenVPN 2.4.7 and OpenVPN 2.4.8. The multicast packets are still delivered on OpenVPN 2.4.3 and OpenVPN 2.4.7, but not on OpenVPN 2.4.8. The packets will also be delivered on OpenVPN 2.4.8 with the help of WireShark? running in promiscuous mode on the clients.
Change History (4)
comment:1 Changed 3 years ago by
comment:2 Changed 3 years ago by
| Milestone: | release 2.4.8 → release 2.4.11 |
|---|
Fixing the milestone from "the release that was observed" to "the release that this might get fixed-in".
comment:3 Changed 3 years ago by
| Owner: | set to tct |
|---|---|
| Status: | new → accepted |
comment:4 Changed 3 years ago by
| Resolution: | → worksforme |
|---|---|
| Status: | accepted → closed |
No reply - Closed
Could you provide some more details so this can be investigated.
Please see this post for an example:
https://forums.openvpn.net/viewtopic.php?f=30&t=22603#p68963
Also, a packet capture showing the error.