Re: IPv4 loopback - solved

[Keith E. Brandt, M.D.]

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 that not work.


I commented it out, and it rebooted with the proper configuration. 
The strange thing is I installed the default configuration, did not 
add in the 'network_interfaces' line manually, and have not edited 
the /etc/defaults/rc.conf file. So I'm not sure how it got broken in 
the first place.


Bottom line is all is up and running now.

Thanks!



LtCol Keith E. Brandt, MD, MPH
USAF-NASA Aerospace Medicine Liaison Officer
Johnson Space Center, Houston, Texas
[EMAIL PROTECTED]

Goodbye cruel world that was my home-
  there's cleaner space out here to roam
Put my feet up on the moons of Mars-
  sit back, relax, and count the stars

*This message transmitted with 100% recycled electrons  


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

IPv4 loopback - solved

[Keith E. Brandt, M.D.]

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 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=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
options=8VLAN_MTU
inet 192.168.0.100 netmask 0xff00 broadcast 192.168.0.255
ether 00:08:54:dd:65:8d
media: Ethernet autoselect (100baseTX full-duplex)
status: active
plip0: flags=108810POINTOPOINT,SIMPLEX,MULTICAST,NEEDSGIANT mtu 1500
lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
inet6 ::1 prefixlen 128

and after manually configuring:

rl0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
options=8VLAN_MTU
inet 192.168.0.100 netmask 0xff00 broadcast 192.168.0.255
ether 00:08:54:dd:65:8d
media: Ethernet autoselect (100baseTX full-duplex)
status: active
plip0: flags=108810POINTOPOINT,SIMPLEX,MULTICAST,NEEDSGIANT mtu 1500
lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
inet6 ::1 prefixlen 128
inet 127.0.0.1 netmask 0xff00


What do I need to configure to get it to come up at bootup? Any 
thoughts as to why it disappears?

(I'm running FreeBSD 6.2 stable, downloaded and installed about 3 wks ago).

Keith
(newcomer to FreeBSD)




LtCol Keith E. Brandt, MD, MPH
USAF-NASA Aerospace Medicine Liaison Officer
Johnson Space Center, Houston, Texas
[EMAIL PROTECTED]

Goodbye cruel world that was my home-
  there's cleaner space out here to roam
Put my feet up on the moons of Mars-
  sit back, relax, and count the stars

*This message transmitted with 100% recycled electrons  


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: IPv4 loopback - solved

[Kevin Downey]

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 default value for it in 6.2 is 'auto' and
I have never seen that not work.

--
The biggest problem with communication is the illusion that it has occurred.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]