Re: ZFS V28

2011-04-15 Thread Xin LI 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Leon Meßner wrote:
| On Fri, Apr 15, 2011 at 06:28:07PM +0300, George Kontostanos wrote:
|> I was wondering if ZFS v28 is going to be MFC to 8-Stable or not.
|
| On Fri, Apr 15, 2011 at 06:28:07PM +0300, George Kontostanos wrote:
|> I was wondering if ZFS v28 is going to be MFC to 8-Stable or not.
|
| Is there a recent patch against stable sources ? I tried the following:
|
|
http://people.freebsd.org/~mm/patches/zfs/v28/stable-8-zfsv28-20110317.patch.xz
|
| This patch failes at sys/cddl/compat/opensolaris/sys/sysmacros.h which i
| think should just be deleted. I tried deleting this file and then
| building produces some errors then walls of text and then aborts.
| The first errors look like this:

This file should be removed.  The rejection might be caused by SCM tag
from checkout, which depends on your configuration, and can be safely
ignored.

Cheers,
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAk2o4r0ACgkQOfuToMruuMCQkwCfZZtClSQmciKJt81t79NyyH1k
WgIAn0gJj075PeieFsg6gzpTmG7EDb9O
=CTU7
-END PGP SIGNATURE-
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: ZFS V28

2011-04-15 Thread George Kontostanos 
I think that at this point it takes more than a patch. That is way I am
asking if there is a plan to MFC to 8-Stable.

On Fri, Apr 15, 2011 at 9:48 PM, Leon Meßner
wrote:

> On Fri, Apr 15, 2011 at 06:28:07PM +0300, George Kontostanos wrote:
> > I was wondering if ZFS v28 is going to be MFC to 8-Stable or not.
>
> On Fri, Apr 15, 2011 at 06:28:07PM +0300, George Kontostanos wrote:
> > I was wondering if ZFS v28 is going to be MFC to 8-Stable or not.
>
> Is there a recent patch against stable sources ? I tried the following:
>
>
> http://people.freebsd.org/~mm/patches/zfs/v28/stable-8-zfsv28-20110317.patch.xz
>
> This patch failes at sys/cddl/compat/opensolaris/sys/sysmacros.h which i
> think should just be deleted. I tried deleting this file and then
> building produces some errors then walls of text and then aborts.
> The first errors look like this:
>
> Script started on Fri Apr 15 18:32:36 2011
> make -j 6 buildworld
> "/usr/share/mk/bsd.prog.mk", line 128: warning: duplicate script for
> target "_EXTRADEPEND" ignored
> "Makefile", line 222: warning: duplicate script for target "clean"
> ignored
> "Makefile", line 222: warning: duplicate script for target "cleandepend"
> ignored
> "Makefile", line 222: warning: duplicate script for target "distribute"
> ignored
> "Makefile", line 222: warning: duplicate script for target "lint"
> ignored
> "Makefile", line 222: warning: duplicate script for target "obj" ignored
> "Makefile", line 222: warning: duplicate script for target "objlink"
> ignored
> "Makefile", line 222: warning: duplicate script for target "tags"
> ignored
> "Makefile", line 222: warning: duplicate script for target "files"
> ignored
> "Makefile", line 222: warning: duplicate script for target "includes"
> ignored
> --
> >>> World build started on Fri Apr 15 18:32:36 UTC 2011
> --
>
> cherio,
> Leon
>
> > Regards,
>



-- 
George Kontostanos
aisecure.net 
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: [regression] unable to boot: no GEOM devices found.

2011-04-15 Thread David Naylor 
On Friday 15 April 2011 18:28:06 John Baldwin wrote:
> On Wednesday, April 13, 2011 1:07:06 pm David Naylor wrote:
> > On Tuesday 12 April 2011 22:12:55 Alexander Motin wrote:
> > > David Naylor wrote:
> > > > On Tuesday 12 April 2011 08:17:51 Alexander Motin wrote:
> > > >> David Naylor wrote:
> > > >>> I am running -current and since a few days ago (at least
> > > >>> 2011/04/11) I am unable to boot.
> > > >>> 
> > > >>> The boot process stops when it looks to find a bootable device. 
> > > >>> The prompt (when pressing '?') does not display any device and
> > > >>> yielding
> 
> one
> 
> > > >>> second (or more) to the kernel (by pressing '.') does not improve
> > > >>> the situation.
> > > >>> 
> > > >>> A known working date is 2011/02/20.
> > > >>> 
> > > >>> I am running amd64 on a nVidia MCP51 chipset.
> > > >> 
> > > >> MCP51... again...
> > > 
> > > +ata2: reiniting channel ..
> > > +ata2: SATA connect time=0ms status=0113
> > > +ata2: reset tp1 mask=01 ostat0=58 ostat1=00
> > > +ata2: stat0=0x50 err=0x01 lsb=0x00 msb=0x00
> > > +ata2: reset tp2 stat0=50 stat1=00 devices=0x1
> > > +ata2: reinit done ..
> > > +unknown: FAILURE - ATA_IDENTIFY timed out LBA=0
> > > 
> > > As soon as all devices detected but not responding to commands, I would
> > > suppose that there is something wrong with ATA interrupts. There is a
> > > long chain of interrupt problems in this chipset. I have already tried
> > > to debug one case where ATA wasn't generating interrupts at all.
> > > Unfortunately, without success -- requests were executing, but not
> > > generating interrupts, it wasn't looked like ATA driver problem.
> > > 
> > > What's about possible candidate to revision triggering your problem, I
> > > would look on this message:
> > > +pcib0: Enabling MSI window for HyperTransport slave at pci0:0:9:0
> > > 
> > > At least it is recent (SVN revs 219737,219740 on 2011-03-18 by jhb) and
> > > it is interrupt related.
> > 
> > I reverted those two revs and everything works again.
> 
> Hmm, can you provide a full boot verbose dmesg?  Alternatively, can you see
> if the device at pci0:0:9:0 is a PCI-PCI bridge?

I can provide a verbose dmesg if the following is not enough:

none17@pci0:0:9:0:  class=0x05 card=0x50011458 chip=0x027010de 
rev=0xa2 hdr=0x00
vendor = 'NVIDIA Corporation'
device = 'MCP51 Host Bridge'
class  = memory
subclass   = RAM

I see two PCI-PCI bridges at pci0:0:3:0 and pci0:0:16:0.  I've attached the 
full `pciconf -lv` output.  
hostb0@pci0:0:0:0:  class=0x06 card=0x chip=0x03a310de rev=0xa2 
hdr=0x00
vendor = 'NVIDIA Corporation'
device = 'C55 Host Bridge'
class  = bridge
subclass   = HOST-PCI
none0@pci0:0:0:1:   class=0x05 card=0x chip=0x03ac10de rev=0xa1 
hdr=0x00
vendor = 'NVIDIA Corporation'
device = 'C55 Memory Controller'
class  = memory
subclass   = RAM
none1@pci0:0:0:2:   class=0x05 card=0x chip=0x03aa10de rev=0xa1 
hdr=0x00
vendor = 'NVIDIA Corporation'
device = 'C55 Memory Controller'
class  = memory
subclass   = RAM
none2@pci0:0:0:3:   class=0x05 card=0x chip=0x03a910de rev=0xa1 
hdr=0x00
vendor = 'NVIDIA Corporation'
device = 'C55 Memory Controller'
class  = memory
subclass   = RAM
none3@pci0:0:0:4:   class=0x05 card=0x chip=0x03ab10de rev=0xa1 
hdr=0x00
vendor = 'NVIDIA Corporation'
device = 'C55 Memory Controller'
class  = memory
subclass   = RAM
none4@pci0:0:0:5:   class=0x05 card=0x chip=0x03a810de rev=0xa2 
hdr=0x00
vendor = 'NVIDIA Corporation'
device = 'C55 Memory Controller'
class  = memory
subclass   = RAM
none5@pci0:0:0:6:   class=0x05 card=0x chip=0x03b510de rev=0xa1 
hdr=0x00
vendor = 'NVIDIA Corporation'
device = 'C55 Memory Controller'
class  = memory
subclass   = RAM
none6@pci0:0:0:7:   class=0x05 card=0x chip=0x03b410de rev=0xa1 
hdr=0x00
vendor = 'NVIDIA Corporation'
device = 'C55 Memory Controller'
class  = memory
subclass   = RAM
none7@pci0:0:1:0:   class=0x05 card=0x chip=0x03ad10de rev=0xa1 
hdr=0x00
vendor = 'NVIDIA Corporation'
device = 'C55 Memory Controller'
class  = memory
subclass   = RAM
none8@pci0:0:1:1:   class=0x05 card=0x chip=0x03ae10de rev=0xa1 
hdr=0x00
vendor = 'NVIDIA Corporation'
device = 'C55 Memory Controller'
class  = memory
subclass   = RAM
none9@pci0:0:1:2:   class=0x05 card=0x chip=0x03af10de rev=0xa1 
hdr=0x00
vendor = 'NVIDIA Corporation'
device = 'C55 Memory Controller'
class  = memory
subclass   = RAM
none10@pci0:0:1:3:  class=0x05 card=0x chip=0x03b010de rev=0xa1 
hdr=0x00
vendor = 'NVIDIA Corpora

Re: ZFS V28

2011-04-15 Thread Leon Meßner 
On Fri, Apr 15, 2011 at 06:28:07PM +0300, George Kontostanos wrote:
> I was wondering if ZFS v28 is going to be MFC to 8-Stable or not.

On Fri, Apr 15, 2011 at 06:28:07PM +0300, George Kontostanos wrote:
> I was wondering if ZFS v28 is going to be MFC to 8-Stable or not.
 
Is there a recent patch against stable sources ? I tried the following:
 
http://people.freebsd.org/~mm/patches/zfs/v28/stable-8-zfsv28-20110317.patch.xz
 
This patch failes at sys/cddl/compat/opensolaris/sys/sysmacros.h which i
think should just be deleted. I tried deleting this file and then 
building produces some errors then walls of text and then aborts.
The first errors look like this:
 
Script started on Fri Apr 15 18:32:36 2011
make -j 6 buildworld
"/usr/share/mk/bsd.prog.mk", line 128: warning: duplicate script for
target "_EXTRADEPEND" ignored
"Makefile", line 222: warning: duplicate script for target "clean"
ignored
"Makefile", line 222: warning: duplicate script for target "cleandepend"
ignored
"Makefile", line 222: warning: duplicate script for target "distribute"
ignored
"Makefile", line 222: warning: duplicate script for target "lint"
ignored
"Makefile", line 222: warning: duplicate script for target "obj" ignored
"Makefile", line 222: warning: duplicate script for target "objlink"
ignored
"Makefile", line 222: warning: duplicate script for target "tags"
ignored
"Makefile", line 222: warning: duplicate script for target "files"
ignored
"Makefile", line 222: warning: duplicate script for target "includes"
ignored
--
>>> World build started on Fri Apr 15 18:32:36 UTC 2011
--
 
cherio,
Leon

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

Re: [regression] unable to boot: no GEOM devices found.

2011-04-15 Thread John Baldwin 
On Wednesday, April 13, 2011 1:07:06 pm David Naylor wrote:
> On Tuesday 12 April 2011 22:12:55 Alexander Motin wrote:
> > David Naylor wrote:
> > > On Tuesday 12 April 2011 08:17:51 Alexander Motin wrote:
> > >> David Naylor wrote:
> > >>> I am running -current and since a few days ago (at least 2011/04/11) I
> > >>> am unable to boot.
> > >>> 
> > >>> The boot process stops when it looks to find a bootable device.  The
> > >>> prompt (when pressing '?') does not display any device and yielding 
one
> > >>> second (or more) to the kernel (by pressing '.') does not improve the
> > >>> situation.
> > >>> 
> > >>> A known working date is 2011/02/20.
> > >>> 
> > >>> I am running amd64 on a nVidia MCP51 chipset.
> > >> 
> > >> MCP51... again...
> >
> > +ata2: reiniting channel ..
> > +ata2: SATA connect time=0ms status=0113
> > +ata2: reset tp1 mask=01 ostat0=58 ostat1=00
> > +ata2: stat0=0x50 err=0x01 lsb=0x00 msb=0x00
> > +ata2: reset tp2 stat0=50 stat1=00 devices=0x1
> > +ata2: reinit done ..
> > +unknown: FAILURE - ATA_IDENTIFY timed out LBA=0
> > 
> > As soon as all devices detected but not responding to commands, I would
> > suppose that there is something wrong with ATA interrupts. There is a
> > long chain of interrupt problems in this chipset. I have already tried
> > to debug one case where ATA wasn't generating interrupts at all.
> > Unfortunately, without success -- requests were executing, but not
> > generating interrupts, it wasn't looked like ATA driver problem.
> > 
> > What's about possible candidate to revision triggering your problem, I
> > would look on this message:
> > +pcib0: Enabling MSI window for HyperTransport slave at pci0:0:9:0
> > 
> > At least it is recent (SVN revs 219737,219740 on 2011-03-18 by jhb) and
> > it is interrupt related.
> 
> I reverted those two revs and everything works again.

Hmm, can you provide a full boot verbose dmesg?  Alternatively, can you see if 
the device at pci0:0:9:0 is a PCI-PCI bridge?

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

ZFS V28

2011-04-15 Thread George Kontostanos 
I was wondering if ZFS v28 is going to be MFC to 8-Stable or not.

Regards,

-- 
George Kontostanos
aisecure.net 
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: IPv6 tunnel problem

2011-04-15 Thread Marcin Cieslak 
>> Mattia Rossi  wrote:
> I have accept_rtadv enabled if it's not a router. See my post.

I think I have a similar setup (only using sixxs-aiccu). Since 
my machine is a gateway to the outside IPv6 world (via www.sixxs.net)
I am not accepting router adverisements there, but I'm running
rtadvd and sending them to other hosts on the LAN:

nd6 options=21

> ifconfig with tunnel up is:
>
> ifconfig
> bge0: flags=8843 metric 0 mtu 1500
>  
> options=8009b
>  ether 00:0d:9d:51:d4:7e
>  inet 136.186.229.112 netmask 0xff00 broadcast xxx.xxx.xxx.xxx
>  inet6 fe80:::::%bge0 prefixlen 64 scopeid 0x5
>  inet6 ::::: prefixlen 64 duplicated
**
 what's up here?
>  nd6 options=23
>  media: Ethernet autoselect (1000baseT )
>  status: active

Why is this address "duplicated"? If this machine *is* the gateway
to the outside IPv6 world, should *not* it be accepting rtadv
and have a global IPv6 address configured statically


> tun0: flags=8051 metric 0 mtu 1280
>  options=8
>  inet6 fe80:::::%tun0 prefixlen 64 scopeid 0x9
>  inet6 :::: --> :::: prefixlen 128
>  nd6 options=29
 **
 Does "ifconfig tun0 inet6 -ifdisabled" 
help?

I don't know why gateway6 (I don't use this software) leaves it as "IFDISABLED"

This is /etc/rc.conf from my tunnel gateway machine (two tunnels, tun0 and
tun1) - it runs a few-month-old -CURRENT:

ipv6_gateway_enable="YES"
rtadvd_enable="YES"
# Internal WLAN
rtadvd_interfaces="wlan0"
ifconfig_wlan0_ipv6="inet6 a::::1/64"
# Tunnel via tun0 is configured automatically by aiccu
# and has NO /etc/rc.conf entry at all
# Tunnel via tun1 is configured statically (it serves only some networks)
ifconfig_tun1_ipv6="inet6 a:::8000::1"  

//Marcin

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

Re: IPv6 tunnel problem

2011-04-15 Thread Mattia Rossi 

I have accept_rtadv enabled if it's not a router. See my post.

ifconfig with tunnel up is:

ifconfig
bge0: flags=8843 metric 0 mtu 1500

options=8009b
ether 00:0d:9d:51:d4:7e
inet 136.186.229.112 netmask 0xff00 broadcast xxx.xxx.xxx.xxx
inet6 fe80:::::%bge0 prefixlen 64 scopeid 0x5
inet6 ::::: prefixlen 64 duplicated
nd6 options=23
media: Ethernet autoselect (1000baseT )
status: active
fxp0: flags=8802 metric 0 mtu 1500

options=4219b
ether 00:02:b3:eb:28:b0
media: Ethernet autoselect (none)
status: no carrier
plip0: flags=8810 metric 0 mtu 1500
lo0: flags=8049 metric 0 mtu 16384
options=3
inet 127.0.0.1 netmask 0xff00
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x8
nd6 options=21
tun0: flags=8051 metric 0 mtu 1280
options=8
inet6 fe80:::::%tun0 prefixlen 64 scopeid 0x9
inet6 :::: --> :::: prefixlen 128
nd6 options=29
Opened by PID 17726


I canceled the address in case you wonder.

Mat
On 15/04/2011 17:54, Marcin Cieslak wrote:

Mattia Rossi  wrote:

fxp0 and em0


Can you show us what does "ifconfig" say on
your interfaces? There are few parameters
for the ICMPv6 Neighbor Discovery Protocol
that might be needed:
  "ifconfig em0 inet6 accept_rtadv"

Those are nicely documented in ifconfig(8).

This is usually handled by the /etc/rc.d/*
stuff IF you have a current version of
/etc/rc.conf settings. (They changed a bit
in the meantime).

//Marcin


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


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

Re: IPv6 tunnel problem

2011-04-15 Thread Marcin Cieslak 
>> Mattia Rossi  wrote:
> fxp0 and em0

Can you show us what does "ifconfig" say on
your interfaces? There are few parameters
for the ICMPv6 Neighbor Discovery Protocol
that might be needed:
 "ifconfig em0 inet6 accept_rtadv" 

Those are nicely documented in ifconfig(8).

This is usually handled by the /etc/rc.d/*
stuff IF you have a current version of
/etc/rc.conf settings. (They changed a bit
in the meantime).

//Marcin


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

IPv6 tunnel problem

2011-04-15 Thread Mattia Rossi 

Hi all,

I'm having some trouble with my IPv6 tunnel lately (net/gateway6 port).

I'm running revision 220613.

The tunnel runs fine on 8.2, I can ping6 ipv6.google.com from all 
interfaces using all IPv6 addresses. Route Advertisements are sent, 
Linux Machines, Mac OS X machiens and FreeBSD 8.2/8.1 machines are all 
receiveing the advertisements and are able to ping and use the IPv6 network.


On the machines running CURRENT anyhow, route advertisements don't work. 
They arrive at the interface, but nothing happens.
If i set up an IPv6 address and route by hand, I don't get anywhere, as 
it's permanently marked as "tentative", and trying to use that address 
as source address in ping6 results in:


ping6: bind: Can't assign requested address

This brings me to my main problem: the tunnel. If I set up a tunnel on a 
CURRENT machine, the tunnel gets set up (because it's IPv4) but the IPv6 
part does not work. I'm not able to send pings (which means KEEPALIVES 
are not sent either), so it just doesn't work.


I'm using IPv6 in UDP over IPv4 tunneling, as that's what I use on the 
8.2 machine as well.


The error when trying to ping on the CURRENT machine where the tunnel 
runs( for the short period the tunnel is up) is:


ping6: sendmsg: Network is down

Route advertisements are not sent either, as again, the IPv6 address 
assigned to the interface by the tunnel is marked as tentative, so 
rtadvd refuses to work.


Something is badly broken with IPv6 and/or NDP.

More info about the systems:

Interfaces in use on the machines running CURRENT:

bge0 and em0

Interfaces on the working 8.2 machine:

fxp0 and em0

sysctls on the broken machines when in router mode:

net.inet6.ip6.forwarding: 1
net.inet6.ip6.redirect: 1
net.inet6.ip6.hlim: 64
net.inet6.ip6.maxfragpackets: 6400
net.inet6.ip6.accept_rtadv: 0
net.inet6.ip6.keepfaith: 0
net.inet6.ip6.log_interval: 5
net.inet6.ip6.hdrnestlimit: 15
net.inet6.ip6.dad_count: 1
net.inet6.ip6.auto_flowlabel: 1
net.inet6.ip6.defmcasthlim: 1
net.inet6.ip6.gifhlim: 30
net.inet6.ip6.kame_version: FreeBSD
net.inet6.ip6.use_deprecated: 1
net.inet6.ip6.rr_prune: 5
net.inet6.ip6.v6only: 1
net.inet6.ip6.rtexpire: 3600
net.inet6.ip6.rtminexpire: 10
net.inet6.ip6.rtmaxcache: 128
net.inet6.ip6.use_tempaddr: 0
net.inet6.ip6.temppltime: 86400
net.inet6.ip6.tempvltime: 604800
net.inet6.ip6.auto_linklocal: 1
net.inet6.ip6.prefer_tempaddr: 0
net.inet6.ip6.use_defaultzone: 0
net.inet6.ip6.maxfrags: 6400
net.inet6.ip6.mcast_pmtu: 0
net.inet6.ip6.mcast.loop: 1
net.inet6.ip6.mcast.maxsocksrc: 128
net.inet6.ip6.mcast.maxgrpsrc: 512
security.jail.param.ip6.saddrsel: 0
security.jail.param.ip6.: 0

on the working machine router mode:

net.inet6.ip6.forwarding: 1
net.inet6.ip6.redirect: 1
net.inet6.ip6.hlim: 64
net.inet6.ip6.maxfragpackets: 6400
net.inet6.ip6.accept_rtadv: 0
net.inet6.ip6.keepfaith: 0
net.inet6.ip6.log_interval: 5
net.inet6.ip6.hdrnestlimit: 15
net.inet6.ip6.dad_count: 1
net.inet6.ip6.auto_flowlabel: 1
net.inet6.ip6.defmcasthlim: 1
net.inet6.ip6.gifhlim: 30
net.inet6.ip6.kame_version: FreeBSD
net.inet6.ip6.use_deprecated: 1
net.inet6.ip6.rr_prune: 5
net.inet6.ip6.v6only: 1
net.inet6.ip6.rtexpire: 3600
net.inet6.ip6.rtminexpire: 10
net.inet6.ip6.rtmaxcache: 128
net.inet6.ip6.use_tempaddr: 0
net.inet6.ip6.temppltime: 86400
net.inet6.ip6.tempvltime: 604800
net.inet6.ip6.auto_linklocal: 1
net.inet6.ip6.prefer_tempaddr: 0
net.inet6.ip6.use_defaultzone: 0
net.inet6.ip6.maxfrags: 6400
net.inet6.ip6.mcast_pmtu: 0
net.inet6.ip6.mcast.loop: 1
net.inet6.ip6.mcast.maxsocksrc: 128
net.inet6.ip6.mcast.maxgrpsrc: 512

If they're not routers:

net.inet6.ip6.forwarding: 0
net.inet6.ip6.redirect: 0
net.inet6.ip6.accept_rtadv: 1

And on the interfaces

ifconfig em0 inet6 accept_rtadv

And finally I have a question:

Why is there a net.inet6.ip6.accept_rtadv sysctl?
If we have to enable/disable route advertisements per interface, this 
sysctl shouldn't be there at all.
Immagine a system (like mine) where you have multiple interfaces, and 
which acts as IPv6 router amongst other stuff.


Shouldn't you be able to deactivate route advertisements on one 
interface, which is where route advertisements are sent from, but enable 
it on the other ones, so you don't need to statically configure them? If 
there's a sysctl, you'll disable and enable route advertisements for the 
whole machine, so the per interface stuff is useless, or am I wrong?


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