Debian on Gemini - Usage

[galodoido]

OK so basically the connman and the NM are both doing the same for your WiFi, you get a connection but for some reason the auto redirect to guest login is failing.

Correct, in connman and NM, I can see that it says I'm connected to the guest network, but in browsers, it fails to go to the guest login page.

So can you go back to the D9 laptop and get to the guest network login web page, check whats in the address bar, then see what happens if you type that into the gemini address bar.

Just did this, but I still get 'Unable to Connect' error message.....

I also assume you've tried both firefox and chromium.

Correct, have tried both browsers......


 

Hi,

I can't do the test because I have no network with captive login page near my house.
But I saw 3 possibilities searching google :

1-


Make the connection to the WIFI.

 If you are connected, but can not browse the web, Open a terminal and type sudo  route. You should receive a display such as:


Destination Gateway Genmask Flags Metric Ref Use Iface


If you type the default Gateway (i.e., 10.1.0.1) into your browser's address bar, you will receive the WIFI login page.

maybe you can Enjoy your time on the internet.

2-

When you are behind a captive portal you can open a browse to a HTTP site (not HTTPS), the portal will redirect you to a login page.

Maybe you are not redirected because you are trying to open a HTTPS site. The portal usually blocks that entirely, because attempting to redirect it would anyway result in a certificate warning.

3-

sudo dpkg-reconfigure resolvconf


good luck !

[ArchiMark]

Thank you for your help, galodoido. Greatly appreciate it!

Have tried 1 and 2....but no go....

For number 2, I use neverssl.com....

Can try 3 and test on Monday, when I am back at office.....

[galodoido]

Thank you for your help, galodoido. Greatly appreciate it!

Have tried 1 and 2....but no go....

For number 2, I use neverssl.com....

Can try 3 and test on Monday, when I am back at office.....

Ok.

I saw this also searching on google :

https://blog.ham1.co.uk/2016/02/06/cannot-s...ux-ubuntu-mint/

I had trouble connecting to the Internet while abroad using the hotel1 WiFi2 on my Linux Mint laptop.

The Problem
I could connect to the WiFi and obtain an IP address, however, the hotel’s internet sign-in page failed to load in both Chromium or Firefox. Turns out it was a DNS oddity.

The Solution
Update (thanks to Abe)
For Ubuntu 17.04 simply run:

sudo dhclient -r
Original Solution
When I had this problem on Linux Mint the following solved the problem for me:

Comment out dns=dnsmasq in /etc/NetworkManager/NetworkManager.conf (i.e. put a # at the beginning of the line)
Restart network-manager: sudo service networking restart
Additional Steps
The following commands might also be required for some:

sudo dhclient -r
sudo dhclient

[ArchiMark]

Thank you for your help, galodoido. Greatly appreciate it!

Have tried 1 and 2....but no go....

For number 2, I use neverssl.com....

Can try 3 and test on Monday, when I am back at office.....

Ok.

I saw this also searching on google :

https://blog.ham1.co.uk/2016/02/06/cannot-s...ux-ubuntu-mint/

I had trouble connecting to the Internet while abroad using the hotel1 WiFi2 on my Linux Mint laptop.

The Problem
I could connect to the WiFi and obtain an IP address, however, the hotel’s internet sign-in page failed to load in both Chromium or Firefox. Turns out it was a DNS oddity.

The Solution
Update (thanks to Abe)
For Ubuntu 17.04 simply run:

sudo dhclient -r
Original Solution
When I had this problem on Linux Mint the following solved the problem for me:

Comment out dns=dnsmasq in /etc/NetworkManager/NetworkManager.conf (i.e. put a # at the beginning of the line)
Restart network-manager: sudo service networking restart
Additional Steps
The following commands might also be required for some:

sudo dhclient -r
sudo dhclient

THANK YOU for the additional suggestions....

Will report back on Monday after I do more testing.....

[ArchiMark]

At office...tried

3 - sudo dpkg-reconfigure resolvconf

No change, can't get to login page....


Tried the other suggestions:

I saw this also searching on google :

https://blog.ham1.co.uk/2016/02/06/cannot-s...ux-ubuntu-mint/

I had trouble connecting to the Internet while abroad using the hotel1 WiFi2 on my Linux Mint laptop.

The Problem
I could connect to the WiFi and obtain an IP address, however, the hotel’s internet sign-in page failed to load in both Chromium or Firefox. Turns out it was a DNS oddity.

The Solution
Update (thanks to Abe)
For Ubuntu 17.04 simply run:

sudo dhclient -r

Nope, that did not work....

Original Solution
When I had this problem on Linux Mint the following solved the problem for me:

Comment out dns=dnsmasq in /etc/NetworkManager/NetworkManager.conf (i.e. put a # at the beginning of the line)
Restart network-manager: sudo service networking restart

Looked at NetworkManager.conf. It did not have the line "dns=dnsmasq" in it. So, nothing to comment out.....

Additional Steps
The following commands might also be required for some:

sudo dhclient -r
sudo dhclient

Nope, that did not work....and got error messages that "dhclient" could not be found....


 

[galodoido]

At office...tried

3 - sudo dpkg-reconfigure resolvconf

No change, can't get to login page....


Tried the other suggestions:

I saw this also searching on google :

https://blog.ham1.co.uk/2016/02/06/cannot-s...ux-ubuntu-mint/

I had trouble connecting to the Internet while abroad using the hotel1 WiFi2 on my Linux Mint laptop.

The Problem
I could connect to the WiFi and obtain an IP address, however, the hotel’s internet sign-in page failed to load in both Chromium or Firefox. Turns out it was a DNS oddity.

The Solution
Update (thanks to Abe)
For Ubuntu 17.04 simply run:

sudo dhclient -r

Nope, that did not work....

Original Solution
When I had this problem on Linux Mint the following solved the problem for me:

Comment out dns=dnsmasq in /etc/NetworkManager/NetworkManager.conf (i.e. put a # at the beginning of the line)
Restart network-manager: sudo service networking restart

Looked at NetworkManager.conf. It did not have the line "dns=dnsmasq" in it. So, nothing to comment out.....

Additional Steps
The following commands might also be required for some:

sudo dhclient -r
sudo dhclient

Nope, that did not work....and got error messages that "dhclient" could not be found....


 

This seems to be a problem. Let's continue searching.
Good luck !

[ArchiMark]

This seems to be a problem. Let's continue searching.
Good luck !

Yes, indeed, and a very strange one!

Especially, since I can connect to networks elsewhere with no problem.....

Wish there was a way to diagnose the problem....

[Varti]

Seem like dhclient isn't installed by default on the Gemini, dhcpcd might be used instead, you can check this with

Code: [Select]

type -a dhclient
type -a dhcpcd
Reference: https://superuser.com/questions/393887/dhcl...real-difference

In your case it looks like the DHCP is assigning you a default gateway, but your system for some reason can't reach it. What is the IP address you have been assigned, and what does ping (IP address) return? Also, it could be helpful to see from the logs what does the DHCP client output when getting an IP address:

Code: [Select]

journalctl | grep -Ei 'dhcp'or

Code: [Select]

cat /var/log/syslog | grep -Ei 'dhcp'https://superuser.com/questions/944687/how-...hcp-client-does

Also, please post your routing table with

Code: [Select]

ip routesince there might be already a static route to a different gateway that gets in the way.

Varti

[ArchiMark]

THANKS for your help, varti!

Here's info requested:

Code: [Select]

$ type -a dhclient
dhclient: not found

$ type -a dhcpcd
dhcpcd: not found

Code: [Select]

$ hostname -I

10.15.19.82  192.168.0.71

Code: [Select]

$ ping -c 3 192.168.0.71

PING 192.168.0.71 (192.168.0.71) 56(84) bytes of data.
64 bytes from 192.168.0.71: icmp_seq=1 ttl=64 time=0.225 ms
64 bytes from 192.168.0.71: icmp_seq=2 ttl=64 time=0.459 ms
64 bytes from 192.168.0.71: icmp_seq=3 ttl=64 time=0.415 ms

--- 192.168.0.71 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003 ms
rtt min/avg/max/mdev = 0.225/0.366/0.459/0.102 ms

Code: [Select]

$ sudo journalctl | grep -Ei ‘dhcp’

Sudo: unable to resolve host localhost.localdomain: Connection refused

Jun 18 06:37:49 localhost dhcpd [685]: Wrote 0 leases to leases file.

Jun 18 06:37:50 localhost dhcpd [685]: Server starting service.

Jun 18 06:39:00 localhost.localdomain Network Manager [702]: [1529329140.0248] dhcp-init: Using DHCP client ‘dhclient’

Jun 18 06:39:00 localhost.localdomain Network Manager [702]: [1529329140.0264] dhcp4 (wlan0) : activation: beginning transaction (timeout in 45 seconds)

Jun 18 06:39:00 localhost.localdomain Network Manager [702]: [1529329140.0345] dhcp4 (wlan0): dhclient started with pid 2609

Jun 18 06:39:00 localhost.localdomain dhclient [2609]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7

Jun 18 06:39:01 localhost.localdomain dhclient [2609]: DHCPREQUEST of 192.168.0.71 on wlan0 to 255.255.255.255 port 67

Jun 18 06:39:01 localhost.localdomain dhclient [2609] DHCPOFFER of 192.168.0.71 from 192.168.0.2

Jun 18 06:39:01 localhost.localdomain NetworkManager [702]: [1529329140.1894] dhcp4 (wlan0):  address 192.168.0.71

Jun 18 06:39:01 localhost.localdomain NetworkManager [702]: [1529329140.1906] dhcp4 (wlan0):  plen 24 (255.255.255.255)

Jun 18 06:39:01 localhost.localdomain NetworkManager [702]: [1529329140.1907] dhcp4 (wlan0):  gateway 192.168.0.1

Jun 18 06:39:01 localhost.localdomain NetworkManager [702]: [1529329140.1908] dhcp4 (wlan0):  server identifier 192.168.0.2

Jun 18 06:39:01 localhost.localdomain NetworkManager [702]: [1529329140.1908] dhcp4 (wlan0):  lease time 1800

Jun 18 06:39:01 localhost.localdomain NetworkManager [702]: [1529329140.1909] dhcp4 (wlan0):  nameserver ‘8.8.4.4’

Jun 18 06:39:01 localhost.localdomain NetworkManager [702]: [1529329140.1909] dhcp4 (wlan0):  nameserver ‘8.8.8.8’

Jun 18 06:39:01 localhost.localdomain NetworkManager [702]: [1529329140.1910] dhcp4 (wlan0):  state change unknown -> bound

Code: [Select]

$ ip route
Default via 192.168.0.1 dev wlan0 proto static metric 600
10.0.0.0/8 dev rndis0 proto kernel scope link src 10.15.19.82
192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.71
192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.71 metric 600

Think this is everything....if not, please let me know...

Thanks,

Mark

UPDATE

Went to the place nearby that has free WiFi. Last time I got to their login page with no problem.

Today, I could not get to login page. Even though in NetworkManager, I was connected to their network.

So, things are getting worse.....

 

[raesene]

<snip>

Code: [Select]

$ ip route
Default via 192.168.0.1 dev wlan0 proto static metric 600
10.0.0.0/8 dev rndis0 proto kernel scope link src 10.15.19.82
192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.71
192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.71 metric 600

so I've not got my gemini yet to be  able to check, but I think I can see a problem for you there, which might explain the issue.  You've got two interfaces (wlan0 and rndis0) .  rndis0 has got a route to 10.0.0.0/8 which means that any traffic for addresses in that range (IIRC your captive portal was in the 10.x range?) will go over that interface, when presumably you're wanting it to go over the wlan0 interface.

In theory, you should be able to delete the route in question to see if that affects things (e.g. https://serverfault.com/questions/181094/ho...-routing-table) , but I'm not sure without seeing a setup, why that route has been put in place...

[ArchiMark]

<snip>

Code: [Select]

$ ip route
Default via 192.168.0.1 dev wlan0 proto static metric 600
10.0.0.0/8 dev rndis0 proto kernel scope link src 10.15.19.82
192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.71
192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.71 metric 600

so I've not got my gemini yet to be  able to check, but I think I can see a problem for you there, which might explain the issue.  You've got two interfaces (wlan0 and rndis0) .  rndis0 has got a route to 10.0.0.0/8 which means that any traffic for addresses in that range (IIRC your captive portal was in the 10.x range?) will go over that interface, when presumably you're wanting it to go over the wlan0 interface.

In theory, you should be able to delete the route in question to see if that affects things (e.g. https://serverfault.com/questions/181094/ho...-routing-table) , but I'm not sure without seeing a setup, why that route has been put in place...

THANK YOU, raesene!

Sounds like a reasonable possibility to explain the problem.....

In post #26, back a few pages, the Great Adam Boardman, our Debian on Gemini dev, explained what rndis0 is for:

The rndis is the usb tethering that can be used for initial setup when connected to a PC via the USB cable.

So, don't want to mess things up in case I need to tether Gemini to PC again....

Any advice on how to adjust routing parameters to let wlan0 get to web address instead of rndis0 ?

Thanks,

Mark

[galodoido]

<snip>

Code: [Select]

$ ip route
Default via 192.168.0.1 dev wlan0 proto static metric 600
10.0.0.0/8 dev rndis0 proto kernel scope link src 10.15.19.82
192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.71
192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.71 metric 600

so I've not got my gemini yet to be  able to check, but I think I can see a problem for you there, which might explain the issue.  You've got two interfaces (wlan0 and rndis0) .  rndis0 has got a route to 10.0.0.0/8 which means that any traffic for addresses in that range (IIRC your captive portal was in the 10.x range?) will go over that interface, when presumably you're wanting it to go over the wlan0 interface.

In theory, you should be able to delete the route in question to see if that affects things (e.g. https://serverfault.com/questions/181094/ho...-routing-table) , but I'm not sure without seeing a setup, why that route has been put in place...

THANK YOU, raesene!


Hi



Sounds like a reasonable possibility to explain the problem.....

In post #26, back a few pages, the Great Adam Boardman, our Debian on Gemini dev, explained what rndis0 is for:

The rndis is the usb tethering that can be used for initial setup when connected to a PC via the USB cable.

So, don't want to mess things up in case I need to tether Gemini to PC again....

Any advice on how to adjust routing parameters to let wlan0 get to web address instead of rndis0 ?

Thanks,

Mark

Hi ArchiMArk,

I had  a similar problem when configuring my usb modem 3g. It was connected, but all sites were unreachable.
After a long search I found that resolv.conf was always rewrited when the gemini was rebooted.
So I've installed dnsmasq ( apt-get install dnsmasq) and put the open dns ip's  at the end of /etc/dnsmasq.conf file like below ( sudo nano /etc/dnsmasq.conf )

server 208.67.222.222
server 208.67.220.220

Saved and rebooted the gemini.
My problem was solved.
I think your problem can be solved with this.
Good luck.

[Adam Boardman]

Sorry completely not paying attention to this, so yes the usb-tethering was grabbing all the 10.* IP addresses (as indicated by ip route) so as your local network was on that range things were all confused. I've just updated the usb tethering to only nab 10.15.19.* so that should make it a lot less likely to conflict with various networks you might like to connect to.

You'll need to apt update & upgrade, and reboot for it to take effect.

[ArchiMark]

Thank you, galodoido and Adam for your help.

Out of office today. Will upgrade system as suggested and test when I get back to office on Monday and report back the results.

[ArchiMark]

Woo Hoo!!!!

Finally able to connect to the guest network at my workplace!

THANKS to ALL who provided input to get this resolved. Truly appreciate it greatly!

It proves what a great community is here at OESF.

This is a BIG relief having internet connection at my workplace as I spend a lot of time here during the week.

Now, onto more fun things with Gemini.....

 

Mark