New answers tagged

0

You should do tcpdump on your client and server to figure out where the protocol is going wrong. In passive mode, the server opens a connection on some random port and the client connects to that for data transfers. A lot can go wrong, with NAT, with security and with firewalling. You need a packet-inspecting firewall to selectively open the port for the ...


2

This could be an issue with ARP not being able to resolve the MAC address of your Pi Zero W. Each host maintains an ARP cache mapping IP address to MAC address for connected LAN networks. When a host needs to connect to some LAN-connected address (say 192.168.1.1), it will first send an ARP who-has request (tcpdump output): # tcpdump -n -i wlan0 arp ... 18:...


0

Thank you for your answers. I never managed to properly get dhcpcd and wpasupplicant to work but I noticed that wpa2-enterprise networks works well with the ubuntu + mate environment supplied on the raspberry pi website. It looked like it was using network manager so what I did was go back to raspbian lite and run: sudo apt install network-manager network-...


0

According to: This post! dated: 2019-11-27 13:23 It appears that pi 4, until an update is released, will have wifi connecting problems on higher resolutions. you need to bootup your pi at lower resolutions (for me it worked at 640 * 400). After booting you can switch to high resolution!. I tried other resolutions too but for me 640 * 400 only works!


0

Assuming this is your Pi: root@pitest:~# ifconfig -a eth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 ether b8:27:eb:92:87:21 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 ...


0

I assume you have installed Raspberry Pi Os Buster. If it's not buster, first download it from https://www.raspberrypi.org/downloads/ and try again. Buster uses dhcpcd to enable detected WiFi interfaces. In particular, when a WiFi interface is found, dhcpcd will launch: wpa_supplicant -B -c/etc/wpa_supplicant/wpa_supplicant.conf -iwlan0 -Dnl80211,wext This ...


1

Assuming you are running the standard Raspbian Operating System then you can use VNC to access the Pi without Port Forwarding. Set up the Pi Enable VNC Create an account at RealVNC free of charge - you need a real email address On the VNC web site create a team On the Pi log in to VNC using the icon at the top right of the screen You can now connect to the ...


1

open /etc/dhcpcd.conf make sure the option section looks like this (notice adding , routers and commenting the next line about classless_static_routers): # A list of options to request from the DHCP server. option domain_name_servers, domain_name, domain_search, host_name, routers # option classless_static_routes reboot and enjoy, tested on a pi 3b with ...


0

Contrary to other questions I would say this requires special care and is by no means "very simple". Set up the pi as Access Point to let other devices (smartphones, mostly) access it is something I already consider nontrivial but let's just assume you'll execute what suggested in the linked answers. What you get is a WiFi bubble working "in ...


1

AFAIK there is no GUI tool, but it can easily be done by editing a couple of files. See Use different wpa_supplicant files in How to set up networking/WiFi


2

The conventional solution is to set the Pi as an Access Point, which gives clients access to services on the Pi. There are many ways of doing this. The Foundation tutorial Setting up a Raspberry Pi as a routed wireless access point has step by step instructions. If you just want an Access Point without internet access stop before Set up the network router


4

I would look to use something like Pirate Box (Wiki note here) despite it closing down at the end of this year as the core base has been stable and runs well on the Pi. Other packages are Freedom Box or Library Box You may also like to offer Wikipedia using Kiwix (also shares web sites) and details on portable Wikipedia is here Obviously be careful over ...


3

It is very simple to create a stand alone access point with a Raspberry Pi without internet connection. So all devices supporting WiFi can connect to it and share its data. You can use the RasPi to store data and/or run useful server like a web server or a NAS. You are free to install what you want to have available on the local network. For a simple setup a ...


0

It could make sense to use the Raspberry Pi if you develop for the Raspberry Pi(arm-architecture). But I guess you like to develop an application which should run on a x86 and or x64(x86-64) system. The problem is if you split the work (let the Pi generate some compiled object files (.o)), then there is still the problem that your Pi has to emulate the 32/64 ...


0

This page ranks quite highly in search results for people looking for networking help on Raspberry Pi. Unfortunately, the steps detailed here are out-of-date as of Feb 2020. At that point in time, to get Network Manager handling wifi on current Pi OS: sudo apt update sudo apt install network-manager network-manager-gnome Check /etc/network/interfaces - it ...


1

I was able to find an answer, I don't know if it is the right one for the application, but it worked. import subprocess cmd_permission="sudo chmod 777 /etc/wpa_supplicant/wpa_supplicant.conf" subprocess.run(cmd_permission, shell=True) cmd="sudo echo "network={ssid="rede" psk="pass" key+mgmt=WPA-PSK}" >> /...


2

Your problem is well known as dynamic failover and supported by Linux with its bonding driver. It will switch to the next connection as long as it is connected. The first step is to bring up all connections. I prefer to use systemd-networkd so Use systemd-networkd for general networking. You will find examples in section ♦ Create interface file for a wired ...


0

I had this exact same problem, and I diagnosed it. In short, the problem is your choice of WiFi adapter. The RTL8188EUS / r8188eu does not work properly with out of the box software configurations. This is evident in your log messages: May 3 00:04:05 raspberrypi dhcpcd[306]: eth0: waiting for carrier May 3 00:04:05 raspberrypi kernel: [ 11.679881] ...


2

I haven't used Ubuntu so far, so I cannot say anything about it. But with the Raspberry Pi OS, you also used, you should not use /etc/network/interfaces anymore, because it is deprecated on RaspiOS as noted in the interfaces file. It seems you only want to configure a simple router. I prefer to use systemd-networkd. You will find some examples to Use ...


0

If I understand your rather vague Question you are asking about the allocation of names to Network Interfaces. You should use Predictable Network Interface Names which have been used in other distributions for some time. These are designed for multiple network interfaces to eliminate the enumeration race condition. There is an option in raspi-config to ...


2

After troubleshooting for a while I realised that the problem was on the client-side, i.e. on the computer from which I tried to access the pie. Still not sure what the actual issue was but a simple reboot of the computer solved the issue.


0

If you're using continuous recording just set a specific length for the video. Motioneyeos gives you the option (in seconds if i remember rightly) to continuously record but start a new file every x seconds. For my setup I use continuous recording with a 300 second time limit which splits the recording into 5 minute clips.


1

Try this first: arp -a | grep -E --ignore-case 'b8:27:eb|dc:a6:32' The two hex strings (b8:27:eb|dc:a6:32) in this command reflect the two OUI values used by "The Foundation" for production of all RPi devices - through RPi ver 4B as of this writing. If your RPi isn't in your arp cache this command won't yield anything useful. If that's the case, ...


3

I have not changed anything (as far as I recall...) on the router or on the Pi. You have done a very essential modification. You set a static ip for the ethernet in your router. This breaks the computer based configuration of your network, done by your router, in particular you are also using docker containers. Doing this is not a task to simplify things. ...


0

If time, date is not correctly set, the DNS resolving is not working. To setup time, date and timezone do: Check time, date and timezone timedatectl status Chose you're timezone: timedatectl list-timezones Disable ntp sudo timedatectl set-ntp false Set correct timezone, example: Buenos Aires sudo timedatectl set-timezone "America/Argentina/...


1

I don't know why but this worked for me! This method is quite strange though I don't take guarantee that it will work in all situations, it's just that it worked for me. I urgently needed the internet connection on pi 4b so what I did was I connected a usb wifi adapter I had lying around. It took some time for pi to recognize it and after a quick reboot the ...


Top 50 recent answers are included