Congratulations!

[Valid RSS] This is a valid RSS feed.

Recommendations

This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.

Source: https://www.sixxs.net/forum/rss/?general

  1. <?xml version="1.0" encoding="utf-8"?>
  2. <!-- RSS generated by SixXS (https://www.sixxs.net) for general -->
  3. <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  4. <channel>
  5. <title>SixXS Forum: General</title>
  6. <link>https://www.sixxs.net/forum/?msg=general&amp;from=rss</link>
  7. <description>If it doesn't fit in any of the other forums then it apparently needs to go here.
  8.  
  9. </description>
  10. <language>en-us</language>
  11. <copyright>Copyright 2000-2017 SixXS</copyright>
  12. <lastBuildDate>Mon, 05 Jun 2017 18:00:00 +0000</lastBuildDate>
  13. <docs>http://cyber.law.harvard.edu/rss/rss.html</docs>
  14. <generator>SixXS Website (https://www.sixxs.net)</generator>
  15. <category domain="IPv6">SixXS Forum</category>
  16. <managingEditor>info@sixxs.net (SixXS)</managingEditor>
  17. <webMaster>info@sixxs.net (SixXS)</webMaster>
  18. <ttl>30</ttl>
  19. <atom:link href="https://www.sixxs.net/forum/rss/?general" rel="self" type="application/rss+xml" />
  20. <item>
  21. <title>Thanks to SixXS and FTB Nederland</title>
  22. <link>https://www.sixxs.net/forum/?msg=general-16091709&amp;from=rss</link>
  23. <comments>https://www.sixxs.net/forum/?msg=general-16091709&amp;from=rss</comments>
  24. <description>Thanks to SixXS for giving me years of IPv6 access.
  25. Thanks to FTB Nederland for providing native IPv6 on their FTTB network in Nootdorp, the Netherlands, just in time!
  26.  
  27. </description>
  28. <pubDate>Sun, 04 Jun 2017 22:36:29 +0000</pubDate>
  29. <guid>https://www.sixxs.net/forum/?msg=general-16091709&amp;from=rss</guid>
  30. <author>PZ1453-RIPE@whois.sixxs.net (Pim  Zandbergen)</author>
  31. </item>
  32. <item>
  33. <title>Status; thanks</title>
  34. <link>https://www.sixxs.net/forum/?msg=general-16086121&amp;from=rss</link>
  35. <comments>https://www.sixxs.net/forum/?msg=general-16086121&amp;from=rss</comments>
  36. <description>First, thanks for providing the service.
  37.  
  38. Despite many calls and escalations (dating back to 2008), Verizon's FiOs service (U.S., one of the few Fiber to the Home services), has not deployed IPv6.
  39.  
  40. There have been many promises/trial balloons (reports of field trials, promises of deployment dates etc) from various levels of management, but no results.
  41.  
  42. Calling doesn't help; sales doesn't want to hear about anything not in the book - the old &#38;quot;We're the telephone company, we don't have to care&#38;quot; line comes to mind.  The tech support people come in two camps: Those who haven't a clue what IPv6 is, and those who do, commiserate, but can't help.  The latter tell wildly different stories - from &#38;quot;coming soon&#38;quot;, to &#38;quot;you don't need it&#38;quot;, to &#38;quot;we haven't had an update since 2010&#38;quot;, to &#38;quot;it's on the backbone, but not to the field&#38;quot;, to &#38;quot;it's in the field, but can't be turned on due to provisioning issues&#38;quot;.   And that's just a subset.  Mangers listen sympathetically, promise to investigate and call back - but never do.
  43.  
  44. I used to have direct lines to the product mangers, but they've retired/moved on.  Current employees can't provide the new names.  And calls to the Executive offices get no results either.
  45.  
  46. I couldn't find a place to login to your wiki; this status belongs there.  Verizon is a huge provider - and in the US, often the only one serving a city.  Or in the rare case where there is some competition, the only one with symmetric speeds.  They've also stopped their fiber roll-out in favor of wireless investment; places that have their DSL service are in worse shape. DSL speeds AND no IPv6.   (Verizon took over the GTE ISP business years ago.)
  47.  
  48. How long will it be before the address blocks are reissued?  Tracking down all the firewalls that need to block the old addresses (especially on systems that boot infrequently/are mobile) will take longer than expected...
  49.  
  50. Thanks again for your dedication and years of service.
  51.  
  52. </description>
  53. <pubDate>Wed, 31 May 2017 08:06:03 +0000</pubDate>
  54. <guid>https://www.sixxs.net/forum/?msg=general-16086121&amp;from=rss</guid>
  55. <author>TLC6-SIXXS@whois.sixxs.net (Timothe litt)</author>
  56. </item>
  57. <item>
  58. <title>Thank you!</title>
  59. <link>https://www.sixxs.net/forum/?msg=general-16024509-16082921&amp;from=rss</link>
  60. <comments>https://www.sixxs.net/forum/?msg=general-16024509-16082921&amp;from=rss</comments>
  61. <description>Josh Haupt wrote:
  62. &#60;div class=&#34;quote&#34;&#62;Thank you for providing such a great service.
  63. I wish you best of luck on your future projects.
  64.  
  65. -Josh
  66. &#60;/div&#62;
  67.  
  68. I think, it's a good idea to do it in the same way:
  69. Thank you and the involved ISP for providing such a very good service.
  70. Personally I think, ip6-tunneling is still a good option for the future (may be for backup-purposes, providing really static-ip6-Adresses and so on). So I'm a little bit worried about Sixxs taking down the service. So I just shut down my tunnel -- sigh. Thanks a lot.
  71.  
  72. Martin Moutarde
  73.  
  74. </description>
  75. <pubDate>Sun, 28 May 2017 19:35:30 +0000</pubDate>
  76. <guid>https://www.sixxs.net/forum/?msg=general-16024509-16082921&amp;from=rss</guid>
  77. <author>MMX12-SIXXS@whois.sixxs.net (Martin Moutarde)</author>
  78. </item>
  79. <item>
  80. <title>Thank you!</title>
  81. <link>https://www.sixxs.net/forum/?msg=general-16024509-16080825&amp;from=rss</link>
  82. <comments>https://www.sixxs.net/forum/?msg=general-16024509-16080825&amp;from=rss</comments>
  83. <description>Premium work at SixXS.  Thank you for the great service.  One of my sites has native IPv6 (Comcast residential in Connecticut) and the other still does not (Cablevision residential in Connecticut.)  
  84.  
  85. SixXS punked mult-billion dollar Cablevision in IPv6 support!  Nice.
  86.  
  87. </description>
  88. <pubDate>Fri, 26 May 2017 19:40:31 +0000</pubDate>
  89. <guid>https://www.sixxs.net/forum/?msg=general-16024509-16080825&amp;from=rss</guid>
  90. <author>DMC2-SIXXS@whois.sixxs.net (Daniel Massameno)</author>
  91. </item>
  92. <item>
  93. <title>Sorry to see SixXS go</title>
  94. <link>https://www.sixxs.net/forum/?msg=general-16068441&amp;from=rss</link>
  95. <comments>https://www.sixxs.net/forum/?msg=general-16068441&amp;from=rss</comments>
  96. <description>I'm really sorry to see SixXS go.   Looking back through my archives, I see I've been using SixXS for almost six years and it looks as though until I switched tunnel provider at the weekend my tunnel had been up and running for just over five years (that was my second tunnel replacing the original ayiya tunnel I'd had for the previous year).
  97.  
  98. My ISP, Plusnet, has said that they'll eventually provide IPv6 but they won't tell me their timescales.
  99.  
  100. Special thanks to everyone involved in SixXS.
  101.  
  102. jch
  103.  
  104. </description>
  105. <pubDate>Wed, 17 May 2017 08:39:48 +0000</pubDate>
  106. <guid>https://www.sixxs.net/forum/?msg=general-16068441&amp;from=rss</guid>
  107. <author>JHS13-SIXXS@whois.sixxs.net (John Haxby)</author>
  108. </item>
  109. <item>
  110. <title>Where to go post Sixxs?</title>
  111. <link>https://www.sixxs.net/forum/?msg=general-16037109-16037129-16037313-16037321-16057353-16058817&amp;from=rss</link>
  112. <comments>https://www.sixxs.net/forum/?msg=general-16037109-16037129-16037313-16037321-16057353-16058817&amp;from=rss</comments>
  113. <description>Jeroen Massar wrote:
  114. &#60;div class=&#34;quote&#34;&#62;SPF checks for gmail work quite fine. Can you be more specific?
  115. &#60;/div&#62;
  116.  
  117. gmail's SPF checks seem to work fine now, but a few years ago had some weird issues and I had to temporarily force my emails to gmail's servers to use IPv6. The problem disappeared after a few weeks.
  118.  
  119. </description>
  120. <pubDate>Tue, 16 May 2017 11:23:05 +0000</pubDate>
  121. <guid>https://www.sixxs.net/forum/?msg=general-16037109-16037129-16037313-16037321-16057353-16058817&amp;from=rss</guid>
  122. <author>ISJ2-SIXXS@whois.sixxs.net (Ivan Skytte Joergensen)</author>
  123. </item>
  124. <item>
  125. <title>Where to go post Sixxs?</title>
  126. <link>https://www.sixxs.net/forum/?msg=general-16037109-16065577&amp;from=rss</link>
  127. <comments>https://www.sixxs.net/forum/?msg=general-16037109-16065577&amp;from=rss</comments>
  128. <description>Andre-John Mas wrote:
  129. &#60;div class=&#34;quote&#34;&#62;Not all of us are in a position to get native IPv6 in the local area, due to dinosaur or monopoly ISPs. For people in that position, what alternatives are recommended?
  130.  
  131. Currently Hurricane Electric and Teredo come to mind, though it would be good to have a list of other solutions as fallback plans.
  132. &#60;/div&#62;
  133.  
  134. Your ISP may offer you a tunnel. I can't speak for any Canadian ISPs but in the US, Charter and Sonic.net both offer IPv6 by 6rd.
  135.  
  136. </description>
  137. <pubDate>Mon, 15 May 2017 04:06:12 +0000</pubDate>
  138. <guid>https://www.sixxs.net/forum/?msg=general-16037109-16065577&amp;from=rss</guid>
  139. <author>JHD7-SIXXS@whois.sixxs.net (Josh Haupt)</author>
  140. </item>
  141. <item>
  142. <title>Where to go post Sixxs?</title>
  143. <link>https://www.sixxs.net/forum/?msg=general-16037109-16037129-16037313-16037321-16057353-16058781&amp;from=rss</link>
  144. <comments>https://www.sixxs.net/forum/?msg=general-16037109-16037129-16037313-16037321-16057353-16058781&amp;from=rss</comments>
  145. <description>&#60;div class=&#34;quote&#34;&#62;I can't speak for others but I have been using IPv6 to route around damage, eg. gmail's malfunctioning SPF checks.&#60;/div&#62;
  146. SPF checks for gmail work quite fine. Can you be more specific?
  147.  
  148. </description>
  149. <pubDate>Wed, 10 May 2017 13:46:42 +0000</pubDate>
  150. <guid>https://www.sixxs.net/forum/?msg=general-16037109-16037129-16037313-16037321-16057353-16058781&amp;from=rss</guid>
  151. <author>JRM1-RIPE@whois.sixxs.net (Jeroen Massar)</author>
  152. </item>
  153. <item>
  154. <title>ULA registration</title>
  155. <link>https://www.sixxs.net/forum/?msg=general-16053053-16058757&amp;from=rss</link>
  156. <comments>https://www.sixxs.net/forum/?msg=general-16053053-16058757&amp;from=rss</comments>
  157. <description>Michiel van der Vlist wrote:
  158. &#60;div class=&#34;quote&#34;&#62;I registered an RFC4193 Unique Local Address wth SixXs.
  159.  
  160. What will happen to that after SixXs sunset?
  161. &#60;/div&#62;
  162.  
  163. Like the rest of the website, it will become static.
  164.  
  165. Please do read the ULA page, it contains very important information about that registry since the day we put it up there.
  166.  
  167. </description>
  168. <pubDate>Wed, 10 May 2017 13:44:20 +0000</pubDate>
  169. <guid>https://www.sixxs.net/forum/?msg=general-16053053-16058757&amp;from=rss</guid>
  170. <author>JRM1-RIPE@whois.sixxs.net (Jeroen Massar)</author>
  171. </item>
  172. <item>
  173. <title>Where to go post Sixxs?</title>
  174. <link>https://www.sixxs.net/forum/?msg=general-16037109-16037129-16037313-16037321-16057353&amp;from=rss</link>
  175. <comments>https://www.sixxs.net/forum/?msg=general-16037109-16037129-16037313-16037321-16057353&amp;from=rss</comments>
  176. <description>Jeroen Massar wrote:
  177. &#60;div class=&#34;quote&#34;&#62;The better question you should be asking is what you want to achieve.
  178. &#60;/div&#62;
  179.  
  180. I can't speak for others but I have been using IPv6 to route around damage, eg. gmail's malfunctioning SPF checks.
  181.  
  182. AWS EC2 also finally offers IPv6 and I was planning on giving my 10+ instances IPv6 addresses so I can access them directly instead of going via a jump server or paying for additional static IPv4 addresses. But then the Sixxs announcement ticked in...
  183.  
  184. I have been looking for native IPv6 for more than 10 years, but without luck. Where I live I can get fiber (no IPv6 offered), cable (no IPv6 offered) and xDSL. One (1) of the xDSL ISPs offer IPv6 depending on the equipment the incumbent telco has installed. That ISP is also the only ISP that don't have enough IPv4 addresses so you get stuck behind CG-NAT.
  185.  
  186. So I'm looking into how get IPv6 connectivity. So far it looks like a tunnel from he.net, or my own setup with openvpn tunnel to a VPS in a hosting center that has IPv6.
  187.  
  188. I'm not complaining about the closure of Sixxs. I understand the reason. The IPv6 connectivity has allowed me to develop applications with IPv6 support for more than 10 years and and it would have been possible with Sixxs.
  189.  
  190. </description>
  191. <pubDate>Tue, 09 May 2017 18:56:08 +0000</pubDate>
  192. <guid>https://www.sixxs.net/forum/?msg=general-16037109-16037129-16037313-16037321-16057353&amp;from=rss</guid>
  193. <author>ISJ2-SIXXS@whois.sixxs.net (Ivan Skytte Joergensen)</author>
  194. </item>
  195. <item>
  196. <title>ULA registration</title>
  197. <link>https://www.sixxs.net/forum/?msg=general-16053053&amp;from=rss</link>
  198. <comments>https://www.sixxs.net/forum/?msg=general-16053053&amp;from=rss</comments>
  199. <description>I registered an RFC4193 Unique Local Address wth SixXs.
  200.  
  201. What will happen to that after SixXs sunset?
  202.  
  203. </description>
  204. <pubDate>Sat, 06 May 2017 23:09:29 +0000</pubDate>
  205. <guid>https://www.sixxs.net/forum/?msg=general-16053053&amp;from=rss</guid>
  206. <author>MVDV4-SIXXS@whois.sixxs.net (Michiel van der Vlist)</author>
  207. </item>
  208. <item>
  209. <title>Does account removal also remove the -SIXXS RIR handle?</title>
  210. <link>https://www.sixxs.net/forum/?msg=general-16047733-16048893-16048973&amp;from=rss</link>
  211. <comments>https://www.sixxs.net/forum/?msg=general-16047733-16048893-16048973&amp;from=rss</comments>
  212. <description>Jeroen Massar wrote:
  213. &#60;div class=&#34;quote&#34;&#62;But per 2017-06-06 all will be gone.
  214. &#60;/div&#62;
  215.  
  216. That answers my question and is as I'd expect it would be. Thanks for both the answer and SixXS in general.
  217.  
  218. </description>
  219. <pubDate>Wed, 03 May 2017 11:33:15 +0000</pubDate>
  220. <guid>https://www.sixxs.net/forum/?msg=general-16047733-16048893-16048973&amp;from=rss</guid>
  221. <author>EKVW1-SIXXS@whois.sixxs.net (Ewoud Kohl van Wijngaarden)</author>
  222. </item>
  223. <item>
  224. <title>Does account removal also remove the -SIXXS RIR handle?</title>
  225. <link>https://www.sixxs.net/forum/?msg=general-16047733-16048893&amp;from=rss</link>
  226. <comments>https://www.sixxs.net/forum/?msg=general-16047733-16048893&amp;from=rss</comments>
  227. <description>Ewoud Kohl van Wijngaarden wrote:
  228. &#60;div class=&#34;quote&#34;&#62;I couldn't find this in the FAQ, but I'm wondering if removing my account also removes the -SIXXS RIR handle. In case it's not obvious, it has no other use and I'd like it removed.
  229. &#60;/div&#62;
  230.  
  231. Note that SixXS is &#60;b&#62;NOT&#60;/b&#62; a RIR, as such there is no such thing as a '-SIXXS RIR handle'.
  232. You likely just mean &#38;quot;-SIXXS whois person record'.
  233.  
  234. Removing an account marks the handle as deleted, for -SIXXS that means it becomes invisible to the system and that whois.sixxs.net does not show it anymore.
  235.  
  236. For non -SIXXS handles (-RIPE, -ARIN, -AP etc) one would separately need to remove it from that RIR.
  237.  
  238. For RIPE and APNIC prefixes, the related inet6nums will get cleaned up after a month.
  239.  
  240. But per 2017-06-06 all will be gone.
  241.  
  242. </description>
  243. <pubDate>Wed, 03 May 2017 07:02:07 +0000</pubDate>
  244. <guid>https://www.sixxs.net/forum/?msg=general-16047733-16048893&amp;from=rss</guid>
  245. <author>JRM1-RIPE@whois.sixxs.net (Jeroen Massar)</author>
  246. </item>
  247. <item>
  248. <title>Does account removal also remove the -SIXXS RIR handle?</title>
  249. <link>https://www.sixxs.net/forum/?msg=general-16047733&amp;from=rss</link>
  250. <comments>https://www.sixxs.net/forum/?msg=general-16047733&amp;from=rss</comments>
  251. <description>I couldn't find this in the FAQ, but I'm wondering if removing my account also removes the -SIXXS RIR handle. In case it's not obvious, it has no other use and I'd like it removed.
  252.  
  253. </description>
  254. <pubDate>Tue, 02 May 2017 23:30:46 +0000</pubDate>
  255. <guid>https://www.sixxs.net/forum/?msg=general-16047733&amp;from=rss</guid>
  256. <author>EKVW1-SIXXS@whois.sixxs.net (Ewoud Kohl van Wijngaarden)</author>
  257. </item>
  258. <item>
  259. <title>IPv6 with pfSense</title>
  260. <link>https://www.sixxs.net/forum/?msg=general-16040373&amp;from=rss</link>
  261. <comments>https://www.sixxs.net/forum/?msg=general-16040373&amp;from=rss</comments>
  262. <description>For those of you interested in IPv6:
  263.  
  264. IPv6-Verteilung
  265. page 131
  266. ct 2016, Heft 24
  267. https://www.heise.de/ct/ausgabe/2016-24-pfSense-als-Load-Balancer-3458348.html
  268.  
  269. I'll try this with my pfSense running on Shuttle DS437. Already with Multi-WAN VDSL (sunrise.ch private IPv4 only) and LTE.
  270.  
  271. I ordered now one more naked DSL for getting IPv6.
  272.  
  273. This is triple Multi-WAN (VDSL IPv4 only, VDSL dual stack and LTE) with load balancing. Also with Unbound DNS Resolver.
  274.  
  275. This is fun ;-)
  276.  
  277. </description>
  278. <pubDate>Thu, 27 Apr 2017 15:58:44 +0000</pubDate>
  279. <guid>https://www.sixxs.net/forum/?msg=general-16040373&amp;from=rss</guid>
  280. <author>AWD5-SIXXS@whois.sixxs.net (Andreas WERNER)</author>
  281. </item>
  282. <item>
  283. <title>Where to go post Sixxs?</title>
  284. <link>https://www.sixxs.net/forum/?msg=general-16037109-16037129-16037313-16037321&amp;from=rss</link>
  285. <comments>https://www.sixxs.net/forum/?msg=general-16037109-16037129-16037313-16037321&amp;from=rss</comments>
  286. <description>Yes, monopolies are all around the world. Call Your Government to solve that problem (they won't because those monopolies have invested lots of money in that government... they learned from Bell, AT&#38;amp;T and Microsoft...).
  287.  
  288.  
  289. The better question you should be asking is what you want to achieve.
  290.  
  291.  
  292. For most people that seems to be &#38;quot;the ability to easily reach my machines at home&#38;quot;. The other one &#38;quot;I do not trust my local ISP&#38;quot; and another &#38;quot;I don't ever want to renumber&#38;quot;.
  293.  
  294. For many of those cases, a bog-standard VPN (we recommend Wireguard and OpenVPN) can be the best way to go.
  295.  
  296. But if you actually had an ISP that delivered what you wanted, then you would not have to do those tricks ;)
  297.  
  298. </description>
  299. <pubDate>Tue, 25 Apr 2017 17:13:33 +0000</pubDate>
  300. <guid>https://www.sixxs.net/forum/?msg=general-16037109-16037129-16037313-16037321&amp;from=rss</guid>
  301. <author>JRM1-RIPE@whois.sixxs.net (Jeroen Massar)</author>
  302. </item>
  303. <item>
  304. <title>Where to go post Sixxs?</title>
  305. <link>https://www.sixxs.net/forum/?msg=general-16037109-16037129-16037313&amp;from=rss</link>
  306. <comments>https://www.sixxs.net/forum/?msg=general-16037109-16037129-16037313&amp;from=rss</comments>
  307. <description>Jeroen Massar wrote:
  308. &#60;div class=&#34;quote&#34;&#62;IPv6 is 20 years old.
  309.  
  310.  
  311. You had quite a bit of time to convince an ISP to start doing IPv6 by complaining and voting with your money.
  312.  
  313. Contacting your Network Operator Groups (NANOG, FrNOG, SwiNOG, NLNOG, DENOG, etc) is a good place to complain, bit late to do that, but you can always try....
  314.  
  315.  
  316. Btw: Teredo is long long dead fortunately.
  317. &#60;/div&#62;
  318.  
  319. Believe me I have tried. Welcome to North America, a continent where ISP choice is not always an option and when it is the alternatives aren't much better. But, I hear you.
  320.  
  321. </description>
  322. <pubDate>Tue, 25 Apr 2017 17:08:37 +0000</pubDate>
  323. <guid>https://www.sixxs.net/forum/?msg=general-16037109-16037129-16037313&amp;from=rss</guid>
  324. <author>AME4-SIXXS@whois.sixxs.net (Andre-John Mas)</author>
  325. </item>
  326. <item>
  327. <title>Where to go post Sixxs?</title>
  328. <link>https://www.sixxs.net/forum/?msg=general-16037109-16037129&amp;from=rss</link>
  329. <comments>https://www.sixxs.net/forum/?msg=general-16037109-16037129&amp;from=rss</comments>
  330. <description>IPv6 is 20 years old.
  331.  
  332.  
  333. You had quite a bit of time to convince an ISP to start doing IPv6 by complaining and voting with your money.
  334.  
  335. Contacting your Network Operator Groups (NANOG, FrNOG, SwiNOG, NLNOG, DENOG, etc) is a good place to complain, bit late to do that, but you can always try....
  336.  
  337.  
  338. Btw: Teredo is long long dead fortunately.
  339.  
  340. </description>
  341. <pubDate>Tue, 25 Apr 2017 10:28:15 +0000</pubDate>
  342. <guid>https://www.sixxs.net/forum/?msg=general-16037109-16037129&amp;from=rss</guid>
  343. <author>JRM1-RIPE@whois.sixxs.net (Jeroen Massar)</author>
  344. </item>
  345. <item>
  346. <title>Thank you!</title>
  347. <link>https://www.sixxs.net/forum/?msg=general-16024509-16037121&amp;from=rss</link>
  348. <comments>https://www.sixxs.net/forum/?msg=general-16024509-16037121&amp;from=rss</comments>
  349. <description>I also echo the thanks for making a SixXS a solution for getting IPv6 when there were no easy ways to get it.
  350.  
  351. While native IPv6 may still not be available for everyone, this is a great opportunity for other transition solutions to make themselves available and for continuing noise to be made on the technology.
  352.  
  353. </description>
  354. <pubDate>Tue, 25 Apr 2017 10:25:53 +0000</pubDate>
  355. <guid>https://www.sixxs.net/forum/?msg=general-16024509-16037121&amp;from=rss</guid>
  356. <author>AME4-SIXXS@whois.sixxs.net (Andre-John Mas)</author>
  357. </item>
  358. <item>
  359. <title>Where are the IPv6 Wifi repeaters/extenders?</title>
  360. <link>https://www.sixxs.net/forum/?msg=general-16037093-16037113&amp;from=rss</link>
  361. <comments>https://www.sixxs.net/forum/?msg=general-16037093-16037113&amp;from=rss</comments>
  362. <description>Wi-Fi does not care (too much) about IPv6, as it is just Ethernet on that layer.
  363.  
  364. The only problem for any carrier of IPv6, be that normal wired Ethernet or not-wired Ethernet (aka Wi-Fi) is primarily Multicast. This due to Neighbour Discovery.
  365.  
  366. Nothing special is needed for any Wi-Fi device though. But like switches that do L2 MLD snooping, that kind of construct can also conflict with IPv6.
  367.  
  368. The device that handles the actual routing needs to support IPv6 explicitly though.
  369.  
  370.  
  371. That said, Wifi &#38;quot;repeaters&#38;quot; and &#38;quot;extenders&#38;quot; are typically a really bad idea: they at minimum cut the throughput in half, as it receives and then re-sends in the same frequency band.
  372.  
  373.  
  374. A Raspberry Pi, or any other such solution, would have the same problems, just deploy one with two WiFi-sticks, let one play AP and the other a client to the network you are trying to extend. As per above: you lose a lot of bandwidth that way....
  375.  
  376. Better to just pull an Ethernet cable to a second Access Point and let it properly distribute the Wi-Fi signal there.
  377.  
  378. Or if you can't pull a wire, get a proper access point, for budget minded, the &#60;a href=&#34;https://www.ubnt.com/unifi/unifi-ap-ac-pro/&#34;&#62;Ubiquiti AP AC Pro&#60;/a&#62; comes to mind, which is a very normal Layer 2 Wi-Fi Access Point and thus does no routing of any kind, that is for a router to do....
  379.  
  380. </description>
  381. <pubDate>Tue, 25 Apr 2017 10:24:45 +0000</pubDate>
  382. <guid>https://www.sixxs.net/forum/?msg=general-16037093-16037113&amp;from=rss</guid>
  383. <author>JRM1-RIPE@whois.sixxs.net (Jeroen Massar)</author>
  384. </item>
  385. <item>
  386. <title>Where to go post Sixxs?</title>
  387. <link>https://www.sixxs.net/forum/?msg=general-16037109&amp;from=rss</link>
  388. <comments>https://www.sixxs.net/forum/?msg=general-16037109&amp;from=rss</comments>
  389. <description>Not all of us are in a position to get native IPv6 in the local area, due to dinosaur or monopoly ISPs. For people in that position, what alternatives are recommended?
  390.  
  391. Currently Hurricane Electric and Teredo come to mind, though it would be good to have a list of other solutions as fallback plans.
  392.  
  393. </description>
  394. <pubDate>Tue, 25 Apr 2017 10:22:21 +0000</pubDate>
  395. <guid>https://www.sixxs.net/forum/?msg=general-16037109&amp;from=rss</guid>
  396. <author>AME4-SIXXS@whois.sixxs.net (Andre-John Mas)</author>
  397. </item>
  398. <item>
  399. <title>Where are the IPv6 Wifi repeaters/extenders?</title>
  400. <link>https://www.sixxs.net/forum/?msg=general-16037093&amp;from=rss</link>
  401. <comments>https://www.sixxs.net/forum/?msg=general-16037093&amp;from=rss</comments>
  402. <description>So I head down to FNAC, in France and get a Wifi extender, set it up and no IPv6? Checks the calendar: April 2017; check my provider: Free.fr; contacts TP-Link: yeah, no IPv6 support; looks at the FNAC online catalogue: IPv6 search results 0; I quietly scream in despair!?
  403.  
  404. TP-Link shared me their FAQ page, which lists zero IPv6 wifi repeaters or access points: http://www.tp-link.com/en/faq-482.html . They also can't give me a date of when an IPv6 capable IPv6 wifi repeater would be available.
  405.  
  406. Can anyone tell me of any IPv6 capable wifi repeaters targeted at the home market? Worst case are there any good projects for making a Raspberry Pi or equivalent device into a wifi extender?
  407.  
  408. </description>
  409. <pubDate>Tue, 25 Apr 2017 10:16:52 +0000</pubDate>
  410. <guid>https://www.sixxs.net/forum/?msg=general-16037093&amp;from=rss</guid>
  411. <author>AME4-SIXXS@whois.sixxs.net (Andre-John Mas)</author>
  412. </item>
  413. <item>
  414. <title>So long, and thanks for all the fish!</title>
  415. <link>https://www.sixxs.net/forum/?msg=general-16032077&amp;from=rss</link>
  416. <comments>https://www.sixxs.net/forum/?msg=general-16032077&amp;from=rss</comments>
  417. <description>Thanks a lot for all the services you provided over the past years for so many people around the world.
  418.  
  419. It's sad to see you go. When asked for IPv6 tunnels I always referred people here because of your excellent service.
  420.  
  421. Since my ISP started providing native IPv6 some years ago, I stopped using the tunnel. I just kept it as a safety measure (you know, just in case...).
  422.  
  423. I wish you all the best for your future lives and projects.
  424.  
  425. cu
  426. Joe
  427.  
  428. </description>
  429. <pubDate>Sat, 22 Apr 2017 14:43:49 +0000</pubDate>
  430. <guid>https://www.sixxs.net/forum/?msg=general-16032077&amp;from=rss</guid>
  431. <author>JSP13-SIXXS@whois.sixxs.net (Jochen Sommer)</author>
  432. </item>
  433. <item>
  434. <title>Thank you!</title>
  435. <link>https://www.sixxs.net/forum/?msg=general-16024509-16029129&amp;from=rss</link>
  436. <comments>https://www.sixxs.net/forum/?msg=general-16024509-16029129&amp;from=rss</comments>
  437. <description>Josh Haupt wrote:
  438. &#60;div class=&#34;quote&#34;&#62;Thank you for providing such a great service.
  439. I wish you best of luck on your future projects.
  440.  
  441. -Josh
  442. &#60;/div&#62;
  443. Likewise thanks.
  444. I took down the tunnel and discovered that my ISP had provided native IPv6 while I'd been using the tunnel. Had you not been closing the service I'd not have found out.
  445.  
  446. </description>
  447. <pubDate>Thu, 20 Apr 2017 06:33:32 +0000</pubDate>
  448. <guid>https://www.sixxs.net/forum/?msg=general-16024509-16029129&amp;from=rss</guid>
  449. <author>RJG4-SIXXS@whois.sixxs.net (Robert J  Gray)</author>
  450. </item>
  451. <item>
  452. <title>Why Brighthouse Networks still has not implemented IPV6</title>
  453. <link>https://www.sixxs.net/forum/?msg=general-15784457-16024513&amp;from=rss</link>
  454. <comments>https://www.sixxs.net/forum/?msg=general-15784457-16024513&amp;from=rss</comments>
  455. <description>Since Charter, Time Warner and Bright House are now one big company called &#38;quot;Spectrum&#38;quot;, they may still implement IPv6 in former Bright House markets.
  456.  
  457. &#60;a href=&#34;http://www.spectrum.net/support/internet/ipv6/?domain-redirect=true&#34;&#62;Spectrum IPv6&#60;/a&#62;
  458.  
  459. Eventually....
  460.  
  461. </description>
  462. <pubDate>Mon, 17 Apr 2017 22:34:04 +0000</pubDate>
  463. <guid>https://www.sixxs.net/forum/?msg=general-15784457-16024513&amp;from=rss</guid>
  464. <author>JHD7-SIXXS@whois.sixxs.net (Josh Haupt)</author>
  465. </item>
  466. <item>
  467. <title>Thank you!</title>
  468. <link>https://www.sixxs.net/forum/?msg=general-16024509&amp;from=rss</link>
  469. <comments>https://www.sixxs.net/forum/?msg=general-16024509&amp;from=rss</comments>
  470. <description>Thank you for providing such a great service.
  471. I wish you best of luck on your future projects.
  472.  
  473. -Josh
  474.  
  475. </description>
  476. <pubDate>Mon, 17 Apr 2017 22:20:15 +0000</pubDate>
  477. <guid>https://www.sixxs.net/forum/?msg=general-16024509&amp;from=rss</guid>
  478. <author>JHD7-SIXXS@whois.sixxs.net (Josh Haupt)</author>
  479. </item>
  480. <item>
  481. <title>Thank you</title>
  482. <link>https://www.sixxs.net/forum/?msg=general-16022037&amp;from=rss</link>
  483. <comments>https://www.sixxs.net/forum/?msg=general-16022037&amp;from=rss</comments>
  484. <description>Jeroen and Pim, thank you for providing this wonderful free service for us all these years. I have native IPv6 from my ISP now, but thanks to you, I could play around with IPv6 five years earlier than if I had to wait for my ISP. Thanks.
  485.  
  486. </description>
  487. <pubDate>Sun, 16 Apr 2017 23:40:23 +0000</pubDate>
  488. <guid>https://www.sixxs.net/forum/?msg=general-16022037&amp;from=rss</guid>
  489. <author>MVDV4-SIXXS@whois.sixxs.net (Michiel van der Vlist)</author>
  490. </item>
  491. <item>
  492. <title>SixXS sunset &amp; save</title>
  493. <link>https://www.sixxs.net/forum/?msg=general-16001161-16001169-16016577&amp;from=rss</link>
  494. <comments>https://www.sixxs.net/forum/?msg=general-16001161-16001169-16016577&amp;from=rss</comments>
  495. <description>Jeroen Massar wrote:
  496. &#60;div class=&#34;quote&#34;&#62;The website will become static and will remain available for the foreseeable future.
  497. &#60;/div&#62;
  498.  
  499. Thank you for the fish.
  500. Sorry to see you go, but as in life all good things must come to an end.
  501. I agree with the original poster.
  502.  
  503. Ian
  504.  
  505. </description>
  506. <pubDate>Wed, 12 Apr 2017 14:30:07 +0000</pubDate>
  507. <guid>https://www.sixxs.net/forum/?msg=general-16001161-16001169-16016577&amp;from=rss</guid>
  508. <author>IMY1-SIXXS@whois.sixxs.net (Ian Morehouse)</author>
  509. </item>
  510. <item>
  511. <title>SixXS sunset &amp; save</title>
  512. <link>https://www.sixxs.net/forum/?msg=general-16001161-16001169&amp;from=rss</link>
  513. <comments>https://www.sixxs.net/forum/?msg=general-16001161-16001169&amp;from=rss</comments>
  514. <description>The website will become static and will remain available for the foreseeable future.
  515.  
  516. </description>
  517. <pubDate>Mon, 03 Apr 2017 12:11:08 +0000</pubDate>
  518. <guid>https://www.sixxs.net/forum/?msg=general-16001161-16001169&amp;from=rss</guid>
  519. <author>JRM1-RIPE@whois.sixxs.net (Jeroen Massar)</author>
  520. </item>
  521. <item>
  522. <title>SixXS sunset &amp; save</title>
  523. <link>https://www.sixxs.net/forum/?msg=general-16001161&amp;from=rss</link>
  524. <comments>https://www.sixxs.net/forum/?msg=general-16001161&amp;from=rss</comments>
  525. <description>Hi!
  526.  
  527. Thanks you alle for your excellent SixXS service. Just not only an infrastructure, but also a body of knowlegde and a forum for IPv6 relates questions.
  528.  
  529. It was cool!
  530.  
  531. I know a free service cannot be maintained forever. Nothing is forever. But I do hope that the information gathered in the wiki and forum can be saved for later reference to anyone who will configure a network for IPv6.
  532.  
  533. Wishing you all the best!
  534.  
  535. Kind regards, Arjen
  536.  
  537. </description>
  538. <pubDate>Mon, 03 Apr 2017 12:06:44 +0000</pubDate>
  539. <guid>https://www.sixxs.net/forum/?msg=general-16001161&amp;from=rss</guid>
  540. <author>AAMR-6BONE@whois.sixxs.net (Arjen A.M. Runsink)</author>
  541. </item>
  542. </channel>
  543. </rss>
  544.  

If you would like to create a banner that links to this page (i.e. this validation result), do the following:

  1. Download the "valid RSS" banner.

  2. Upload the image to your own server. (This step is important. Please do not link directly to the image on this server.)

  3. Add this HTML to your page (change the image src attribute if necessary):

If you would like to create a text link instead, here is the URL you can use:

http://www.feedvalidator.org/check.cgi?url=https%3A//www.sixxs.net/forum/rss/%3Fgeneral

Copyright © 2002-9 Sam Ruby, Mark Pilgrim, Joseph Walton, and Phil Ringnalda