BitFolk Users January 2011

users@mailman.bitfolk.com

34 participants
22 discussions

by Andy Smith

Hi, You may recall recently that there was a period of poor network performance because the customer DNS resolver on 212.13.194.71 was overloaded: http://lists.bitfolk.com/lurker/message/20110102.221800.b90128dc.en.html In that thread I promised to provision a new dedicated resolver to avoid a re-occurrence of the issue. Instead I took the opportunity to provision several new resolver hosts in a cluster with fail over for the service IPs. All customers should change their resolvers from: 212.13.194.71 212.13.194.96 to: 85.119.80.232 85.119.80.233 There's some maintenance coming up in February (details in a separate email, shortly) which will take 212.13.194.71 offline for several hours. It's therefore important that you change to using the new resolvers before this time, otherwise you will experience severe network performance problems. If you have any questions please direct to users list or support(a)bitfolk.com. Cheers, Andy -- http://bitfolk.com/ -- No-nonsense VPS hosting _______________________________________________ announce mailing list announce(a)lists.bitfolk.com https://lists.bitfolk.com/mailman/listinfo/announce

13 years, 1 month

2011-02-26 1700Z onwards - scheduled maintenance for customers on curacao, faustino, kahlua, obstler, urquell

by Andy Smith

Hi, On the evening of Saturday 26th February 2011 starting from about 1700Z we will be taking part in maintenance to completely re-rack all servers in one suite. Goals of this maintenance: - Turn the rack around 180 degrees to improve air flow based on the location of cold air ingress from the under-floor air conditioning. - Adjust rack posts to allow better air flow up through the rack. - Re-rack servers in a way that doesn't impede air flow. - Install new power metering equipment. This is expected to take several hours. It's difficult to be more specific because it depends on how fast we are able to work; obviously we will be working as fast as is safely possible. Customers on the following servers will be affected because these servers are in the rack that we'll be working on: - curacao - kahlua - obstler - urquell Additionally, - faustino which is currently in a different suite will be powered off and moved. This outage will be much shorter - should be no more than 30 minutes maximum. This will be done after the other work is completed so it's not possible to specify a time. How to find out which server you are on: https://bitfolk.com/customer_information.html#toc_3_Which_piece_of_actual_h… We will be performing a clean shut down of all VPSes, followed by a boot again when servers are re-racked. The following BitFolk services will be unavailable during the maintenance: - The old primary DNS resolver, 212.13.194.71 - apt-cacher - cacti - tracker - wiki The resolver outage means that it's important that all customers configure use of the new resolvers that were announced here: http://lists.bitfolk.com/lurker/message/20110124.233915.2c058600.en.html Failure to do this will lead to very poor network performance during the outage, because your first resolver will not respond at all. If you are otherwise unaffected by the maintenance and assuming you configure the new resolvers, the absence of the above services should not impact the operation of your VPS. We can't alter the date/time of the maintenance, but if this timing is disastrous for you then please let support(a)bitfolk.com know and me may be able to accommodate a move of your VPS to a server that will be unaffected. Cheers, Andy -- http://bitfolk.com/ -- No-nonsense VPS hosting _______________________________________________ announce mailing list announce(a)lists.bitfolk.com https://lists.bitfolk.com/mailman/listinfo/announce

13 years, 1 month

Lenny to Squeeze

by Rakhesh Sasidharan

Hi, Now that Squeeze is around the corner, I was wondering if there are any special steps I need to take while dist-upgrade from Lenny to Squeeze since I am running on Xen. Any experiences/ suggestions welcome! Thanks, Rakhesh

13 years, 2 months

Re: [bitfolk] "IPocalpyse"

by G. Miliotis

On 30/1/2011 12:17 μμ, Michael Stevens wrote: > I've been keeping my eye out for consumer IPv6 DSL routers, I hear > reports something may be available in the next few weeks. > > Michael > We have IPV6 trials here in Greece. I'm running on dual stack ADSL right now. I use a FritzBox! (AVM) with IPV6 support. I also read that D-Link has ipv6 support in new models. Read for more CPEs here: http://labs.ripe.net/Members/marco/content-ipv6-cpe-survey I have not looked into the firewall issue yet on my Fritzbox but I will eventually. I believe Teredo should always be disabled on any corporate machine, laptop or not, as a matter of policy. Firewalling some of my IPV6 servers was not hard, just work with a DENY-by-default logic. There are some glitches (eg mobility) but you can pretty much secure a server easily. I don't know about an IPV6 fridge, though. Ppl may cause your milk to spoil, after all. Regards, G

13 years, 2 months

"IPocalpyse"

by Daniel Case

Hiya, While I know that IPocalypse as the news hype is calling it, is a little bit overkill. It makes me wonder what will happen to ISP's such as Bitfolk when the IPv4's do run out? I know a lot of home users are not up to the IPv6 standard yet (Sky Broadband are terrible) so will giving users a V6 address only mean that people still on v4 can't get to them? Daniel

13 years, 2 months

Re-enabling IPv6

by Daniel Case

I recently reinstalled the OS on my server (due to a lot of misconfiguration, I thought it would be easiest to start again) following the guide on the wiki: https://tools.bitfolk.com/wiki/Using_the_self-serve_net_installer It installed correctly, and now I am working through the "Things you might like to change after install" part. I set up the cacher and NTP but I am completely stumped on IPv6. According to "ifconfig" IPv6 is there (I have an inet6 address) so I tried to ping6 ipv6.google.com and it failed as i suspected. The next thing I tried was just adding my settings to /etc/network/interfaces: iface eth0 inet6 static pre-up modprobe ipv6 # Perhaps you will only use this one for web serving address fe80::216:5eff:fe00:1e5 netmask 64 gateway 2001:ba8:1f1:f004::1 but that didn't work either...does anybody have any idea how I can enable v6? Thank you! Daniel

13 years, 2 months

Hardening your VPS

by Ciemon Dunville

I setup a new VPS a month or so ago, but in the last week things have got a little wild in the apache access and error logs. I'm using firehol, denyhosts and fail2ban to try and stop the constant traffic, and I guess it's my lack of regex knowledge that isn't helping there. Those packages should help prevent stuff like: 203.186.54.50 - - [26/Jan/2011:12:42:12 +0000] "CONNECT 80.176.162.50:25 HTTP/1.0" 200 10417 "-" "-" 178.162.131.33 - - [26/Jan/2011:12:42:53 +0000] "GET http://vastdata.net/ HTTP/1.1" 200 10312 "-" "-" 123.165.11.194 - - [26/Jan/2011:12:38:18 +0000] "GET http://proxyjudge2.proxyfire.net/fastenv HTTP/1.1" 404 537 "-" "Mozill a/4.0 (compatible; MSIE 6.0; Windows NT 5.1)" [Wed Jan 26 05:01:05 2011] [error] [client 76.253.161.24] File does not exist: /var/www/vch/data [Wed Jan 26 05:03:21 2011] [error] [client 112.194.97.133] script '/var/www/vch/proxycheck.php' not found or unable to stat [Wed Jan 26 05:07:57 2011] [error] [client 116.248.134.82] script '/var/www/vch/proxygrade.php' not found or unable to stat, referer: http://www.proxygrade.com/proxygrade.php?hash=C59C2E3FD31372BAD D1004781F90050A953698723D3E Comments, advice and regex guidance are always welcome. Cie

13 years, 2 months

TOR and BitTorrent

by Andy Smith

Hello, In the last few months there's been an increase in the number of notices of claimed infringement we have received from various companies acting on behalf of rights owners such as Columbia Pictures, CBS, etc.. A number of times this has been traced back to customers running TOR exit nodes. Assuming that you do not wish to trigger these allegations, I would suggest that those operating TOR exit nodes at BitFolk might like to consider whether they want to all people to be using BitTorrent through their node. Or indeed whether they want to be running an exit node at all (as opposed to a routing node which only talks to other TOR nodes). Some further information: http://www.chrisbrunner.com/2006/07/09/why-you-shouldnt-run-bittorrent-over… Cheers, Andy -- http://bitfolk.com/ -- No-nonsense VPS hosting _______________________________________________ announce mailing list announce(a)lists.bitfolk.com https://lists.bitfolk.com/mailman/listinfo/announce

13 years, 3 months

Snapshots.

by Isabell Long

Hi all, Having today switched to a BitFolk VPS and having received a snapshot from my old VPS, I'm wondering what to do with it to, well, make it work?! Thanks in advance, Isabell.

13 years, 3 months

Re: [bitfolk] Any interest in fail-over IPs?

by Andy Loughran

Guys, What advantage does Up takeover have over a 5 minute ttl on dns? Aside from the obvious, in that ip change can have s lower change time. On 19 Jan 2011 01:03, "SP SP" <sundancecloud(a)gmail.com> wrote: Andy, Yes, I would agree with your analysis. I've just seen a failure at another site where both disks in a RAID configuration failed. Our sites were down for 24 hours while we re-constructed the sites and restored data. So, depending on the net cost and specific details, there could be some benefit to IP failover. BTW when I mentioned that another provider would be beneficial ... I was not hinting that BitFolk was not a great provider! :-) - Sandy On Tue, Jan 18, 2011 at 6:34 PM, Andy Smith <andy(a)bitfolk.com> wrote: > > > > Hi Sandy, > > > > It's important to weigh up the common faults against the cost of > > protecting agai... > > > -----BEGIN PGP SIGNATURE----- > > Version: GnuPG v1.4.9 (GNU/Linux) > > > iEYEAREDAAYFAk02I3AACgkQIJm2TL8VSQsG6gCeMljZ6NGV8g/167ylbRoHKBTO > dicAoNwxWLz8l+oCuevdD9gJ53quXaNa > =q8Q3 > > > > -----END PGP SIGNATURE----- > > > > _______________________________________________ > > users mailing l... > _______________________________________________ users mailing list users(a)lists.bitfolk.com https://lists.bitfolk.com/mailman/listinfo/users

13 years, 3 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

BitFolk Users January 2011