i have a RevPi connect + with 2 Ethernet interfaces
i need to connect eth0 (port A on the RevPi, DHCP) to a server where my application is running
and eth1 (port B on the RevPi, static ip address) to a local network connected to multiple barcode readers
my problem is when i connect both Ethernet simultaneously one of them is always ignored (eth1) ,
a socket error 113 is raised
and i can't even access with vnc with the eth1
however when i try to connect with only one of them the connection is established successfully so i assume it is not a hardware problem.
note: the 2 networks are independent and totally separated from one another
here's a diagram of what i need to do
using both ethernet ports of RevPi connect +
Re: using both ethernet ports of RevPi connect +
Hi, thank you for your information. Maybe you fix the blank lines from your initial post and also please check the sketch or picture that you wanted to provide.
Please post your network configuration. The fastes way is that you generate and post a sos report. Is takes 1 minute:
Have a look at the Knowledge Base article "RevolutionPi Copy Files" on how to copy files from your device.
Please post your network configuration. The fastes way is that you generate and post a sos report. Is takes 1 minute:
Code: Select all
sudo apt update
sudo apt install revpi-sos
revpi-sos
Re: using both ethernet ports of RevPi connect +
i solved this problem which was related to the static ip address i chose
i initially chose a static ip for port B to be 10.10.20.x/24
after looking for similar problem with raspberry pi i found out that "for security reasons, interfaces that are within a LAN naturally reject network packets that come from the public space" as i quote from the thread i found
when i changed it to 192.168.0.x/24 it worked as it should
i can now access the revpi from direct Ethernet connection over port B
and connect via the network linked with port A simultaneously
i initially chose a static ip for port B to be 10.10.20.x/24
after looking for similar problem with raspberry pi i found out that "for security reasons, interfaces that are within a LAN naturally reject network packets that come from the public space" as i quote from the thread i found
when i changed it to 192.168.0.x/24 it worked as it should
i can now access the revpi from direct Ethernet connection over port B
and connect via the network linked with port A simultaneously