So, I have Raspberry Pi B+. And compatible (I have checked, it worked) Wi-Fi module for RPi. I use Raspbian.
My task is build a router from RPi (with Wi-Fi access point).
But, one important detail there.
I don't need internet access on this setup.
This setup will only give us communication between Wi-Fi (1 or more) and Ethernet (1) clients.
For example, in this LAN:
192.168.1.1 - is RPi itself
192.168.1.10 - Ethernet client
192.168.1.15 - Wi-Fi client #1
192.168.1.20 - Wi-Fi client #2
...
How to build router on RPi, which works without internet by scheme described above?
Thank you for your help! If you have questions, feel free to ask, please.
Related
I installed a PPP (Point to Point Protocol) in my Raspberry pi in order to connect with another Linux based card using serial port (with USB-RS422 cable). The PPP is well installed and configured, so from the raspberry pi I can ping the Linux card, my goal is to access the Linux card through the raspberry pi, I active the port forwarding in my raspberry pi also I added a route in my PC (Windows based).
For information, my PC is under my company network, the raspberry is under an IoT device network managed also by my company. Please have a look at the below diagram to well understood the situation.
enter image description here
My Question is : Do you have any idea to how can I access the based Linux
Card through the raspberry pi? Should I use nftables for that? if yes how? any other suggestions?
To clarify more, I changed the design, which means I connect my raspberry pi to my pc using ethernet cable and tried to ping the based card through the raspberry pi, it works well, means that I could ping the based card from my pc. Please have a look at the below picture:
enter image description here
I have an Android tablet and A Raspberry Pi and I want to established a connection between them automatically when the tablet sends a request to the Pi.
I followed an Android application example here and start discovering any nearby devices. (https://www.youtube.com/watch?v=qnY97iBxp30)
At the same time i run sudo wpa_cli and p2p_find 20. The Android application detects the Pi, and I try to establish connection with the Pi which will display
<3>P2P-GO-NEG-REQUEST TABLET_MAC_ADDRESS dev_passwd_id=4
Normally I would just p2p_connect TABLET_MAC_ADDRESS pbc to successfully connect them together but I find it inefficient if I were to swap to another mobile device.
Are there any other ways to connect the tablet without writing the tablet mac address? For example connecting to that specific device ssid when they send a P2P-GO-NEG-REQUEST to the pi?
TL;DR Nope.
If we look at the OSI ISO 7 layer model for network communication we can see that the Media Access Control (MAC) address is vital for identifying which device is which within a wifi network.
You could try setting up a bluetooth connection or a token-ring, but I suspect that would be more effort than you are looking for.
With IPv6 your devices could use neighbour discovery to automate past the MAC entry to the Internet Protocol, and its possible to connect between devices using their link-local address (fe80::some:thing)
Wifi carries packets of data, that have addresses. By analogy, if I tell you which town I live in, but don't write my building address on the packet, you are going to have a hard time delivering it.
As far as I figured out, Raspberry pi 3 which runs DP 4.1 cannot get IP address from my switch. Other devices on switch like PC's running windows or Rasbian installed Rasberries can get IP address as it should and be able to communicate each other. I tested my pi with both WiFi and cable connected router and it was able to get IP address normally. So I'm nearly sure that there is no problem on my Ethernet cable, pi or switch.
As a last note, the switches is Cisco sg100d-05 and I cannot use a router instead of this switch.
Is there anything that I can do to join this closed network on switch?
I've been having problems with a project of mine. I had a raspberry pi connected to webcams but I found that this was too much load for the RPI. This is why I decided to purchase and use an IP camera. The only problem though, is that the IP camera does not get wifi reception where the it should be placed but I have a powerful Directional antenna which I can attach to the RPI. I want the RPI to route internet traffic from the camera plugged into ethernet, over the wifi. I'm not one hundred percent sure how to do this but so far I have giving the wifi priority over the Ethernet and set up a dhcp server so that the camera gets an ip address.
In my current setup, when I am hard-wired into the Raspberry pi, I can connect to the camera (on 192.168.2.10) but outside, I can only connect to the web server which is also running on on the RPI. I'm not sure if the port forwarding of the camera works but I want to be able to access the webserver on 192.168.1.117 (this works) and I want to see the camera on 192.168.1.117:10 (this does not work). To try to do this, I followed this tutorial but I cant seem to get any results after finishing it.
Any help is greatly appreciated! thanks.
You may want to try UV4L with the mjpegstream driver. It turns your IP camera into a (virtual) Video device available on your RPi. An example is here (in step 3 pass the URL of your IP camera stream).
I have a server running Debian 7. The eth0 interface is configured to use the on-board ethernet card. This is basically used to connect to the internet. As it happens, I had to connect this server to some PCs through a switch, obviously on a different series of IPs. for this, I installed an external NIC in the PCI slot but, strangely it didn't seen to work. The configurations were alright. I checked them more times than I can imagine. So, I disabled my eth0 interface and connected eth1 (external NIC) to the internet. If for the same settings, the on-board card worked, so should the external one. But, it didn't. When I tried to ping some servers like 8.8.8.8, it gives me Destination Host Unreachable and on termination shows, 0 packets "transmitted" and 0 packets received, which is baffling, to say the least. The PCI slot is working because I checked if the drivers were being recognised or not. The NIC itself is working (checked with another machine running Debian 6). Any help/sugesstions would be appreciated.
P.S The NIC in question is D-Link System DGE-530T Gigabit Ethernet Adapter (rev 11)
You need to check to see if the card is being listed in lspci or not. Second, is this a virtual machine?
I would also check to see if the BIOS is handling IRQ's in auto or are they specifically assigned.