Re: IPv4 loopback address is missing, why?
/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=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 inet6 ::1 prefixlen 128 so we added to /etc/rc.conf : ifconfig_lo0=inet 127.0.0.1 netmask 255.0.0.0 ... still not inet4 loopback if (so commented it out). no errors in /var/log/messages, dmesg -a shows no error, ... other than services failing to grab ports on 127.0.0.1 thanks Len ___ 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 address is missing, why?
and we can do this, too: ifconfig lo 127.0.0.1 netmask 255.0.0.0 up then ifconfig shows: 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 thanks Len ___ 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 address is missing, why?
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=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 inet6 ::1 prefixlen 128 so we added to /etc/rc.conf : ifconfig_lo0=inet 127.0.0.1 netmask 255.0.0.0 ... still not inet4 loopback if (so commented it out). no errors in /var/log/messages, dmesg -a shows no error, ... other than services failing to grab ports on 127.0.0.1 thanks Len Do you have network_interfaces set to something different than auto in /etc/rc.conf? Yuri ___ 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 address is missing, why?
/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=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 inet6 ::1 prefixlen 128 so we added to /etc/rc.conf : ifconfig_lo0=inet 127.0.0.1 netmask 255.0.0.0 ... still not inet4 loopback if (so commented it out). no errors in /var/log/messages, dmesg -a shows no error, ... other than services failing to grab ports on 127.0.0.1 thanks Len Do you have network_interfaces set to something different than auto in /etc/rc.conf? I read this thread but missed that some pkg_add added network_interfaces in rc.conf, and left out lo thanks, Yuri Len ___ 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 address is missing, why?
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 different, but I don't know what). I see in his /etc/defaults/rc.conf the ifconfig_lo0 line is *NOT* commented out or otherwise altered and his file looks the same as mine (at least on this point, I haven't contrasted the two entirely). So, why would his system not be configuring an IPv4 loopback address? After bootup, I can add the address manually using ifconfig. Do you know if the machine was set up with IPv6 or IPv4 at install? I've never used IPv6, but perhaps when that is chosen, `ifconfig' doesn't show the IPv4 address for lo0. Just a guess. -- Glen Barber http://www.dev-urandom.com/ ___ 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 address is missing, why?
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 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 /etc/defaults/rc.conf the ifconfig_lo0 line is *NOT* commented out or otherwise altered and his file looks the same as mine (at least on this point, I haven't contrasted the two entirely). So, why would his system not be configuring an IPv4 loopback address? After bootup, I can add the address manually using ifconfig. Do you have network_interfaces=something in your /etc/rc.conf ? If so you need also to add lo0. Hope this helps His machine does have it in /etc/defaults/rc.conf (I assume this is where it's supposed to be because my /etc/rc.conf file doesn't have it either but I do have it in /etc/defaults/rc.conf), but not in /etc/rc.conf. Basically, his rc.conf files look nearly identical to mine (mine works). I didn't look closely at this /etc/hosts file as the other respondent mentioned but I will. Andy -- A: Because it messes up the order in which people normally read text. Q: Why is it such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ 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 address is missing, why?
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 system (obviously something is different, but I don't know what). I see in his /etc/defaults/rc.conf the ifconfig_lo0 line is *NOT* commented out or otherwise altered and his file looks the same as mine (at least on this point, I haven't contrasted the two entirely). So, why would his system not be configuring an IPv4 loopback address? After bootup, I can add the address manually using ifconfig. Andy I don't know, but the first place I'd look is /etc/hosts and make sure it's configured correctly there. It's also configured in /etc/network.subr Did you do a make buildworld recently and not complete it entirely? James ___ 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 address is missing, why?
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 same as on my system (obviously something is different, but I don't know what). I see in his /etc/defaults/rc.conf the ifconfig_lo0 line is *NOT* commented out or otherwise altered and his file looks the same as mine (at least on this point, I haven't contrasted the two entirely). So, why would his system not be configuring an IPv4 loopback address? After bootup, I can add the address manually using ifconfig. Do you have network_interfaces=something in your /etc/rc.conf ? If so you need also to add lo0. Hope this helps Andy ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- There's this old saying: Give a man a fish, feed him for a day. Teach a man to fish, feed him for life. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
IPv4 loopback address is missing, why?
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 /etc/defaults/rc.conf the ifconfig_lo0 line is *NOT* commented out or otherwise altered and his file looks the same as mine (at least on this point, I haven't contrasted the two entirely). So, why would his system not be configuring an IPv4 loopback address? After bootup, I can add the address manually using ifconfig. Andy ___ 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
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'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? hm, nothing. It's there by default... nik:0:~$ grep lo0 /etc/defaults/rc.conf ifconfig_lo0=inet 127.0.0.1 # default loopback device configuration. #ifconfig_lo0_alias0=inet 127.0.0.254 netmask 0x # Sample alias entry. Any thoughts as to why it disappears? Did you by any chance edit /etc/defaults/rc.conf? what grep lo0 /etc/rc.conf /etc/defaults/rc.conf reveals? Make the desired changes to /etc/rc.conf and keep /etc/defaults/rc.conf as it comes. Nikos ___ 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
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
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]
IPv4 loopback
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
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]
