No wifi logon page in FF

English Network/Internet
#1

I log on using KDE and NetworkManager connects to a wifi access point, but when I start FireFox I don’t get the wifi logon page. This used to work, and I’m not sure what I changed.

Are there any diagnostic data that I should collect? Any ideas? Thanks.

#2

Please post:

ping -c1 1.1.1.1

ping -c1 google.com

cat /etc/resolv.conf
#3

Hello,

Maybe it’s a cache problem of firefox.
Delete your favo etc.

often you also have to go to a website that does not use https
Than Access points usually come with the login page

Suc6!

#4

I mean your history NOT your favo

#5 
linux-0ksw:~ # ping -c1 1.1.1.1
PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
--- 1.1.1.1 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms


linux-0ksw:~ # ping -c1 google.com
ping: google.com: Name or service not known


linux-0ksw:~ # cat /etc/resolv.conf
### /etc/resolv.conf file autogenerated by netconfig!
#
# Before you change this file manually, consider to define the
# static DNS configuration using the following variables in the
# /etc/sysconfig/network/config file:
#     NETCONFIG_DNS_STATIC_SEARCHLIST
#     NETCONFIG_DNS_STATIC_SERVERS
#     NETCONFIG_DNS_FORWARDER
# or disable DNS configuration updates via netconfig by setting:
#     NETCONFIG_DNS_POLICY=''
#
# See also the netconfig(8) manual page and other documentation.
#
# Note: Manual change of this file disables netconfig too, but
# may get lost when this file contains comments or empty lines
# only, the netconfig settings are same with settings in this
# file and in case of a "netconfig update -f" call.
#
### Please remove (at least) this line when you modify the file!

Clearing the FF history does not resolve the problem. I also tried logging on with Gnome instead of KDE, and got the same results.

#6

this result is normal you are not connected to access point

comes the login page if you visit a website that does not use ssl / https

#7

I tried using the http schema and got the same results.

#8

I think, only a DNS Problem.
As root:

netconfig update -f
#9

I concur with this. It is a name resolution issue ie no valid name server applied.

#10

That did it. Thanks.