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

Address collision issue #129

Open
chidambar2000 opened this issue May 9, 2024 · 3 comments
Open

Address collision issue #129

chidambar2000 opened this issue May 9, 2024 · 3 comments

Comments

@chidambar2000
Copy link

Hi @marten-seemann ,

I have configured tcp-cross-traffic to run over the network shaper between client and server, but it fails stating that

"[2Ksim | 2024-05-09T17:26:13.842535476Z Using scenario: tcp-cross-traffic --delay=15ms --bandwidth=10Mbps --queue=25
�[2Ksim | 2024-05-09T17:26:13.930512428Z msg="Ipv4AddressGeneratorImpl::Add(): Address Collision: 193.167.50.1", +0.000000000s -1 file=/ns3/src/internet/model/ipv4-address-generator.cc, line=384
�[2Ksim | 2024-05-09T17:26:13.930523054Z NS_FATAL, terminating"

which makes the server doesn't show up and the URL doesn't fetch anything.

I have used the already built traffic-shaper with scenario : tcp-cross-traffic keeping the image same i.e martenseemann/quic-network-simulator

@marten-seemann
Copy link
Collaborator

It seems to work on CI: https://interop.seemann.io/

@chidambar2000
Copy link
Author

Could you please pin-point the tcp-cross-traffic directory?
I can only see the simple p2p here

@Jazkiel
Copy link

Jazkiel commented Oct 16, 2024

Hi,

In the tcp-cross-traffic scenario, when using the QuicPointtoPointHelper::Install function 3 times, every time the base is set as 193.167.50.0, which is leading to address collision issues. Since the route is anyways via 193.167.0.0/16, I changed
the Base to different IP addresses based on each call and it works for me. Not sure how it works in the CI.

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

No branches or pull requests

3 participants