It is giving you garbage for the netmask, I always see 255.255.255.0 for that one on my working addresses. Track down that setting origin and you will solve it.
root@buster-raspi:~# ifconfig -a
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.0.116 netmask 255.255.255.0 broadcast 192.168.0.255
I should confess and tell you that I use git for windows to access my pi, so git-bash gives me a minimal bash environment on Windows. You may prefer Putty or WSL etc. This method will work with Mac, Linux and WSL, and it answers the OPs question of "How do I".
Assign the pi a static ip address
use ~/.ssh/config to create your ssh "address ...
You asked five questions. This is usually not the optimal format for this site. But I see your problem and will give some information how I would solve it. I prefer to Use systemd-networkd for general networking because it can do many things out of the box.
I need some advice on selecting an OS. I have downloaded Raspbian (32 bit), Ubuntu 20.10 (64 bit) and ...
To add to what @Ingo said, they actually have a third OUI now: E4-5F-01
Not sure why that happened either, but I have hardware with a MAC with that OUI.
I'd have commented that, but don't have enough reputation.
To do this without constantly polling your network would require monitoring your power and then having your Pi send a message to your phone. Twilio offers an affordable service that allows you to send sms text messages programmatically and their API is easy to use. To monitor your power would require that you operate Pi off of a battery, and then have a ...
I know this is old. All you need to do is change the rkhunter.conf lines 593-600 to reflect location of egrep, fgrep, etc. Here is what it looks like.
This took me far too long to figure out, but in the end I found this guide which shows exactly how to get it working, worked first try for me on a Raspberry Pi CM3: Edimax EW-7811UN V2 driver installation.
To quickly find your kernel version, use the command uname -r. Getting it working does require an existing internet connection, I was using a USB-Ethernet ...
Open /etc/dhcp/dhclient.conf and input a line starting with supersede. This line makes sure that only the supplied list of values for domain-name-servers on it's right will be written inside /etc/resolv.conf when writing event happens.
supersede domain-name-servers 127.0.0.1, ::1;
Get some free web hosting somewhere have the Pi upload a file it creates with the date in time in it. Run a cron job at the interval desired use a program like rsync to upload the file. Check in your browser and the web page can use the file for its data. Displaying a message it is up at this date and time. A cron job run on that machine checking if the file ...
I know you already solved this, but just in case: if something more complicated must be done on network link events, one way to implement this is to write an udev rule with SUBSYSTEM=="net" and run a custom script from it.
There are a few other errors that happen prior to this but I'm not sure if they're relevant
They're actually an hour previous (dunno if you noticed this).
The bit after the hostname, if it isn't kernel, is a process name and PID (eg. bluetoothd. The kernel stuff there isn't an error except for the note about dhcpcd (which is something that is spit out ...
RaspiOS Buster (the official Raspberry Pi operating system based on Debian 10) uses dhcpcd to configure network interfaces, both eth0 and wlan0. The use of /etc/network/interfaces is obsolete and there is not a way to configure a static IP address alias into /etc/dhcpcd.conf. It is possible however to create an user defined hook script following the dhcpcd-...
Old bug coming back to get you, your country code is unset when that /sbin/crda is called which cause the network to fail when it runs.
Process '/sbin/crda' failed with exit code 255
Personally I would thought it fixed by now as the first ...
I have 8 networks in my wpa_supplicant.conf - some on different continents and I can move seamlessly between them.
There is no point in priority unless multiple networks are visible.
Your file looks OK but not sure if psk=NONE is affecting results.
I don't see why it does not work properly; if it does not find the first network it should look for the other. You might debug this by looking at wpa_supplicant's output -- I am not sure where it is by default or if wpa_supplicant has its own service by default on RpiOS/Raspbian (I use customized dhcpcd scripts to manage that and discard the defaults when I ...
Solved (a bit by magic) as stated in the edits of the questions. I retain that keeping the configuration temporary is a good think because it allows a clean rework on next attempt.
Here is a summary of my commands :
On the laptop/router :
ip addr add 169.254.187.69/16 dev enp2s0
iptables -t nat -A POSTROUTING -o wlo1 -j MASQUERADE
Not to forget editing /...
after plugging in the 4g dongle, run the below command and your dongle will be installed and now you must set up a new connection after the installation, sure this will help out who are all out there...
$ sudo apt update \
&& sudo apt install network-manager network-manager-gnome openvpn openvpn-systemd-resolved network-manager-openvpn network-...
I was able to resolve this issue by adding my region to the /etc/default/crda file.
# Set REGDOMAIN to a ISO/IEC 3166-1 alpha2 country code so that iw(8) may set
# the initial regulatory domain setting for IEEE 802.11 devices which operate
# on this system.
# Governments assert the right to regulate usage of radio spectrum within
# their respective ...
NTFS is slower on any Linux machine than a native Linux filesystem. I found slow transfer speeds when I added a 2 TB USB3 drive to my Raspberry Pi 4 to use it as a NAS. I backed up the data, formatted the drive as ext4 and replaced the data. I could now get 100 MB/S read and write. I have since added a 3 TB USB3 drive, with similar performance. I suggest ...
The Ethernet IS working at full speed.
That doesn't mean you will get anything like that from the file system which is limited by the CPU and transfer rate of the USB port.
NTFS performs poorly on the Pi (indeed on Linux). The driver runs in userspace.
Use ext4 which will be several times faster (and more reliable as it supports journaling).
Several references say that MACVLAN is good for ethernet interfaces but that with wireless interfaces an IPVLAN L2 should be used.
I will assume that answer for this question to rework the script and test.
You need to do NAT forwarding on your laptop it is not simply enough to connect the cable to it. You do not mention the OS on it so impossible to give directions on this part of it, you need to enable it regardless of OS. This allows it to pass the connection to your network where it should allow the Pi to connect and get a connection to get the IP and the ...
SSH has a really cool "jump host" option; basically, it allows you to jump through to another host on the network:
Connect to the target host by first making a ssh connection to the jump host described by destination and then establishing a TCP forwarding to the ultimate destination from there. Multiple jump hops may be ...
I just had the idea whether the problem is related to the Public vs Private categorization of your LAN Ethernet network within Windows: some features are configured differently for these. Mine for example, when used without a router on it, typically gets categorized as Public.
On Windows, open Powershell with administrator rights, and issue the following:
As it turns out, I merely misunderstood how IPv6's work. I'll reference the ServerFault question mentioned by Dirk: https://serverfault.com/questions/918472/why-is-a-128-ipv6-address-assigned-via-dhcpv6-in-ubuntu
Yes, this is the normal behaviour. DHCPv6 servers give out addresses (with the IA_NA option) but don't tell the client anything about ...
Option 1 - Using nohook wpa_supplicant
The /etc/dhcpcd.conf configuration file of dhcpcd can be edited to define which wireless interfaces need wpa_supplicant.
For each identified interface, dhcpcd executes all scripts (hooks) found in /lib/dhcpcd/dhcpcd-hooks in lexical order. One of the scripts is 10-wpa_supplicant, which starts wpa_supplicant. It can be ...
Starting with the question:
Is there a reason this process would work for eth0 but not wlan0?
There is a difference in how the eth0 interface treats packets compared to wlan0. A comment on a blog post poses a plausible explanation:
I read somewhere that wireless doesn't work because frames coming in are then found to have a 'wrong' mac address. The frames ...
This is an XY problem.
You have decided (for whatever reason) that you "need" multiple IP addresses for the same interface and are diving more deeply into that rabbit hole (mixing incompatible networking systems without understanding either).
It may be possible to achieve your primary goal, but first you have to clearly define exactly what you are ...
So it turns out it was a hardware issue rather than a software issue. Looking at my question again, I recalled that 2.4 GHz wireless connections are well known for dropping due to any kind of interference of other devices that give off the 2.4GHz noise frequency while 5GHz doesn't have that problem. One of the things I failed to mention earlier in the ...
I solved this by getting a lead over at the Pi Forums. See Ethernet Problems. It turns out my Ethernet is only running at 10/100. The Broadcom Chipset on the Pi4 doesn't support fallback from Gigabit to Fast Ethernet. As such I bought a USB 3.0 to Gigabit Ethernet Adapter TU3-ETG, which does support fallback, and is supported by the upstream linux kernel, ...
create a file in /etc/network/interfaces.d - lets call it eth0 - doesn't matter what the name is.
In this file add the following
iface eth0 inet manual
up ip link add link eth0 name eth01 address 02:00:00:00:00:01 type macvlan
up ip link add link eth0 name eth02 address 02:00:00:00:00:02 type macvlan
Now restart networking
sudo systemctl ...
You can check the name used by using service or systemctl
alexis@Oreo:~$ sudo systemctl status avahi-daemon
[sudo] password for alexis:
● avahi-daemon.service - Avahi mDNS/DNS-SD Stack
Loaded: loaded (/lib/systemd/system/avahi-daemon.service; enabled; vendor pre
Active: active (running) since Wed 2021-02-03 08:33:50 CET; 5h 50min ago
Main PID: 1692 (...
Here's how I would do it - for multiple IP's you'll be creating a file in /etc/network/interfaces.d
lets create /etc/network/interfaces.d/wlan0 - name doesn't matter really
iface wlan0 inet manual
up ip address add 192.168.1.100/24 dev wlan0 label wlan0:0
up ip address add 192.168.1.101/24 dev wlan0 label wlan0:1
Clearly, you would use the ...
The Wikipedia article on Link-local Address says that "RFC 3927, the Internet Engineering Task Force (IETF) has reserved the IPv4 address block 169.254.0.0/16 (169.254.0.0 – 169.254.255.255) for link-local addressing" so my issue is probably related to dhcp configuration, a separate issue from this post.
wicd runs dhclient with config file in /var/lib/wicd which gets copied there from /etc/wicd/dhclient.conf.template. The default config file contained the line: send host-name "$_HOSTNAME"; the comment says "# wicd will replace $_HOSTNAME in the following line with the appropriate hostname for this system". This didn't seem to be working ...
To answer your questions:
A. automatically connect to an available open wifi network?
wpa_supplicant will only connect to networks that are specified in /etc/wpa_supplicant/wpa_supplicant.conf. To connect to an open WiFi network you have to set this in wpa_supplicant.conf:
Then wpa_supplicant will automatically connect to the ...
If you just want to resolve a few LAN names locally (that is, on the Pi itself), just add those names to /etc/hosts, e.g.:
If you want to run an actual DNS server, you could start by trying out systemd-resolved, which can be configured by editing /etc/systemd/resolved.conf. Depending on your needs, this ...
Following up on the eventHandler comment that wlan0 should not be in the same NAT as eth0 did the following:
In /etc/dhcpcd.conf changed wlan0 from 0.3 to 1.1:
From the chat session, it seems you have overlooked the necessity to create the ssh file in the /boot partition of the SD card. This is done while the SD card is still mounted in your PC (Mac, Windows, Linux). /boot is formatted as a FAT32 partition, so it may be read and written by virtually any computer on earth.
To create the ssh file, simply mount the SD ...
You want to have two connections to the same destination. This is mainly a routing problem to decide what interface to use. I can't see an easy solution at first glance because the destination is the same subnet, so you cannot use classical routing.
But to make a weak connection more stable with a second connection there is a well known solution called "...