William Case wrote:
On re-boot the script messages still show, -- "setting NetworkManger
waiting for network - failed". Then, "httpd: could not reliably
determine the servers fully qualified domain name using 127.0.0.1 for
server name."
The little NetworkManager gui in my notification panel sh
Hi Kevin;
On Wed, 2008-08-06 at 01:03 -0400, Kevin J. Cummings wrote:
> William Case wrote:
> > Hi Kevin et al;
> >
> > It just got stranger;
> >
> > On Wed, 2008-08-06 at 00:07 -0400, Kevin J. Cummings wrote:
> >> William Case wrote:
> >>> Although my browsers don't work externally they did fi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
William Case wrote:
> LAN
> IP Address 192.168.1.1
> Subnet Mask 255.255.255.0
> DHCP Server Enabled Firewall Enabled
>
> INFORMATION
> System Time 2008/08/05 21:28:28
> System Boot Up Time 0 days 05:17:37
> Connected Clients 3
> Runtime Code Ver
William Case wrote:
Hi Kevin et al;
It just got stranger;
On Wed, 2008-08-06 at 00:07 -0400, Kevin J. Cummings wrote:
William Case wrote:
Although my browsers don't work externally they did find
http://192.168.1.1 which gave me a setup page. I didn't change anything
but here is the output:
Hi Kevin et al;
It just got stranger;
On Wed, 2008-08-06 at 00:07 -0400, Kevin J. Cummings wrote:
> William Case wrote:
> > Although my browsers don't work externally they did find
> > http://192.168.1.1 which gave me a setup page. I didn't change anything
> > but here is the output:
> >
> > L
William Case wrote:
Although my browsers don't work externally they did find
http://192.168.1.1 which gave me a setup page. I didn't change anything
but here is the output:
LAN
IP Address 192.168.1.1
Subnet Mask 255.255.255.0
DHCP Server Enabled Firewall Enabled
INFORMATION
System Time
Hi Mikkel;
On Tue, 2008-08-05 at 17:56 -0500, Mikkel L. Ellertson wrote:
> William Case wrote:
[snip]
> The usual way to check/change settings on the router is to open the
> web browser to http://192.168.1.1 and log in. This should be covered
> by the router manual.
Neat trick. I will copy an
