I installed FC14 today on my laptop. I can connect to the Internet and download software. I can also ping sites out on the Internet from the command line. However, the browser refuses to load any pages and Evolution won't connect to a mail server. I tried turning off the firewall altogether and this made no difference. Any ideas on what the issue could be?
On 02/26/11 18:29, Jim Philips wrote:
I installed FC14 today on my laptop. I can connect to the Internet and download software. I can also ping sites out on the Internet from the command line. However, the browser refuses to load any pages and Evolution won't connect to a mail server. I tried turning off the firewall altogether and this made no difference. Any ideas on what the issue could be?
I don't know about evolution, but I've had a recurring problem with firefox in which for unknown reasons DNS lookups start to fail. I try chrome and everything works, but firefox will not connect. After a while firefox will suddenly start working again.
Paolo
I discovered that while I can ping to www.google.com, I can't do a traceroute to the same address. It won't resolve the name.
On Sat, Feb 26, 2011 at 8:29 PM, Jim Philips briarpatch.jim@gmail.comwrote:
I installed FC14 today on my laptop. I can connect to the Internet and download software. I can also ping sites out on the Internet from the command line. However, the browser refuses to load any pages and Evolution won't connect to a mail server. I tried turning off the firewall altogether and this made no difference. Any ideas on what the issue could be?
On Sat, 2011-02-26 at 20:29 -0500, Jim Philips wrote:
I installed FC14 today on my laptop. I can connect to the Internet and download software. I can also ping sites out on the Internet from the command line. However, the browser refuses to load any pages and Evolution won't connect to a mail server. I tried turning off the firewall altogether and this made no difference. Any ideas on what the issue could be?
Which browser? Firefox and Evolution both use NetworkManager to determine if the machine is connected. Even if the network is working, if NM is not configured to manage the interface, these apps will think there is no connection.
poc
On 02/26/2011 08:43 PM, Patrick O'Callaghan wrote:
Which browser? Firefox and Evolution both use NetworkManager to determine if the machine is connected. Even if the network is working, if NM is not configured to manage the interface, these apps will think there is no connection.
That's interesting. I have NetworkManager disabled on this box because if I don't it throws away my DNS numbers every time I reboot. I use the older network service which does what I want the way I want it and Firefox has never had the slightest difficulty finding my connection.
On Sat, 2011-02-26 at 21:08 -0800, Joe Zeff wrote:
On 02/26/2011 08:43 PM, Patrick O'Callaghan wrote:
Which browser? Firefox and Evolution both use NetworkManager to determine if the machine is connected. Even if the network is working, if NM is not configured to manage the interface, these apps will think there is no connection.
That's interesting. I have NetworkManager disabled on this box because if I don't it throws away my DNS numbers every time I reboot. I use the older network service which does what I want the way I want it and Firefox has never had the slightest difficulty finding my connection.
If NM is disabled, then no problem. The difficulty is when it's enabled but not properly configured. This is well-known and has been discussed on this and other lists before. See also http://live.gnome.org/Evolution/FAQ#Why_is_Evolution_offline_when_my_net_con... for example.
poc
are you sure about this???
where is the pointer to docs to state this?
i seriously doubt that firefox has any way of knowing about NM specifically..
but it is curious that you can ping, but not access via FF.. what happens if you download/check with Opera..
On Sat, Feb 26, 2011 at 8:43 PM, Patrick O'Callaghan pocallaghan@gmail.com wrote:
On Sat, 2011-02-26 at 20:29 -0500, Jim Philips wrote:
I installed FC14 today on my laptop. I can connect to the Internet and download software. I can also ping sites out on the Internet from the command line. However, the browser refuses to load any pages and Evolution won't connect to a mail server. I tried turning off the firewall altogether and this made no difference. Any ideas on what the issue could be?
Which browser? Firefox and Evolution both use NetworkManager to determine if the machine is connected. Even if the network is working, if NM is not configured to manage the interface, these apps will think there is no connection.
poc
-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
On Sun, Feb 27, 2011 at 1:20 AM, bruce badouglas@gmail.com wrote:
On Sat, Feb 26, 2011 at 8:43 PM, Patrick O'Callaghan pocallaghan@gmail.com wrote:
On Sat, 2011-02-26 at 20:29 -0500, Jim Philips wrote:
I installed FC14 today on my laptop. I can connect to the Internet and download software. I can also ping sites out on the Internet from the command line. However, the browser refuses to load any pages.
Which browser? Firefox and Evolution both use NetworkManager to determine if the machine is connected. Even if the network is working, if NM is not configured to manage the interface, these apps will think there is no connection.
are you sure about this???
where is the pointer to docs to state this?
i seriously doubt that firefox has any way of knowing about NM specifically..
but it is curious that you can ping, but not access via FF.. what happens if you download/check with Opera..
If NM's active but isn't managing an interface, it reports to FF that the interface is down.
http://lists.fedoraproject.org/pipermail/devel/2009-November/042414.html
but the OP had stated that NM wasn't active..
and i'm still not convinced that NM is "reporting" to Firefox. Which isn't to say that FF isn't accessing something to connect to the the port.
On Sat, Feb 26, 2011 at 10:41 PM, Tom H tomh0665@gmail.com wrote:
On Sun, Feb 27, 2011 at 1:20 AM, bruce badouglas@gmail.com wrote:
On Sat, Feb 26, 2011 at 8:43 PM, Patrick O'Callaghan pocallaghan@gmail.com wrote:
On Sat, 2011-02-26 at 20:29 -0500, Jim Philips wrote:
I installed FC14 today on my laptop. I can connect to the Internet and download software. I can also ping sites out on the Internet from the command line. However, the browser refuses to load any pages.
Which browser? Firefox and Evolution both use NetworkManager to determine if the machine is connected. Even if the network is working, if NM is not configured to manage the interface, these apps will think there is no connection.
are you sure about this???
where is the pointer to docs to state this?
i seriously doubt that firefox has any way of knowing about NM specifically..
but it is curious that you can ping, but not access via FF.. what happens if you download/check with Opera..
If NM's active but isn't managing an interface, it reports to FF that the interface is down.
http://lists.fedoraproject.org/pipermail/devel/2009-November/042414.html
users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
On Sat, 2011-02-26 at 23:52 -0800, bruce wrote:
but the OP had stated that NM wasn't active..
But... does that mean they've disabled the service, or they've simply not configured it for use.
On Sat, 2011-02-26 at 23:52 -0800, bruce wrote:
but the OP had stated that NM wasn't active..
and i'm still not convinced that NM is "reporting" to Firefox. Which isn't to say that FF isn't accessing something to connect to the the port.
[Please don't top-post on this list. See the Guidelines]
The OP didn't mention NM, so he could hardly have said that it wasn't active. And NM isn't "reporting" anything to Firefox. NM is registering a service (presumably via D-bus, though I haven't checked) and FF is picking it up. That's the way desktop apps are supposed to work.
poc
On Sun, Feb 27, 2011 at 10:02 AM, Patrick O'Callaghan <pocallaghan@gmail.com
wrote:
On Sat, 2011-02-26 at 23:52 -0800, bruce wrote:
but the OP had stated that NM wasn't active..
and i'm still not convinced that NM is "reporting" to Firefox. Which isn't to say that FF isn't accessing something to connect to the the port.
[Please don't top-post on this list. See the Guidelines]
The OP didn't mention NM, so he could hardly have said that it wasn't active. And NM isn't "reporting" anything to Firefox. NM is registering a service (presumably via D-bus, though I haven't checked) and FF is picking it up. That's the way desktop apps are supposed to work.
poc
I didn't do anything with Network Manager at the beginning, nor was I
prompted to. Shouldn't there have been a wizard to lead me through settings?
By the way, things all work with my wired connection now. Haven't gotten wireless working yet. Need another test.
On Sun, 2011-02-27 at 10:07 -0500, Jim Philips wrote:
I didn't do anything with Network Manager at the beginning, nor was
I prompted to. Shouldn't there have been a wizard to lead me through settings?
Is this a fresh install or an upgrade? I would expect a fresh install to give some prompting at install time. OTOH an upgrade would tend not to mess with existing network settings. However if you feel this is wrong then report it to BZ.
Note that many older apps don't ask NM about connectivity, which is why they still work. This is definitely confusing as the ones that don't work are those which have taken on board the NM model and believe what it says.
poc
On 2/27/11 8:15 AM, Patrick O'Callaghan wrote:
On Sun, 2011-02-27 at 10:07 -0500, Jim Philips wrote:
I didn't do anything with Network Manager at the beginning, nor was
I prompted to. Shouldn't there have been a wizard to lead me through settings?
Is this a fresh install or an upgrade? I would expect a fresh install to give some prompting at install time. OTOH an upgrade would tend not to mess with existing network settings. However if you feel this is wrong then report it to BZ.
Note that many older apps don't ask NM about connectivity, which is why they still work. This is definitely confusing as the ones that don't work are those which have taken on board the NM model and believe what it says.
the real question is does nslookup or dig work?
If not networking is not setup properly. If it does, then something else is not working...
James McKenzie
On Sun, Feb 27, 2011 at 10:15 AM, Patrick O'Callaghan <pocallaghan@gmail.com
wrote:
On Sun, 2011-02-27 at 10:07 -0500, Jim Philips wrote:
I didn't do anything with Network Manager at the beginning, nor was
I prompted to. Shouldn't there have been a wizard to lead me through settings?
Is this a fresh install or an upgrade? I would expect a fresh install to give some prompting at install time. OTOH an upgrade would tend not to mess with existing network settings. However if you feel this is wrong then report it to BZ.
This was a fresh install of Fedora. So, that was why I would have expected
some kind of configuration wizard. Do new users normally see one? Or did something fail in my case?
On Sun, Feb 27, 2011 at 10:07 AM, Jim Philips briarpatch.jim@gmail.com wrote:
I didn't do anything with Network Manager at the beginning, nor was I prompted to. Shouldn't there have been a wizard to lead me through settings? By the way, things all work with my wired connection now. Haven't gotten wireless working yet. Need another test.
From the F14 User Guide:
7.1. The Network Manager Applet
Network Manager has been the default network configuration application for the GNOME desktop since Fedora 11. This application can be used to configure a wide variety of network devices and connections that allow you to access the Internet. Network Manager is used to configure all your network connections from wired to wireless network as well as xDSL, VPN, and mobile broadband with extend support for Bluetooth DUN. And if you don't know about DNS, DHCP or pppoe, Network Manager does it all for you. If you use your computer at home, and have an xDSL connection that is already working, you do not need to configure anything. Just connect to the wired network. With a wireless or broadband connection, the steps needed to setup them are simple and easy to do, just a few clicks and fill in your personal information.
Network Manager executes automatically when you start your session and it is visible in GNOME as the nm-applet icon on the top right of the desktop. If you move the mouse over it, it shows the active connection.
Left-clicking on the icon provides a context sensitive menu divided in three sections. The first section shows the active connection or connections along with an option to Disconnect The second section views the other available connections. Switch to one of them with a simple click and the previous one closes automatically. The VPN Connections submenu provides option to configure or disconnect to a VPN.
Right clicking on the nm-applet show another context sensitive menu that allows you to Enable Networking and if available Enable Wireless or Enable Mobile Broadband. You can also Enable Notifications as well as view the Connection Information or Edit Connections... When editing connections, Network Manager opens in a new window, in which you configure the network devices and connections. The About option provides information about the project and the people that created the application, with a link to the Project Web-Site .
Just like its GNOME counterpart, KDE provides an applet interface for NetworkManager, known as KNetworkManager. This application development was started by Novell and provides an integrated QT-based experience with similar usage and configuration as its GNOME counterpart, nm-applet.
From the F14 Deployment Guide:
Chapter 5. Network Configuration
NetworkManager is a dynamic network control and configuration system that attempts to keep network devices and connections up and active when they are available. NetworkManager consists of a core daemon, a GNOME Notification Area applet that provides network status information, and graphical configuration tools that can create, edit and remove connections and interfaces. NetworkManager can be used to configure the following types of connections: Ethernet, wireless, mobile broadband (such as cellular 3G), and DSL and PPPoE (Point-to-Point over Ethernet). In addition, NetworkManager allows for the configuration of network aliases, static routes, DNS information and VPN connections, as well as many connection-specific parameters. Finally, NetworkManager provides a rich API via D-Bus which allows applications to query and control network configuration and state.
Previous versions of Fedora shipped with the Network Administration Tool, which was commonly known as system-config-network after its command line invocation. In Fedora 14, NetworkManager replaces the former Network Administration Tool while providing enhanced functionality, such as user-specific and mobile broadband configuration. It is also possible to configure the network in Fedora 14 by editing interface configuration files; refer to Chapter 4, Network Interfaces for more information.
NetworkManager may be installed by default on Fedora. To ensure that it is, first run the following command as the root user:
~]# yum install NetworkManager
5.1. The NetworkManager Daemon
The NetworkManager daemon runs with root privileges and is usually configured to start up at boot time. You can determine whether the NetworkManager daemon is running by entering this command as root:
~]# service NetworkManager status NetworkManager (pid 1527) is running...
The service command will report NetworkManager is stopped if the NetworkManager service is not running. To start it for the current session:
~]# service NetworkManager start
Run the chkconfig command to ensure that NetworkManager starts up every time the system boots:
~]# chkconfig NetworkManager on
For more information on starting, stopping and managing services and runlevels, refer to Chapter 7, Controlling Access to Services.
On Sun, 2011-02-27 at 10:07 -0500, Jim Philips wrote:
On Sun, Feb 27, 2011 at 10:02 AM, Patrick O'Callaghan pocallaghan@gmail.com wrote: On Sat, 2011-02-26 at 23:52 -0800, bruce wrote: > but the OP had stated that NM wasn't active.. > > and i'm still not convinced that NM is "reporting" to Firefox. Which > isn't to say that FF isn't accessing something to connect to the the > port.
[Please don't top-post on this list. See the Guidelines] The OP didn't mention NM, so he could hardly have said that it wasn't active. And NM isn't "reporting" anything to Firefox. NM is registering a service (presumably via D-bus, though I haven't checked) and FF is picking it up. That's the way desktop apps are supposed to work. pocI didn't do anything with Network Manager at the beginning, nor was I prompted to. Shouldn't there have been a wizard to lead me through settings?
What settings of NM do you want to be led through. NM wireless has always worked for me out of the box?
By the way, things all work with my wired connection now. Haven't gotten wireless working yet. Need another test.
On Sun, Feb 27, 2011 at 10:02 AM, Patrick O'Callaghan pocallaghan@gmail.com wrote:
The OP didn't mention NM, so he could hardly have said that it wasn't active. And NM isn't "reporting" anything to Firefox. NM is registering a service (presumably via D-bus, though I haven't checked) and FF is picking it up. That's the way desktop apps are supposed to work.
Apologies for using "reporting" in lieu of "registering a service via D-bus"...
On Sun, 2011-02-27 at 13:01 -0500, Tom H wrote:
On Sun, Feb 27, 2011 at 10:02 AM, Patrick O'Callaghan pocallaghan@gmail.com wrote:
The OP didn't mention NM, so he could hardly have said that it
wasn't
active. And NM isn't "reporting" anything to Firefox. NM is
registering
a service (presumably via D-bus, though I haven't checked) and FF is picking it up. That's the way desktop apps are supposed to work.
Apologies for using "reporting" in lieu of "registering a service via D-bus"...
This is more than a pedantic difference. "Reporting to FF" implies some kind of special relationship between NM and FF, which is not the case. Just so we're clear.
poc
On Sun, Feb 27, 2011 at 5:20 PM, Patrick O'Callaghan pocallaghan@gmail.com wrote:
On Sun, 2011-02-27 at 13:01 -0500, Tom H wrote:
On Sun, Feb 27, 2011 at 10:02 AM, Patrick O'Callaghan pocallaghan@gmail.com wrote:
The OP didn't mention NM, so he could hardly have said that it
wasn't
active. And NM isn't "reporting" anything to Firefox. NM is
registering
a service (presumably via D-bus, though I haven't checked) and FF is picking it up. That's the way desktop apps are supposed to work.
Apologies for using "reporting" in lieu of "registering a service via D-bus"...
This is more than a pedantic difference. "Reporting to FF" implies some kind of special relationship between NM and FF, which is not the case. Just so we're clear.
IMHO totally pedantic...
On Tue, 2011-03-01 at 03:53 -0500, Tom H wrote:
IMHO totally pedantic...
But completely important.
NetworkManager sets a status that you're on- or off-line, and any application can check for that. It doesn't individually inform every network-using application about its status. NetworkManager, nor any notifier, doesn't need to be coded to support this, that, and the other application.
But any application that wants to know network status can be coded to check for status in one place.
On Sun, Feb 27, 2011 at 2:52 AM, bruce badouglas@gmail.com wrote:
On Sat, Feb 26, 2011 at 10:41 PM, Tom H tomh0665@gmail.com wrote:
On Sun, Feb 27, 2011 at 1:20 AM, bruce badouglas@gmail.com wrote:
On Sat, Feb 26, 2011 at 8:43 PM, Patrick O'Callaghan pocallaghan@gmail.com wrote:
On Sat, 2011-02-26 at 20:29 -0500, Jim Philips wrote:
I installed FC14 today on my laptop. I can connect to the Internet and download software. I can also ping sites out on the Internet from the command line. However, the browser refuses to load any pages.
Which browser? Firefox and Evolution both use NetworkManager to determine if the machine is connected. Even if the network is working, if NM is not configured to manage the interface, these apps will think there is no connection.
are you sure about this???
where is the pointer to docs to state this?
i seriously doubt that firefox has any way of knowing about NM specifically..
but it is curious that you can ping, but not access via FF.. what happens if you download/check with Opera..
If NM's active but isn't managing an interface, it reports to FF that the interface is down.
but the OP had stated that NM wasn't active..
and i'm still not convinced that NM is "reporting" to Firefox. Which isn't to say that FF isn't accessing something to connect to the port.
The OP might not be using NM but, AFAIK, if it's launched by the init scripts and "NM_CONTROLLED=no" isn't set in the ifcfg scripts, NM controls the interfaces.
Did you read the fedora-devel thread that I've also posted in this thread?
-
Aaron Konstam -
bruce -
James McKenzie -
Jim Philips -
Joe Zeff -
Paolo Galtieri -
Patrick O'Callaghan -
Tim -
Tom H