How to configure packet forwarder to direct packets to a computer via ethernet?

[Stephen Horn]

I need to configure the Packet Forwarder to send all the packets to a bridge which I have installed on a computer. The gateway is connected to the computer via ethernet. The packets will be received by a program — a gateway bridge — on the computer.

Is this possible? How would I go about it?

Network Interfaces Configuration shows,

Name eth0
Direction LAN
Type ETHER
IP Mode --
IP Address -- 
Bridge br0

Name br0
Direction LAN IPv4
Type BRIDGE
IP Mode Static
IP Address  192.168.2.1/24
Bridge br0

The Packet Forwarded is configured manually with a global_conf.json , a portion which is shown below. This will likely need to be changed per your advice.

"gateway_conf": {
		"server_address": "192.168.2.1",
		"serv_port_up":  1700,
		"serv_port_down": 1700,
		"keepalive_interval": 10,
		"stat_interval": 20,
		"push_timeout_ms": 100,
		"forward_crc_valid": true,
		"forward_crc_error": true,
		"forward_crc_disabled": false,
                "autoquit_threshold": 60,
                "fake_gps": true,
        "ref_latitude" : 99.1345990,
        "ref_longitude":-99.9357860,
        "ref_altitude" : 18

	}

[Jason Reiss]

Of course it is possible, this is the function of the packet forwarder.

What is the PC OS?
What is the PC IP address? This will be set as server_address.
Are the UDP ports opened and accessible on the 192.168.2.x network?
Are you also wanting to connect the PC to the Internet over Ethernet?

[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
   
   

[Jason Reiss]

I see you have opened a support case regarding installation of the bridge directly on the gateway. I suggest choosing one configuration setup and working toward that. The support team will be able to answer your questions.

https://www.chirpstack.io/gateway-bridge/
https://www.chirpstack.io/gateway-bridge/gateway/multitech/

The Chirpstack forum will also be a good resource.
https://forum.chirpstack.io/

https://forum.chirpstack.io/t/multitech-conduit-setup-assistance/6877

[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 1 year, 8 months ago by Stephen Horn.

[Jason Reiss]

The Gateway can also be a router and have a connection to the Internet over cellular. So I cannot rule out either scenario in a realistic deployment.

If the Gateway is Ethernet only then an connection to an external router providing Internet access is one popular network configuration.

[Author]

Posts