Dec 21st, 2024, 6:13pm
Welcome, Guest. Please Login or Register.
Pages: 1  Reply Reply  Notify of replies Notify of replies  Print Print
   Author  Topic: Port forwarding does not work for multi-dnat chain  (Read 4416 times)
Port forwarding does not work for multi-dnat chain
on: Jul 20th, 2017, 10:17pm
Quote Quote  Modify Modify

Hi!
I am trying to get the software work to pass through USB device from physical Windows XP host into VM
 
The result is that there is a chain of "machines" involved
 
host 2 has a physical NIC passed through to it to make connection to USBNetServer (physical box)
 
[USB-recipient-VM]==[DNAT-to-host1]==>host1==[DNAT-to-host2]==>host 2==[DNAT-to-USBNetServer]==>USBNetServer
 
The server plain does not see the connection.
 
However, if I passthrough the NIC to host 1 and use host one as gateway it works
 
[USB-recipient-VM]===>host1 (as gateway)==[DNAT-to-USBNetServer]==>USBNetServer
 
Somehow, adding a +1 machine breaks it.
 
It is definitely not a latency thing (NICs in QubesOS are super fast)
 
Does Fabulatech's protocol take notice of source and destination IPs (which don't match the ones specified in case of a long DNAT chain)?
IP Logged
Re: Port forwarding does not work for multi-dnat c
Reply #1 on: Jul 21st, 2017, 2:11pm
Quote Quote  Modify Modify

Hi,
Thanks for the interest in our products and for your request.
Your question is related to the network routing.
You must have:
- route between server and client;
- available TCP port on both sides.
Last Edit: Jul 21st, 2017, 2:12pm by Sergey_Jarovski IP Logged

Sergey Jarovski

FabulaTech
===================
http://www.fabulatech.com
Re: Port forwarding does not work for multi-dnat c
Reply #2 on: Jul 23rd, 2017, 11:42am
Quote Quote  Modify Modify

Hi! Thanks for prompt reply!
 
I do seem to have both route and port, as indicated by:
 
pings going through without issue
 
the network client seeing the remote device and connecting to it.
 
HOWEVER, in the "long route" scenario, connectivity issues arise as if packets are being partially lost or something
 
Symptoms:
If I share a printer in the "long route" scenario, printer is seen by client and can be connected, but about 2-3 pages in, it resets and reports being offline (waiting for device message in client)
 
In "short route" scenario no such problem exists and client connects / prints flawlessly
IP Logged
Re: Port forwarding does not work for multi-dnat c
Reply #3 on: Jul 24th, 2017, 8:33am
Quote Quote  Modify Modify

Hi again,
Please let me know the value of the network latency in both cases ("long/short route" scenario).
IP Logged

Sergey Jarovski

FabulaTech
===================
http://www.fabulatech.com
Re: Port forwarding does not work for multi-dnat c
Reply #4 on: Jul 24th, 2017, 9:35am
Quote Quote  Modify Modify

ping time  < 50 ms in "short" route
 
ping time < 65 ms on "long" route
IP Logged
Re: Port forwarding does not work for multi-dnat c
Reply #5 on: Jul 24th, 2017, 10:23am
Quote Quote  Modify Modify

Hi again,
 
We need to have the logs from both sides (server/client) for both situations:
1) server log and client log for "long route" scenario;
2) server log and client log for "short route" scenario.
You can find the needed instructions here ("If there is a bug with the functionality of our software, do the following" section):
https://www.fabulatech.com/usb-over-network-server-help/troubleshooting-server.html
https://www.fabulatech.com/usb-over-network-client-help/troubleshooting-client.html
Zip these 4 logs and send to support@fabulatech.com.
IP Logged

Sergey Jarovski

FabulaTech
===================
http://www.fabulatech.com
Pages: 1  Reply Reply  Notify of replies Notify of replies  Print Print

Previous topic | Next topic
Online Talk to our
support team or
sales department.