Congratulations!

[Valid Atom 1.0] This is a valid Atom 1.0 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/atom/?better

  1. <?xml version="1.0" encoding="utf-8"?>
  2. <!-- ATOM generated by SixXS (https://www.sixxs.net) on -->
  3. <feed xmlns="http://www.w3.org/2005/Atom">
  4. <id>tag:forum.sixxs.net,2001:atom</id>
  5. <title>SixXS Forum - better</title>
  6. <subtitle>SixXS Forum (ATOM 1.0)</subtitle>
  7. <link rel="self" type="application/atom+xml" href="https://www.sixxs.net/forum/atom/better.atom" />
  8. <link rel="alternate" type="text/html" href="https://www.sixxs.net/forum/" />
  9. <updated>2017-06-05T18:00:00-00:00</updated>
  10. <author>
  11. <name>SixXS Forum</name>
  12. <email>info@sixxs.net</email>
  13. </author>
  14. <entry>
  15. <title>please make reporting problems less painful</title>
  16. <link rel="alternate" type="text/html" href="https://www.sixxs.net/forum/?msg=better-15721229-15721245&amp;from=atom" />
  17. <id>tag:forum.sixxs.net,2016-11-14:better.15721229.15721245</id>
  18. <published>2016-11-14T14:11:50-00:00</published>
  19. <updated>2016-11-14T14:11:50-00:00</updated>
  20. <author><name>Jeroen Massar</name><email>JRM1-RIPE@whois.sixxs.net</email></author>
  21. <content type="html">
  22. &#60;div class=&#34;quote&#34;&#62;If there is a problem, then usually this means a lot of stress.&#60;/div&#62;
  23. Why so much stress? What is the problem? Why in a hurry? Did you Call Your ISP and ask them about IPv6? Does their trained helpdesk know about IPv6?
  24.  
  25. &#60;div class=&#34;quote&#34;&#62;You really don't want to read and follow 20+ items on a checklist (hidden on yet another web page to read).&#60;/div&#62;
  26. Networking is not a simple thing. There is no simple answer. It simply does not exist as networks are big and many variable parts are involved. It is almost easier to debug a human body.
  27.  
  28. The checklist on the not so &#38;quot;hidden&#38;quot; webpage called &#60;a href=&#34;https://www.sixxs.net/contact/&#34;&#62;Contact&#60;/a&#62; and linked from the forums and many other places is just a good starting point.
  29.  
  30. Guess how many people actually check that list and provide those items when reporting a problem?...
  31.  
  32. &#60;div class=&#34;quote&#34;&#62;Some shell script automatically collecting the information would be very helpful.&#60;/div&#62;
  33. Please make that 'shell script' that knows everything about every system and runs on every kind of platform.
  34.  
  35. Noting also that Tunnel Brokers is just one type of deployment.
  36.  
  37. Not very possible and it would not cover anything remotely near a complete picture.
  38.  
  39. There is not even a single person in the world who would know the solution to all problems, let alone a way to diagnose all problems.
  40.  
  41. Instead, describe your problem in the forums, and then get it discussed and solved. The forums are there for a reason: to help people who have problems and want to see them resolved. Together one can figure it out.
  42.  
  43. There are many many other problems that are way more difficult (eg PMTU issues etc).
  44.  
  45. AICCU has a 'test' mode build in, but it simply traceroutes and pings some things.
  46.  
  47. Note that there is a very nice &#60;a href=&#34;http://ipv6-test.com/&#34;&#62;IPv6 Test&#60;/a&#62; website. It only tells you that something is broken though, not what is broken.
  48.  
  49. </content>
  50. </entry>
  51. <entry>
  52. <title>please make reporting problems less painful</title>
  53. <link rel="alternate" type="text/html" href="https://www.sixxs.net/forum/?msg=better-15721229&amp;from=atom" />
  54. <id>tag:forum.sixxs.net,2016-11-14:better.15721229</id>
  55. <published>2016-11-14T14:11:44-00:00</published>
  56. <updated>2016-11-14T14:11:44-00:00</updated>
  57. <author><name>Harald Dunkel</name><email>HDG5-SIXXS@whois.sixxs.net</email></author>
  58. <content type="html">
  59. My top item on the wishlist for sixxs.net: Please become less painful on reporting problems.
  60.  
  61. If there is a problem, then usually this means a lot of stress. You &#60;b&#62;really&#60;/b&#62; don't want to read and follow 20+ items on a checklist (hidden on yet another web page to read).
  62.  
  63. Some shell script automatically collecting the information would be very helpful.
  64.  
  65. Regards
  66. Harri
  67.  
  68. </content>
  69. </entry>
  70. <entry>
  71. <title>Just to say Thank you for a great service!</title>
  72. <link rel="alternate" type="text/html" href="https://www.sixxs.net/forum/?msg=better-10379250-15293029-15295481&amp;from=atom" />
  73. <id>tag:forum.sixxs.net,2016-05-27:better.10379250.15293029.15295481</id>
  74. <published>2016-05-27T05:05:36-00:00</published>
  75. <updated>2016-05-27T05:05:36-00:00</updated>
  76. <author><name>Jeroen Massar</name><email>JRM1-RIPE@whois.sixxs.net</email></author>
  77. <content type="html">
  78. You are specifying features of an Internet connection that you should be asking for from your ISP, the one you are paying for connectvity.
  79.  
  80. You can get those features, but you will have to pay for them.
  81.  
  82.  
  83. SixXS is about IPv6 Deployment. IPv6 Tunnelling is a IPv6 Transition technique.
  84.  
  85. At one point there will not be such a free service anymore. Hence, call your ISP, as the freebies will stop at one point: the IPv6 transition will be over.
  86.  
  87. </content>
  88. </entry>
  89. <entry>
  90. <title>Just to say Thank you for a great service!</title>
  91. <link rel="alternate" type="text/html" href="https://www.sixxs.net/forum/?msg=better-10379250-15293029&amp;from=atom" />
  92. <id>tag:forum.sixxs.net,2016-05-26:better.10379250.15293029</id>
  93. <published>2016-05-26T21:05:31-00:00</published>
  94. <updated>2016-05-26T21:05:31-00:00</updated>
  95. <author><name>Frederik Heissner</name><email>FHW5-SIXXS@whois.sixxs.net</email></author>
  96. <content type="html">
  97. I also want to thank you so much because of the stable service for many years - you guys are really doing a good job.
  98. your ipv6-service does ease so many things in the 'modern world' and i also think that you provide a service which shouldnt be stopped.
  99. by using sixxs i get a stable fixed subnet which many isps are not able to deliver.
  100. also the dns-delegation works like a charm and i've never seen any comparable service by any vps/root-provider.
  101.  
  102. Thank you and keep up the good work!
  103.  
  104. </content>
  105. </entry>
  106. <entry>
  107. <title>Finally got native!</title>
  108. <link rel="alternate" type="text/html" href="https://www.sixxs.net/forum/?msg=better-15243913&amp;from=atom" />
  109. <id>tag:forum.sixxs.net,2016-05-09:better.15243913</id>
  110. <published>2016-05-09T11:05:35-00:00</published>
  111. <updated>2016-05-09T11:05:35-00:00</updated>
  112. <author><name>Bart Kuivenhoven</name><email>BKI3-SIXXS@whois.sixxs.net</email></author>
  113. <content type="html">
  114. I'd like to thank the SixXS team and the ISP's that offer this great service for their efforts over the past few years.
  115.  
  116. I had some issues in the beginning (with my ISP blocking the tunnel and all) but now, finally, after years of promising, our ISP has finally implemented a native IPv6 connection into our home.
  117.  
  118. Unfortunately, even after closing my home tunnel, I still have another tunnel remaining for experiments at university. They won't turn on the IPv6 services on their network for a while, despite surfnet offering them a full native connection, as well as having their website run natively.
  119.  
  120. I'll keep on whining for a native IPv6 service for now, and hopefully they'll roll it out before I graduate.
  121.  
  122. I've also used the experimental tunnel for showing the teachers that all of the network assignments can be done using IPv6. The only things that I had to fall back to IPv4 for were the NAT practicum, as well as showing a wireshark dump of an IPv4 packet, though in the latter case, I also did an IPv6 packet and gave explanations for each and every field there.
  123.  
  124. So, thank you for enabling me to get some bonus points there, as well as just offering simple and usable service.
  125.  
  126. </content>
  127. </entry>
  128. <entry>
  129. <title>Closest POP selection for Ukraine</title>
  130. <link rel="alternate" type="text/html" href="https://www.sixxs.net/forum/?msg=better-14177617-14177729&amp;from=atom" />
  131. <id>tag:forum.sixxs.net,2015-08-28:better.14177617.14177729</id>
  132. <published>2015-08-28T11:08:11-00:00</published>
  133. <updated>2015-08-28T11:08:11-00:00</updated>
  134. <author><name>Jeroen Massar</name><email>JRM1-RIPE@whois.sixxs.net</email></author>
  135. <content type="html">
  136. The reply from the ticket you also filed:
  137. &#60;div class=&#34;quote&#34;&#62;The ISPs who host (read: pay) for the PoP decide who can be the PoPs users.
  138.  
  139. Most PoPs are restricted to &#38;quot;users in our country&#38;quot;, so is plwaw01 which only caters to Polish endpoints.
  140.  
  141. Only the ruled01 PoP accepts Russian and Ukrainian endpoints.
  142. &#60;/div&#62;
  143.  
  144. </content>
  145. </entry>
  146. <entry>
  147. <title>Closest POP selection for Ukraine</title>
  148. <link rel="alternate" type="text/html" href="https://www.sixxs.net/forum/?msg=better-14177617&amp;from=atom" />
  149. <id>tag:forum.sixxs.net,2015-08-28:better.14177617</id>
  150. <published>2015-08-28T10:08:24-00:00</published>
  151. <updated>2015-08-28T10:08:24-00:00</updated>
  152. <author><name>Mike Tkachuk</name><email>MTF14-SIXXS@whois.sixxs.net</email></author>
  153. <content type="html">
  154. Hello,
  155.  
  156. Currently when creating a tunnel from Ukraine SixXS offer to use only Russian POP ruled01, which have RTT near 80ms while for example Polish POP plwaw01 have 15ms RTT.
  157.  
  158. Please enable to choose Polish POPs for users from Ukraine.
  159.  
  160. Thanks.
  161.  
  162. </content>
  163. </entry>
  164. <entry>
  165. <title>possible smaller subnet</title>
  166. <link rel="alternate" type="text/html" href="https://www.sixxs.net/forum/?msg=better-13114445-13114517-13864153-13864169&amp;from=atom" />
  167. <id>tag:forum.sixxs.net,2015-06-29:better.13114445.13114517.13864153.13864169</id>
  168. <published>2015-06-29T19:06:58-00:00</published>
  169. <updated>2015-06-29T19:06:58-00:00</updated>
  170. <author><name>Jeroen Massar</name><email>JRM1-RIPE@whois.sixxs.net</email></author>
  171. <content type="html">
  172. A /48 subnet is a privilege for folks who want to do more. One has to earn that privilege.
  173.  
  174. If one is unable to earn that, then there is likely something afoul with how one manages the tunnel and thus is not worthy of a subnet.
  175.  
  176. </content>
  177. </entry>
  178. <entry>
  179. <title>possible smaller subnet</title>
  180. <link rel="alternate" type="text/html" href="https://www.sixxs.net/forum/?msg=better-13114445-13114517-13864153&amp;from=atom" />
  181. <id>tag:forum.sixxs.net,2015-06-29:better.13114445.13114517.13864153</id>
  182. <published>2015-06-29T19:06:53-00:00</published>
  183. <updated>2015-06-29T19:06:53-00:00</updated>
  184. <author><name>Gerrit Sangel</name><email>GSX8-SIXXS@whois.sixxs.net</email></author>
  185. <content type="html">
  186. I today thought about the same, but would rather do it differently:
  187.  
  188. Provide a /56 or (maybe) a /60 by default to all new tunnels, somehow included in the price. I would never need a /48 subnet, but at least doing some subnetting stuff would be nice. The problem is rather that one needs to apply for a subnet, costing credits.
  189.  
  190. Currently most Internet providers give out (as far as I know) a /56 or (in my case) a /59 subnet, which is usually completely sufficent for private end users. When giving out a /56 by default and a /48 by application, it should not be difficult for most people.
  191.  
  192. </content>
  193. </entry>
  194. <entry>
  195. <title>More Info Re PoP Outages</title>
  196. <link rel="alternate" type="text/html" href="https://www.sixxs.net/forum/?msg=better-13606385-13606397&amp;from=atom" />
  197. <id>tag:forum.sixxs.net,2015-05-07:better.13606385.13606397</id>
  198. <published>2015-05-07T09:05:04-00:00</published>
  199. <updated>2015-05-07T09:05:04-00:00</updated>
  200. <author><name>Jeroen Massar</name><email>JRM1-RIPE@whois.sixxs.net</email></author>
  201. <content type="html">
  202. &#60;div class=&#34;quote&#34;&#62;Specifically my PoP aubne01.sixxs.net is currently offline&#60;/div&#62;
  203. PoP is technically up and working, it is just that there is a routing issue causing our monitoring system not being able to reach the PoP.
  204.  
  205. &#60;div class=&#34;quote&#34;&#62;More information and possibly email notifications to advise us of the status of our PoP's would be great&#60;/div&#62;
  206. There is a RSS feed and twitter.
  207.  
  208. We are not going to spam people per email as then all email would be ignored.
  209. We only send email when something major is happening (eg down tunnel) or somebody requests a new tunnel/subnet etc. Hence all user-actionable items.
  210.  
  211. Also note that there is nothing you as an enduser can do about this.
  212. What we can do is typically already limited.
  213.  
  214. &#60;div class=&#34;quote&#34;&#62;Things I would like to know:&#60;/div&#62;
  215. See our &#60;a href=&#34;https://www.sixxs.net/faq/connectivity/?faq=popdown&#34;&#62;FAQ&#60;/a&#62;
  216.  
  217. </content>
  218. </entry>
  219. <entry>
  220. <title>More Info Re PoP Outages</title>
  221. <link rel="alternate" type="text/html" href="https://www.sixxs.net/forum/?msg=better-13606385&amp;from=atom" />
  222. <id>tag:forum.sixxs.net,2015-05-07:better.13606385</id>
  223. <published>2015-05-07T09:05:38-00:00</published>
  224. <updated>2015-05-07T09:05:38-00:00</updated>
  225. <author><name>Todd Murphy</name><email>TMG15-SIXXS@whois.sixxs.net</email></author>
  226. <content type="html">
  227. Information regarding PoP outages, at least in my limited experience seems to be very minimal.
  228.  
  229. Specifically my PoP aubne01.sixxs.net is currently offline and no information other than this seems to be provided. More information and possibly email notifications to advise us of the status of our PoP's would be great (the latter I realise would be much more painful to implement) so if we notice odd behaviour on our network we immediately know why (I'm not always home, this would be useful, for example if my partner is and I'm not and she complains that the network is experiencing issues).
  230.  
  231. Things I would like to know:
  232. - Estimate on how long this will be down for (even 'unknown' would be better than nothing)
  233. - Cause of the issue
  234. - If there is anything I should/could be doing as an end-user
  235.  
  236. </content>
  237. </entry>
  238. <entry>
  239. <title>More stats and info</title>
  240. <link rel="alternate" type="text/html" href="https://www.sixxs.net/forum/?msg=better-6264554-6268298-13395813-13396141&amp;from=atom" />
  241. <id>tag:forum.sixxs.net,2015-03-27:better.6264554.6268298.13395813.13396141</id>
  242. <published>2015-03-27T09:03:29-00:00</published>
  243. <updated>2015-03-27T09:03:29-00:00</updated>
  244. <author><name>Jeroen Massar</name><email>JRM1-RIPE@whois.sixxs.net</email></author>
  245. <content type="html">
  246. &#60;div class=&#34;quote&#34;&#62;Tunnel statistics could be changed not to crop input side of graph in cases where&#60;/div&#62;&#60;div class=&#34;quote&#34;&#62;input/output are close to each other. If I recall correctly, earlier it had some bandwidth&#60;/div&#62;&#60;div class=&#34;quote&#34;&#62;scaling selectbox, but I guess that was removed in favor of automatic scaling.&#60;/div&#62;
  247. The range selection was causing unnecessary burden on our backends, we thus removed it.
  248.  
  249. &#60;div class=&#34;quote&#34;&#62;Seeing uncropped version of both input &#38;amp; output graphs besides latency graph would help understand various AQM settings better.&#60;/div&#62;
  250. Which AQM settings?
  251.  
  252. Remind yourself that a tunnel spans over the IPv4 network. Hence a lot of hops are involved that could do a lot of things to the tunneled packets.
  253.  
  254. You won't be able to make any conclusions from RRDs that get compressed/bucketed over time.
  255.  
  256. </content>
  257. </entry>
  258. <entry>
  259. <title>More stats and info</title>
  260. <link rel="alternate" type="text/html" href="https://www.sixxs.net/forum/?msg=better-6264554-6268298-13395813&amp;from=atom" />
  261. <id>tag:forum.sixxs.net,2015-03-27:better.6264554.6268298.13395813</id>
  262. <published>2015-03-27T06:03:38-00:00</published>
  263. <updated>2015-03-27T06:03:38-00:00</updated>
  264. <author><name>Tuomas Heino</name><email>TH28-6BONE@whois.sixxs.net</email></author>
  265. <content type="html">
  266. Jeroen Massar wrote:
  267. &#60;div class=&#34;quote&#34;&#62;I think that all possible statistics possible which are not confidential in nature are on the website already.
  268. And yes, we are aware that traffic monitoring needs to be fixed. But some things need to be done first.
  269. &#60;/div&#62;
  270.  
  271. I don't know whether replying to old posts is considered bad from ovet here, but since yoy mentioned statistics:
  272.  
  273. Tunnel statistics could be changed not to crop input side of graph in cases where input/output are close to each other. If I recall correctly, earlier it had some bandwidth scaling selectbox, but I guess that was removed in favor of automatic scaling.
  274.  
  275. Seeing uncropped version of both input &#38;amp; output graphs besides latency graph would help understand various AQM settings better.
  276.  
  277. </content>
  278. </entry>
  279. <entry>
  280. <title>possible smaller subnet</title>
  281. <link rel="alternate" type="text/html" href="https://www.sixxs.net/forum/?msg=better-13114445-13114517&amp;from=atom" />
  282. <id>tag:forum.sixxs.net,2015-02-04:better.13114445.13114517</id>
  283. <published>2015-02-04T02:02:06-00:00</published>
  284. <updated>2015-02-04T02:02:06-00:00</updated>
  285. <author><name>Jeroen Massar</name><email>JRM1-RIPE@whois.sixxs.net</email></author>
  286. <content type="html">
  287. One size fits all. Hence one gets a default /64 and if requested a /48.
  288.  
  289. The SixXS PoPs have thousands of /48s, and if we run out of a /40 we just ask for a new one from the PoP.
  290.  
  291. Hence, no need to start splitting up /48s into smaller prefixes. It is already complicated enough for most people.
  292.  
  293. </content>
  294. </entry>
  295. <entry>
  296. <title>Just to say Thank you for a great service!</title>
  297. <link rel="alternate" type="text/html" href="https://www.sixxs.net/forum/?msg=better-10379250-13114469&amp;from=atom" />
  298. <id>tag:forum.sixxs.net,2015-02-04:better.10379250.13114469</id>
  299. <published>2015-02-04T01:02:06-00:00</published>
  300. <updated>2015-02-04T01:02:06-00:00</updated>
  301. <author><name>Jason lewis</name><email>JLE14-SIXXS@whois.sixxs.net</email></author>
  302. <content type="html">
  303. yes, thank you for the service.
  304.  
  305. ooooh, native IPv6, that would be nice.  My ISP has vowed to not look at IPv6 for a few years.  I could move on, but the only other offering in my area is 256k speeds.  Looks like I might be stuck on a tunnel for a while.
  306.  
  307. </content>
  308. </entry>
  309. <entry>
  310. <title>possible smaller subnet</title>
  311. <link rel="alternate" type="text/html" href="https://www.sixxs.net/forum/?msg=better-13114445&amp;from=atom" />
  312. <id>tag:forum.sixxs.net,2015-02-04:better.13114445</id>
  313. <published>2015-02-04T01:02:44-00:00</published>
  314. <updated>2015-02-04T01:02:44-00:00</updated>
  315. <author><name>Jason lewis</name><email>JLE14-SIXXS@whois.sixxs.net</email></author>
  316. <content type="html">
  317. Here is an interesting thought.  As a home user, I have no need for more than two to four subnets at most (between testing and my divided home and guest networks).  I picked up a /48 from he.net but that kinda seems wasteful when the tunnel server might be running out of space.  Maybe once a tunnel gets down to the last few subnets, it can be offered as a /56 or something possibly smaller for specified home users.  A /56 would allow 65,535 subnets out of the /40 instead of only the normal 256.  As it stands, I do not need more than the /64 at this time, so I am not requesting it, but it might be a possibility for home users that might only need a smaller pie.  I cannot imagine how a home user would need more than 8 subnets at home.  They would have a different tunnel at work.  Maybe two subnet definitions say enterprise (/48) and home (/56).
  318.  
  319. </content>
  320. </entry>
  321. <entry>
  322. <title>BGP Support</title>
  323. <link rel="alternate" type="text/html" href="https://www.sixxs.net/forum/?msg=better-12330521-12330573&amp;from=atom" />
  324. <id>tag:forum.sixxs.net,2014-09-18:better.12330521.12330573</id>
  325. <published>2014-09-18T05:09:57-00:00</published>
  326. <updated>2014-09-18T05:09:57-00:00</updated>
  327. <author><name>Jeroen Massar</name><email>JRM1-RIPE@whois.sixxs.net</email></author>
  328. <content type="html">
  329. &#60;div class=&#34;quote&#34;&#62;What is the reason SixXS doesn't support BGP and ASes to announce their own prefixes ?&#60;/div&#62;
  330. Because the ISPs who provide the PoPs do not provide that service.
  331.  
  332. Also, because peering over tunnels is a bad idea, especially as it is 2014 already. The 6bone experiment was concluded in 2006.
  333.  
  334. Check our &#60;a href=&#34;https://www.sixxs.net/faq/connectivity/?faq=ipv6transit&#34;&#62;FAQ: Where can I get native IPv6 transit?&#60;/a&#62; where to get native IPv6 connectivity.
  335.  
  336. </content>
  337. </entry>
  338. <entry>
  339. <title>BGP Support</title>
  340. <link rel="alternate" type="text/html" href="https://www.sixxs.net/forum/?msg=better-12330521&amp;from=atom" />
  341. <id>tag:forum.sixxs.net,2014-09-18:better.12330521</id>
  342. <published>2014-09-18T02:09:23-00:00</published>
  343. <updated>2014-09-18T02:09:23-00:00</updated>
  344. <author><name>Fernando Frediani</name><email>FFZ3-SIXXS@whois.sixxs.net</email></author>
  345. <content type="html">
  346. Hello,
  347.  
  348. What is the reason SixXS doesn't support BGP and ASes to announce their own prefixes ?
  349. For South America where there is a single POP this would make a significant difference specially for ISPs. Some of them may have two transit providers but only one provides Native IPv6. An alternative would be to set a tunnel to SixXS announcing its own prefixes being able to keep connectivity in the case of loss of connection to the native transit provider.
  350.  
  351. The only alternative to that now is using HE.net which does supports BGP but the nearest POP is Miami and imposes a significant latency.
  352.  
  353. Thanks
  354.  
  355. FF
  356.  
  357. </content>
  358. </entry>
  359. <entry>
  360. <title>IPv6 check over SSL requests mixed content</title>
  361. <link rel="alternate" type="text/html" href="https://www.sixxs.net/forum/?msg=better-12240689&amp;from=atom" />
  362. <id>tag:forum.sixxs.net,2014-08-31:better.12240689</id>
  363. <published>2014-08-31T13:08:11-00:00</published>
  364. <updated>2014-08-31T13:08:11-00:00</updated>
  365. <author><name>Jean-Pierre Schwickerath</name><email>JSA4-SIXXS@whois.sixxs.net</email></author>
  366. <content type="html">
  367. The IPv6-Check at https://www.sixxs.net/tools/ipv6check/ doesn't work on current versions of firefox unles you specifically allow mixed content.
  368. Some of the scripts to test the connectivity are fetched over http altough the page is accessed via https.
  369. Could you eventually look into the possibility to have it all served over https?
  370.  
  371. </content>
  372. </entry>
  373. <entry>
  374. <title>My assigned POP is &quot;disabled&quot;</title>
  375. <link rel="alternate" type="text/html" href="https://www.sixxs.net/forum/?msg=better-11729505-11741949&amp;from=atom" />
  376. <id>tag:forum.sixxs.net,2014-06-04:better.11729505.11741949</id>
  377. <published>2014-06-04T17:06:54-00:00</published>
  378. <updated>2014-06-04T17:06:54-00:00</updated>
  379. <author><name>Jeroen Massar</name><email>JRM1-RIPE@whois.sixxs.net</email></author>
  380. <content type="html">
  381. &#60;div class=&#34;quote&#34;&#62;What happened?&#60;/div&#62;
  382. The PoP provider stopped providing the service.
  383.  
  384. &#60;div class=&#34;quote&#34;&#62;How do I get mu tunnel back.&#60;/div&#62;
  385. You can't. The only thing you can do is request a new tunnel from another PoP.
  386. If you require credits for that, contact info@sixxs.net.
  387.  
  388. </content>
  389. </entry>
  390. <entry>
  391. <title>My assigned POP is &quot;disabled&quot;</title>
  392. <link rel="alternate" type="text/html" href="https://www.sixxs.net/forum/?msg=better-11729505&amp;from=atom" />
  393. <id>tag:forum.sixxs.net,2014-06-02:better.11729505</id>
  394. <published>2014-06-02T19:06:43-00:00</published>
  395. <updated>2014-06-02T19:06:43-00:00</updated>
  396. <author><name>Michael Reilly</name><email>MRZ1-SIXXS@whois.sixxs.net</email></author>
  397. <content type="html">
  398. When my tunnel went down I checked on the web site. It was marked as POP is down.  I didn't do anything at that time since I expected it would come back.
  399. When it didn't come back I checked again and my tunnel is deleted and the POP is marked as &#38;quot;disabled&#38;quot;.  
  400.  
  401. What happened?  How do I get mu tunnel back.
  402.  
  403. usphx01 - Highwinds Network Group Inc68.0.133.2102001:1938:81:46::2 PoP is disabled
  404.  
  405. </content>
  406. </entry>
  407. <entry>
  408. <title>info on nlams01 shutdown</title>
  409. <link rel="alternate" type="text/html" href="https://www.sixxs.net/forum/?msg=better-11728497-11728537-11729201&amp;from=atom" />
  410. <id>tag:forum.sixxs.net,2014-06-02:better.11728497.11728537.11729201</id>
  411. <published>2014-06-02T17:06:32-00:00</published>
  412. <updated>2014-06-02T17:06:32-00:00</updated>
  413. <author><name>Thijs Kroesbergen</name><email>TK26-SIXXS@whois.sixxs.net</email></author>
  414. <content type="html">
  415. Well, I must have missed that somehow. Anyway, thanks for the great service.
  416.  
  417. </content>
  418. </entry>
  419. <entry>
  420. <title>info on nlams01 shutdown</title>
  421. <link rel="alternate" type="text/html" href="https://www.sixxs.net/forum/?msg=better-11728497-11728537&amp;from=atom" />
  422. <id>tag:forum.sixxs.net,2014-06-02:better.11728497.11728537</id>
  423. <published>2014-06-02T15:06:58-00:00</published>
  424. <updated>2014-06-02T15:06:58-00:00</updated>
  425. <author><name>Jeroen Massar</name><email>JRM1-RIPE@whois.sixxs.net</email></author>
  426. <content type="html">
  427. Emails where sent and there was also an announcement on the news page:
  428.  
  429. &#60;a href=&#34;https://www.sixxs.net/news/2014/#sixxssaysagoodbyetoconceptsict-0415&#34;&#62;2014-04-15 - SixXS says a goodbye to Concepts ICT: nlams01 shutting down&#60;/a&#62;
  430. which was also thus announced through our RSS feed.
  431.  
  432. Hence, you had quite a long time of warning, if you where unaware, check your spam filters.
  433.  
  434. </content>
  435. </entry>
  436. <entry>
  437. <title>info on nlams01 shutdown</title>
  438. <link rel="alternate" type="text/html" href="https://www.sixxs.net/forum/?msg=better-11728497&amp;from=atom" />
  439. <id>tag:forum.sixxs.net,2014-06-02:better.11728497</id>
  440. <published>2014-06-02T15:06:02-00:00</published>
  441. <updated>2014-06-02T15:06:02-00:00</updated>
  442. <author><name>Thijs Kroesbergen</name><email>TK26-SIXXS@whois.sixxs.net</email></author>
  443. <content type="html">
  444. I couldn't find any notification (in my mailbox) about the nlams01 pop being shut down. Did you send out such notification? To me this is kind of a (unpleasant at this moment) surprise.
  445.  
  446. </content>
  447. </entry>
  448. <entry>
  449. <title>BUG: Per-POP RSS links are shifted</title>
  450. <link rel="alternate" type="text/html" href="https://www.sixxs.net/forum/?msg=better-11630553-11630557-11630613&amp;from=atom" />
  451. <id>tag:forum.sixxs.net,2014-05-16:better.11630553.11630557.11630613</id>
  452. <published>2014-05-16T12:05:24-00:00</published>
  453. <updated>2014-05-16T12:05:24-00:00</updated>
  454. <author><name>Dario Minnucci</name><email>DMY8-SIXXS@whois.sixxs.net</email></author>
  455. <content type="html">
  456. The issue *was* present using:
  457.  
  458. Debian/GNU Linux --&#38;gt; Mozilla/5.0 (X11; Linux i686; rv:29.0) Gecko/20100101 Firefox/29.0 Iceweasel/29.0.1
  459.  
  460. Flushing cache solved the problem.
  461.  
  462. Heheh, this means the issue was there once but looks like no ISKs for me this time.
  463.  
  464. Thanks for your quick answer.
  465.  
  466. Regards.
  467.  
  468. </content>
  469. </entry>
  470. </feed>
  471.  

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 Atom 1.0" 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/atom/%3Fbetter

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