| View previous topic :: View next topic |
| Author |
Message |
javeree
Guru
Joined: 29 Jan 2006
Posts: 453
|
 Posted: Fri Oct 11, 2019 10:43 am Post subject: Not getting IPv4 on boot |
 |
|
Booting Gentoo, both my fixed ethernet and wifi are started using hotplug.
Ethernet is not connected, so gets in state 'down'. That is correct.
Wifi sets up a connection using dhcpcd. When I log in, I see that the interface received from the ISP modem an IPv6 address, but no IPv4.
I need to remark that openrc shows a lot of services 'waiting for network (xxx seconds), probably until the wifi gets its address.
| Quote: | 3: wlp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 44:03:2c:e9:da:a4 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.20/24 brd 192.168.1.255 scope global noprefixroute wlp4s0
valid_lft forever preferred_lft forever
inet6 fda9:b95d:923b:0:22f7:cbd1:1e44:23a5/64 scope global mngtmpaddr noprefixroute
valid_lft forever preferred_lft forever
inet6 2a02:a03f:4ed7:e800:3d53:258:1bc4:7205/64 scope global dynamic mngtmpaddr noprefixroute
valid_lft 200340sec preferred_lft 200340sec
inet6 fe80::4603:2cff:fee9:daa4/64 scope link
valid_lft forever preferred_lft forever
|
That means that I have internet access (I can ping google), but cannot ping other PCs on the network that do have an IPv4 address.
When I manually restart: rc-servicehttps://pastebin.com/W2XwTnKT net.wlp4s0 restart, I get both IPv4 and IPv6, and have access to my lan.
| Quote: | 3: wlp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 44:03:2c:e9:da:a4 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.20/24 brd 192.168.1.255 scope global noprefixroute wlp4s0
valid_lft forever preferred_lft forever
inet6 fda9:b95d:923b:0:22f7:cbd1:1e44:23a5/64 scope global mngtmpaddr noprefixroute
valid_lft forever preferred_lft forever
inet6 2a02:a03f:4ed7:e800:3d53:258:1bc4:7205/64 scope global dynamic mngtmpaddr noprefixroute
valid_lft 200340sec preferred_lft 200340sec
inet6 fe80::4603:2cff:fee9:daa4/64 scope link
valid_lft forever preferred_lft forever
|
This is dmesg until I have manually restarted https://pastebin.com/W2XwTnKT
I believe these are the relevant snippets:
| Quote: |
[ 2.102196] iwlwifi 0000:04:00.0: enabling device (0000 -> 0002)
[ 2.108533] iwlwifi 0000:04:00.0: Found debug destination: EXTERNAL_DRAM
[ 2.108534] iwlwifi 0000:04:00.0: Found debug configuration: 0
[ 2.109086] iwlwifi 0000:04:00.0: loaded firmware version 36.77d01142.0 op_mode iwlmvm
[ 2.149214] iwlwifi 0000:04:00.0: Detected Intel(R) Dual Band Wireless AC 8265, REV=0x230
[ 2.156411] iwlwifi 0000:04:00.0: Applying debug destination EXTERNAL_DRAM
[ 2.156711] iwlwifi 0000:04:00.0: Allocated 0x00400000 bytes for firmware monitor.
[ 2.207846] iwlwifi 0000:04:00.0: base HW address: 44:03:2c:e9:da:a4
[ 2.282229] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
[ 2.283389] iwlwifi 0000:04:00.0 wlp4s0: renamed from wlan0
[ 2.534400] iwlwifi 0000:04:00.0: Applying debug destination EXTERNAL_DRAM
[ 2.664939] iwlwifi 0000:04:00.0: Applying debug destination EXTERNAL_DRAM
[ 2.729432] iwlwifi 0000:04:00.0: FW already configured (0) - re-configuring
[ 6.511879] wlp4s0: authenticate with a6:b1:e9:b1:96:bc
[ 6.521718] wlp4s0: send auth to a6:b1:e9:b1:96:bc (try 1/3)
[ 6.527503] wlp4s0: authenticated
[ 6.528185] wlp4s0: associate with a6:b1:e9:b1:96:bc (try 1/3)
[ 6.536726] wlp4s0: RX AssocResp from a6:b1:e9:b1:96:bc (capab=0x511 status=0 aid=1)
[ 6.540934] wlp4s0: associated
..... << probably this is where my services waiting for network
[ 32.955107] Segment Routing with IPv6 No idea what this is, but I guess this is where I get the IPv6 address only
..... << manual restart
[ 213.778311] wlp4s0: deauthenticating from a6:b1:e9:b1:96:bc by local choice (Reason: 3=DEAUTH_LEAVING)
[ 214.031620] iwlwifi 0000:04:00.0: Applying debug destination EXTERNAL_DRAM
[ 214.166265] iwlwifi 0000:04:00.0: Applying debug destination EXTERNAL_DRAM
[ 214.232420] iwlwifi 0000:04:00.0: FW already configured (0) - re-configuring
[ 218.002151] wlp4s0: authenticate with a6:b1:e9:b1:96:bc
[ 218.009883] wlp4s0: send auth to a6:b1:e9:b1:96:bc (try 1/3)
[ 218.015461] wlp4s0: authenticated
[ 218.016096] wlp4s0: associate with a6:b1:e9:b1:96:bc (try 1/3)
[ 218.024756] wlp4s0: RX AssocResp from a6:b1:e9:b1:96:bc (capab=0x511 status=0 aid=2)
[ 218.029182] wlp4s0: associated
[ 218.051033] IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link becomes ready It does not mention IPv4, but I still get an IPV4 address here
|
Clearly there is a difference between what is happening at boot and what happens when I restart wifi. I have no idea what or why. |
|
| Back to top |
|
 |
e3k
Guru
Joined: 01 Oct 2007
Posts: 515
Location: Quantum Flux
|
| Posted: Tue Oct 15, 2019 6:31 pm Post subject: Re: Not getting IPv4 on boot |
|
|
| javeree wrote: | Booting Gentoo, both my fixed ethernet and wifi are started using hotplug.
Ethernet is not connected, so gets in state 'down'. That is correct.
Wifi sets up a connection using dhcpcd. When I log in, I see that the interface received from the ISP modem an IPv6 address, but no IPv4.
I need to remark that openrc shows a lot of services 'waiting for network (xxx seconds), probably until the wifi gets its address.
| Quote: | 3: wlp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 44:03:2c:e9:da:a4 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.20/24 brd 192.168.1.255 scope global noprefixroute wlp4s0
valid_lft forever preferred_lft forever
inet6 fda9:b95d:923b:0:22f7:cbd1:1e44:23a5/64 scope global mngtmpaddr noprefixroute
valid_lft forever preferred_lft forever
inet6 2a02:a03f:4ed7:e800:3d53:258:1bc4:7205/64 scope global dynamic mngtmpaddr noprefixroute
valid_lft 200340sec preferred_lft 200340sec
inet6 fe80::4603:2cff:fee9:daa4/64 scope link
valid_lft forever preferred_lft forever
|
That means that I have internet access (I can ping google), but cannot ping other PCs on the network that do have an IPv4 address.
When I manually restart: rc-servicehttps://pastebin.com/W2XwTnKT net.wlp4s0 restart, I get both IPv4 and IPv6, and have access to my lan.
| Quote: | 3: wlp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 44:03:2c:e9:da:a4 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.20/24 brd 192.168.1.255 scope global noprefixroute wlp4s0
valid_lft forever preferred_lft forever
inet6 fda9:b95d:923b:0:22f7:cbd1:1e44:23a5/64 scope global mngtmpaddr noprefixroute
valid_lft forever preferred_lft forever
inet6 2a02:a03f:4ed7:e800:3d53:258:1bc4:7205/64 scope global dynamic mngtmpaddr noprefixroute
valid_lft 200340sec preferred_lft 200340sec
inet6 fe80::4603:2cff:fee9:daa4/64 scope link
valid_lft forever preferred_lft forever
|
This is dmesg until I have manually restarted https://pastebin.com/W2XwTnKT
I believe these are the relevant snippets:
| Quote: |
[ 2.102196] iwlwifi 0000:04:00.0: enabling device (0000 -> 0002)
[ 2.108533] iwlwifi 0000:04:00.0: Found debug destination: EXTERNAL_DRAM
[ 2.108534] iwlwifi 0000:04:00.0: Found debug configuration: 0
[ 2.109086] iwlwifi 0000:04:00.0: loaded firmware version 36.77d01142.0 op_mode iwlmvm
[ 2.149214] iwlwifi 0000:04:00.0: Detected Intel(R) Dual Band Wireless AC 8265, REV=0x230
[ 2.156411] iwlwifi 0000:04:00.0: Applying debug destination EXTERNAL_DRAM
[ 2.156711] iwlwifi 0000:04:00.0: Allocated 0x00400000 bytes for firmware monitor.
[ 2.207846] iwlwifi 0000:04:00.0: base HW address: 44:03:2c:e9:da:a4
[ 2.282229] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
[ 2.283389] iwlwifi 0000:04:00.0 wlp4s0: renamed from wlan0
[ 2.534400] iwlwifi 0000:04:00.0: Applying debug destination EXTERNAL_DRAM
[ 2.664939] iwlwifi 0000:04:00.0: Applying debug destination EXTERNAL_DRAM
[ 2.729432] iwlwifi 0000:04:00.0: FW already configured (0) - re-configuring
[ 6.511879] wlp4s0: authenticate with a6:b1:e9:b1:96:bc
[ 6.521718] wlp4s0: send auth to a6:b1:e9:b1:96:bc (try 1/3)
[ 6.527503] wlp4s0: authenticated
[ 6.528185] wlp4s0: associate with a6:b1:e9:b1:96:bc (try 1/3)
[ 6.536726] wlp4s0: RX AssocResp from a6:b1:e9:b1:96:bc (capab=0x511 status=0 aid=1)
[ 6.540934] wlp4s0: associated
..... << probably this is where my services waiting for network
[ 32.955107] Segment Routing with IPv6 No idea what this is, but I guess this is where I get the IPv6 address only
..... << manual restart
[ 213.778311] wlp4s0: deauthenticating from a6:b1:e9:b1:96:bc by local choice (Reason: 3=DEAUTH_LEAVING)
[ 214.031620] iwlwifi 0000:04:00.0: Applying debug destination EXTERNAL_DRAM
[ 214.166265] iwlwifi 0000:04:00.0: Applying debug destination EXTERNAL_DRAM
[ 214.232420] iwlwifi 0000:04:00.0: FW already configured (0) - re-configuring
[ 218.002151] wlp4s0: authenticate with a6:b1:e9:b1:96:bc
[ 218.009883] wlp4s0: send auth to a6:b1:e9:b1:96:bc (try 1/3)
[ 218.015461] wlp4s0: authenticated
[ 218.016096] wlp4s0: associate with a6:b1:e9:b1:96:bc (try 1/3)
[ 218.024756] wlp4s0: RX AssocResp from a6:b1:e9:b1:96:bc (capab=0x511 status=0 aid=2)
[ 218.029182] wlp4s0: associated
[ 218.051033] IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link becomes ready It does not mention IPv4, but I still get an IPV4 address here
|
Clearly there is a difference between what is happening at boot and what happens when I restart wifi. I have no idea what or why. |
i had no problems with dhcpcd yet. what version are you using? what happens if you force -4 via dhcpcd.config?
could be a problem of the router.
also what is hotplug?
_________________
Flux & Contemplation - Portrait of an Artist in Isolation
|
|
| Back to top |
|
|
toralf
Developer
Joined: 01 Feb 2004
Posts: 3940
Location: Hamburg
|
| Posted: Tue Oct 15, 2019 8:12 pm Post subject: |
|
|
I do have | Code: | tfoerste@t44 ~ $ tail -n 4 /etc/dhcpcd.conf
# by toralf
#
waitip 4 |
|
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Networking & Security
