New answers tagged

0

I think your issue is having more than one static router defined in /etc/dhcpcd.conf. I got it working by following https://www.sbprojects.net/projects/raspberrypi/vlan.php sudo apt-get install vlan Then sudo nano /etc/network/interfaces.d/vlans auto eth0.2 iface eth0.2 inet manual vlan-raw-device eth0 Then nano /etc/dhcpcd.conf and add interface eth0....


1

I solved my problem first by installing dhcpcd by running # apt-get install dhcpcd dhcpcd-gtk and then by uninstalling wicd by using # apt purge wicd, then # apt autoremove. Now if I unplug ethernet and reconnect it, it reconnects automatically.


1

It seems OMV completely occupies the network setup with its own settings and destroy the default Raspbian networking with dhcpcd. OMV modifies /etc/network/interfaces and claims to use systemd-networkd for network setups. Both systems are not used by Raspbian so I'm afraid you are without luck to use OMV with Raspbian if you do not find instructions from OMV ...


0

Try adding id_str to the network definition: network={ ssid="mywifi1" psk="psswd" key_mgmt=WPA-PSK id_str = "wlan1" } network={ ssid="mywifi2" psk="passwd" key_mgmt=WPA-PSK id_str = "wlan2" }


-1

Under Buster, you will need to set in raspi-config under 4 Localisation Options the Wifi country I4 Change Wi-fi Country otherwise, the Wifi will be disabled by rfkill.


0

You could also set up the USB port for networking if you have a Mac or PC you can use - that would give you access via SSH to set up the Wifi using raspi-config. Many tutorials on the net - e.g. one from a random Google


1

Everything seems to to be all right. The only possibility I see so far is to login to the RasPi and analyze what's wrong with the WiFi connection. So you should purchase a keyboard/mouse. You can also use a simple USB cable to connect the RasPi to your Linux computer and use the OTG gadget connection. Then you can ssh into the raspi. You may also consider to ...


1

You can use iptables to mangle the destination ip address. For example you can use the ip address 192.168.123.1 to address the DSLR and use routing to get connected to this ip address from your local area network 192.168.1.0/24. Of course this will not reach the DSLR because it has the ip address 192.168.1.1. But then you can use iptables with destination ...


0

There is an article here https://forum.heliconsoft.com/viewtopic.php?t=8991 that suggests you can change the IP address on your D7200 to another subnet e.g. 192.168.2.1


2

A few thoughts: Is you SSID hidden? If so, add scan_ssid=1 one a new line just after the SSID line Make sure the file has only line feeds at the end - no carriage returns You may have a keyboard / language issue. From memory the default until reset is UK English and any other characters used to generate the SSID or pass phrase can give issues. Spaces ...


0

Same thing for me. My PC was on 5 GHz band, Pi on 2.4 GHz band of router. Moved PC to 2.4 GHz, now I can Putty and CMD Ping to Pi ip.


1

I don't know your switch but it must have an interface for manageing it, sometimes with an extra serial connection, but mostly with a connection through any of its ethernet ports. You should always find a text console on the management connection but most modern switches also provide a http interface that you can use with an internet browser. With the RasPi ...


1

A problem that I've encountered multiple times is that I will set the password locally before changing the keyboard layout (which, for me, is English US). The default layout is UK, so when I enter my password it records the characters appropriate to the UK layout. When I then try to ssh into the rpi, the characters that are sent are from the US layout, and ...


1

You want to bundle two connections to increase bandwidth. In general bundling connections is done with bonding. This has different Network Bonding Modes. For your use case the default mode 0 (Round-robin) is appropriate. Unfortunately I haven't a setup available for mode 0. But for using mode 1, Active Backup, I have an example at Howto migrate from ...


0

To configure your network (wlan0) if you did remove dhcpcd, takes those few steps : edit the interfaces file sudo vi /etc/network/interfaces # /etc/network/interfaces -- configuration file for ifup(8), ifdown(8) # The loopback interface auto lo iface lo inet loopback # Wired or wireless interfaces iface eth0 inet manual allow-hotplug wlan0 iface ...


1

I cannot see much from the link you have referenced. From your description I assume you want to have an access point together with a WiFi client connection as uplink to another hotspot. I don't know anything about the Compute Module but because you wrote it may be software compatible to RPi 3B+ and 4B you can have a look at solutions for them. The error ...


1

As you said the two RasPis are connected by a network so you should be able to ping each other and also use ssh. I assume on the start-raspi, where the timer is connected, you have commands to start and stop the timer. For example I will name them mytimer start and mytimer stop. Starting the timer is no problem. You can stop it with the trigger on the stop-...


1

Fiber optics, 500 meter wiring... this sounds hard. Summary: Perhaps a simpler system would be to: time sync your two RPis 'starting line' RPi writes the start time to a file 'finish line' RPi writes the finish time to a file Afterwards, you collect the two times & subtract to get course timing. Some Details: You've not given us much detail in ...


1

In abstract : You have 2 Pi's: Starting-Pi and Finish-Pi. Starting-Pi: Has the trigger mech or button to start the timer and initiate the starting of the timing... Starting-Pi Sends Signal of 'START' to Finish-Pi, Finish-Pi receives Signal, determines its a 'START' signal, and begins it's timer. Once payload (runner or racer) reaches the Finish-Pi, you ...


1

what kind if "server" is this? my best guess is that the two USB ethernet adapters connected to the server are giving ip addresses on the server, not giving IP addresses to the pis. since there are 169.254 addresses, you don't have a dhcp server, so your server is giving itself an apipa address. and there are probably good reasons for a machine to not give ...


1

Removing a USB socket will achieve nothing: you won't be able to solder an RJ45 in its place anyway, and there's a chance you will damage your Raspberry while trying. If your project has such constraints that there's no way to fit an USB Ethernet adapter, look into other boards. For instance there's Orange Pi R1 which has two Ethernet ports + WiFi and is ...


2

An access point is defined by its ssid. If you want to have more than one ssid then you have to create additional access points, one for each ssid. The built-in WiFi device of a Raspberry Pi can only spawn one access point. You can verify it with: rpi ~$ iw phy0 info --- snip --- valid interface combinations: * #{ managed } <= 1, #{ P2P-device } ...


Top 50 recent answers are included