I understand this is a long post to get into, but I would like to provide as much information as possible to the awesome people that help me.
I have two devices that are connected via an Ethernet Connection. Let's call them Host and Client.
I would like to make the host and client connection wireless, but I do not have access to the source code for the devices. Therefore, I am unable to change the IP addressing / network configuration that the devices have.
Through an Awesome program, Wireshark, I was able to plug each end into a raspberry pi and decode the packets being sent from each side. from my limited networking experience, I can at least see that this is what appears to be a standard 802.11 TCP/IP protocol.
Also, Upon inspection of the cable that connects the Host and Client devices, it appears to be a "4-wire twisted pair connection" Meaning that there are two sets of +/- wires as opposed to the newer and more modern Ethernet connections. Please see
https://en.wikipedia.org/wiki/Ethernet_ ... ingle-pair
for reference to the type of cable that I plan to replace.
My Idea is to plug the Host into a Raspberry Pi(AP Mode) and Plug the client into a Raspberry Pi(Normal Client Mode) and with Bridging, be able to make the Host and Client "Think" they are still connected via direct Ethernet connection.
For feasibility's sake, lets assume that the wireless connection can support the level of traffic between the two devices without any worry of a slow connection.
Here's the current setup I am using to try and achieve this.
Host Raspberry Pi Configuration: (Raspberry Pi 3B+)
- Guide for Setting up Pi as an Access Point / Bridgehttps://www.raspberrypi.org/documentati ... s-point.md
- I Have followed the Guide In order to setup the Host Pi as an Access Point that has a bridges wlan0 to Eth0
- In this configuration, I can ping the Host device from the Host Raspberry Pi
- I have tested this configuration with and without the iptable entries. But I think I should not use the iptable entries as they only provide single direction communication? Versus the bridge allowing dual direction?
Client Raspberry Pi Configuration: (Raspberry Pi 3B)
- From the guide above, I have tried just setting up the bridge between wlan0 and eth0 as well as just statically assigning IP addresses.
- In these configurations, I can ping the Client Device from the client raspberry pi
My problem is that when I connect the Client Raspberry Pi to the Host Raspberry Pi's Access Point, I cannot ping one Raspberry Pi from the other, and subsequently, I cannot ping one device from another.
I am not understanding why In this configuration, Even though the Client Raspberry Pi shows to be associated with the Host raspberry Pi's Access Point, I cannot ping One from the other.
My Main problem now is that the Raspberry Pi's appear to be connected, but they will not ping each other.
Please see diagram below: Using the
Code: Select all
Code: Select all