Hi,
At approximately 22:24Z, host "hen" rebooted itself unexpectedly. It
all appears to be back up again now, and I am investigating to try
to determine the cause.
Apologies for the disruption.
Cheers,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting
_______________________________________________
announce mailing list
announce(a)lists.bitfolk.com
https://lists.bitfolk.com/mailman/listinfo/announce
Hello,
Unfortunately some security flaws have been discovered in the
hypervisor software we use (Xen) so we will need to patch and reboot
everything before the public release of the details on 20 November.
I expect we will do this work in the early hours of the morning (UK
time) between Saturday 17 and Monday 19 November, but customers will
soon receive an individual email confirming the hour-long
maintenance window specific to their server(s). The actual work for
each server is expected to take 10–30 minutes within that window.
As before we should be able to do a suspend/restore of your guest if
you have enabled that at:
<https://panel.bitfolk.com/account/config/>
Cheers,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting
> The optimum programming team size is 1.
Has Jurassic Park taught us nothing? — pfilandr
_______________________________________________
announce mailing list
announce(a)lists.bitfolk.com
https://lists.bitfolk.com/mailman/listinfo/announce
I'm not sure how many people have made the transition from iptables to
nftables.
I have just done so on one VPS, had a couple of minor hiccups on the way
but am very pleased with the result. Easy to do and the much more
human-readable and simplified syntax make it easy to read and maintain. I
particularly like the way that you just write one set of rules for ipv4 and
ipv6 and that as sets are built in it avoids all the problems involved in
making a table with sets reboot safe.
I was toying with doing a wiki page to share the experience and tips that I
picked up, but wiki syntax seems harder to fathom than nftables syntax. I
did a lot of googling on the issue but many of the How-To sites were either
contradictory, totally missing the new features (iptables rules translated
line by line and not taking advantage of new features), downright wrong or
rip-off copies of official documentation.
Keith
Andy, do you run a mail relay/smarthost for customers?
I've got nullmailer running on one of my VPS, and it looks like I
configured it with a bitfolk.com smarthost, but it doesn't dig/accept SMTP
(so I'm guessing it either used to exist and doesn't any more, or it never
existed and I just made some shit up)
Kind regards
Murray Crane
Hello,
On Fri, Nov 09, 2018 at 06:27:28PM +0000, Henry Gomersall wrote:
> I agree, I'm going to back off and try to clobber everything with
> sensible configs.
>
> Is there are reference for what the settings _should_ be? (default gw,
> dns etc)
Hmm, not really. You can piece it together from various pages on the
panel but perhaps a summary would be a good thing for us to add to
https://panel.bitfolk.com/account/config/ ?
In your case:
IPv4:
Address: 85.119.83.128
Netmask: 255.255.248.0
Gateway: 85.119.80.1
IPv6:
Address: 2001:ba8:1f1:f1e5::2
Netmask: 64
Gateway: 2001:ba8:1f1:f1e5::1
DNS:
85.119.80.232
85.119.80.233
2001:ba8:1f1:f205::53
2001:ba8:1f1:f206::53
Cheers,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting
Following an upgrade to Ubuntu 18.04, my network is not coming up
properly. The interface seems to come up, but traffic is not being
routed properly.
Andy checked and he can ping my VPS some within Bitfolk, but from the
machine I cannot see the outside world, nor can I see the machine from
the outside world.
/etc/network/interfaces is as below. Does anybody have any ideas as to
what is wrong?
#### BEGIN
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet static
address 85.119.83.128
netmask 255.255.248.0
gateway 85.119.80.1
auto eth0:1
iface eth0:1 inet static
address 212.13.195.128
netmask 255.255.255.255
iface eth0 inet6 static
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet static
address 85.119.83.128
netmask 255.255.248.0
gateway 85.119.80.1
auto eth0:1
iface eth0:1 inet static
address 212.13.195.128
netmask 255.255.255.255
address 2001:ba8:1f1:f1e5::2
netmask 64
gateway fe80::fcff:ffff:feff:ffff
pre-up echo "/sbin/modprobe ipv6" &&
/sbin/modprobe ipv6 || true
post-up echo "/proc/sys/net/ipv6/conf/default/forwarding=0" &&
echo 0 > /proc/sys/net/ipv6/conf/default/forwarding || true
post-up echo "/proc/sys/net/ipv6/conf/all/forwarding=0" &&
echo 0 > /proc/sys/net/ipv6/conf/all/forwarding || true
post-up echo "/proc/sys/net/ipv6/conf/default/accept_ra=0" &&
echo 0 > /proc/sys/net/ipv6/conf/default/accept_ra || true
post-up echo "/proc/sys/net/ipv6/conf/all/accept_ra=0" &&
echo 0 > /proc/sys/net/ipv6/conf/all/accept_ra || true
post-up echo "/proc/sys/net/ipv6/conf/$IFACE/accept_ra=0" &&
echo 0 > /proc/sys/net/ipv6/conf/$IFACE/accept_ra || true
post-up echo "/proc/sys/net/ipv6/conf/default/autoconf=0" &&
echo 0 > /proc/sys/net/ipv6/conf/default/autoconf || true
post-up echo "/proc/sys/net/ipv6/conf/all/autoconf=0" &&
echo 0 > /proc/sys/net/ipv6/conf/all/autoconf || true
post-up echo "/proc/sys/net/ipv6/conf/$IFACE/autoconf=0" &&
echo 0 > /proc/sys/net/ipv6/conf/$IFACE/autoconf || true
#### END
Hello,
On Fri, Nov 09, 2018 at 03:10:54PM +0000, Henry Gomersall wrote:
> On 09/11/2018 15:08, Andy Smith wrote:
> > $ sudo ip route add default via 85.119.80.1
> >
> > Does that cause it to work?
>
> Yes, that fixed it, thanks! Does that need to be made permanent somewhere?
Need to work out why the default route from your
/etc/network/interfaces is not being set.
Also you didn't seem to have working IPv6 either, so that should be
investigated.
Cheers,
Andy
