Wire client wire Server Wire server keeps sending reset

[Ayberk ORHON]

Hello I am having trouble with setting up and using the wire client-server feature of packetdrill. I had no problems running packetdrill in the local mode. I am setting up the server in the Silicom CPE. The client is in a virtual machine running ubuntu. The client and server do the normal syns and acks but when the script starts the server sends reset. The client sends syn but the server doesnt send syn ack back. Im having trouble making the server communicate with the client. My test script is one of packetdrills script. I am also getting a malformed packet.

client side:

command: sudo ./packetdrill  --wire_client --wire_server_ip=192.168.1.40 --wire_client_dev=ens33  --local_ip=10.0.0.1 --gateway_ip=10.0.0.5 --netmask_ip=255.255.255.0 --remote_ip=10.1.0.4 tests/linux/fast_retransmit/test1.pkt

network:

Server side :

command :sudo ./packetdrill --wire_server --wire_server_dev=enp4s0

network:

also when I run the server without server_dev(sudo ./packetdrill --wire_server)  command I get this error in the cleint side.

I would really appreciate your help. Thank you.

[Ayberk ORHON]

I forgot to show wireshark 

You can see there is a malformed packet and the cript im using is the sendfile simple.

[Neal Cardwell]

Thanks for the report.

It sounds like you are trying to get packetdrill to work in a scenario where the client is inside a virtualized environment, and the server is outside the virtualized environment, on the host. The packetdrill tool is not designed for that to work. You may be able to get that to work with enough coding and debugging. However, is there a reason to do that? 

Would it be possible to use one of the supported scenarios, like:

(a) packetdrill local mode, inside a VM or on a physical machine

(b) packetdrill remote mode, where both server and client are either (a) inside the same L2 virtualized network, or (b) inside the same L2 physical network

Can you help me understand your motivation for trying to get packetdrill to work in a scenario where the client is inside a virtualized environment, and the server is outside the virtualized environment?

best regards,
neal

--
You received this message because you are subscribed to the Google Groups "packetdrill" group.
To unsubscribe from this group and stop receiving emails from it, send an email to packetdrill...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/packetdrill/9ef59b95-d931-499e-abdd-3c80a6f6f1dbn%40googlegroups.com.

[Ayberk ORHON]

Thank you for replying. We wanted to run packetdrill on the CPE and had only a VM of Linux on hand. We will try with a primary Linux OS PC. Have a nice day. :)

[Ayberk ORHON]

Neal sorry I just wanna be clear and not misunderstood.I am using the virtual machine on the pc to use linux and work with packetdrill. The Pc is the client. The server is on a seperate device that runs on linux. They are both on the same LAN. In this situation packetdriller can not work, yes ? 

[Neal Cardwell]

If both packetdrill processes are on the same physical L2 LAN, then there is a chance that packetdrill wire client/server mode could work.

From your description of the symptoms, I'm not sure why it's not working. That output seems to indicate that perhaps the TCP control socket was established but then the server side unexpectedly closed the connection.  If you need to get that working then I'd suggest debugging both processes with gdb and dumping the packets for the traffic under test and the control channel with something like "tcpdump -XXX -s 1600 -i any -n port 8080 or port 8081".

I'm afraid I don't have time to offer more involvement than that. :-)

best regards,

neal

To view this discussion on the web visit https://groups.google.com/d/msgid/packetdrill/9bffc444-8a43-4f60-a908-b8026c36e31dn%40googlegroups.com.