Re: will ip 6 in ip4 tunnelling be fixed anytime soon ?
Date:Tue, 10 Oct 2000 02:21:48 +0200 From: Bernd Eckenfels <[EMAIL PROTECTED]> We will see who feels responsible for adding it to the kernel source. Alexey? Andi? Davem? Alan? I have applied the fix, and will send it to Linus. Later, David S. Miller [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: will ip 6 in ip4 tunnelling be fixed anytime soon ?
Date: Mon, 09 Oct 2000 11:44:34 +0200 From: Jorg de Jong <[EMAIL PROTECTED]> attached you will find my patch again Patch applied, thanks for being so patient. Later, David S. Miller [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: will ip 6 in ip4 tunnelling be fixed anytime soon ?
On Mon, Oct 09, 2000 at 11:44:34AM +0200, Jorg de Jong wrote:
> your just a bit off here, I believe Gerhard has posted this bug
> a number of times, further more I have submitted a fix for this
> bug, but has still not been accepted. Neither has there been any feedback
> on why ?
the address for bug fixes for the net-tools is [EMAIL PROTECTED] Your
patch does not address the net-tool, therefore i cannot apply it. We will
see who feels responsible for adding it to the kernel source. Alexey? Andi?
Davem? Alan?
I dont think there is a workaround in the net tools possible,m since the
SIOCSIFDSTADDR which is dispateched to addrconf_set_dstaddr will use
__dev_get_by_name to find the device (i dont know what for) and that will
fail without your patch.
Do u think a workaround in the net-tools is possible? I'm a little bit
confused where exactly the call fails. Since creating a sit device and then
assigning a tunnel address does not work, eighter.
Greetings
Bernd
--
(OO) -- [EMAIL PROTECTED] --
( .. ) ecki@{inka.de,linux.de,debian.org} http://home.pages.de/~eckes/
o--o *plush* 2048/93600EFD eckes@irc +497257930613 BE5-RIPE
(OO) When cryptography is outlawed, bayl bhgynjf jvyy unir cevinpl!
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
Re: will ip 6 in ip4 tunnelling be fixed anytime soon ?
> But you are right, here is a bug nobody reported before. I will take care of > it. > Hmm, your just a bit off here, I believe Gerhard has posted this bug a number of times, further more I have submitted a fix for this bug, but has still not been accepted. Neither has there been any feedback on why ? attached you will find my patch again. it's trivial but works no the less. I hope you will succeed where I have obvious have failed ... regards, Jorg de Jong Hi, I found that creating an ipv6 tunnel with ifconfig does not work. after some comparing between a 2.2 kernel and 2.4.0.testX I found that the name of the newly created sit device is not passed back to the reqestor. See linux/net/ipv6/addrconf.c and follow the call chain. This seems to be introduced by fact that the parameters in 2.4 are copied while in 2.2 kernels this was not the case. My simple patch fixes this one problem. after applying I can now successfuly create ipv6 tunnels with ifconfig. Please apply this patch. thanks, Jorg -- Jorg de Jong Work : mailto:[EMAIL PROTECTED] Play : mailto:[EMAIL PROTECTED] --- linux-2.4.0-test8/net/ipv6/sit.cMon Aug 28 21:03:11 2000 +++ linux/net/ipv6/sit.cTue Aug 15 22:28:27 2000 @@ -188,7 +188,7 @@ } if (i==100) goto failed; - memcpy(parms->name, dev->name, IFNAMSIZ); + memcpy(nt->parms.name, dev->name, IFNAMSIZ); } if (register_netdevice(dev) < 0) goto failed;
Re: will ip 6 in ip4 tunnelling be fixed anytime soon ?
But you are right, here is a bug nobody reported before. I will take care of it. Hmm, your just a bit off here, I believe Gerhard has posted this bug a number of times, further more I have submitted a fix for this bug, but has still not been accepted. Neither has there been any feedback on why ? attached you will find my patch again. it's trivial but works no the less. I hope you will succeed where I have obvious have failed ... regards, Jorg de Jong Hi, I found that creating an ipv6 tunnel with ifconfig does not work. after some comparing between a 2.2 kernel and 2.4.0.testX I found that the name of the newly created sit device is not passed back to the reqestor. See linux/net/ipv6/addrconf.c and follow the call chain. This seems to be introduced by fact that the parameters in 2.4 are copied while in 2.2 kernels this was not the case. My simple patch fixes this one problem. after applying I can now successfuly create ipv6 tunnels with ifconfig. Please apply this patch. thanks, Jorg -- Jorg de Jong Work : mailto:[EMAIL PROTECTED] Play : mailto:[EMAIL PROTECTED] --- linux-2.4.0-test8/net/ipv6/sit.cMon Aug 28 21:03:11 2000 +++ linux/net/ipv6/sit.cTue Aug 15 22:28:27 2000 @@ -188,7 +188,7 @@ } if (i==100) goto failed; - memcpy(parms-name, dev-name, IFNAMSIZ); + memcpy(nt-parms.name, dev-name, IFNAMSIZ); } if (register_netdevice(dev) 0) goto failed;
Re: will ip 6 in ip4 tunnelling be fixed anytime soon ?
On Mon, Oct 09, 2000 at 11:44:34AM +0200, Jorg de Jong wrote:
your just a bit off here, I believe Gerhard has posted this bug
a number of times, further more I have submitted a fix for this
bug, but has still not been accepted. Neither has there been any feedback
on why ?
the address for bug fixes for the net-tools is [EMAIL PROTECTED] Your
patch does not address the net-tool, therefore i cannot apply it. We will
see who feels responsible for adding it to the kernel source. Alexey? Andi?
Davem? Alan?
I dont think there is a workaround in the net tools possible,m since the
SIOCSIFDSTADDR which is dispateched to addrconf_set_dstaddr will use
__dev_get_by_name to find the device (i dont know what for) and that will
fail without your patch.
Do u think a workaround in the net-tools is possible? I'm a little bit
confused where exactly the call fails. Since creating a sit device and then
assigning a tunnel address does not work, eighter.
Greetings
Bernd
--
(OO) -- [EMAIL PROTECTED] --
( .. ) ecki@{inka.de,linux.de,debian.org} http://home.pages.de/~eckes/
o--o *plush* 2048/93600EFD eckes@irc +497257930613 BE5-RIPE
(OO) When cryptography is outlawed, bayl bhgynjf jvyy unir cevinpl!
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
Re: will ip 6 in ip4 tunnelling be fixed anytime soon ?
Date:Tue, 10 Oct 2000 02:21:48 +0200 From: Bernd Eckenfels [EMAIL PROTECTED] We will see who feels responsible for adding it to the kernel source. Alexey? Andi? Davem? Alan? I have applied the fix, and will send it to Linus. Later, David S. Miller [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: will ip 6 in ip4 tunnelling be fixed anytime soon ?
On Sat, Oct 07, 2000 at 11:07:18PM -0700, Gerhard Mack wrote:
> [root@innerfire /root]# ifconfig sit0 tunnel ::206.123.31.102
> SIOCSIFDSTADDR: No buffer space available
what are you trying to do with this command? In case you want to set the
IPv4 Endpoint of the Tunnel you should set the IPv4 Address.
Well, anyway, for the tunnel (DSTADDR) you can use iptunnel.
But you are right, here is a bug nobody reported before. I will take care of
it.
Greetings
Bernd
--
(OO) -- [EMAIL PROTECTED] --
( .. ) ecki@{inka.de,linux.de,debian.org} http://home.pages.de/~eckes/
o--o *plush* 2048/93600EFD eckes@irc +497257930613 BE5-RIPE
(OO) When cryptography is outlawed, bayl bhgynjf jvyy unir cevinpl!
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
Re: will ip 6 in ip4 tunnelling be fixed anytime soon ?
On Sat, Oct 07, 2000 at 11:07:18PM -0700, Gerhard Mack wrote: > I would call this a bug: > [root@innerfire /root]# ifconfig sit0 tunnel ::206.123.31.102 > SIOCSIFDSTADDR: No buffer space available I noticed the same problem over here with Linux 2.4 (haven't tried test9 yet). BTW with Linux 2.2.17 it works fine. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: will ip 6 in ip4 tunnelling be fixed anytime soon ?
On Sun, 8 Oct 2000, Bernd Eckenfels wrote: > In article <[EMAIL PROTECTED]> you wrote: > > Is there an ETA on having ip6 in ip4 tunnelling working with the latest > > net-utils?? > > what is the problem? Do u have a bug or do u mean general IPv6 Support? > There are a lot of unoficial IPv6 Packages, Debian has a good Collection, > and we are trying to get them back into the Upstream. > > For net-tools, everything should be ok with 1.57 > > Greetings > Bernd I would call this a bug: [root@innerfire /root]# ifconfig sit0 tunnel ::206.123.31.102 SIOCSIFDSTADDR: No buffer space available [root@innerfire /root]# ifconfig -V net-tools 1.57 ifconfig 1.40 (2000-05-21) Dmesg confirms I've compiled in support: IPv6 v0.8 for NET4.0 IPv6 over IPv4 tunneling driver early initialization of device sit0 is deferred Gerhard -- Gerhard Mack [EMAIL PROTECTED] <>< As a computer I find your faith in technology amusing. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: will ip 6 in ip4 tunnelling be fixed anytime soon ?
On Sat, Oct 07, 2000 at 11:07:18PM -0700, Gerhard Mack wrote: I would call this a bug: [root@innerfire /root]# ifconfig sit0 tunnel ::206.123.31.102 SIOCSIFDSTADDR: No buffer space available I noticed the same problem over here with Linux 2.4 (haven't tried test9 yet). BTW with Linux 2.2.17 it works fine. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: will ip 6 in ip4 tunnelling be fixed anytime soon ?
On Sat, Oct 07, 2000 at 11:07:18PM -0700, Gerhard Mack wrote:
[root@innerfire /root]# ifconfig sit0 tunnel ::206.123.31.102
SIOCSIFDSTADDR: No buffer space available
what are you trying to do with this command? In case you want to set the
IPv4 Endpoint of the Tunnel you should set the IPv4 Address.
Well, anyway, for the tunnel (DSTADDR) you can use iptunnel.
But you are right, here is a bug nobody reported before. I will take care of
it.
Greetings
Bernd
--
(OO) -- [EMAIL PROTECTED] --
( .. ) ecki@{inka.de,linux.de,debian.org} http://home.pages.de/~eckes/
o--o *plush* 2048/93600EFD eckes@irc +497257930613 BE5-RIPE
(OO) When cryptography is outlawed, bayl bhgynjf jvyy unir cevinpl!
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
Re: will ip 6 in ip4 tunnelling be fixed anytime soon ?
In article <[EMAIL PROTECTED]> you wrote: > Is there an ETA on having ip6 in ip4 tunnelling working with the latest > net-utils?? what is the problem? Do u have a bug or do u mean general IPv6 Support? There are a lot of unoficial IPv6 Packages, Debian has a good Collection, and we are trying to get them back into the Upstream. For net-tools, everything should be ok with 1.57 Greetings Bernd - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: will ip 6 in ip4 tunnelling be fixed anytime soon ?
In article [EMAIL PROTECTED] you wrote: Is there an ETA on having ip6 in ip4 tunnelling working with the latest net-utils?? what is the problem? Do u have a bug or do u mean general IPv6 Support? There are a lot of unoficial IPv6 Packages, Debian has a good Collection, and we are trying to get them back into the Upstream. For net-tools, everything should be ok with 1.57 Greetings Bernd - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
will ip 6 in ip4 tunnelling be fixed anytime soon ?
Is there an ETA on having ip6 in ip4 tunnelling working with the latest net-utils?? -- Gerhard Mack [EMAIL PROTECTED] <>< As a computer I find your faith in technology amusing. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
will ip 6 in ip4 tunnelling be fixed anytime soon ?
Is there an ETA on having ip6 in ip4 tunnelling working with the latest net-utils?? -- Gerhard Mack [EMAIL PROTECTED] As a computer I find your faith in technology amusing. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
