I thought that I would do this address change while it is fresh.
I do not want to remove the old address until I have updated other config (eg
DNS [forward & back], whois) and had that propagate - so both must work for a
while.
I set the new address thus:
ip address add 2a0a:1100:1012::114 dev enX0
Why :114 - the IPv4 address is 85.119.82.114 so having the last component the
same helps my head in understanding that they both belong to the same machine.
That works and I can ssh into it.
I am running Debian so I added this into /etc/network/interfaces, I will remove
the old iface enX0 when this is all done.
iface enX0 inet6 static
address 2a0a:1100:1012::114
netmask 48
gateway 2001:ba8:1f1:f0e3::1
# These commands disable IPv6 autoconfiguration because we are statically
# configuring it above.
pre-up echo 0 > /proc/sys/net/ipv6/conf/default/accept_ra || true
pre-up echo 0 > /proc/sys/net/ipv6/conf/all/accept_ra || true
pre-up echo 0 > /proc/sys/net/ipv6/conf/$IFACE/accept_ra || true
pre-up echo 0 > /proc/sys/net/ipv6/conf/default/autoconf || true
pre-up echo 0 > /proc/sys/net/ipv6/conf/all/autoconf || true
pre-up echo 0 > /proc/sys/net/ipv6/conf/$IFACE/autoconf || true
I copied the old one and changed: address & netmask [ 64 -> 48]
The stansa that concerns me is 'gateway' - above is a copy of the old one, what
should I set this to ?
Regards
--
Alain Williams
Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer.
+44 (0) 787 668 0256 https://www.phcomp.co.uk/
Parliament Hill Computers. Registration Information: https://www.phcomp.co.uk/Contact.html
#include <std_disclaimer.h>
Hi,
I suppose it's relevant to anyone who might be target of harassment, but
for the three of you¹ currently running Tor relays at BitFolk please be
aware of:
https://delroth.net/posts/spoofed-mass-scan-abuse/
There isn't actually anything you can do about it other than reply to
abuse reports accordingly.
Thanks,
Andy
¹ curl -s 'https://onionoo.torproject.org/details?search=running:true' | \
jq '.relays[] | select(.or_addresses[] | startswith("85.119.8"))'
--
https://bitfolk.com/ -- No-nonsense VPS hosting
"I am the permanent milk monitor of all hobbies!" — Simon Quinlank
Hi,
I've updated this article on the wiki for the new /48s and just general
relevance as it was first authored almost 14 years ago:
https://tools.bitfolk.com/wiki/IPv6
It could do with some info about firewalling with nft. Also I do not
know how to set preferred_lft using nmcli or even if you can.
Of course if you spot any other errors or omissions just edit it.
I also went through and tried to modernise the VPN article:
https://tools.bitfolk.com/wiki/IPv6
I haven't used tinc in about 20 years though so I've no idea if any of
that is still correct. I also think it's probably better done with
WireGuard these days, so please show us how. 😀
Thanks,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting
Hi,
The new /48s have now been assigned to all existing customers and you
can see what yours is at
https://panel.bitfolk.com/dns/
Assigning addresses and routes within these assignments should just work
for you, but I need to write some documentation for existing customers
(on the wiki) and then I will post something to announce@.
If you have any problems feel free to ask questions but if it's
something I will cover in the instructions then you may have to wait for
that.
Thanks,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting
Hi,
If you do not use or care about IPv6 with regard to your BitFolk VM(s)
you can stop reading this now.
As of this month we have started assigning IPv6 /48 netblocks to new
customers out of BitFolk's own allocation rather than continue giving
out /64s from our colo provider's allocation. Yesterday evening we also
assigned /48s to all existing customer VMs.
New installs (including those done yourself) will get set up with your
/48 from the start but existing VMs do need a few changes to make use of
this new address apace. If you know what you are doing you can just look
at:
https://panel.bitfolk.com/dns/
to find your /48 assignment and start configuring addresses and routes
from within that. They should work.
If that doesn't work or if you need more guidance here is an article
aimed at existing customers:
https://tools.bitfolk.com/wiki/New_/48_assignments,_October_2024
If you still have any questions not covered by the Troubleshooting or
Frequently Asked Questions sections then please do ask, by reply email
or support ticket or on Telegram or IRC.
Thanks,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting
Hi,
It was good to chat to some customers at OggCamp last weekend in
Manchester.
I will also be attending BarCamp London next month on Saturday 23
November. Do say hello if you are there too!
https://thirteen.barcamplondon.org/
Thanks,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting
Hi,
I think we're ready now for people to try out the new IPv6 /48
assignments so if there's any of you that have a little time to play
around with that please contact me off-list.
I expect everything¹ to work. You won't need to reboot. The /48 you are
assigned will not change later on. Your legacy IPv6 assignments will not
be affected.
Everyone else will get their /48s assigned and routed to them after a
short period of these volunteers trying theirs out.
Thanks,
Andy
¹ I have not yet been through all of BitFolk's firewall rules so there
will be some services that are meant for only customers that will be
unreachable from these IP blocks until I get around to that. We also
need to update all of the IPv6 documentation on the wiki as it is now
out of date.
--
https://bitfolk.com/ -- No-nonsense VPS hosting
Hi,
Very nearly ready to start assigning /48s from the BitFolk net block.
At present each VM has a /64 of the form:
2001:ba8:1f1:fxxx::/64
We are going to start assigning /48s to customers from
2a0a:1100:1000::/48 onwards. That means that the first one is
2a0a:1100:1000::/48
and then the next is
2a0a:1100:1001::/48
and they continue to increment like
2a0a:1100:1002::/48
2a0a:1100:1003::/48
2a0a:1100:1004::/48
and so on.
My question is, do you feel there is any value whatsoever in matching
the customer-specific part of an existing customer's /64 assignment with
their new /48 assignment?
For example, if you currently had 2001:ba8:1f1:f1d7::/64 then you could
ALSO have 2a0a:1100:11d7::/48.
Or, we could just assign them incrementally from the bottom up if it's
felt there is no value in that.
Personally I kind of feel like there isn't really any value here. By the
time we have explained how you mentally map from one to the other I
think you could have just looked at https://panel.bitfolk.com/dns/ and
seen what your new /48 is. I'm not even convinced that there are very
many people who remember the last part of their current /64 off by heart
anyway.
But it was put to me by a non-customer that we "should" do this, so I
thought I would ask! If there's even one person that would like that
then I guess we can do it.
Either way, new customers would just get the first available from the
bottom.
Thanks,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting
Hi,
If there's any of you who are actively using an IPv6 /56 that we've
routed to you, and you don't overly mind rebooting your VM to test
something (maybe a couple of times) could you get in touch off-list
please?
Our records say there's only 19 of you so it's a bit of a long shot.
I'd rather not try this with someone who doesn't normally make use of a
/56 as you may not immediately spot the difference between working
and not. Also I've already tested as many setups as I can think of so
I'd only be suggesting things I already tested!
I can add a little bit of free service for the inconvenience.
(Trying to set reply-to on this but Mailman will probably override it so
be careful not to reply on-list if that wasn't your intention.)
Thanks!
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting
