Wifi Problem After Setting Static IP in Ubuntu 18.04.01 LTS
up vote
0
down vote
favorite
I set a static IP by following the instructions on https://www.itzgeek.com/how-tos/linux/ubuntu-how-tos/netplan-how-to-configure-static-ip-address-in-ubuntu-18-04-using-netplan.html
At first, it worked. However, when I rebooted my laptop, Wifi didn't work anymore. The corresponding information are the following:
networkctl status -a
1: lo
Link File: /lib/systemd/network/99-default.link
Network File: n/a
Type: loopback
State: carrier (unmanaged)
Address: 127.0.0.1
::1
● 2: enp2s0
Link File: /lib/systemd/network/99-default.link
Network File: n/a
Type: ether
State: routable (unmanaged)
Path: pci-0000:02:00.0
Driver: r8169
Vendor: Realtek Semiconductor Co., Ltd.
Model: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
HW Address: ... (ASUSTek COMPUTER INC.)
Address: 10.5.150.56
...
Gateway: 10.5.148.1 (Cisco Systems, Inc)
● 3: wlp3s0
Link File: /lib/systemd/network/99-default.link
Network File: /run/systemd/network/10-netplan-wlp3s0.network
Type: wlan
State: off (configuring)
Path: pci-0000:03:00.0
Driver: rtl8723be
Vendor: Realtek Semiconductor Co., Ltd.
Model: RTL8723BE PCIe Wireless Network Adapter
HW Address: 30:52:cb:ee:5c:c2 (Liteon Technology Corporation)
DNS: 8.8.8.8
8.8.4.4
/etc/netplan/01-netcfg.yaml
network:
version: 2
renderer: networkd
wifis:
wlp3s0:
dhcp4: no
addresses: [192.168.43.131/24]
gateway4: 192.168.1.1
nameservers:
addresses: [8.8.8.8,8.8.4.4]
access-points:
F3-:
password: ...
ifconfig -a
enp2s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 10.5.150.56 netmask 255.255.252.0 broadcast 10.5.151.255
inet6 ... prefixlen 64 scopeid 0x20<link>
ether ... txqueuelen 1000 (Ethernet)
RX packets 13169 bytes 9405575 (9.4 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 7706 bytes 1033540 (1.0 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
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 1251 bytes 164695 (164.6 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1251 bytes 164695 (164.6 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlp3s0: flags=4098<BROADCAST,MULTICAST> mtu 1500
ether ... txqueuelen 1000 (Ethernet)
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
So, what can be the problem? Thanks in advance...
networking 18.04 network-manager static-ip netplan
add a comment |
up vote
0
down vote
favorite
I set a static IP by following the instructions on https://www.itzgeek.com/how-tos/linux/ubuntu-how-tos/netplan-how-to-configure-static-ip-address-in-ubuntu-18-04-using-netplan.html
At first, it worked. However, when I rebooted my laptop, Wifi didn't work anymore. The corresponding information are the following:
networkctl status -a
1: lo
Link File: /lib/systemd/network/99-default.link
Network File: n/a
Type: loopback
State: carrier (unmanaged)
Address: 127.0.0.1
::1
● 2: enp2s0
Link File: /lib/systemd/network/99-default.link
Network File: n/a
Type: ether
State: routable (unmanaged)
Path: pci-0000:02:00.0
Driver: r8169
Vendor: Realtek Semiconductor Co., Ltd.
Model: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
HW Address: ... (ASUSTek COMPUTER INC.)
Address: 10.5.150.56
...
Gateway: 10.5.148.1 (Cisco Systems, Inc)
● 3: wlp3s0
Link File: /lib/systemd/network/99-default.link
Network File: /run/systemd/network/10-netplan-wlp3s0.network
Type: wlan
State: off (configuring)
Path: pci-0000:03:00.0
Driver: rtl8723be
Vendor: Realtek Semiconductor Co., Ltd.
Model: RTL8723BE PCIe Wireless Network Adapter
HW Address: 30:52:cb:ee:5c:c2 (Liteon Technology Corporation)
DNS: 8.8.8.8
8.8.4.4
/etc/netplan/01-netcfg.yaml
network:
version: 2
renderer: networkd
wifis:
wlp3s0:
dhcp4: no
addresses: [192.168.43.131/24]
gateway4: 192.168.1.1
nameservers:
addresses: [8.8.8.8,8.8.4.4]
access-points:
F3-:
password: ...
ifconfig -a
enp2s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 10.5.150.56 netmask 255.255.252.0 broadcast 10.5.151.255
inet6 ... prefixlen 64 scopeid 0x20<link>
ether ... txqueuelen 1000 (Ethernet)
RX packets 13169 bytes 9405575 (9.4 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 7706 bytes 1033540 (1.0 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
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 1251 bytes 164695 (164.6 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1251 bytes 164695 (164.6 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlp3s0: flags=4098<BROADCAST,MULTICAST> mtu 1500
ether ... txqueuelen 1000 (Ethernet)
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
So, what can be the problem? Thanks in advance...
networking 18.04 network-manager static-ip netplan
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I set a static IP by following the instructions on https://www.itzgeek.com/how-tos/linux/ubuntu-how-tos/netplan-how-to-configure-static-ip-address-in-ubuntu-18-04-using-netplan.html
At first, it worked. However, when I rebooted my laptop, Wifi didn't work anymore. The corresponding information are the following:
networkctl status -a
1: lo
Link File: /lib/systemd/network/99-default.link
Network File: n/a
Type: loopback
State: carrier (unmanaged)
Address: 127.0.0.1
::1
● 2: enp2s0
Link File: /lib/systemd/network/99-default.link
Network File: n/a
Type: ether
State: routable (unmanaged)
Path: pci-0000:02:00.0
Driver: r8169
Vendor: Realtek Semiconductor Co., Ltd.
Model: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
HW Address: ... (ASUSTek COMPUTER INC.)
Address: 10.5.150.56
...
Gateway: 10.5.148.1 (Cisco Systems, Inc)
● 3: wlp3s0
Link File: /lib/systemd/network/99-default.link
Network File: /run/systemd/network/10-netplan-wlp3s0.network
Type: wlan
State: off (configuring)
Path: pci-0000:03:00.0
Driver: rtl8723be
Vendor: Realtek Semiconductor Co., Ltd.
Model: RTL8723BE PCIe Wireless Network Adapter
HW Address: 30:52:cb:ee:5c:c2 (Liteon Technology Corporation)
DNS: 8.8.8.8
8.8.4.4
/etc/netplan/01-netcfg.yaml
network:
version: 2
renderer: networkd
wifis:
wlp3s0:
dhcp4: no
addresses: [192.168.43.131/24]
gateway4: 192.168.1.1
nameservers:
addresses: [8.8.8.8,8.8.4.4]
access-points:
F3-:
password: ...
ifconfig -a
enp2s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 10.5.150.56 netmask 255.255.252.0 broadcast 10.5.151.255
inet6 ... prefixlen 64 scopeid 0x20<link>
ether ... txqueuelen 1000 (Ethernet)
RX packets 13169 bytes 9405575 (9.4 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 7706 bytes 1033540 (1.0 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
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 1251 bytes 164695 (164.6 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1251 bytes 164695 (164.6 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlp3s0: flags=4098<BROADCAST,MULTICAST> mtu 1500
ether ... txqueuelen 1000 (Ethernet)
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
So, what can be the problem? Thanks in advance...
networking 18.04 network-manager static-ip netplan
I set a static IP by following the instructions on https://www.itzgeek.com/how-tos/linux/ubuntu-how-tos/netplan-how-to-configure-static-ip-address-in-ubuntu-18-04-using-netplan.html
At first, it worked. However, when I rebooted my laptop, Wifi didn't work anymore. The corresponding information are the following:
networkctl status -a
1: lo
Link File: /lib/systemd/network/99-default.link
Network File: n/a
Type: loopback
State: carrier (unmanaged)
Address: 127.0.0.1
::1
● 2: enp2s0
Link File: /lib/systemd/network/99-default.link
Network File: n/a
Type: ether
State: routable (unmanaged)
Path: pci-0000:02:00.0
Driver: r8169
Vendor: Realtek Semiconductor Co., Ltd.
Model: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
HW Address: ... (ASUSTek COMPUTER INC.)
Address: 10.5.150.56
...
Gateway: 10.5.148.1 (Cisco Systems, Inc)
● 3: wlp3s0
Link File: /lib/systemd/network/99-default.link
Network File: /run/systemd/network/10-netplan-wlp3s0.network
Type: wlan
State: off (configuring)
Path: pci-0000:03:00.0
Driver: rtl8723be
Vendor: Realtek Semiconductor Co., Ltd.
Model: RTL8723BE PCIe Wireless Network Adapter
HW Address: 30:52:cb:ee:5c:c2 (Liteon Technology Corporation)
DNS: 8.8.8.8
8.8.4.4
/etc/netplan/01-netcfg.yaml
network:
version: 2
renderer: networkd
wifis:
wlp3s0:
dhcp4: no
addresses: [192.168.43.131/24]
gateway4: 192.168.1.1
nameservers:
addresses: [8.8.8.8,8.8.4.4]
access-points:
F3-:
password: ...
ifconfig -a
enp2s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 10.5.150.56 netmask 255.255.252.0 broadcast 10.5.151.255
inet6 ... prefixlen 64 scopeid 0x20<link>
ether ... txqueuelen 1000 (Ethernet)
RX packets 13169 bytes 9405575 (9.4 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 7706 bytes 1033540 (1.0 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
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 1251 bytes 164695 (164.6 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1251 bytes 164695 (164.6 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlp3s0: flags=4098<BROADCAST,MULTICAST> mtu 1500
ether ... txqueuelen 1000 (Ethernet)
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
So, what can be the problem? Thanks in advance...
networking 18.04 network-manager static-ip netplan
networking 18.04 network-manager static-ip netplan
asked Jul 31 at 14:35
qwerty
1
1
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
First, the gateway address 192.168.1.1 is not in the same subnet with 192.168.43.131/24. One of the two is incorrect.
Second, netplan is very specific as to format, convention, indentation, spacing, etc. You can check an example here:
cat /usr/share/doc/netplan.io/examples/wireless.yaml
I suggest that you revise your yaml file to:
network:
version: 2
renderer: networkd
wifis:
wlp3s0:
dhcp4: no
addresses: [192.168.43.131/24]
gateway4: 192.168.43.1
nameservers:
addresses: [8.8.8.8, 8.8.4.4]
access-points:
"F3-":
password: "..."
NOTE: Is F3- really the name of your network as the yaml file in your question suggests? Or is it F3 or some other? Substitute your details above.
Next, apply the changes:
sudo netplan apply
Any improvement?
F3 is the name of the network. Networkctl state turned to "no-carrier" but wifi still doesn't work.
– qwerty
Jul 31 at 16:06
Are there any clues in the log?dmesg | grep -e wlp -e net
May I assume that Network Manager is not installed and running here?
– chili555
Jul 31 at 18:45
If the name of your network is F3 then this config looks incorrect since it lists F3-
– slangasek
Jul 31 at 19:48
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
First, the gateway address 192.168.1.1 is not in the same subnet with 192.168.43.131/24. One of the two is incorrect.
Second, netplan is very specific as to format, convention, indentation, spacing, etc. You can check an example here:
cat /usr/share/doc/netplan.io/examples/wireless.yaml
I suggest that you revise your yaml file to:
network:
version: 2
renderer: networkd
wifis:
wlp3s0:
dhcp4: no
addresses: [192.168.43.131/24]
gateway4: 192.168.43.1
nameservers:
addresses: [8.8.8.8, 8.8.4.4]
access-points:
"F3-":
password: "..."
NOTE: Is F3- really the name of your network as the yaml file in your question suggests? Or is it F3 or some other? Substitute your details above.
Next, apply the changes:
sudo netplan apply
Any improvement?
F3 is the name of the network. Networkctl state turned to "no-carrier" but wifi still doesn't work.
– qwerty
Jul 31 at 16:06
Are there any clues in the log?dmesg | grep -e wlp -e net
May I assume that Network Manager is not installed and running here?
– chili555
Jul 31 at 18:45
If the name of your network is F3 then this config looks incorrect since it lists F3-
– slangasek
Jul 31 at 19:48
add a comment |
up vote
0
down vote
First, the gateway address 192.168.1.1 is not in the same subnet with 192.168.43.131/24. One of the two is incorrect.
Second, netplan is very specific as to format, convention, indentation, spacing, etc. You can check an example here:
cat /usr/share/doc/netplan.io/examples/wireless.yaml
I suggest that you revise your yaml file to:
network:
version: 2
renderer: networkd
wifis:
wlp3s0:
dhcp4: no
addresses: [192.168.43.131/24]
gateway4: 192.168.43.1
nameservers:
addresses: [8.8.8.8, 8.8.4.4]
access-points:
"F3-":
password: "..."
NOTE: Is F3- really the name of your network as the yaml file in your question suggests? Or is it F3 or some other? Substitute your details above.
Next, apply the changes:
sudo netplan apply
Any improvement?
F3 is the name of the network. Networkctl state turned to "no-carrier" but wifi still doesn't work.
– qwerty
Jul 31 at 16:06
Are there any clues in the log?dmesg | grep -e wlp -e net
May I assume that Network Manager is not installed and running here?
– chili555
Jul 31 at 18:45
If the name of your network is F3 then this config looks incorrect since it lists F3-
– slangasek
Jul 31 at 19:48
add a comment |
up vote
0
down vote
up vote
0
down vote
First, the gateway address 192.168.1.1 is not in the same subnet with 192.168.43.131/24. One of the two is incorrect.
Second, netplan is very specific as to format, convention, indentation, spacing, etc. You can check an example here:
cat /usr/share/doc/netplan.io/examples/wireless.yaml
I suggest that you revise your yaml file to:
network:
version: 2
renderer: networkd
wifis:
wlp3s0:
dhcp4: no
addresses: [192.168.43.131/24]
gateway4: 192.168.43.1
nameservers:
addresses: [8.8.8.8, 8.8.4.4]
access-points:
"F3-":
password: "..."
NOTE: Is F3- really the name of your network as the yaml file in your question suggests? Or is it F3 or some other? Substitute your details above.
Next, apply the changes:
sudo netplan apply
Any improvement?
First, the gateway address 192.168.1.1 is not in the same subnet with 192.168.43.131/24. One of the two is incorrect.
Second, netplan is very specific as to format, convention, indentation, spacing, etc. You can check an example here:
cat /usr/share/doc/netplan.io/examples/wireless.yaml
I suggest that you revise your yaml file to:
network:
version: 2
renderer: networkd
wifis:
wlp3s0:
dhcp4: no
addresses: [192.168.43.131/24]
gateway4: 192.168.43.1
nameservers:
addresses: [8.8.8.8, 8.8.4.4]
access-points:
"F3-":
password: "..."
NOTE: Is F3- really the name of your network as the yaml file in your question suggests? Or is it F3 or some other? Substitute your details above.
Next, apply the changes:
sudo netplan apply
Any improvement?
answered Jul 31 at 15:18
chili555
37.6k55077
37.6k55077
F3 is the name of the network. Networkctl state turned to "no-carrier" but wifi still doesn't work.
– qwerty
Jul 31 at 16:06
Are there any clues in the log?dmesg | grep -e wlp -e net
May I assume that Network Manager is not installed and running here?
– chili555
Jul 31 at 18:45
If the name of your network is F3 then this config looks incorrect since it lists F3-
– slangasek
Jul 31 at 19:48
add a comment |
F3 is the name of the network. Networkctl state turned to "no-carrier" but wifi still doesn't work.
– qwerty
Jul 31 at 16:06
Are there any clues in the log?dmesg | grep -e wlp -e net
May I assume that Network Manager is not installed and running here?
– chili555
Jul 31 at 18:45
If the name of your network is F3 then this config looks incorrect since it lists F3-
– slangasek
Jul 31 at 19:48
F3 is the name of the network. Networkctl state turned to "no-carrier" but wifi still doesn't work.
– qwerty
Jul 31 at 16:06
F3 is the name of the network. Networkctl state turned to "no-carrier" but wifi still doesn't work.
– qwerty
Jul 31 at 16:06
Are there any clues in the log?
dmesg | grep -e wlp -e net
May I assume that Network Manager is not installed and running here?– chili555
Jul 31 at 18:45
Are there any clues in the log?
dmesg | grep -e wlp -e net
May I assume that Network Manager is not installed and running here?– chili555
Jul 31 at 18:45
If the name of your network is F3 then this config looks incorrect since it lists F3-
– slangasek
Jul 31 at 19:48
If the name of your network is F3 then this config looks incorrect since it lists F3-
– slangasek
Jul 31 at 19:48
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1061131%2fwifi-problem-after-setting-static-ip-in-ubuntu-18-04-01-lts%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown