Henning Moll wrote:
> Is my understanding correct that even this fix
> does not solve the problem for all applications?
Of course, it does not solve the problem for applications calling the
resolver explicitly with AF_INET6. That's bound to fail. These
applications would fail worse if libc behavio
Thomsas Butter wrote:
> Thanks for the good fix!
Is my understanding correct that even this fix does not solve the
problem for all applications?
--
IPv6 should be disabled by default
https://bugs.launchpad.net/bugs/24828
You received this bug notification because you are a member of Ubuntu
Bugs,
David: I've re-raised this as bug 156720 and a fix is in progress.
Thanks.
--
IPv6 should be disabled by default
https://bugs.launchpad.net/bugs/24828
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bug
This bug is back in gutsy. The patch should be applied again.
--
IPv6 should be disabled by default
https://bugs.launchpad.net/bugs/24828
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubunt
Thanks for the good fix!
--
IPv6 should be disabled by default
https://bugs.launchpad.net/bugs/24828
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailma
Rock, I really do feel this is the right solution
I guess at the end of the day your blacklisting kicked enough upraw to
fix the problem, so I guess it was the right move :)
Cheers!
Trent
--
IPv6 should be disabled by default
https://bugs.launchpad.net/bugs/24828
You received this bug notificat
Yes the blacklist has been removed already.
Fabio
--
IPv6 should be disabled by default
https://bugs.launchpad.net/bugs/24828
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https
As I understand it, a patch has now been applied to glibc
"A fixed glibc with the following patch has been uploaded today:
14:30 < Mithrandir> Uploading to ubuntu (via ftp to upload.ubuntu.com):
glibc_2.5-0ubuntu13.dsc: done. glibc_2.5-0ubuntu13.diff.gz: done.
glibc_2.5-0ubuntu13_source.changes:
Ouch, another comment here to say that blacklisting this broke a
perfectly working ipv6 system. I can see doing this for new installs,
but I don't think it's a good idea to break existing ones.
--
IPv6 should be disabled by default
https://bugs.launchpad.net/bugs/24828
You received this bug noti
>First my apologies for the initial remark. I did not realize that
>getaddrinfo() actually stopped doing if ipv6 was not loaded even
>if AI_ADDRCONFIG was not set.
Is it true?
Here feisty with libc-2.5.0ubuntu12
no ip6
but wget, for example, still request records
--
IPv6 should be di
The Vista DNS Query Behaviour is described here:
http://www.microsoft.com/technet/network/ipv6/vista_dns.mspx
"- If the host has only link-local or Teredo IPv6 addresses assigned, the DNS
Client service sends a single query for A records.
- If the host has at least one IPv6 address assigned that
First my apologies for the initial remark. I did not realize that
getaddrinfo() actually stopped doing if ipv6 was not loaded even
if AI_ADDRCONFIG was not set.
Answers inline.
Le lundi 2 avril 2007 06:53, Fabio Massimo Di Nitto a écrit :
> Remi, restoring IPv6 is a matter of adding/uncomm
On Tue, 03 Apr 2007 05:50:13 -, Thomas Butter <[EMAIL PROTECTED]> wrote:
> The relevant changes in glibc 2.5 are address sorting related. I don't
> think it allows disabling queries in gai.conf
Yes. These changes will NOT AT ALL fix the timeout problem. But some
people reported ther
Thomas Butter wrote:
>> Link local addresses aren't limited to just "link diagnostics", also
>> when using avahi/zeroconf, you may well have dns for just the local link.
>>
>
> I am no avahi expert so I could be wrong. I think avahi/zeroconf only
> uses the dns protocol, but won't use the glib
> Link local addresses aren't limited to just "link diagnostics", also
> when using avahi/zeroconf, you may well have dns for just the local link.
I am no avahi expert so I could be wrong. I think avahi/zeroconf only
uses the dns protocol, but won't use the glibc name resolution functions
with lin
Has anyone affected by this tried this in feisty? Apparently there may
be some changes in glibc 2.5 which affect this?
Trent
--
IPv6 should be disabled by default
https://bugs.launchpad.net/bugs/24828
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct s
Howdy,
>>> breaking ip6tables completely, since IPv6 autoloading got disabled,
>>> and any sane person will do firewall configuration before
>>> configuration the network interfaces.
> On my system, the upgrade also had the very unkind effect ofI usually
> load a firewall on given protocol once
Le lundi 2 avril 2007 18:39, vous avez écrit :
> /etc/network/interfaces is not considered a configuration file and no
> packages owns it. So you can modify it at will.
I was referring to the backlist file, not interfaces.
(...)
> I think the overall price is worth the benefit.
You won't think t
Rémi Denis-Courmont wrote:
> First my apologies for the initial remark. I did not realize that
> getaddrinfo() actually stopped doing if ipv6 was not loaded even
> if AI_ADDRCONFIG was not set.
no problem :)
>
> Answers inline.
>
> Le lundi 2 avril 2007 06:53, Fabio Massimo Di Nitto a éc
Remi, restoring IPv6 is a matter of adding/uncommenting a line in
interfaces or removing the blacklist. I don't believe that it can be
such big source of headackes.
What MacOS does is also not completely proper. I can have only link-local
address and use them to connect from one machine to anothe
I have serious doubts that blacklisting IPv6 really solves the problem.
glibc's getaddrinfo() will still query regardless, unless
AI_ADDRCONFIG flag is set. And it is very often *not* set, if only
because it is a "proprietary" GNU extension.
In other words, the problem is now fixed merely for
Scott: the problems are 2. hardware that people are forced to use and
broken ISP DNS.
once you load ipv6, the glibc resolver will query first and A later
as specified by Internet RFC's.
so when your application (clearly FF is the first one to really show it)
attempts to connect to www.foo.b
Maybe I'm missing the documentation, but with the exception of the
Firefox resolution thing, has anyone worked out why when v6 is enabled
DNS resolution is taking so much longer in these cases?
I have installed Ubuntu on many machines, none accessing a v6 network..
and yet none seem to have this p
Sami: done thanks. the comment should be there from the monday install
CD's or tomorrow network installations.
Fabio
--
IPv6 should be disabled by default
https://launchpad.net/bugs/24828
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-
Sami: good suggestion. I will see if i can get it done asap.
Fabio
--
IPv6 should be disabled by default
https://launchpad.net/bugs/24828
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Should there be a change in the default interfaces file so that it
includes a commented IPv6 line to allow easier enabling of IPv6 support?
--
IPv6 should be disabled by default
https://launchpad.net/bugs/24828
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/ma
Thomas, that's exactly what i told you.. just add a line like:
iface lo inet6 manual
to interfaces and you are done. no other changes.. everything will just
work from there on.. loading ipv6, autoconf and etc.
Fabio
--
IPv6 should be disabled by default
https://launchpad.net/bugs/24828
--
ub
> this change comes in combo with ifupdown that will do the
> right thing once you have at least one instance that
> requires ipv6.
ifupdown won't be able to know if I need ipv6 since ipv6 uses auto-
configuration when a router advertisement arrives and some applications
use link-local addresses w
Most of the beneficiaries of this change won't notice it. So let me say
"thank you" here.
Thanks to the developers for taking this action.
Thanks to those established users who know that IPv6 is an issue, for
making a small sacrifice to help out new users - like me - who don't
know that.
It's m
as explained on IRC, repeating here again i can add docs to the
ReleaseNotes...
this change comes in combo with ifupdown that will do the right thing
once you have at least one instance that requires ipv6.
it's the easiest solution that makes everybody happy.
Fabio
--
IPv6 should be disabled b
This is the most BS solution that I have seen in a while. I understand
that the technology is in its infancy, but disabling it is not the right
solution either.
In any case, I see your point.
Now for those of you who DO use ipv6 and care, perhaps you have enough
knowledge to simply enable the thi
Yes.. hence we need the ReleaseNote.. there is no other way around that
without a lot of magic that can behave really badly.
Fabio
--
IPv6 should be disabled by default
https://launchpad.net/bugs/24828
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/li
It is worth noting while the ifupdown changes will cause any static
setups to continue working, it will break setups relying on
autoconfiguration, which are quite common for those using IPv6.
--
IPv6 should be disabled by default
https://launchpad.net/bugs/24828
--
ubuntu-bugs mailing list
ubun
2 things:
1) a change to ifupdown has been done so that current setups will not
break (or shouldn't)
2) information to the Release note will be added as soon as somebody
from the doc team can tell me where they did move the page.
Fabio
--
IPv6 should be disabled by default
https://launchpad.ne
Ubuntu had IPv6 enabled for a long time. Now all other major OS (Vista,
OSX) have enabled it by default and Ubuntu will disable it without
warning for existing users?
--
IPv6 should be disabled by default
https://launchpad.net/bugs/24828
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Fixed in feisty by blacklisting ipv6
** Changed in: netcfg (Ubuntu)
Status: In Progress => Fix Released
--
IPv6 should be disabled by default
https://launchpad.net/bugs/24828
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Changed in: netcfg (Ubuntu)
Assignee: (unassigned) => Fabio Massimo Di Nitto
Status: Confirmed => In Progress
--
IPv6 should be disabled by default
https://launchpad.net/bugs/24828
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/
Here in France, Tecom AH4222 is distributed by one of the major FAIs,
and it suffers from this bug too.
Your reaction to the report is strange. I think we need to allow
disabling IPv6 easily, eg via a checkbox in System -> Administration
->Network, along with Avahi enabling option. We could add a
Thomas, perhaps I don't understand very well the features of ipv6 that
you mention. If it was just a matter of additional features, then the
solution would be the same as with providing compiz or beryl by default:
even if the scale (OSX exposé alike) plugin is really an usability aid,
since it show
I would be ok with leaving it enabled if there were an easy process to
disable it if needed. After doing a little research I did find this to
be a prevelent problem with Linux reguardless of distribution. Seems
that whatever solution is provided would benefit to any distro which has
IPv6 enabled.
> Disable IPv6 now and work towards getting a compatibility check in
place with clear and simple procedures for the users.
IPv6 is used in many university, some company networks. New routers
(e.g. the new Apple Airport Extreme) give you an 6to4 address
automatically. Disabling would remove an ofte
On 17/3/07 Trent Lloyd wrote:
> Please remember this has *nothing* to do with whether your modem/router
> *supports* IPv6, but whether its inherrently broken and doesn't handle DNS
> queries properly.
I agree with you 100% on this. I hate to have to find workarounds for
poorly developed software
I see a "solution" to this bug. In my opinion, if you need ipv6, your
ISP will warn you, and you will know. So, the solution could be
blacklisting ipv6 by default, and putting a checkbox in
system/administration/network/general to enable it (the module can be
loaded on the fly I suppose, so there w
Please remember this has *nothing* to do with whether your modem/router
*supports* IPv6, but whether its inherrently broken and doesn't handle
DNS queries properly.
I'm not saying this makes it any less of a problem but you must
understand its a bug in the devices, they should just pass the DNS
re
I believe that enabling or disabling ipv6 on install or in the network
management application should be an option. With appropriate warnings
about future compatibility and current performance issues.
In trying out Ubuntu 6.10 Edgy-Eft I found Internet access with Firefox
extremely slow to non-exi
The problem is caused by buggy caching dns servers in the routers. The
IPv4 (!) dns query for a is simply ignored and not answered so the
resolver waits until it timeouts.
You can see this when you do a "host -t www.kame.net" on a machine
behind that router and on any other machine with
Disabling and enabling ipv6 is simple, so, given the current transition
situation, we should provide a menu entry and a simple dialog to do
this.
Regarding choosing the default behavior, I still am inclined towards
ipv4, since if you need ipv6, then your ISP will warn you and you will
know this, b
A very simple explanation on why I did set this to wishlist is because
there are other users like you that have the exact opposite problems.
There is no straight solution to this issue if not complaining to your
hw manifacturer or ISP to install some decent compliant software.
The same way I did s
I personally *suspect* from what I've seen vista would see the same
problems, however I don't know, haven't tested, and would be interested
to hear from anyone that has tried it.
Also this isn't about IPv6 at all, this is about disabling a potentially
usefull feature, to work around broken hardwar
Well, interesting debate. Glad I've made a difference by resurrecting
the defect - though getting it put onto the wishlist was not actually
what I hoped for!
Perhaps Vicenzo you are right that this needs to go onto a developer
discussion, and not just because the defect has been iced. There are
On 12/23/06, Vincenzo Ciancia <[EMAIL PROTECTED]> wrote:
> Kristian: we all fixed that ourselves, I personally am worried for
> newbies who will just not understand why e.g. google earth is unusable
> on their system, and will trash ubuntu. Many of them will trash
> GNU/linux "in toto", because ubu
Kristian: we all fixed that ourselves, I personally am worried for
newbies who will just not understand why e.g. google earth is unusable
on their system, and will trash ubuntu. Many of them will trash
GNU/linux "in toto", because ubuntu is nowadays advertised as the "best
and easiest to use" linux
Trent Lloyd : most of the people here use "Analog: Netopia" 3346 or "ISDN:
Netopia 3356".
This information can be found on the homepage of the biggest swiss ISP:
http://de.bluewin.ch/internetzugang/index.php/endgeraete_adsl
--
IPv6 should be disabled by default
https://launchpad.net/bugs/24828
** Changed in: netcfg (Ubuntu)
Importance: Medium => Wishlist
--
IPv6 should be disabled by default
https://launchpad.net/bugs/24828
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
> By that same token of advice, why not just disable IPv6 yourself?
I have done!
It took me eight hours of my own time, spread over several days, and the
involvement of five members of the Ubuntu community on the newbie forum,
to work out that I needed to do that.
I would have been seriously mor
On 12/20/06, Martin Tasker <[EMAIL PROTECTED]> wrote:
> I respect Kristian Hermansen's conciliatory suggestion, but I am not
> keen on it. It's bad to offer users a choice between options they don't
> understand. If you offer them such choice, you must of course tell
> people to select IPv4 unles
Vicenzo Ciancia wrote: "I think it would be better to disable it until a
better solution is found. I have seen bugs wait for months an important
decision leaving users machines broken, when a quick fix was known ..."
I agree 100%. And with Vicenzo's other comments.
Trent Lloyd wrote: "Windows Vi
Asraniel - and as I requested, what make/model are the routers that "98%
of switzerland" use?
--
IPv6 should be disabled by default
https://launchpad.net/bugs/24828
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Why not just change the Ubuntu installer to query the user for IPv6
support? Jzzz!
--
Kristian Hermansen
--
IPv6 should be disabled by default
https://launchpad.net/bugs/24828
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bug
Il giorno mer, 20/12/2006 alle 07.36 +, Trent Lloyd ha scritto:
So the way to fix the problems with an upcoming technology is to supress
> it? Thats silly.. Disabling it by default out of the box also does not
> aid adoption.
>
Well, I never liked to be pushed to early adoption of a technology
98% dont have a problem?thats not true. in switzerland 98% of the
routers have this problem, just that you know it.
--
IPv6 should be disabled by default
https://launchpad.net/bugs/24828
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bu
So the way to fix the problems with an upcoming technology is to supress
it? Thats silly.. Disabling it by default out of the box also does not
aid adoption.
As far as I can see, this is a limited issue to those with "broken"
routers, probably 98% of devices on the market have no problems with
thi
Please raise this to critical and schedule into Feisty.
It's critical because it's part of the post-installation user experience
and damages Ubuntu's credibility exactly in the eyes of those whom its
trying to reach. This bug's been open for 14 months now, and is trivial
to fix, so obviously any
I had strange behavior on NFS mounts via wifi at home, it had high
bandwidth in the beginning but then it dropped down, and with delays
large enough to forbid watching videos over NFS. Other laptops on the
same network have no problems (running dapper), and using other
distributions (suse 10.0) on
** Changed in: Ubuntu
Sourcepackagename: None => netcfg
--
IPv6 should be disabled by default
https://launchpad.net/bugs/24828
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Just my $0.002: I had horrible DNS resolution times ( > 10 seconds ) for
a long time and I assumed that it was because my router / ISP didn't
support ipv6, so I went through the hassle of turning off ipv6 and the
problems that come from that.
This week I decided to switch to openDNS
http://en.wiki
> It is worse than that. In the time it takes for the IPv6 DNS request to
> fail the application times out on making its connection.
seems ipv6 causes connection issues as in:
http://ubuntuforums.org/showthread.php?t=258686 though I'm not sure if
that's a problem with the user's router or with the
** Tags added: ipv6
--
IPv6 should be disabled by default
https://launchpad.net/bugs/24828
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
On Fri, Jul 28, 2006 at 04:23:11AM -, Martin Hosken wrote:
> Dear Trent,
> > Disabling IPv6 increaseing the throughput of your internet connection
> > makes no sense and I think thats just circumstantial, sorry :)
> >
> > The place where it *does* make a difference is the speed of new
> > conne
Dear Trent,
> Disabling IPv6 increaseing the throughput of your internet connection
> makes no sense and I think thats just circumstantial, sorry :)
>
> The place where it *does* make a difference is the speed of new
> connections, it seems that in some cases certain dns servers ignore
> requests f
Disabling IPv6 increaseing the throughput of your internet connection
makes no sense and I think thats just circumstantial, sorry :)
The place where it *does* make a difference is the speed of new
connections, it seems that in some cases certain dns servers ignore
requests for IPv6 records and so
** Bug 54156 has been marked a duplicate of this bug
--
IPv6 should be disabled by default
https://launchpad.net/bugs/24828
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
72 matches
Mail list logo
