Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
Client has DNS but no TCP/IP access when connected to Debian host via WiFi
-
- Posts: 22
- Joined: 2019-11-19 08:47
- Has thanked: 4 times
Client has DNS but no TCP/IP access when connected to Debian host via WiFi
I have used NetworkManager to create a "Wi-Fi (shared)" connection as my Debian machine is connected to the internet with a wired connection and I want to share that internet connection with other WiFi devices.
I can connect to the Debian machine over WiFi from an Ubuntu "client" and can ping the Debian access point. I can also ping google.com from the Ubuntu client.
Unfortunately the Ubuntu machine cannot actually connect to any websites. All it can do is ping domains. EDIT: The ping does not actually work - only the domain resolving works. Sorry for my confusion.
What is wrong with my setup? I have the defaults set and was hoping that the NetworkManager wizard would "just work".
I can connect to the Debian machine over WiFi from an Ubuntu "client" and can ping the Debian access point. I can also ping google.com from the Ubuntu client.
Unfortunately the Ubuntu machine cannot actually connect to any websites. All it can do is ping domains. EDIT: The ping does not actually work - only the domain resolving works. Sorry for my confusion.
What is wrong with my setup? I have the defaults set and was hoping that the NetworkManager wizard would "just work".
Last edited by debian_wifi_user on 2022-01-17 00:16, edited 1 time in total.
- argentwolf
- Posts: 201
- Joined: 2021-09-05 23:21
- Has thanked: 185 times
- Been thanked: 15 times
Re: Client has DNS but no TCP/IP access when connected to Debian host via WiFi
You do have a Wireless Access Point (WAP) or you're trying to make your Debian machine with a wireless NIC a WAP?
https://wiki.debian.org/NetworkManager
https://wiki.debian.org/NetworkManager
Vanguard Debian, because nothing's worse than doing nothing, whimsically!
32-bit | 2 Duo T5270 @ 1.40GHz x 2 CPU | 3.9GiB RAM | NV86 117MiB GPU | 465.76GiB SSD
64-bit | i7-4790 @ 3.60GHz x 8 CPU | 15.6GiB RAM | NVD9 1.9GiB GPU | 931.51GiB SSD
32-bit | 2 Duo T5270 @ 1.40GHz x 2 CPU | 3.9GiB RAM | NV86 117MiB GPU | 465.76GiB SSD
64-bit | i7-4790 @ 3.60GHz x 8 CPU | 15.6GiB RAM | NVD9 1.9GiB GPU | 931.51GiB SSD
Re: Client has DNS but no TCP/IP access when connected to Debian host via WiFi
If you can "ping domains" from your Ubuntu client it means that both DNS resolution and routing should be working fine.
Can you actual resolve domains, or have you pinged 1.1.1.1 or 8.8.8.8 or such?
If domain resolution does NOT work (check with e.g. "host www.google.com"), have a look at your /etc/resolv.conf (again, in your client, not at the debian host).
Can you actual resolve domains, or have you pinged 1.1.1.1 or 8.8.8.8 or such?
If domain resolution does NOT work (check with e.g. "host www.google.com"), have a look at your /etc/resolv.conf (again, in your client, not at the debian host).
- ralph.ronnquist
- Posts: 342
- Joined: 2015-12-19 01:07
- Location: Melbourne, Australia
- Been thanked: 6 times
Re: Client has DNS but no TCP/IP access when connected to Debian host via WiFi
You might need to tell the debian machine kernel that forwarding is ok, by
And for convenience you might also want to add the setting into a file in /etc/systctl.d/
Code: Select all
# sysctl net.ipv4.ip_forward=1
-
- Posts: 22
- Joined: 2019-11-19 08:47
- Has thanked: 4 times
Re: Client has DNS but no TCP/IP access when connected to Debian host via WiFi
I want to setup my Debian machine as a wireless access point.argentwolf wrote: ↑2022-01-14 00:03 You do have a Wireless Access Point (WAP) or you're trying to make your Debian machine with a wireless NIC a WAP?
https://wiki.debian.org/NetworkManager
-
- Posts: 22
- Joined: 2019-11-19 08:47
- Has thanked: 4 times
Re: Client has DNS but no TCP/IP access when connected to Debian host via WiFi
I cannot ping 1.1.1.1 from the Ubuntu client.reinob wrote: ↑2022-01-14 07:32 If you can "ping domains" from your Ubuntu client it means that both DNS resolution and routing should be working fine.
Can you actual resolve domains, or have you pinged 1.1.1.1 or 8.8.8.8 or such?
If domain resolution does NOT work (check with e.g. "host www.google.com"), have a look at your /etc/resolv.conf (again, in your client, not at the debian host).
If I ping google.com, it resolves the IP address but the ping fails. Sorry for my original post where I said I could ping domains - I cannot. All I see is it resolve the domain and fail to ping.
-
- Posts: 22
- Joined: 2019-11-19 08:47
- Has thanked: 4 times
Re: Client has DNS but no TCP/IP access when connected to Debian host via WiFi
I tried this but it didn't change anything alas.ralph.ronnquist wrote: ↑2022-01-14 09:37 You might need to tell the debian machine kernel that forwarding is ok, byAnd for convenience you might also want to add the setting into a file in /etc/systctl.d/Code: Select all
# sysctl net.ipv4.ip_forward=1
- ralph.ronnquist
- Posts: 342
- Joined: 2015-12-19 01:07
- Location: Melbourne, Australia
- Been thanked: 6 times
Re: Client has DNS but no TCP/IP access when connected to Debian host via WiFi
And then you probably also need the debian machine to masquerade the network traffic, which you'd do as follows with iptables installed and assuming your Ethernet interface name is ens5:
Code: Select all
# iptables -t nat -A POSTROUTING -o ens5 -j MASQUERADE
-
- Posts: 22
- Joined: 2019-11-19 08:47
- Has thanked: 4 times
Re: Client has DNS but no TCP/IP access when connected to Debian host via WiFi
Thanks a lot. This almost got me there. I ran this command and it said:ralph.ronnquist wrote: ↑2022-01-17 05:31 And then you probably also need the debian machine to masquerade the network traffic, which you'd do as follows with iptables installed and assuming your Ethernet interface name is ens5:Code: Select all
# iptables -t nat -A POSTROUTING -o ens5 -j MASQUERADE
Code: Select all
iptables v1.8.7 (nf_tables): CHAIN_ADD failed (Operation not supported): chain POSTROUTING
Code: Select all
# update-alternatives --set iptables /usr/sbin/iptables-legacy
update-alternatives: using /usr/sbin/iptables-legacy to provide /usr/sbin/iptables (iptables) in manual mode
- argentwolf
- Posts: 201
- Joined: 2021-09-05 23:21
- Has thanked: 185 times
- Been thanked: 15 times
Re: Client has DNS but no TCP/IP access when connected to Debian host via WiFi
Huh! 'Raspberry Pi' is important information given at the beginning of your request for help...
Vanguard Debian, because nothing's worse than doing nothing, whimsically!
32-bit | 2 Duo T5270 @ 1.40GHz x 2 CPU | 3.9GiB RAM | NV86 117MiB GPU | 465.76GiB SSD
64-bit | i7-4790 @ 3.60GHz x 8 CPU | 15.6GiB RAM | NVD9 1.9GiB GPU | 931.51GiB SSD
32-bit | 2 Duo T5270 @ 1.40GHz x 2 CPU | 3.9GiB RAM | NV86 117MiB GPU | 465.76GiB SSD
64-bit | i7-4790 @ 3.60GHz x 8 CPU | 15.6GiB RAM | NVD9 1.9GiB GPU | 931.51GiB SSD
-
- Posts: 22
- Joined: 2019-11-19 08:47
- Has thanked: 4 times
Re: Client has DNS but no TCP/IP access when connected to Debian host via WiFi
Why? I'm not using a Raspberry Pi.argentwolf wrote: ↑2022-01-18 14:05 Huh! 'Raspberry Pi' is important information given at the beginning of your request for help...
- argentwolf
- Posts: 201
- Joined: 2021-09-05 23:21
- Has thanked: 185 times
- Been thanked: 15 times
Re: Client has DNS but no TCP/IP access when connected to Debian host via WiFi
My bad!
Vanguard Debian, because nothing's worse than doing nothing, whimsically!
32-bit | 2 Duo T5270 @ 1.40GHz x 2 CPU | 3.9GiB RAM | NV86 117MiB GPU | 465.76GiB SSD
64-bit | i7-4790 @ 3.60GHz x 8 CPU | 15.6GiB RAM | NVD9 1.9GiB GPU | 931.51GiB SSD
32-bit | 2 Duo T5270 @ 1.40GHz x 2 CPU | 3.9GiB RAM | NV86 117MiB GPU | 465.76GiB SSD
64-bit | i7-4790 @ 3.60GHz x 8 CPU | 15.6GiB RAM | NVD9 1.9GiB GPU | 931.51GiB SSD