Kaixo!
On Mon, Jun 26, 2000 at 01:11:05PM -0400, Christian Zoffoli wrote:
> ...added IPv6 support to tcp_wrappers-7.6-12mdk.ipv6.src.rpm
Are we going IPv6 now ? We need to provide rpms of the kernel with ipv6
module available.
Also, I'm doing some test and put on
http://212.100.178.136/pub/Linux/SRPMS-IPv6/ the src.rpm of the
packages I successfully compiled and run in Ipv6.
(currently I only have there tcp_wrappers and fetchmail; net-tools
and glibc could be there too; but as they already come with IPv6 by
default it is not needed).
I tried compiling netkit-base; but the IPv6 patch I have is only for
the current development version, and don't cleanly apply on current
standard version.
I tried IPv6 connections with a friend, direct, tunneling over IPv4,
and with automatic IPv4 tunneling (6to4); it works well with the ipv6
module of 2.2.* kernels.
Well, I just tested ping and traceroute (and, indirectly, AAAA entries
of DNS).
A friend of mine will try ping and traceroute on some 6bone servers
from a freenet6.net given IPv6 adresse. As he uses a Mandrake 7.1
(is that surprizing ? :) ) we could then know how well does our distro
work with Ipv6.
That was during a Linx party, as I can't do it from my home machine due
to IP masquerading done by the telco router (I talked about that with
a Cisco engineer, and a way would involve replacing the router and
conencting trough ATMF-25 directly to the ADSL modem, but that involves
finding a (supported!) ATMF card for Linux, expensive and a configuration
nightmare... and I have to convince the telco to allow me to do that!
Another, most viable solution, would be to patch the Linux kernel so that
the real internet IPv4 adress assigned to me (212.100.178.136) is used
instead of the internal one (192.168.42.130) on the encapsuled packets
for the sending adress, and in the 2002::/16 adress as well.
Problem now is that I should use 2002:d464:b288::/48 to be able to get
incoming packets (as the telco router does maps all ports on its internet
interface to my machine); but I can't use that as I don' have any
"212.100.178.136" IPv4 interface on my machine (and can't have, the
telco router only accepts to do NAT and route to the internet packets
from local network 192.168.42.0)
I've currently not yet looked at the kernel (and I'm not really a kernel
guru either), so if any of you knows better and could say something about
that idea...
Note also that I'm running from several days with ipv6 module loaded,
and the net-tools, tcp_wrappers and fetchmail with IPv6 support; however
as I can't really do any real IPv6 traffic (and I haven't where to do
either) I use IPv4. That is, tcp_wrappers and fetchmail with IPv6 support
could be included in Linux-Mandrake, there doesn't seem to be any
problems in Ipv4 operations at all (I'm still able to get my mail).
There was however a point: the so patched fetchmail uses service names
*only* (even for IPv4); and the used names weren't in sync with
/etc/services. As a result it didn't worked; when I figured that out
I corrected my /etc/services file. Not a big deal, just the "setup"
package needs to provide the right names. I also added in the src.rpm
the needed %post code so that this is handled automatically.
Thank you
> --
> Yours Sincerly,
> Christian Zoffoli ''~``
> ( o o )
> +---------------------------.oooO--(_)--Oooo.--------------------------+
> | LittlePenguin H 1 L.U.G. http://www.littlepenguin.org |
> | PGP: ~czoffoli/czoffoli.asc |
> | |
> | .oooO [EMAIL PROTECTED] |
> | ICQ: 50684793 ( ) Oooo. [EMAIL PROTECTED] |
> +-----------------------------\ (----( )-----------------------------+
> \_) ) /
> (_/
--
Ki �a vos v�ye b�n,
Pablo Saratxaga
http://www.srtxg.easynet.be/ PGP Key available, key ID: 0x8F0E4975
