Skip to content
This repository was archived by the owner on May 5, 2025. It is now read-only.

port_data: Use a separate socket for reading and writing#7

Open
david-cermak wants to merge 1 commit intointel:masterfrom
david-cermak:bugfix/two_endpoint_port
Open

port_data: Use a separate socket for reading and writing#7
david-cermak wants to merge 1 commit intointel:masterfrom
david-cermak:bugfix/two_endpoint_port

Conversation

@david-cermak
Copy link

Hi!
I am proposing a small update to the ext port-data layer, especially useful if running the titan engine in a VM/docker where the external addresses/ports could be altered by NAT/forwarding...

  • The port code is ready to be used with two separate endpoints with different src_ip and dst_ip, but one common UDP socket was used for both of these endpoints. Added a separate fd for reading and writing, so enabling user having a separate source and destination IPs.
  • Fixed a minor bug in setting the src_ip as a parameter.

The port code is ready to be used with two separate endpoints with different src_ip and dst_ip, but one common UDP socket was used for both of these endpoints. Added a separate fd for reading and writing, so enabling user having a separate source and destination IPs.

Fixed a minor bug in setting the src_ip as a parameter.
@Yao-T
Copy link

Yao-T commented Jul 17, 2020

Hi David, I guess they'd like to test in loopback so the two ports and two ips are needed. It's a more general way. In the tcp2_check.ttcnpp we can check that.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants