DHCP BLUE - "no declaration for blue0" issue after upgrade 124 -> 126

General questions.
Post Reply
emilhem
Posts: 4
Joined: January 10th, 2019, 8:09 pm

DHCP BLUE - "no declaration for blue0" issue after upgrade 124 -> 126

Post by emilhem » January 10th, 2019, 9:10 pm

After upgrading from 124 with hostapd (unsure which version of hostapd) to the 126 with the latest hostapd available as of today I can't connect with my OnePlus X anymore. To me looking at logcat on the Android device and the DHCP Server log it looks as if the DHCP server is the point of failure

Ethernet seems to work like it is supposed to.

I allow all devices on BLUE

Wireless card: wle600vx (QCA986x/988x 802.11ac Wireless Network Adapter)´

Code: Select all

SSID broadcast	ON
HW Mode		802.11gn
Channel		6
Neighborhood	on
Encryption	WPA2
/var/ipfire/dhcp/dhcp.conf

Code: Select all

subnet 192.168.2.0 netmask 255.255.254.0 #BLUE
{
        range 192.168.2.2 192.168.3.253;
        option subnet-mask 255.255.254.0;
        option domain-name "xyz.local";
        option routers 192.168.2.1;
        option domain-name-servers 192.168.2.1;
        default-lease-time 7200;
        max-lease-time 14400;
} #BLUE
DHCP Server log

Code: Select all

21:56:10 dhcpd:  Wrote 0 deleted host decls to leases file.
21:56:10 dhcpd:  Wrote 0 new dynamic host decls to leases file.
21:56:10 dhcpd:  Wrote 21 leases to leases file.
21:56:10 dhcpd:  
21:56:10 dhcpd:  No subnet declaration for blue0 (no IPv4 addresses).
21:56:10 dhcpd:  ** Ignoring requests on blue0.  If this is not what
21:56:10 dhcpd:     you want, please write a subnet declaration
21:56:10 dhcpd:     in your dhcpd.conf file for the network segment
21:56:10 dhcpd:     to which interface blue0 is attached. **
21:56:10 dhcpd:  
21:56:10 dhcpd:  Server starting service.
Wireless system log

Code: Select all

21:32:13 hostapd:  blue0: STA 11:11:11:11:11:11 IEEE 802.11: authentication OK (open system)
21:32:13 hostapd:  blue0: STA 11:11:11:11:11:11 MLME: MLME-AUTHENTICATE.indication(11:11:11:11:11:11, OPEN_SYSTEM)
21:32:13 hostapd:  blue0: STA 11:11:11:11:11:11 MLME: MLME-DELETEKEYS.request(11:11:11:11:11:11)
21:32:13 hostapd:  blue0: STA 11:11:11:11:11:11 IEEE 802.11: authenticated
21:32:13 hostapd:  blue0: STA 11:11:11:11:11:11 IEEE 802.11: association OK (aid 2)
21:32:13 hostapd:  blue0: STA 11:11:11:11:11:11 IEEE 802.11: associated (aid 2)
21:32:13 hostapd:  blue0: STA 11:11:11:11:11:11 MLME: MLME-ASSOCIATE.indication(11:11:11:11:11:11)
21:32:13 hostapd:  blue0: STA 11:11:11:11:11:11 MLME: MLME-DELETEKEYS.request(11:11:11:11:11:11)
21:32:13 hostapd:  blue0: STA 11:11:11:11:11:11 IEEE 802.11: binding station to interface 'blue0'
21:32:13 hostapd:  blue0: STA 11:11:11:11:11:11 WPA: event 1 notification
21:32:13 hostapd:  blue0: STA 11:11:11:11:11:11 WPA: start authentication
21:32:13 hostapd:  blue0: STA 11:11:11:11:11:11 IEEE 802.1X: unauthorizing port
21:32:13 hostapd:  blue0: STA 11:11:11:11:11:11 WPA: sending 1/4 msg of 4-Way Handshake
21:32:13 hostapd:  blue0: STA 11:11:11:11:11:11 WPA: received EAPOL-Key frame (2/4 Pairwise)
21:32:13 hostapd:  blue0: STA 11:11:11:11:11:11 WPA: sending 3/4 msg of 4-Way Handshake
21:32:13 hostapd:  blue0: STA 11:11:11:11:11:11 WPA: received EAPOL-Key frame (4/4 Pairwise)
21:32:13 hostapd:  blue0: STA 11:11:11:11:11:11 IEEE 802.1X: authorizing port
21:32:13 hostapd:  blue0: STA 11:11:11:11:11:11 RADIUS: starting accounting session ABCD
21:32:13 hostapd:  blue0: STA 11:11:11:11:11:11 WPA: pairwise key handshake completed (RSN)
21:32:49 hostapd:  blue0: STA 11:11:11:11:11:11 WPA: event 3 notification
21:32:49 hostapd:  blue0: STA 11:11:11:11:11:11 IEEE 802.1X: unauthorizing port
21:32:49 hostapd:  blue0: STA 11:11:11:11:11:11 IEEE 802.11: deauthenticated
21:32:49 hostapd:  blue0: STA 11:11:11:11:11:11 MLME: MLME-DEAUTHENTICATE.indication(11:11:11:11:11:11, 3)
21:32:49 hostapd:  blue0: STA 11:11:11:11:11:11 MLME: MLME-DELETEKEYS.request(11:11:11:11:11:11)
21:32:51 hostapd:  blue0: STA 11:11:11:11:11:11 IEEE 802.11: authentication OK (open system)
21:32:51 hostapd:  blue0: STA 11:11:11:11:11:11 MLME: MLME-AUTHENTICATE.indication(11:11:11:11:11:11, OPEN_SYSTEM)
21:32:51 hostapd:  blue0: STA 11:11:11:11:11:11 MLME: MLME-DELETEKEYS.request(11:11:11:11:11:11)
21:32:51 hostapd:  blue0: STA 11:11:11:11:11:11 IEEE 802.11: authenticated
21:32:51 hostapd:  blue0: STA 11:11:11:11:11:11 IEEE 802.11: association OK (aid 2)
21:32:51 hostapd:  blue0: STA 11:11:11:11:11:11 IEEE 802.11: associated (aid 2)
21:32:51 hostapd:  blue0: STA 11:11:11:11:11:11 MLME: MLME-ASSOCIATE.indication(11:11:11:11:11:11)
21:32:51 hostapd:  blue0: STA 11:11:11:11:11:11 MLME: MLME-DELETEKEYS.request(11:11:11:11:11:11)
21:32:51 hostapd:  blue0: STA 11:11:11:11:11:11 IEEE 802.11: binding station to interface 'blue0'
21:32:51 hostapd:  blue0: STA 11:11:11:11:11:11 WPA: event 1 notification
21:32:51 hostapd:  blue0: STA 11:11:11:11:11:11 WPA: start authentication
21:32:51 hostapd:  blue0: STA 11:11:11:11:11:11 IEEE 802.1X: unauthorizing port
21:32:51 hostapd:  blue0: STA 11:11:11:11:11:11 WPA: sending 1/4 msg of 4-Way Handshake
21:32:51 hostapd:  blue0: STA 11:11:11:11:11:11 WPA: received EAPOL-Key frame (2/4 Pairwise)
21:32:51 hostapd:  blue0: STA 11:11:11:11:11:11 WPA: sending 3/4 msg of 4-Way Handshake
21:32:51 hostapd:  blue0: STA 11:11:11:11:11:11 WPA: received EAPOL-Key frame (4/4 Pairwise)
21:32:51 hostapd:  blue0: STA 11:11:11:11:11:11 IEEE 802.1X: authorizing port
21:32:51 hostapd:  blue0: STA 11:11:11:11:11:11 RADIUS: starting accounting session EFGH
21:32:51 hostapd:  blue0: STA 11:11:11:11:11:11 WPA: pairwise key handshake completed (RSN)
Image
Wireless: wle600vx (QCA986x/988x 802.11ac Wireless Network Adapter)

AlSimmons
Posts: 1
Joined: October 11th, 2009, 11:20 am
Contact:

Re: DHCP BLUE - "no declaration for blue0" issue after upgrade 124 -> 126

Post by AlSimmons » January 11th, 2019, 6:40 pm

Hi emilhem,

Happy New Year!

I was able to sort it out changing the option to block Windows Ports on the blue Interface within the Firewall options.

Currently i'm on business trip but I can double check and verify tomorrow morning.

Good luck

emilhem
Posts: 4
Joined: January 10th, 2019, 8:09 pm

Re: DHCP BLUE - "no declaration for blue0" issue after upgrade 124 -> 126

Post by emilhem » January 26th, 2019, 3:23 pm

AlSimmons wrote:
January 11th, 2019, 6:40 pm
I was able to sort it out changing the option to block Windows Ports on the blue Interface within the Firewall options.
What do you mean with Windows ports?
Image
Wireless: wle600vx (QCA986x/988x 802.11ac Wireless Network Adapter)

Lux73
Posts: 34
Joined: January 31st, 2017, 5:40 pm

Re: DHCP BLUE - "no declaration for blue0" issue after upgrade 124 -> 126

Post by Lux73 » January 29th, 2019, 5:44 pm

emilhem wrote:
January 10th, 2019, 9:10 pm

Code: Select all

subnet 192.168.2.0 netmask 255.255.254.0 #BLUE
{
        range 192.168.2.2 192.168.3.253;
        option subnet-mask 255.255.254.0;
        option domain-name "xyz.local";
        option routers 192.168.2.1;
        option domain-name-servers 192.168.2.1;
        default-lease-time 7200;
        max-lease-time 14400;
} #BLUE
Hi,

your "range 192.168.2.2 192.168.3.253;" seems not to be correct...

it should be "range 192.168.2.2 192.168.2.253;"
IPFire 2.21 (x86_64) - Core Update 133 | RGBO
APU2c4 Bios 4.0.25|mSATA i530 120GB|Compex WLE600-VX@ac|PRG310-51

emilhem
Posts: 4
Joined: January 10th, 2019, 8:09 pm

Re: DHCP BLUE - "no declaration for blue0" issue after upgrade 124 -> 126

Post by emilhem » January 29th, 2019, 7:38 pm

Lux73 wrote:
January 29th, 2019, 5:44 pm
your "range 192.168.2.2 192.168.3.253;" seems not to be correct...

it should be "range 192.168.2.2 192.168.2.253;"
Notice the subnet 255.255.254.0 which makes my config correct. Thanks anyway! :)

Really useful tool to find out about the address range is DuckDuckGo searchengine, ref: https://duckduckgo.com/?q=192.168.2.1%2F23
Image
Wireless: wle600vx (QCA986x/988x 802.11ac Wireless Network Adapter)

emilhem
Posts: 4
Joined: January 10th, 2019, 8:09 pm

Re: DHCP BLUE - "no declaration for blue0" issue after upgrade 124 -> 126

Post by emilhem » January 30th, 2019, 6:46 am

I managed to solve it by reinstalling 126 (from 124) by doing the following in a SSH session:

Code: Select all

echo 124 > /opt/pakfire/db/core/mine
pakfire upgrade
Image
Wireless: wle600vx (QCA986x/988x 802.11ac Wireless Network Adapter)

Post Reply