Bug#701884: kfreebsd: unknown method 'inet6 auto'

2013-04-03 Thread Steven Chamberlain
Control: tags -1 serious

Justification:  if an IPv6 route announcement is seen at install time,
the kfreebsd-* system would have no network connectivity on first boot,
ifup will fail and even the loopback interface will not be set up.

Also IPv6 and GNU/kFreeBSD are both still release goals I believe.

This has been fixed in sid for some time but we absolutely must see it
fixed in wheezy.

Thanks,
Regards,
-- 
Steven Chamberlain
ste...@pyro.eu.org


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#701884: kfreebsd: unknown method 'inet6 auto'

2013-02-28 Thread Andrew Shadura
Hello,

On Thu, 28 Feb 2013 13:39:04 +
Steven Chamberlain ste...@pyro.eu.org wrote:

 I think at this stage it would be simplest to add an 'inet6 auto'
 implementation to ifupdown on kfreebsd to fix this bug.  It can be
 copied from method 'dhcp', minus the dhclient lines.

 While here, I would recommend setting sysctl
 net.inet6.ip6.accept_rtadv=1 (just like the Linux 'inet6 auto' method
 does).  GNU/kFreeBSD kernels have this enabled by default currently,
 but we may want to change that.  (It may be the only way we can fix
 #684072).

So, should this be enough?

ifconfig %iface% [[link %hwaddress%]] up
sysctl -q -e net.inet6.ip6.accept_rtadv=1

Also, on kfreebsd, are -q and -e valid options to sysctl (not sure if
it's implemented the same way or is it a BSD-specific utility there)?

-- 
WBR, Andrew


signature.asc
Description: PGP signature


Bug#701884: kfreebsd: unknown method 'inet6 auto'

2013-02-28 Thread Christoph Egger
Hi!

Andrew Shadura bugzi...@tut.by writes:
 On Thu, 28 Feb 2013 13:39:04 +
 Steven Chamberlain ste...@pyro.eu.org wrote:

 I think at this stage it would be simplest to add an 'inet6 auto'
 implementation to ifupdown on kfreebsd to fix this bug.  It can be
 copied from method 'dhcp', minus the dhclient lines.

 While here, I would recommend setting sysctl
 net.inet6.ip6.accept_rtadv=1 (just like the Linux 'inet6 auto' method
 does).  GNU/kFreeBSD kernels have this enabled by default currently,
 but we may want to change that.  (It may be the only way we can fix
 #684072).

 So, should this be enough?

 ifconfig %iface% [[link %hwaddress%]] up
 sysctl -q -e net.inet6.ip6.accept_rtadv=1

 Also, on kfreebsd, are -q and -e valid options to sysctl (not sure if
 it's implemented the same way or is it a BSD-specific utility there)?

Both are supported[0], kFreeBSD has a additional -p option that is
supported by a wrapper.

Christoph

[0] http://www.freebsd.org/cgi/man.cgi?query=sysctlsektion=8


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#701884: kfreebsd: unknown method 'inet6 auto'

2013-02-28 Thread Steven Chamberlain
Hi Andrew,

On 28/02/13 18:20, Andrew Shadura wrote:
 ifconfig %iface% [[link %hwaddress%]] up
 sysctl -q -e net.inet6.ip6.accept_rtadv=1

Yes that should be fine.  I would have put the sysctl first, and then
bring up the interface;  not sure if it makes any difference though really.

 Also, on kfreebsd, are -q and -e valid options to sysctl (not sure if
 it's implemented the same way or is it a BSD-specific utility there)?

Yes I just tried the sysctl and it works as intended.

Thanks!
Regards,
-- 
Steven Chamberlain
ste...@pyro.eu.org


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#701884: kfreebsd: unknown method 'inet6 auto'

2013-02-28 Thread Andrew Shadura
Hello,

(Overquoting a bit, as other recipients have fallen out of Cc loop)

On Thu, 28 Feb 2013 10:52:16 -0800
Christoph Egger christ...@debian.org wrote:

 Andrew Shadura bugzi...@tut.by writes:
  On Thu, 28 Feb 2013 10:33:08 -0800
  Christoph Egger christ...@debian.org wrote:

   Also, on kfreebsd, are -q and -e valid options to sysctl (not
   sure if it's implemented the same way or is it a BSD-specific
   utility there)?

  Both are supported[0], kFreeBSD has a additional -p option that is
  supported by a wrapper.
 
  Well, that page says things different from procps' sysctl's
  manpage. Is sysctl a wrapper to provide usual command-line options,
  when a real sysctl is somewhere under /lib or something?

 Exactly, well for providing -p:

 % cat /sbin/sysctl  
 #!/bin/sh
 set -e
 
 args=
 quiet=false
 use_sysctl_conf=false
 
 while [ $# -gt 0 ]; do
   case $1 in
 -q) quiet=true ;;
 -p) use_sysctl_conf=true ;;
 *)  if [ -n ${args} ] ; then args=${args} $1 ; else
 args=$1 ; fi ;; esac
   shift
 done
 
 if ${quiet} ; then
   if ${use_sysctl_conf} ; then
 sed /etc/sysctl.conf -e s/\( \|\t\)*//g -e /^#/d -e /^$/d \
 | (while read i ; do /lib/freebsd/sysctl ${args} ${i}
 | /dev/null ; done)
   else
 /lib/freebsd/sysctl ${args} /dev/null
   fi
 else
   if ${use_sysctl_conf} ; then
 sed /etc/sysctl.conf -e s/\( \|\t\)*//g -e /^#/d -e /^$/d \
 | (while read i ; do /lib/freebsd/sysctl ${args} ${i} ; done)
   else
 exec /lib/freebsd/sysctl ${args}
   fi
 fi

So, what is better to do: to use the wrapper, or to
call /lib/freebsd/sysctl directly?

-- 
WBR, Andrew


signature.asc
Description: PGP signature


Bug#701884: kfreebsd: unknown method 'inet6 auto'

2013-02-28 Thread Christoph Egger
Andrew Shadura bugzi...@tut.by writes:

 On Thu, 28 Feb 2013 10:52:16 -0800
 Christoph Egger christ...@debian.org wrote:

 Andrew Shadura bugzi...@tut.by writes:
  On Thu, 28 Feb 2013 10:33:08 -0800
  Christoph Egger christ...@debian.org wrote:

   Also, on kfreebsd, are -q and -e valid options to sysctl (not
   sure if it's implemented the same way or is it a BSD-specific
   utility there)?

  Both are supported[0], kFreeBSD has a additional -p option that is
  supported by a wrapper.
 
  Well, that page says things different from procps' sysctl's
  manpage. Is sysctl a wrapper to provide usual command-line options,
  when a real sysctl is somewhere under /lib or something?

 Exactly, well for providing -p:

 So, what is better to do: to use the wrapper, or to
 call /lib/freebsd/sysctl directly?

I'd go with the wrapper. Even if we would decide to drop the wrapper
/sbin/sysctl should still be around while the /lib/freebsd/sysctl might
go away.

Christoph


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#701884: kfreebsd: unknown method 'inet6 auto'

2013-02-28 Thread Steven Chamberlain
Hi,

On 28/02/13 18:59, Andrew Shadura wrote:
 So, what is better to do: to use the wrapper, or to
 call /lib/freebsd/sysctl directly?

I think you should just use whatever is in the path, consistent with
GNU/Linux.  (Currently on GNU/kFreeBSD this is the wrapper for our own
sysctl).

Regards,
-- 
Steven Chamberlain
ste...@pyro.eu.org


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#701884: kfreebsd: unknown method 'inet6 auto'

2013-02-28 Thread Steven Chamberlain
Package: ifupdown
Version: 0.7.5
Severity: important
Tags: d-i ipv6
User: debian-...@lists.debian.org
Usertags: kfreebsd
X-Debbugs-Cc: debian-...@lists.debian.org
Control: reassign -1 ifupdown,netcfg

Hi,

If IPv6 SLAAC is used by the installer, netcfg will create an invalid
/e/n/i file on kfreebsd.  This means even the loopback interface will
not come up on boot:

# ifup -v br0
/etc/network/interfaces:12: unknown method
ifup: couldn't read interfaces file /etc/network/interfaces

/etc/network/interfaces :
  1# This file describes the network interfaces available on your system
  2# and how to activate them. For more information, see interfaces(5).
  3
  4# The loopback network interface
  5auto lo0
  6iface lo0 inet loopback
  7
  8# The primary network interface
  9auto vr0
 10iface vr0 inet dhcp
 11# This is an autoconfigured IPv6 interface
 12iface vr0 inet6 auto

The 'inet6 auto' method is not implemented for kfreebsd.  There is only
an 'inet6 dhcp' (which implements stateful DHCPv6).  The other methods
(static, manual) are not really suitable for SLAAC.

Thanks.

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing'), (1, 'experimental')
Architecture: kfreebsd-amd64 (x86_64)

Kernel: kFreeBSD 9.0-2-amd64-xenhvm
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages ifupdown depends on:
ii  dpkg   1.16.8
ii  freebsd-net-tools [net-tools]  9.0+ds1-9
ii  initscripts2.88dsf-34
ii  libc0.12.13-37
ii  lsb-base   4.1+Debian7

ifupdown recommends no packages.

Versions of packages ifupdown suggests:
ii  isc-dhcp-client [dhcp-client]  4.2.2.dfsg.1-5+deb70u2
pn  pppnone
pn  rdnssd none

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#701884: kfreebsd: unknown method 'inet6 auto'

2013-02-28 Thread Steven Chamberlain
found 701884 ifupdown/0.7.5
found 701884 netcfg/1.106
# /e/n/i generation was broken in netcfg before 1.105
fixed 701884 netcfg/1.105
thanks

I think at this stage it would be simplest to add an 'inet6 auto'
implementation to ifupdown on kfreebsd to fix this bug.  It can be
copied from method 'dhcp', minus the dhclient lines.

While here, I would recommend setting sysctl
net.inet6.ip6.accept_rtadv=1 (just like the Linux 'inet6 auto' method
does).  GNU/kFreeBSD kernels have this enabled by default currently, but
we may want to change that.  (It may be the only way we can fix #684072).

Regards,
-- 
Steven Chamberlain
ste...@pyro.eu.org


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org