0 Members and 1 Guest are viewing this topic.
Quote from: chrisgbk on February 24, 2008, 08:40:52 pmQuote from: bja888 on February 24, 2008, 08:14:42 pmQuote from: chrisgbk on February 24, 2008, 07:46:39 pmIn particular the one misguided individal who believed that IPv6 was synonymous was static addresses for every deviceThat would be awesome.You misunderstand what was meant by said person;...Humm... that would be rather stupid.Isn't the MAC address static? But you can't search the internet via MAC addr can you...
Quote from: bja888 on February 24, 2008, 08:14:42 pmQuote from: chrisgbk on February 24, 2008, 07:46:39 pmIn particular the one misguided individal who believed that IPv6 was synonymous was static addresses for every deviceThat would be awesome.You misunderstand what was meant by said person;...
Quote from: chrisgbk on February 24, 2008, 07:46:39 pmIn particular the one misguided individal who believed that IPv6 was synonymous was static addresses for every deviceThat would be awesome.
In particular the one misguided individal who believed that IPv6 was synonymous was static addresses for every device
Quote from: bja888 on February 25, 2008, 01:27:16 amQuote from: chrisgbk on February 24, 2008, 08:40:52 pmQuote from: bja888 on February 24, 2008, 08:14:42 pmQuote from: chrisgbk on February 24, 2008, 07:46:39 pmIn particular the one misguided individal who believed that IPv6 was synonymous was static addresses for every deviceThat would be awesome.You misunderstand what was meant by said person;...Humm... that would be rather stupid.Isn't the MAC address static? But you can't search the internet via MAC addr can you...A MAC address is only quasi-unique; not guaranteed to be unique. The original address assigned to a device never changes, but it's a trivial task to spoof a different MAC address, and many routers in particular support this functionality.
Plus MAC addresses are only visible on your local subnet. Your MAC address is only broadcasted as far as your router. MAC addresses are used to identify machines on links, so outside your local network it would then be the MAC of your cable modem and whatever devices are on that network, and then the next network would have the MACs of that network, etc, etc.So there is no way for, for example, me, to know what your MAC address is without being in your house.edit: Chris, you haven't answered me yet The question (about whether an AAAA record should be added) extends to anyone else who is familiar with IPv6 as well.
The main (only?) problem with people serving content on a dual-stacked machine under the same hostname is that some users have their applications and operating systems configured in such a way that their application/OS/etc thinks it has IPv6 connectivity, but it really doesn't. This will result in, say, Firefox having an A and AAAA record, and attempting to connect to the IPv6 address when it really doesn't have a functinal ipv6 connection. In this situation, the site would either take 10 minutes to load after every image and stylesheet request times out and falls back to ipv4, never loads at all, or at least times out once (then the application falls back to ipv4 for all subsquent requests).Mind you this happens to only people who have actively fecked up their configuration, or otherwise have very bad default configurations.I suppose it is worth a test at first, like if I scheduled a 1 hour time where the forums would have A and AAAA records, and then wait to see what kinds of problems people had (if any). If no problems we could try it again for a longer period of time, etc etc.Thoughts?
is there any benefit to you? It won't go any faster, it won't make breakfast. you don't really gain anything from using it except maybe you might feel good about being an early adopter. Thats about it.
Quote from: FliesLikeABrick on February 25, 2008, 02:46:38 pmThe main (only?) problem with people serving content on a dual-stacked machine under the same hostname is that some users have their applications and operating systems configured in such a way that their application/OS/etc thinks it has IPv6 connectivity, but it really doesn't. This will result in, say, Firefox having an A and AAAA record, and attempting to connect to the IPv6 address when it really doesn't have a functinal ipv6 connection. In this situation, the site would either take 10 minutes to load after every image and stylesheet request times out and falls back to ipv4, never loads at all, or at least times out once (then the application falls back to ipv4 for all subsquent requests).Mind you this happens to only people who have actively fecked up their configuration, or otherwise have very bad default configurations.I suppose it is worth a test at first, like if I scheduled a 1 hour time where the forums would have A and AAAA records, and then wait to see what kinds of problems people had (if any). If no problems we could try it again for a longer period of time, etc etc.Thoughts?I'd say go for it.
Quote from: †on April 14, 2008, 01:25:20 pmTo sum up my point: We had a multipage debate about toilet padding. (Putting TP in the water so you don't get splashed.)And we still don't know if dead guys can keep a stiffy.
To sum up my point: We had a multipage debate about toilet padding. (Putting TP in the water so you don't get splashed.)
Changing the system could just as easily give us a headache as it could save time and effort. All in all, it'd be up to you. I don't really see how any website would need the sheer volume of address space that IPv6 provides, but if it works, hell, why not use it?