Re: loopback interface broken on current

2013-01-10 Thread O. Hartmann
Am 01/09/13 09:59, schrieb Gleb Smirnoff: > On Wed, Jan 09, 2013 at 09:56:25AM +0100, Hartmann, O. wrote: > H> Same here. > H> The OS: FreeBSD 10.0-CURRENT/amd64 r245218. Since I have three boxes > H> running approximately the same configurations (I share my configs > H> between lab and home), but

Re: loopback interface broken on current

2013-01-09 Thread Gleb Smirnoff
On Wed, Jan 09, 2013 at 09:56:25AM +0100, Hartmann, O. wrote: H> Same here. H> The OS: FreeBSD 10.0-CURRENT/amd64 r245218. Since I have three boxes H> running approximately the same configurations (I share my configs H> between lab and home), but different hardware, I'm confused. H> H> The symptom

Re: loopback interface broken on current

2013-01-09 Thread Hartmann, O.
On 01/04/13 09:45, Gary Jennejohn wrote: > On Thu, 03 Jan 2013 20:30:18 +0900 > KAHO Toshikazu wrote: > >> Hello, >> >>> There is still >ifa_del_loopback_route: deletion failed: 3 >>> that wasn't there before,but the 127.0.0.1 seems to be configured now: >> >> Do you have a line like net

Re: loopback interface broken on current

2013-01-04 Thread Gary Jennejohn
On Thu, 03 Jan 2013 20:30:18 +0900 KAHO Toshikazu wrote: > Hello, > > > There is still >ifa_del_loopback_route: deletion failed: 3 > > that wasn't there before,but the 127.0.0.1 seems to be configured now: > > Do you have a line like network_interfaces="lo0 bge0" in /etc/rc.conf? > If

Re: loopback interface broken on current

2013-01-03 Thread KAHO Toshikazu
Hello, > If I comment out : > ifconfig_bge0="inet 192.168.0.5 netmask 255.255.255.0" > Network doesn't work. Yes, you should not commnet out it, you cannot connect from/to outside. network_interfaces="auto" is same as /etc/default/rc.conf, so that you can remove it safely from /etc/rc.conf

Re: loopback interface broken on current

2013-01-03 Thread Manfred Antar
At 03:30 AM 1/3/2013, KAHO Toshikazu wrote: > Hello, > >> There is still >ifa_del_loopback_route: deletion failed: 3 >> that wasn't there before,but the 127.0.0.1 seems to be configured now: > > Do you have a line like network_interfaces="lo0 bge0" in /etc/rc.conf? >If you have it, try to re

Re: loopback interface broken on current

2013-01-03 Thread Manfred Antar
At 03:30 AM 1/3/2013, KAHO Toshikazu wrote: > Hello, > >> There is still >ifa_del_loopback_route: deletion failed: 3 >> that wasn't there before,but the 127.0.0.1 seems to be configured now: > > Do you have a line like network_interfaces="lo0 bge0" in /etc/rc.conf? >If you have it, try to re

Re: loopback interface broken on current

2013-01-03 Thread KAHO Toshikazu
Hello, > There is still >ifa_del_loopback_route: deletion failed: 3 > that wasn't there before,but the 127.0.0.1 seems to be configured now: Do you have a line like network_interfaces="lo0 bge0" in /etc/rc.conf? If you have it, try to remove it. I think something broken, but people us

Re: loopback interface broken on current

2013-01-02 Thread Manfred Antar
At 07:09 PM 1/2/2013, KAHO Toshikazu wrote: > Hello, > >I have a similar problem if "ifconfig_lo0" line is exist in /etc/rc.conf. >Can you remove lo0 configure line from /etc/rc.conf. > >> /etc/rc.conf: >> ifconfig_lo0="inet 127.0.0.1" # default loopback device >> configuration. Ok I c

Re: loopback interface broken on current

2013-01-02 Thread KAHO Toshikazu
Hello, I have a similar problem if "ifconfig_lo0" line is exist in /etc/rc.conf. Can you remove lo0 configure line from /etc/rc.conf. > /etc/rc.conf: > ifconfig_lo0="inet 127.0.0.1" # default loopback device > configuration. -- vi...@elam.kais.kyoto-u.ac.jp

Re: loopback interface broken on current

2013-01-02 Thread Manfred Antar
> > >Ok, so this is my failure. :( Sorry. I will look at it as soon as >I get to decent internet connection. Right now I am on very bad GPRS. > >Can you please show your rc.conf (the network related part)? > > >-- >Totus tuus, Glebius. Here you go: /etc/hosts: ::1 localhost loc

Re: loopback interface broken on current

2013-01-02 Thread Gleb Smirnoff
On Tue, Jan 01, 2013 at 12:42:47PM -0800, Manfred Antar wrote: M> OK M> I tracked it down to revision 244678 M> 244677 works M> the files involved are: M> (src)5012}svn up -r 244678 M> Updating '.': M> Usys/netinet/in.c M> Usys/netinet6/in6.c M> Updated to revision 244678 M> M> It seems li

Re: loopback interface broken on current

2013-01-01 Thread O. Hartmann
Am 01/01/13 21:42, schrieb Manfred Antar: > At 11:48 AM 1/1/2013, Gleb Smirnoff wrote: >> On Tue, Jan 01, 2013 at 02:39:58AM -0800, Manfred Antar wrote: >> M> >On Thu, Dec 27, 2012 at 09:05:26AM -0800, Manfred Antar wrote: >> M> >M> For the past few days the loopback interface 127.0.0.1 is broken

Re: loopback interface broken on current

2013-01-01 Thread Manfred Antar
At 11:48 AM 1/1/2013, Gleb Smirnoff wrote: >On Tue, Jan 01, 2013 at 02:39:58AM -0800, Manfred Antar wrote: >M> >On Thu, Dec 27, 2012 at 09:05:26AM -0800, Manfred Antar wrote: >M> >M> For the past few days the loopback interface 127.0.0.1 is broken on >current. >M> >M> The last good kernel that wo

Re: loopback interface broken on current

2013-01-01 Thread Garrett Cooper
Maybe it's this commit? HTH, -Garrett r244678 | glebius | 2012-12-25 05:01:58 -0800 (Tue, 25 Dec 2012) | 17 lines The SIOCSIFFLAGS ioctl handler runs if_up()/if_down() that notify all interested parties in case if inte

Re: loopback interface broken on current

2013-01-01 Thread Mark Atkinson
On 1/1/2013 2:22 AM, Gleb Smirnoff wrote: > Manfred, > > On Thu, Dec 27, 2012 at 09:05:26AM -0800, Manfred Antar wrote: > M> For the past few days the loopback interface 127.0.0.1 is broken on > current. > M> The last good kernel that works for me is r244662: Mon Dec 24 06:43:07 > PST 2012 >

Re: loopback interface broken on current

2013-01-01 Thread Gleb Smirnoff
Manfred, On Thu, Dec 27, 2012 at 09:05:26AM -0800, Manfred Antar wrote: M> For the past few days the loopback interface 127.0.0.1 is broken on current. M> The last good kernel that works for me is r244662: Mon Dec 24 06:43:07 PST 2012 M> Here are some of the errors from current today: Can yo