| View previous topic :: View next topic |
| Author |
Message |
linux_os2
Apprentice
Joined: 29 Aug 2018
Posts: 221
Location: Zedelgem Belgium
|
 Posted: Mon May 23, 2022 8:29 am Post subject: Wifi get ip-address 169.254.99.134 |
 |
|
Found dozens of entries on google.
ipconfig:
| Code: | ens5: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.0.226 netmask 255.255.255.0 broadcast 192.168.0.255
inet6 fe80::3046:9505:8b25:41c9 prefixlen 64 scopeid 0x20<link>
inet6 2a02:1811:b713:8500:1b15:a893:dafd:61a3 prefixlen 64 scopeid 0x0<global>
ether d8:d3:85:06:ea:e9 txqueuelen 1000 (Ethernet)
RX packets 34 bytes 7024 (6.8 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 28 bytes 2592 (2.5 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 17
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
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 collisions 0
wls1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
---> net 169.254.99.134 netmask 255.255.0.0 broadcast 169.254.255.255
inet6 fe80::ac48:5515:a2dd:659f prefixlen 64 scopeid 0x20<link>
ether 00:26:c7:04:3a:64 txqueuelen 1000 (Ethernet)
RX packets 59 bytes 13562 (13.2 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 20 bytes 3096 (3.0 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 |
cat /etc/wpa_supplicant/
| Code: | wpa_supplicant.confctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel
update_config=1
ctrl_interface_group=0
ap_scan=1
network={
ssid="DEBRUYNE-24G"
psk="secret"
proto=RSN
key_mgmt=WPA-PSK
pairwise=TKIP
auth_alg=OPEN
} |
cat /etc/conf.d/net
| Code: | modules_wls1=("!plug" "wpa_supplicant" "dhcpcd")
ifplugd_ens5="..." |
|
|
| Back to top |
|
 |
szatox
Advocate
Joined: 27 Aug 2013
Posts: 3134
|
| Posted: Mon May 23, 2022 9:19 am Post subject: |
|
|
Ok, so your interface configured itself with apipa, which although rarely used, is a valid way to do that.
And the problem is? |
|
| Back to top |
|
|
linux_os2
Apprentice
Joined: 29 Aug 2018
Posts: 221
Location: Zedelgem Belgium
|
| Posted: Mon May 23, 2022 9:37 am Post subject: |
|
|
| szatox wrote: | Ok, so your interface configured itself with apipa, which although rarely used, is a valid way to do that.
And the problem is? |
when; ping www.gentoo.org
also browser does not work
via ens5 (ethernet cable) OK |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54232
Location: 56N 3W
|
| Posted: Mon May 23, 2022 10:21 am Post subject: |
|
|
linux_os2,
TKIP is regarded as unsafe and its disabled by default on wpa_supplicant now.
If you really want to use tkip, set USE=tkip on wpa_supplicant and rebuild it.
The right thing to do, if you can, is to switch your wifi to WPA2. That requires support form all participating devices, so it way not be an option.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
linux_os2
Apprentice
Joined: 29 Aug 2018
Posts: 221
Location: Zedelgem Belgium
|
| Posted: Mon May 23, 2022 11:30 am Post subject: |
|
|
| NeddySeagoon wrote: | linux_os2,
TKIP is regarded as unsafe and its disabled by default on wpa_supplicant now.
If you really want to use tkip, set USE=tkip on wpa_supplicant and rebuild it.
The right thing to do, if you can, is to switch your wifi to WPA2. That requires support form all participating devices, so it way not be an option. |
Hi, Neddy,
Posted the wrong wpaconfig
cat /etc/wpa_supplicant/wpa_supplicant-wls1.conf
| Code: | ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel
update_config=1
ctrl_interface_group=0
ap_scan=1
network={
ssid="DEBRUYNE"
psk="geheim"
proto=RSN
key_mgmt=WPA-PSK
auth_alg=OPEN
mesh_fwding=1
} |
wpa-gui shows
Last edited by linux_os2 on Mon May 23, 2022 6:52 pm; edited 1 time in total |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54232
Location: 56N 3W
|
| Posted: Mon May 23, 2022 11:39 am Post subject: |
|
|
linux_os2,
Please put your dmesg onto a pastebin so that we can see what happens when the wifi tries to authenticate, or even if it tries at all.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
linux_os2
Apprentice
Joined: 29 Aug 2018
Posts: 221
Location: Zedelgem Belgium
|
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54232
Location: 56N 3W
|
| Posted: Mon May 23, 2022 6:54 pm Post subject: |
|
|
linux_os2,
| Code: | [ 455.818968] wls1: deauthenticating from 58:6d:8f:16:da:ac by local choice (Reason: 3=DEAUTH_LEAVING)
[ 458.273446] wls1: authenticate with 58:6d:8f:16:da:ac
[ 458.278250] wls1: send auth to 58:6d:8f:16:da:ac (try 1/3)
[ 458.281034] wls1: authenticated
[ 458.283004] wls1: associate with 58:6d:8f:16:da:ac (try 1/3)
[ 458.287092] wls1: RX AssocResp from 58:6d:8f:16:da:ac (capab=0x411 status=0 aid=1)
[ 458.294011] wls1: associated |
The radio and crypto works. That (Reason: 3=DEAUTH_LEAVING) means that the system told the wifi to stop.
I was particularly looking for lots of handshakes like that, as happens when two (or more) network controllers fight over the interface.
It looks like dhcpcd tried to get network settings and gave up, so it set a link local address instead.
Is 58:6d:8f:16:da:ac the MAC address of your access point?
What is your dhcpccd timeout set to?
| Code: | May 23 13:51:04 marc dhcpcd[860]: wls1: soliciting a DHCP lease
May 23 13:51:09 marc dhcpcd[860]: wls1: probing for an IPv4LL address |
That looks like 5 seconds. Its probably too short.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
linux_os2
Apprentice
Joined: 29 Aug 2018
Posts: 221
Location: Zedelgem Belgium
|
| Posted: Mon May 23, 2022 9:23 pm Post subject: |
|
|
Neddy,
| Quote: | | Is 58:6d:8f:16:da:ac the MAC address of your access point? |
Yes.
| Quote: | | What is your dhcpccd timeout set to? |
The default (not specified in dhcpcd.conf)
Changed to 60 ==> same effect. |
|
| Back to top |
|
|
linux_os2
Apprentice
Joined: 29 Aug 2018
Posts: 221
Location: Zedelgem Belgium
|
| Posted: Tue May 24, 2022 1:32 pm Post subject: |
|
|
Hi,
tried to connect to the other router:
first it would not work found out that the encryption algorithm was not supported.
emerged wpa_supplicant whit USE=tkip.
Now connection succeeds and we get a ip address in the range of 192.168.x.x
on the other router still the wrong ip address : 169.254.99.134
the modems are connected to the internet as follows.
internet --------------| modem 1 |---------------| modem 2 |
modem 2 is configured as repeater. that is the one on witch the ip address is wrong. |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54232
Location: 56N 3W
|
| Posted: Tue May 24, 2022 1:51 pm Post subject: |
|
|
linux_os2,
Modem 2 will not hand out network setups as its a repeater and does not know what addresses are in use.
That's normal. Two dhcp servers on the same network is a bad thing.
Modem 2 needs to be configured to pass dhcp requests to Modem 1.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
linux_os2
Apprentice
Joined: 29 Aug 2018
Posts: 221
Location: Zedelgem Belgium
|
| Posted: Tue May 24, 2022 5:47 pm Post subject: |
|
|
Neddy,
As usual you are completely right
| Quote: | | Modem 2 needs to be configured to pass dhcp requests to Modem 1. |
Reset the modem2 to factory settings, disabled DHCP and set wifi password.
Now connection is possible to both modems.
Thx a lot |
|
| Back to top |
|
|
|
Networking & Security
