troubleshooting network settings

[Kevin Kinsey]

Malcolm Fitzgerald wrote:
> 
> On 30/05/2006, at 10:29 PM, Kevin Kinsey wrote:
> 
>> Malcolm Fitzgerald wrote:
>>>> Malcolm Fitzgerald wrote:
>>> Running that command returns this:
>>> ifconfig: -inet: bad value
>>
>>
>> Bah!  I'm on the road too much lately.  No "dash"
>> before "inet" ...
> 
> here's the output
> 
> bsd-box# ifconfig lo0 inet 127.0.0.1 netmask 255.255.255.0
> bsd-box# ifconfig -a
> rl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
>  options=8<VLAN_MTU>
>  inet6 fe80::2e0:4cff:fe08:e02a%rl0 prefixlen 64 scopeid 0x1
>  inet 192.168.1.104 netmask 0xffffff00 broadcast 192.168.1.255
>  ether 00:e0:4c:08:e0:2a
>  media: Ethernet autoselect (100baseTX <full-duplex>)
>  status: active
> plip0: flags=108810<POINTOPOINT,SIMPLEX,MULTICAST,NEEDSGIANT> mtu 1500
> lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
>  inet 127.0.0.1 netmask 0xffffff00
>  inet6 ::1 prefixlen 128
>  inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3


In addition to Jorn's advice, check /etc/defaults/rc.conf.  The
file should exist and have permissions like so:

$ ls -l /etc/defaults/rc.conf
-r--r--r--  1 root  wheel  31735 May 15 18:48 /etc/defaults/rc.conf

and it should have the following line within:

$ grep lo0 /etc/defaults/rc.conf
ifconfig_lo0="inet 127.0.0.1"   # default loopback device configuration.

If all these aren't true, that would explain why the loopback isn't
configured.

Kevin Kinsey



-- 
There's an old proverb that says just about whatever you want it to.