Re: FreeBSD wiki offline for a bit

2013-01-08 Thread Alexander Yerenkow
http://wiki.freebsd.org/ZFSTuningGuide

Seems not working :)

-- 
Regards,
Alexander Yerenkow
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Re: FreeBSD wiki offline for a bit

2013-01-08 Thread Bas Smeelen

On 01/08/2013 09:08 AM, Alexander Yerenkow wrote:

http://wiki.freebsd.org/ZFSTuningGuide

Seems not working :)



Works here!


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Re: FreeBSD wiki offline for a bit

2013-01-08 Thread Erich Dollansky
Hi,

On Tue, 8 Jan 2013 10:08:33 +0200
Alexander Yerenkow  wrote:

> http://wiki.freebsd.org/ZFSTuningGuide

Error 503 Service Unavailable

Service Unavailable

Guru Meditation:

XID: 931036950

Varnish cache server

is all I get.

Erich
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Re: FreeBSD wiki offline for a bit

2013-01-08 Thread Bas Smeelen

On 01/08/2013 09:32 AM, Alexander Yerenkow wrote:



2013/1/8 Bas Smeelen mailto:b.smee...@ose.nl>>

On 01/08/2013 09:08 AM, Alexander Yerenkow wrote:

http://wiki.freebsd.org/ZFSTuningGuide

Seems not working :)


Works here!


Hm, could you look at this:
ping wiki.freebsd.org 
PING wfe0.ysv.freebsd.org  (8.8.178.110)


That's strange.
When I go to http://wiki.freebsd.org/ZFSTuningGuide it works.

But when I go to wiki.freebsd.org I get the same Error 503

$ ping wiki.freebsd.org
PING wfe0.ysv.freebsd.org (8.8.178.110) 56(84) bytes of data.
64 bytes from wfe0.ysv.FreeBSD.org (8.8.178.110): icmp_req=1 ttl=54 time=160 ms








Error 503 Service Unavailable

Service Unavailable
Guru Meditation:

XID: 931032464

Varnish cache server



___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Re: FreeBSD wiki offline for a bit

2013-01-08 Thread Bas Smeelen

On 01/08/2013 09:37 AM, Erich Dollansky wrote:

Hi,

On Tue, 8 Jan 2013 10:08:33 +0200
Alexander Yerenkow  wrote:


http://wiki.freebsd.org/ZFSTuningGuide

Error 503 Service Unavailable

Service Unavailable

Guru Meditation:

XID: 931036950

Varnish cache server

is all I get.

Erich


http://wiki.freebsd.org/ThwackAFAQ
http://wiki.freebsd.org/ 
same Error 503 as above

But http://wiki.freebsd.org/ZFSTuningGuide works in two different browsers, 
refreshed the page several times and have no proxy in between.




___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Re: FreeBSD wiki offline for a bit

2013-01-08 Thread Trond Endrestøl
On Tue, 8 Jan 2013 09:39+0100, Bas Smeelen wrote:

> On 01/08/2013 09:32 AM, Alexander Yerenkow wrote:
> > 
> > 
> > 2013/1/8 Bas Smeelen mailto:b.smee...@ose.nl>>
> > 
> > On 01/08/2013 09:08 AM, Alexander Yerenkow wrote:
> > 
> > http://wiki.freebsd.org/ZFSTuningGuide
> > 
> > Seems not working :)
> > 
> > 
> > Works here!
> > 
> > 
> > Hm, could you look at this:
> > ping wiki.freebsd.org 
> > PING wfe0.ysv.freebsd.org  (8.8.178.110)
> 
> That's strange.
> When I go to http://wiki.freebsd.org/ZFSTuningGuide it works.
> 
> But when I go to wiki.freebsd.org I get the same Error 503

It may seem browser cache is playing us some tricks.

Opera 12.12 on Windows (yikes) gave me the wiki front page, but as 
soon as I started clicking on links I haven't touched before, I was 
presented the 503 page:

Error 503 Service Unavailable
Service Unavailable
Guru Meditation:
XID: 931044748
Varnish cache server

I launched links on a 9.1-S and directed the browser to 
http://wiki.freebsd.org/ and was presented with:

Error 503 Service Unavailable
Service Unavailable
Guru Meditation:
XID: 931044247
Varnish cache server

> $ ping wiki.freebsd.org
> PING wfe0.ysv.freebsd.org (8.8.178.110) 56(84) bytes of data.
> 64 bytes from wfe0.ysv.FreeBSD.org (8.8.178.110): icmp_req=1 ttl=54 time=160
> ms
> 
> 
> 
> 
> > 
> > 
> > 
> > Error 503 Service Unavailable
> > 
> > Service Unavailable
> > Guru Meditation:
> > 
> > XID: 931032464
> > 
> > Varnish cache server

-- 
+---++
| Vennlig hilsen,   | Best regards,  |
| Trond Endrestøl,  | Trond Endrestøl,   |
| IT-ansvarlig, | System administrator,  |
| Fagskolen Innlandet,  | Gjøvik Technical College, Norway,  |
| tlf. mob.   952 62 567,   | Cellular...: +47 952 62 567,   |
| sentralbord 61 14 54 00.  | Switchboard: +47 61 14 54 00.  |
+---++___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: FreeBSD wiki offline for a bit

2013-01-08 Thread Charles Sprickman
On Jan 8, 2013, at 3:10 AM, Bas Smeelen wrote:

> On 01/08/2013 09:08 AM, Alexander Yerenkow wrote:
>> http://wiki.freebsd.org/ZFSTuningGuide
>> 
>> Seems not working :)
>> 
> 
> Works here!

What's odd is that it looks like some changes were reverted.  I'd asked someone 
with write privs on it to include a link to mm@'s zfs-stats tool 
(http://www.freebsd.org/cgi/cvsweb.cgi/ports/sysutils/zfs-stats/) and it was 
added, but is now gone.

Things in general feel a little wonky though - the main freebsd page initially 
had issues getting some of the css to me, and svnweb was really laggy.  No idea 
if either thing is hosted in the same location as the wiki though.

Charles

> 
> ___
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Re: Some new hardware with 9.1 does not reboot easily

2013-01-08 Thread Julian Stecklina
Thus spake Andriy Gapon :

> on 29/11/2012 17:16 Willem Jan Withagen said the following:
>> Would that mean that the regular checkout of stable/9 contains enough
>> code to allow "painless" rebooting...
>
> Not yet...

Has this been resolved? I still see a hang on reboot/shutdown on my box
(zfs root on USB thumb drive), but I am not sure if the problem is
related.

Julian

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Re: FreeBSD wiki offline for a bit

2013-01-08 Thread Bas Smeelen

On 01/08/2013 10:00 AM, Trond Endrestøl wrote:

On Tue, 8 Jan 2013 09:39+0100, Bas Smeelen wrote:


On 01/08/2013 09:32 AM, Alexander Yerenkow wrote:


2013/1/8 Bas Smeelen mailto:b.smee...@ose.nl>>

 On 01/08/2013 09:08 AM, Alexander Yerenkow wrote:

 http://wiki.freebsd.org/ZFSTuningGuide

 Seems not working :)


 Works here!


Hm, could you look at this:
ping wiki.freebsd.org 
PING wfe0.ysv.freebsd.org  (8.8.178.110)

That's strange.
When I go to http://wiki.freebsd.org/ZFSTuningGuide it works.

But when I go to wiki.freebsd.org I get the same Error 503

It may seem browser cache is playing us some tricks.

Opera 12.12 on Windows (yikes) gave me the wiki front page, but as
soon as I started clicking on links I haven't touched before, I was
presented the 503 page:

Error 503 Service Unavailable
Service Unavailable
Guru Meditation:
XID: 931044748
Varnish cache server

I launched links on a 9.1-S and directed the browser to
http://wiki.freebsd.org/ and was presented with:

Error 503 Service Unavailable
Service Unavailable
Guru Meditation:
XID: 931044247
Varnish cache server


$ ping wiki.freebsd.org
PING wfe0.ysv.freebsd.org (8.8.178.110) 56(84) bytes of data.
64 bytes from wfe0.ysv.FreeBSD.org (8.8.178.110): icmp_req=1 ttl=54 time=160
ms







Error 503 Service Unavailable

Service Unavailable
Guru Meditation:

XID: 931032464

Varnish cache server


Here it is all working again!

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Re: FreeBSD wiki offline for a bit

2013-01-08 Thread Simon L. B. Nielsen
On 6 January 2013 20:40, Simon L. B. Nielsen  wrote:
> Hey,
>
> tl;dr Wiki is back, and everybody with account need to reset their password.

Small followup. The wiki's surge protection (yet again) got confused
and blocked the frontend proxy. I think it should be fixed now.

If you see any 'varnish guru meditation' please let me know, and
include the XID number so I can trace it in the logs.

-- 
Simon L. B. Nielsen
Hat: clusteradm
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


sendmail vs ipv6 broken after upgrade to 9.1

2013-01-08 Thread Ulrich Spörlein
Hey,

I upgraded a server running 8.x to 9.1 over the weekend and sendmail no
longer wants to bind the AF_INET6 sockets.

So while this still works:

DAEMON_OPTIONS(`Port=smtp, Addr=127.0.0.1, Name=MSA, M=Eu, 
InputMailFilters=dkim')
DAEMON_OPTIONS(`Port=smtp, Addr=::1, Name=MSA, Family=inet6, M=Eu, 
InputMailFilters=dkim')

this is broken:

DAEMON_OPTIONS(`Port=submission, Addr=acme.spoerlein.net, Name=MSA, M=E, 
InputMailFilters=dkim')
DAEMON_OPTIONS(`Port=submission, Addr=acme.spoerlein.net, Name=MSA, 
Family=inet6, M=E, InputMailFilters=dkim')

which makes me believe this has to do with name resolution...

The actual reported errors are:

Jan  8 16:05:03 acme sm-msp-queue[98057]: starting daemon (8.14.6): 
queueing@00:30:00
Jan  8 16:05:03 acme sm-mta[98054]: NOQUEUE: SYSERR(root): opendaemonsocket: 
daemon MSA: cannot bind: Can't assign requested address
Jan  8 16:05:03 acme sm-mta[98054]: daemon MSA: problem creating SMTP socket
Jan  8 16:05:08 acme sm-mta[98054]: NOQUEUE: SYSERR(root): opendaemonsocket: 
daemon MSA: cannot bind: Can't assign requested address
Jan  8 16:05:08 acme sm-mta[98054]: daemon MSA: problem creating SMTP socket
Jan  8 16:05:13 acme sm-mta[98054]: NOQUEUE: SYSERR(root): opendaemonsocket: 
daemon MSA: cannot bind: Can't assign requested address
Jan  8 16:05:13 acme sm-mta[98054]: daemon MSA: problem creating SMTP socket

This will loop a couple of times, but not make any progress. ktrace will show 
what's up:

 98054 sendmail CALL  bind(0x6,0x708c14,0x10)
 98054 sendmail STRU  struct sockaddr { AF_INET, 88.198.49.12:587 }
 98054 sendmail RET   bind 0
 98054 sendmail CALL  socket(PF_INET6,SOCK_STREAM,IPPROTO_IP)
 98054 sendmail RET   socket 7
 98054 sendmail CALL  setsockopt(0x7,SOL_SOCKET,SO_REUSEADDR,0x7fffafa4,0x4)
 98054 sendmail RET   setsockopt 0
 98054 sendmail CALL  setsockopt(0x7,SOL_SOCKET,SO_KEEPALIVE,0x7fffafa4,0x4)
 98054 sendmail RET   setsockopt 0
 98054 sendmail CALL  fcntl(0x7,F_GETFD,0)
 98054 sendmail RET   fcntl 0
 98054 sendmail CALL  fcntl(0x7,F_SETFD,FD_CLOEXEC)
 98054 sendmail RET   fcntl 0
 98054 sendmail CALL  bind(0x7,0x708dbc,0x1c)
 98054 sendmail STRU  struct sockaddr { AF_INET6, [:::88.198.49.12]:587 }
 98054 sendmail RET   bind -1 errno 49 Can't assign requested address

Yeah right ... I don't want an IPv6-mapped-IPv4 address, I want it to bind to 
the real thing.
/etc/nsswitch.conf has
hosts: files dns

and /etc/hosts has
root@acme: /etc/mail# grep acme /etc/hosts
88.198.49.12acme.spoerlein.net acme
2a01:4f8:131:23c2::1acme.spoerlein.net acme

Which shouldn't make a difference anyway, because of:
root@acme: /etc/mail# dig acme.spoerlein.net a +short; dig acme.spoerlein.net 
 +short
88.198.49.12
2a01:4f8:131:23c2::1

How can I unstupid sendmail here?
Uli
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Re: sendmail vs ipv6 broken after upgrade to 9.1

2013-01-08 Thread Gregory Shapiro
> How can I unstupid sendmail here?

I don't think sendmail is being stupid here as it is doing what it has been 
doing under 8.x and 9.1 (the code is the same).  I think something changed with 
the upgrade to 9.1.  As far as tracking it down, the sendmail code does:

getipnodebyname("acme.spoerlein.net", AF_INET6, AI_DEFAULT|AI_ALL, &err);

This will only return an IPv4 mapped address if:

1. There are no IPv6 addresses configured on the interfaces.  How are your IPv6 
addresses assigned?  If auto-configured (DHCPv6, RTADV), is it possible 
sendmail is being started before autoconfiguration has completed?  Restarting 
the MTA after boot and seeing if it still gets the mapped address will say 
whether or not this is the cause.

2. The query for an  record for acme.spoerlein.net failed.  This doesn't 
appear to be the case for dns based on your dig output (assuming you ran that 
dig command on the same machine that is exhibiting the problem).  However, your 
nsswitch.conf lists hosts before dns and there have been broken name resolution 
implementations that, with 'hosts' listed first in nsswitch.conf have given 
back bad info if the first hostname match didn't have the IPv6 address.  You 
could try switching the order in /etc/hosts to see if this helps.  (Note, the 
broken implementation was not FreeBSD.)

You can also test theory #2 by writing a small C program to do the 
getipnodebyname() call shown above and see what you get.  If it gives the same 
bad address, then you need to look outside of sendmail.  In the mean time, 
although not optimal, you can work around the issue by using the IPv6 address 
instead of the hostname in the Addr= equate.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Re: sendmail vs ipv6 broken after upgrade to 9.1

2013-01-08 Thread Michiel Boland

On 01/08/2013 16:18, Ulrich Spörlein wrote:
[...]


  98054 sendmail CALL  bind(0x7,0x708dbc,0x1c)
  98054 sendmail STRU  struct sockaddr { AF_INET6, [:::88.198.49.12]:587 }
  98054 sendmail RET   bind -1 errno 49 Can't assign requested address

Yeah right ... I don't want an IPv6-mapped-IPv4 address, I want it to bind to 
the real thing.


Sendmail uses the first address returned by gethostbyname, rather than scan for 
a 'real' ipv6 address instead of a mapped ipv4 address.


My guess is that things will improve once you do '/etc/rc.d/ip6addrctl 
prefer_ipv6'. This will cause gethostbyname to return the real ipv6 address first.


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Re: sendmail vs ipv6 broken after upgrade to 9.1

2013-01-08 Thread Ulrich Spörlein
On Tue, 2013-01-08 at 18:36:34 +0100, Michiel Boland wrote:
> On 01/08/2013 16:18, Ulrich Spörlein wrote:
> > Hey,
> >
> > I upgraded a server running 8.x to 9.1 over the weekend and sendmail no
> > longer wants to bind the AF_INET6 sockets.
> >
> > So while this still works:
> >
> > DAEMON_OPTIONS(`Port=smtp, Addr=127.0.0.1, Name=MSA, M=Eu, 
> > InputMailFilters=dkim')
> > DAEMON_OPTIONS(`Port=smtp, Addr=::1, Name=MSA, Family=inet6, M=Eu, 
> > InputMailFilters=dkim')
> >
> > this is broken:
> >
> > DAEMON_OPTIONS(`Port=submission, Addr=acme.spoerlein.net, Name=MSA, M=E, 
> > InputMailFilters=dkim')
> > DAEMON_OPTIONS(`Port=submission, Addr=acme.spoerlein.net, Name=MSA, 
> > Family=inet6, M=E, InputMailFilters=dkim')
> >
> > which makes me believe this has to do with name resolution...
> >
> > The actual reported errors are:
> >
> > Jan  8 16:05:03 acme sm-msp-queue[98057]: starting daemon (8.14.6): 
> > queueing@00:30:00
> > Jan  8 16:05:03 acme sm-mta[98054]: NOQUEUE: SYSERR(root): 
> > opendaemonsocket: daemon MSA: cannot bind: Can't assign requested address
> 
> What's the output of the 'ip6addrctl' command on your machine?
> 
> Cheers
> Michiel

root@acme: ~# ip6addrctl
Prefix  Prec Label  Use
:::0.0.0.0/96 50 00
::1/128   40 10
::/0  30 272866
2002::/16 20 34
::/96 10 40

Gah! I remember having to set ip6addrctl_policy="ipv6_prefer" on another
system that I upgraded to 9.x a long time ago.

After setting this, it now looks like this:
root@acme: ~# ip6addrctl
Prefix  Prec Label  Use
::1/128   50 00
::/0  40 10
2002::/16 30 20
::/96 20 30
:::0.0.0.0/96 10 40

And even sendmail is happily finding the sockets to bind to. Thanks for the 
hint!

The bigger question now is, why don't we want to have a working IPv6 out of the
box?

Regards,
Uli
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: sendmail vs ipv6 broken after upgrade to 9.1

2013-01-08 Thread Ulrich Spörlein
On Tue, 2013-01-08 at 10:09:20 -0800, Gregory Shapiro wrote:
> > How can I unstupid sendmail here?
> 
> I don't think sendmail is being stupid here as it is doing what it has been 
> doing under 8.x and 9.1 (the code is the same).  I think something changed 
> with the upgrade to 9.1.  As far as tracking it down, the sendmail code does:
> 
> getipnodebyname("acme.spoerlein.net", AF_INET6, AI_DEFAULT|AI_ALL, &err);
> 
> This will only return an IPv4 mapped address if:
> 
> 1. There are no IPv6 addresses configured on the interfaces.  How are your 
> IPv6 addresses assigned?  If auto-configured (DHCPv6, RTADV), is it possible 
> sendmail is being started before autoconfiguration has completed?  Restarting 
> the MTA after boot and seeing if it still gets the mapped address will say 
> whether or not this is the cause.
> 
> 2. The query for an  record for acme.spoerlein.net failed.  This doesn't 
> appear to be the case for dns based on your dig output (assuming you ran that 
> dig command on the same machine that is exhibiting the problem).  However, 
> your nsswitch.conf lists hosts before dns and there have been broken name 
> resolution implementations that, with 'hosts' listed first in nsswitch.conf 
> have given back bad info if the first hostname match didn't have the IPv6 
> address.  You could try switching the order in /etc/hosts to see if this 
> helps.  (Note, the broken implementation was not FreeBSD.)
> 
> You can also test theory #2 by writing a small C program to do the 
> getipnodebyname() call shown above and see what you get.  If it gives the 
> same bad address, then you need to look outside of sendmail.  In the mean 
> time, although not optimal, you can work around the issue by using the IPv6 
> address instead of the hostname in the Addr= equate.

Turns out it was the missing setting of ip6addrctl_policy="ipv6_prefer"
in rc.conf that also bit me in strange and mysterious ways on another
machine where I did the upgrade. It's very unfortunate that this will
runtime-break sendmail and I honestly don't know why we make ipv4 the
default in this day and age.

Can some IPv6 guru chime in here? This is all thoroughly confusing.

Thanks!
Uli
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


/etc/rc.d/ip6addrctl

2013-01-08 Thread J.R. Oldroyd
On Tue, 8 Jan 2013 19:46:09 +0100 Ulrich Spörlein 
wrote:

> Turns out it was the missing setting of
> ip6addrctl_policy="ipv6_prefer" in rc.conf that also bit me in
> strange and mysterious ways on another machine where I did the
> upgrade. It's very unfortunate that this will runtime-break sendmail
> and I honestly don't know why we make ipv4 the default in this day
> and age.
> 
> Can some IPv6 guru chime in here? This is all thoroughly confusing.
> 
> Thanks!
> Uli
> 

This bit me too, although with something other than sendmail.

It's /etc/rc.d/ip6addrctl that sets the preference for IPv6 or IPv4.  I
think the logic is a bit confusing here, or at least isn't consistent
with what the documentation for these settings (in rc.conf(5)) suggests.

In the startup script, IPv6 is preferred if:
either: ip6addrctl_policy is set to "ipv6_prefer"
or: ip6addrctl_policy is set to "auto", you've not
specified your own policy config file and
ipv6_activate_all_interfaces is set to true

In the documentation, it implies that using ipv6_activate_all_interfaces
is probably not needed for most users:
Note that it is not always necessary to set this variable to
“YES” to use IPv6 functionality on FreeBSD.  In most cases,
just configuring ifconfig_⟨interface⟩_ipv6 variables works.

Seems to me that the ip6addrctl script should also prefer IPv6 if any
interface has IPv6 enabled using one of the ifconfig_(interface)_ipv6
variables.

-jr
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: /etc/rc.d/ip6addrctl

2013-01-08 Thread J.R. Oldroyd
On Tue, 8 Jan 2013 16:02:43 -0500 "J.R. Oldroyd"  wrote:

> Seems to me that the ip6addrctl script should also prefer IPv6 if any
> interface has IPv6 enabled using one of the ifconfig_(interface)_ipv6
> variables.
> 
>   -jr
> 

A simple change along the lines of the attached patch, which also
prefers IPv6 if any i/f uses IPv6 autoconfig, will accomplish this.

-jr
--- ip6addrctl.orig	2013-01-04 00:07:03.0 -0500
+++ ip6addrctl	2013-01-08 16:28:53.0 -0500
@@ -62,7 +62,8 @@
 			ip6addrctl install "${config_file}"
 			checkyesno ip6addrctl_verbose && ip6addrctl
 		else
-			if checkyesno ipv6_activate_all_interfaces; then
+			ipv6auto=`list_net_interfaces autoconf`
+			if [ -n "$ipv6auto" ] || checkyesno ipv6_activate_all_interfaces; then
 ip6addrctl_prefer_ipv6
 			else
 ip6addrctl_prefer_ipv4
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: sendmail vs ipv6 broken after upgrade to 9.1

2013-01-08 Thread Hiroki Sato
Gregory Shapiro  wrote
  in <20130108180920.gj36...@rugsucker.smi.sendmail.com>:

gs> > How can I unstupid sendmail here?
gs>
gs> I don't think sendmail is being stupid here as it is doing what it has
gs> been doing under 8.x and 9.1 (the code is the same).  I think
gs> something changed with the upgrade to 9.1.  As far as tracking it
gs> down, the sendmail code does:
gs>
gs> getipnodebyname("acme.spoerlein.net", AF_INET6, AI_DEFAULT|AI_ALL,
gs> &err);
gs>
gs> This will only return an IPv4 mapped address if:
gs>
gs> 1. There are no IPv6 addresses configured on the interfaces.  How are
gs> your IPv6 addresses assigned?  If auto-configured (DHCPv6, RTADV), is
gs> it possible sendmail is being started before autoconfiguration has
gs> completed?  Restarting the MTA after boot and seeing if it still gets
gs> the mapped address will say whether or not this is the cause.
gs>
gs> 2. The query for an  record for acme.spoerlein.net failed.  This
gs> doesn't appear to be the case for dns based on your dig output
gs> (assuming you ran that dig command on the same machine that is
gs> exhibiting the problem).  However, your nsswitch.conf lists hosts
gs> before dns and there have been broken name resolution implementations
gs> that, with 'hosts' listed first in nsswitch.conf have given back bad
gs> info if the first hostname match didn't have the IPv6 address.  You
gs> could try switching the order in /etc/hosts to see if this helps.
gs> (Note, the broken implementation was not FreeBSD.)

 Just curious, but is there any specific reason not to return an error
 when Family=inet6 and no  RR?

-- Hiroki


pgpKBFOU0X1Fy.pgp
Description: PGP signature


Re: sendmail vs ipv6 broken after upgrade to 9.1

2013-01-08 Thread Hiroki Sato
Ulrich Spörlein  wrote
  in <20130108184051.gi35...@acme.spoerlein.net>:

uq> After setting this, it now looks like this:
uq> root@acme: ~# ip6addrctl
uq> Prefix  Prec Label  Use
uq> ::1/128   50 00
uq> ::/0  40 10
uq> 2002::/16 30 20
uq> ::/96 20 30
uq> :::0.0.0.0/96 10 40
uq> 
uq> And even sendmail is happily finding the sockets to bind to. Thanks for the 
hint!

 I think this just hides the problem.  If gshapiro@'s explanation is
 correct, no :::0.0.0.0/96 address should be returned if the name
 resolution works fine...

-- Hiroki


pgpTBxYwcfkgN.pgp
Description: PGP signature