[zebra 22837] Re: How To Add IPv6 in Linux Fedora COre 1

On Mon, 2006-04-24 at 05:00 +0700, Dwiagusta Taiiiii wrote:
> Hai aLL ,,
>  
> i Just waNt to aSk ,, how to add IPv6 in one of the ethernet card in
> Linux Fedora Core 1 ,, without adding an IPv4 ,, i cannot add IPv6
> using the network configuration menu ,, i can only add IPv6 using
> " /sbin/ip -6 addr add " command in terminal ,, i want to make an IPv6
> Host Only ,, but i can't add without IPv4 added ,, because if i
> delete the IPv4 the ethernet card will be inactive and the IPv6
> address cannot assigned to ethernet card that inactive ,, plis someone
> help me !!!

	This is another request that's way off topic for this mailing list...
Ok...  Nobody is jumping on you, yet, so I'll answer your IPv6 stuff,
and probably a lot more, just because I'm an IPv6 fanatic myself.
There's a little bit of Zebra relevancy at the end, just to keep some
minor remote semblance of relevancy here.

	1) This is not a question that relevant to Zebra, as it doesn't involve
Zebra at all.

	2) This would be more appropriate on one of the Fedora Core mailing
lists, since it's a Fedora Core configuration issue (not even, really,
an IPv6 issue per se), but the version of Fedora Core you are using will
probably get you laughed off the list.

	3) FC1 is way way past its end of life.  It's deep into legacy and
should not be used.  FC4 and FC5 are the only two currently supported
active versions.

	4) I understand from this and your previous post about Teredo/Miredo
that you are getting involved with IPv6.  Great!  But FC1 is using a 2.4
kernel and the 2.6 kernels used in FC3 and later have superior IPv6
capabilities.  2.4 is sufficient and will work, but 2.6 is better.  Even
FC3 (which had the 2.6 kernel) is now in legacy and you should be on FC4
or FC5 if you are going to stick with Fedora Core.

	5) If you are going to do a lot of IPv6 work, you can forget about the
ususal configuration interfaces.  Get use to it.  They are simply not
set up for IPv6 configuration.  Almost everything you do is going to
have to be by hand editing in the configuration files with text editors.

	6) Important!  IPv6 is NOT enabled on Fedora Core anything, by default.
It's enabled by accident.  The NETWORKING_IPv6 parameter defaults to
"no", so none of the IPv6 configuration scripts have run even though you
find the protocol loaded and the interfaces sitting there staring at you
with link local IPv6 addresses.  The only reason everyone sees IPv6 on
the interfaces is that one of the configuration utilities (I suspect
"ip") referenced the PF_INET6 protocol family and the kernel happily
kmoded the ipv6 protocol module into the stacks.  It's in there and in
reasonable shape to act as an "autoconf" leaf node, but none of the
configuration scripts have been run, so none of the blackhole routes and
such have been properly configured.  You really DON'T want to run it
that way.


	So, you want an IPv6-only interface on FC.  No problem.  I do this all
the time...


Assumptions:
	You are not setting up a router (workstation only)
	You already have a router that's advertising IPv6 routes.

	Using your favorite text editor, edit the following files for the
following parameters:

	Edit /etc/sysconfig/network and set:

NETWORKING_IPV6=yes
IPV6FORWARDING=no

	Edit /etc/sysconfig/network-scripts/ifcfg-eth1 (change the number here
and on the DEVICES line to what ever is the correct interface for what
ever you are trying to set up this way) and set...

DEVICE=eth1
BOOTPROTO=static
BROADCAST=
IPADDR=
NETMASK=
NETWORK=
ONBOOT=yes
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6ADDR=
IPV6ADDR_SECONDARIES=

	Now restart your network, an you should be good to go.  This will work
on all flavors of Fedora Core, even the obsolete version you are using.

	If you want to assign static IPv6 addresses to the above, change to
"IPV6_AUTOCONF=no" and put your primary IPv6 global unicast address in
"IPV6ADDR=" and any secondary IPv6 addresses in IPV6ADDR_SECONDARIES
separated by whitespace, something like this (this is from an actual
production IPv6 only interface I have running, you can ping6 these
addresses - they are real and live).  Don't forget the netmask on those
addresses.

IPV6_AUTOCONF=no
IPV6ADDR=2001:4830:3000:2:280:3fff:fe03:455b/64
IPV6ADDR_SECONDARIES="\
  2001:4830:3000:2:280:3fff:4003:455b/64 \
  2001:4830:3000:2:280:3fff:4103:455b/64 \
  2001:4830:3000:2:280:3fff:4203:455b/64 \
  2001:4830:3000:2:280:3fff:4303:455b/64 \
  2001:4830:3000:2:280:3fff:4403:455b/64 \
  2001:4830:3000:2:280:3fff:4503:455b/64 \
"

	If you don't use autoconf, and you have an IPv6 router or tunnels, you
will probably also have to edit on the static-routes-ipv6 file
in /etc/sysconfig and but that's more than I'm going to go into here.

	Once you have restarted your network with "NETWORKING_IPV6=yes" you
only need to run "/sbin/ifdown eth1 ; /sbin/ifup eth1" to make changes
to an individual interface, or run the appropriate "ip -6" command by
hand.  Changes to /etc/sysconfig/networking and/or /etc/sysctl.conf (if
you are going to try and set up a router) will probably require
restarting networking or rebooting (rebooting is never required unless
you are attempting to UNLOAD IPv6, but sometimes it's easier than
running the commands individually by hand).


> regards ,, 

	Just to make this a little on topic, I will remark that I switched from
Zebra on my routers to Quagga, specifically so I could use the router
advertisement facility in quagga and not have to use radvd on those
systems.  Other than that, the IPv6 support seems to be pretty solid.
OCCAID (my IPv6 provider) requires that static tunnels directly
connected to them (IOW, not managed by SixXS) advertise your
assigned /48 address over BGP4+ to drive their dynamic routing.  Zebra
and Quagga have worked very well for this.  Other service providers to
not require you to speak BGP with them to drive their routing process.

> -dimas- 

	Final recommendations...

	1) Upgrade to the latest Fedora Core if you want help in the future.
You won't find much support or sympathy on Fedora Core 1.

	2) Please join one of the Fedora Core lists (fedora-users would
probably be best for you) and raise these issues there.  You will
probably find better support PLUS it will have the side benefit of
raising the very relevant issues of the deficencies in the configuration
interfaces on a list where someone might think to do something about it.
I don't think people there are talking IPv6 seriously yet, even though
there are more routable IPv6 /48 network addresses (1.65 billion
networks are currently advertised and routable for IPv6) in the core BGP
tables than there are routable IPv4 unicast address (1.49 billion
routable IPv4 addresses).


________________________________________________________________________
> Apakah Anda Yahoo!?
> Kunjungi halaman depan Yahoo! Indonesia yang baru!

	Regards,
	Mike
-- 
Michael H. Warfield (AI4NB) | (770) 985-6132 |  [email protected]
   /\/\|=mhw=|\/\/          | (678) 463-0932 |  http://www.wittsend.com/mhw/
   NIC whois: MHW9          | An optimist believes we live in the best of all
 PGP Key: 0xDF1DD471        | possible worlds.  A pessimist is sure of it!

_______________________________________________
Zebra mailing list
[email protected]
http://ml.zebra.org/mailman/listinfo/zebra

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)

iQCVAwUAREzgyeHJS0bfHdRxAQLZTQQAkGUiBh20kkhgulWQWHENzUlf5PDFpj6w
DpV+4MhVfKVXwHP2OocAfe0q45jPH1FAnRHtrHYYdBrSz5H1OfypXRg9q5iLszPj
eWsCAzM2UgXITZzhZfFCDoX5E+Ip4Hf7BOEZcbjmddNtS0d7l9PaRZLB62z2pw2V
Sw3e2CoaajE=
=6hfz
-----END PGP SIGNATURE-----