/etc/hosts :
::1 localhost.mydomain.tld localhost
127.0.0.1 localhost.mydomain.tld localhost
/etc/defaults/rc.conf :
ifconfig_lo0="inet 127.0.0.1" # default loopback device configuration.
... but ifconfig always shows no inet:
lo0: flags=8049 mtu 16384
inet6 fe80::1%lo0 prefixlen 64 s
Len Conrad wrote:
/etc/hosts :
::1 localhost.mydomain.tld localhost
127.0.0.1 localhost.mydomain.tld localhost
/etc/defaults/rc.conf :
ifconfig_lo0="inet 127.0.0.1" # default loopback device configuration.
... but ifconfig always shows no inet:
lo0: flags=8049 mtu 16384
inet6 fe8
and we can do this, too:
ifconfig lo 127.0.0.1 netmask 255.0.0.0 up
then ifconfig shows:
lo0: flags=8049 mtu 16384
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
inet6 ::1 prefixlen 128
inet 127.0.0.1 netmask 0xff00
thanks
Len
_
/etc/hosts :
::1 localhost.mydomain.tld localhost
127.0.0.1 localhost.mydomain.tld localhost
/etc/defaults/rc.conf :
ifconfig_lo0="inet 127.0.0.1" # default loopback device configuration.
... but ifconfig always shows no inet:
lo0: flags=8049 mtu 16384
inet6 fe80::1%lo0 prefixlen
Andrew Falanga said:
> HI,
>
> On my father's computer there isn't an IPv4 loopback address being assigned
> to
> the lo0 interface. What would cause this? I've looked at his configs and
> they're the same as on my system (obviously something is differ
On Feb 17, 2008 1:14 PM, Dominique Goncalves <[EMAIL PROTECTED]>
wrote:
> Hi,
>
> On Feb 16, 2008 6:41 PM, Andrew Falanga <[EMAIL PROTECTED]> wrote:
> > HI,
> >
> > On my father's computer there isn't an IPv4 loopback address being
> assig
Hi,
On Feb 16, 2008 6:41 PM, Andrew Falanga <[EMAIL PROTECTED]> wrote:
> HI,
>
> On my father's computer there isn't an IPv4 loopback address being assigned to
> the lo0 interface. What would cause this? I've looked at his configs and
> they're the sam
On Sat, 2008-02-16 at 10:41 -0700, Andrew Falanga wrote:
> HI,
>
> On my father's computer there isn't an IPv4 loopback address being assigned
> to
> the lo0 interface. What would cause this? I've looked at his configs and
> they're the same as on my sy
HI,
On my father's computer there isn't an IPv4 loopback address being assigned to
the lo0 interface. What would cause this? I've looked at his configs and
they're the same as on my system (obviously something is different, but I
don't know what). I see in his
Disregard - I found the 'network_interfaces' line of rc.conf was
lacking lo0. I added it back in and it seems to be booting correctly.
unless you are sure you need the 'network_interfaces' line in rc.conf
I would comment it out. the default value for it in 6.2 is 'auto' and
I have never seen th
On Monday 19 March 2007 04:59, Keith E. Brandt, M.D. wrote:
> While trying to configure ntp, I discovered that my IPv4 loopback was
> not being configured. I can manually restart it with 'ifconfig lo0
> add 127.0.0.1', however, it does not survive a reboot.
>
> Here
On 3/18/07, Keith E. Brandt, M.D. <[EMAIL PROTECTED]> wrote:
Disregard - I found the 'network_interfaces' line of rc.conf was
lacking lo0. I added it back in and it seems to be booting correctly.
unless you are sure you need the 'network_interfaces' line in rc.conf
I would comment it out. the d
While trying to configure ntp, I discovered that my IPv4 loopback was
not being configured. I can manually restart it with 'ifconfig lo0
add 127.0.0.1', however, it does not survive a reboot.
Here's the output of ipconfig following boot:
rl0: flags=8843 mtu 1500
options
Disregard - I found the 'network_interfaces' line of rc.conf was
lacking lo0. I added it back in and it seems to be booting correctly.
Sorry for the bandwidth!
Keith
While trying to configure ntp, I discovered that my IPv4 loopback
was not being configured. I can manually resta
14 matches
Mail list logo
