[Stephen Horn]

Hi Jason, Thank you for the response. A quick question about this before I proceed. I assume that this direct ether-to-ether connection is not viable for this network scenario. Instead I should have this physical scenario,

W:
[Gateway]<-----ethernet------>[computer]

C:
[Gateway]<---ethernet--->[router]<---ethernet--->[computer]

Method ‘W’ should be used only for purposes of configuration or to alter something through the dashboard. During normal operation of the packet forwarder in any realistic deployment, method ‘C’ should be used. Your thoughts?

• This reply was modified 2 years, 9 months ago by Stephen Horn.

[Stephen Horn]

{edit. I will get back to you after some testing.}

• This reply was modified 2 years, 9 months ago by Stephen Horn.

[Stephen Horn]

>>>What is the PC OS?
Windows 10 Pro 21H2 19044.1889

>>>What is the PC IP address? This will be set as server_address.
Not sure what you are asking since IP addresses are assigned on a device basis. Consult output at bottom.

>>> Are the UDP ports opened and accessible on the 192.168.2.x network?
There is a lease range. Port 1700 has been allowed through the firewall (inbound+outbound) over the entire lease range.
I can only provide the following to help.

This is copied from the dashboard.

Bridge(br0)
 MAC Address =  00:08:00:4B:DB:96
 IPv4 Address = 192.168.2.1
 Mask  = 255.255.255.0
 DHCP State = Enabled
 Lease Range = 192.168.2.100-192.168.2.254
 Interfaces =  eth0
Ethernet(eth0)
 Bridge= br0
 MAC Address =00:08:00:4B:DB:96
 
Current Leases
  Name = DESKTOP-(mycomputername)
  MAC address =50:9A:4C:51:FE:3B
  IP address = 192.168.2.104
  Expiration = 08/24/2022 17:08
Fixed Leases =  50:9A:4C:51:FE:3B , 192.168.2.104

A portion of netstat -an shows,

  TCP    192.168.2.104:139      0.0.0.0:0              LISTENING
  TCP    192.168.2.104:59327    192.168.2.1:443        TIME_WAIT
  TCP    192.168.2.104:59359    192.168.2.1:443        ESTABLISHED
  TCP    192.168.2.104:59360    192.168.2.1:443        ESTABLISHED
  TCP    192.168.2.104:59361    192.168.2.1:443        ESTABLISHED
  UDP    192.168.2.104:137      *:*
  UDP    192.168.2.104:138      *:*
  UDP    192.168.2.104:1900     *:*
  UDP    192.168.2.104:52514    *:*  
   

>>>Are you also wanting to connect the PC to the Internet over Ethernet?
No.

Ethernet adapter vEthernet (Default Switch):

   Connection-specific DNS Suffix  . :
   Link-local IPv6 Address . . . . . : fe80::294a:cb18:bcce:2f04%20
   IPv4 Address. . . . . . . . . . . : 172.19.64.1
   Subnet Mask . . . . . . . . . . . : 255.255.240.0
   Default Gateway . . . . . . . . . :

Ethernet adapter Ethernet:

   Connection-specific DNS Suffix  . :
   Link-local IPv6 Address . . . . . : fe80::64e1:2bdf:413b:7660%16
   IPv4 Address. . . . . . . . . . . : 192.168.2.104
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.2.1

Wireless LAN adapter Wi-Fi:

   Connection-specific DNS Suffix  . : aw4.AAA.BBB(edited) 
   Link-local IPv6 Address . . . . . : fe80::b470:a82f:7777:0000%10(edited)
   IPv4 Address. . . . . . . . . . . : 10.21.XXX.YYY(edited)
   Subnet Mask . . . . . . . . . . . : 255.255.0.0
   Default Gateway . . . . . . . . . : 10.21.0.1

Ethernet adapter vEthernet (nat):

   Connection-specific DNS Suffix  . :
   Link-local IPv6 Address . . . . . : fe80::6171:e43d:a6d3:ace2%54
   IPv4 Address. . . . . . . . . . . : 172.25.80.1
   Subnet Mask . . . . . . . . . . . : 255.255.240.0
   
   

[Author]

Posts