Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ability to auto calculate destination mac address when rewriting destination mutlicast IP addresses #563

Closed
ric9887 opened this issue Jun 10, 2019 · 1 comment · Fixed by #700

Comments

@ric9887
Copy link

ric9887 commented Jun 10, 2019

tcprewrite --enet-vlan=del -S 10.0.0.0/8:10.11.29.0/24 -D 239.126.24.0/24:239.254.24.0/24,239.192.136.0/24:239.64.136.0/24 -i ./trace.pcap -o ./trace-novlanid-changesrc-changedst.pcap

When changing the destination IP address of multicast group addresses, tcprewrite doesnt currently recalculate the destination mac address.
With careful choice of the new destination multicast IP address, I can use a group address which maps onto the same mac address which exists in the capture.
A feature which is able to recalculate the correct corresponding destination mac address for the multicast group would make this far more flexible, and allow any destination IP multicast group to be used without causing havoc to the network.

It is important when switching multicast traffic that the correct corresponding mac address is used in the packet header, as network switches snoop this data and make pseudo entries in their mac address tables for these addresses to avoid flooding packets to all switch ports.

I realise tcprewrite can make changes to mac addresses currently, but this is a laboious task if a range of destination multicast addresses are to be changed

A tcprewrite switch to perform a 'Force recalculation of multicast mac address' similar to the --fixcsum funtion would suffice I believe.

The transpostion of multicast IP addreeses to mac address is well detailed, an example of which is here.

http://www.dqnetworks.ie/toolsinfo.d/multicastaddressing.html

Im my scenario, I have captures of multicast video traffic which I wish to replay.
However, I am unable to replay them using the same destination multicast addresses as they will clash with live traffic - so it is nessessary to chnage the destination multicast group addresses.
This currently works using the example above, but unless I chose the correct corresponding multicast group which matches the mac address already in the captures, the traffic is flooded to the network (as the network switches snoop the packets, and make the wrong pseudo mac address tabel entries).

fklassen added a commit that referenced this issue Jan 31, 2022
@fklassen fklassen linked a pull request Jan 31, 2022 that will close this issue
fklassen added a commit that referenced this issue Jan 31, 2022
@fklassen
Copy link
Member

Feature implemented in PR #700

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants