You have no address on the loopback.
You should have:
ifconfig_lo0="inet 127.0.0.1" # default loopback device configuration.
in /etc/rc.conf or /etc/defaults/rc.conf
Add one of these, and reboot to make sure the problem doesn't recur.
You can manually do an ifconfig:
ifconfig lo0 inet 127.0.0.1 netmask 0xff000000
-Derek
At 02:48 PM 3/15/2006, eoghan wrote:
Derek Ragona wrote:
It sounds like the tcp stack is not even running. What does:
ifconfig -a
show? Do you have any valid IP address on this computer?
-Derek
Yep, I can get to my www files when apachee is started via my assigned ip.
Here is the output of ifconfig:
nathaniel# ifconfig -a
fwe0:
flags=108943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST,NEEDSGIANT>
mtu 1500
options=8<VLAN_MTU>
inet6 fe80::11:6ff:fe99:d9eb%fwe0 prefixlen 64 scopeid 0x1
ether 02:11:06:99:d9:eb
ch 1 dma 0
xl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=9<RXCSUM,VLAN_MTU>
inet6 fe80::2b0:d0ff:fee7:e97d%xl0 prefixlen 64 scopeid 0x2
inet 192.168.1.34 netmask 0xffffff00 broadcast 192.168.1.255
ether 00:b0:d0:e7:e9:7d
media: Ethernet autoselect (100baseTX <full-duplex>)
status: active
plip0: flags=108810<POINTOPOINT,SIMPLEX,MULTICAST,NEEDSGIANT> mtu 1500
lo0: flags=8008<LOOPBACK,MULTICAST> mtu 16384
At 02:37 PM 3/15/2006, eoghan wrote:
Derek Ragona wrote:
> Well, your resolv.conf points to 192.168.1.1, what is at that address?
> Do you have any other DNS issues?
>
> Can you ping localhost, or 127.0.0.1?
>
> Is named running?
>
> -Derek
Hi
192.168.1.1 is my router address.
How can i check if named is running?
There is no reference to named_enable in my rc.conf
When i try ping 127.0.0.1 i get:
ping: sendto: Can't assign requested address
Thanks
> At 02:14 PM 3/15/2006, eoghan wrote:
>> Derek Ragona wrote:
>>> Sorry, my mistake. Check:
>>> /etc/nsswitch.conf
>>> You should the line:
>>> hosts: files dns
>>> With the files listed first
>>> -Derek
>>
>> Hi
>> yes that is in my nsswitch.conf:
>> hosts: files dns
>> any other ideas?
>>
>>> At 01:56 PM 3/15/2006, eoghan wrote:
>>>> Derek Ragona wrote:
>>>>> Check your resolv.conf, should have files first.
>>>>> -Derek
>>>>
>>>> resolve.conf reads
>>>> nameserver 192.168.1.1
>>>>
>>>>
>>>>> At 01:44 PM 3/15/2006, eoghan wrote:
>>>>>> Steve Bertrand wrote:
>>>>>>>> Yes, mine reads:
>>>>>>>> ::1 localhost nathaniel
>>>>>>>> 127.0.0.1 localhost nathaniel
>>>>>>>> Upon starting apache, i can only get to it by using the ip.
>>>>>>>> 127.0.0.1 wont work either. I just get the unable to connect
>>>>>>>> message from the browser. Any ideas?
>>>>>>> Under the Listen directive in your httpd.conf file, are you binding
>>>>>>> Apache to a single IP?
>>>>>>> Mine reads:
>>>>>>> Listen 80
>>>>>>> Which means listen on port 80 on all IP's. If you have an entry
>>>>>>> as such:
>>>>>>> Listen 123.456.789.111:80
>>>>>>> It will listen on port 80 on ONLY that IP, and ignore all other
>>>>>>> requests, including localhost/127.0.0.1.
>>>>>>> Regards,
>>>>>>> Steve
>>>>>>
>>>>>> Hi
>>>>>> Yep, its:
>>>>>> Listen 80
>>>>>> and
>>>>>> ServerName localhost
>>>>>> Where do i get the text from the boot? Im getting some weird
>>>>>> Network is unreachable messages in here that may have something to
>>>>>> do with it?
>>>>>> Eoghan
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
