Are DHCPv6 Information-request messages via unicast permitted?

RFC8415 section 16:

A server MUST discard any Solicit, Confirm, Rebind, or
Information-request messages it receives with a Layer 3 unicast
destination address.

RFC8415 section 18.4:

For example, unicast transmission is not allowed for Solicit,
Confirm, and Rebind messages (see Sections 18.3.1, 18.3.3, and
18.3.5, respectively), even if the Server Unicast option (see
Section 21.12) is configured. For Request, Renew,
Information-request, Release, and Decline messages, it is allowed
only if the Server Unicast option is configured
.

These statements contradict each other. Are unicast transmissions (after the receipt of a Server Unicast option) permitted or not?

Go to Source
Author: betanummeric

DHCP and fallback IP – Can I have two different settings on the same network interface?

I have a project in which a user can change the RPI’s networking settings via a Web Interface from the following:

  • DHCP WiFi
  • DHCP Ethernet
  • Static WiFi
  • Static Ethernet

Each choice re-configures dhcpcd_conf and wpa_conf accordingly. It works perfectly nice.

The whole package is designed to be in DHCP Ethernet on the first boot. But this design has a flaw in it because not every user has a DHCP server in place.

That’s when I thought of making a fallback static Ethernet IP and this is what I came up with:

Case 1 – DHCP Ethernet

# dhcpcd_conf

interface wlan0
noipv4
noipv6

interface eth0
hostname DeviceEth
clientid

profile static_eth0
static ip_address=192.168.1.150/24
static routers=192.168.1.1
static domain_name_servers=8.8.8.8

interface eth0
fallback static_eth0
# wpa_conf
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1

As you can see I set wlan0 to have no IP, then I set eth0 to DHCP and then I set the same eth0 to a fallback profile.
Is this correct ? Can I have two different settings on the same interface ?

Case 2 – DHCP WiFi:

# dhcpcd_conf
interface wlan0
hostname DeviceWiFi
clientid

interface eth0
noipv4
noipv6

profile static_eth0
static ip_address=192.168.1.150/24
static routers=192.168.1.1
static domain_name_servers=8.8.8.8

interface eth0
fallback static_eth0
# wpa_conf
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1
country=RO
network={
ssid="SSID"
psk="password"
}

Here I set wlan0 to DHCP, then I set eth0 to no ip and then I set the same eth0 to a fallback profile.
Is this configuration correct ?

In both cases I want only one interface active, that’s why I configure one to DHCP and the other one to no IP.
In the case of DHCP WiFi it doesn’t matter if wlan0 stays up after the fallback is in effect, because the user will most probably configure a static IP once he reaches the Web Interface and static configuration is similar to the DHCP configuration in the way that it only leaves one interface active at a time.

Go to Source
Author: Jorje12

netctl: Static IP configuration lost automatically after few seconds of starting the interface

I am using netctl in Arch Linux on Hyper-V. I have two ethernet interfaces eth0 & eth1.

IP config:

  1. eth0: dhcp (automatic configuration, no involvment of netctl)
  2. eth1: static ip (10.10.10.1/8) using netctl profile
  3. dhcpcd installed and enabled at startup
  4. NetworkManager installed and enabled at startup

eth1 netctl profile (/etc/netctl/sth1static):

Description='Static IP config for eth1'
Interface=eth1
Connection=ethernet
IP=static
Address=('10.10.10.1/8')
Gateway='10.10.10.2'
DNS=('10.10.10.2')

To start the interface I am doing as follows:

netctl stop eth1static
ip link set eth1 down
netctl start eth1static
netctl enable eth1static

After following the above steps, I am able to see the static IP configuration applied to the interface using ip a. Also I am able to ping the guest interface from my host OS successfully. However after a minute or so, I see the interface lose its configuration and get a fe80: based IPv6 address only and the ping stops working… Even after reboot, I don’t see the IP configurtion on the interface, where as the other interface (eth0) is working fine.

Could anyone suggest what’s going wrong and how to fix it?

Go to Source
Author: Anirban