Tcp Ip Jobs

16 were found based on your criteria {{|number:0 }} were found based on your criteria

show all
  • Hourly ({{ jobTypeController.getFacetCount("0")|number:0}})
  • Fixed Price ({{ jobTypeController.getFacetCount("1")|number:0}})
Hourly - Intermediate ($$) - Est. Time: Less than 1 month, Less than 10 hrs/week - Posted
We have multiple black box applications that consume incoming UDP packets via a NIC and in response, publish outgoing TCP packets via the same (or a different NIC). These applications run on Windows and Linux servers, and they engage in tcp offloading to the NIC (kernel bypass). We're looking to build a tool/process that can help us accurately measure the wire-to-wire latency of these applications.
Skills: TCP/IP Kernel Linux System Administration Network Administration
Fixed-Price - Intermediate ($$) - Est. Budget: $4,000 - Posted
We manufacture an Ethernet product that sits between a computer and the network. We need an inexpensive device to test our product and verify that it is working properly and not impacting the connection speed or throughput for uploads and downloads. Ideally it is a single device with two network connections that connect to either side of our product and has a simple display attached that indicates the test results: - Connected (Yes/No) - Input Connection Speed (10mbps, 100mbps, 1000mbps) - Output Connection Speed (10mbps, 100mbps, 1000mbps) - Upload Speed - Download Speed - Test Result (Pass/Fail) Additional features that would be desirable are: - Simple enough to send to a customer so they can check filters in isolation from the customer’s network environment. - An advanced version that would add additional tests (eg packet loss, bit error rate, sync loss count, etc.) and then allow our technicians to add the product serial number and print a test report.
Skills: TCP/IP Arduino Raspberry Pi
Hourly - Entry Level ($) - Est. Time: More than 6 months, Less than 10 hrs/week - Posted
User must be good with networking which will include, Gateways, Routers, Switches, Access Points. User must be able to understand how to configure DNS, DHCP, Active Directory etc. You will also need to working during 10am-3pm east coast time zone within the USA.
Skills: TCP/IP Computer Networking DHCP DNS
Hourly - Intermediate ($$) - Est. Time: Less than 1 week, Less than 10 hrs/week - Posted
Your job is to extend netfiltersdk demo code with socks5 capability. nfsdk can be found at, download the demo build, there you will find CSharp demo files. TcpRedirectorCS is made to redirect traffic from localport to remote ip:port. If you look at attched picture you will see that it can currently handle SOCKS4 and HTTP and DIRECT. Your task is to extend this c# demonstration with SOCKS5 capability, i will provide you socks5 server where you can do your tests. TcpRedirector is a demonstration of NetfilterSDK capability. It takes tcp connections and proxies by HTTP,SOCKS to target. It is designed to tunnel stuff. Socks5 has many ready implementations on internet, you dont need to reinvent the wheel, i can also provide you something. Your task is not to rewrite socks5 protocoll, you will use something ready for that. I am working with TDI Driver, you would need to install required TDI driver in order to work with Sdk. Do not bid with copy&paste
Skills: TCP/IP C# Computer Networking
Fixed-Price - Expert ($$$) - Est. Budget: $400 - Posted
for an IOT project, i am looking for someone who understand TCP socket programming. Who can set up a TCP server in the cloud ( Azure preferably ) for receiving data from the IOT device ( fleet device) and converting into HTTP/MQTT. Alternatively when the data is retreived, it could be stored and sent to external cloud using REST APIs. I am attaching the spec of the device
Skills: TCP/IP Cloud Foundry REST
Fixed-Price - Entry Level ($) - Est. Budget: $1,000 - Posted
I am looking for someone who is able to implement CurveZMQ protocol in Erlang. This work will build on the existing Erlang implementation of ZMTP protocol found here: 1. It should implement the CurveZMQ 1.0 protocol. 2. Implementation will be tested against other bindings (i.e. libcurve) to make sure it functions correctly. 3. Code clarity is preferred over performance. 4. The implementation MUST support ALL socket types specified in the ZMTP 3.1 protocol. 5. The code MUST work on Windows and Linux (i.e. not use any platform-specific libraries). This is a large project, so please only consider it if you have free time. Will NOT work with an agency - only directly with developers. Relevant references: 1. CurveZMQ 1.0 protocol: 2. ZMTP 3.1 Protocol
Skills: TCP/IP Cryptography Erlang