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
I am running debian 9 on my vps. Filesystem is ext3.
I have cron jobs which drop database dumps into a dropbox folder.
In addition I have created some shared folders so that non techies can
upload material.
However Dropbox are dropping support for ext3 this will be broken soon.
What's my best option here.
Migrate the entire VPS to ext4?
Create a new (ext4) partition?
Something else.
I note from
https://debian-administration.org/article/643/Migrating_a_live_system_from_…
that it is possible to switch from ext3 to ext4 without any conversion by
simply editing the fstab and rebooting.
Does anyone know if that will suffice for Dropbox's new requirements? I
suspect not. :(
Neil Wallace.
I currently relay email for a customer who has a Hetzner server [1].
We had problems sending email as we share an IP address block
with habitual spammers (OSLT - much argument on the mail operator's
mailing list - basically, live next to noisy neighbours, you might
find yourself with an ASBO).
So I relay his mail (obvs., not an *open* relay!).
I used verifier.port25.com and got a fail on the reverse IP
lookup, as they use IPv6.
Bitfolk.com says:
"For IPv6 we can delegate the IPv6 reverse zones to your nameservers. We
can also provide up to three secondary nameservers for you."
and the domain is registered and has DNS provided by 123-reg. Which
doesn't seem to know about IPv6.
Do I have any other options apart from using a different DNS provider?
Or moving the domain away from 123-reg?
[1] Only place I know of where you can get 12TB of disk for "not
too much". We need lots of disk!
Hi,
Has anyone else been seeing (what appears to be) DDOS attempts against
their VPS's?
I've been getting quite a lot of messages like this in my logs over the
past few days:
Sep 30 05:02:06 scruffy kernel: [2103474.700870] TCP: drop open request
from 45.195.133.8/51353
Sep 30 05:02:07 scruffy kernel: [2103476.223611] TCP: drop open request
from 149.56.180.255/25006
Sep 30 05:02:08 scruffy kernel: [2103476.704225] TCP: drop open request
from 45.195.133.8/7947
Sep 30 05:02:08 scruffy kernel: [2103476.713872] TCP: drop open request
from 149.56.180.255/31127
Any ideas also on the best way to block? (I was reading about SYN
cookies, but not sure if this is a good idea or not).
cheers,
Matt.
Hi,
If you aren't running 32-bit Ubuntu then you can probably skip this
message.
A customer reported that they'd updated their 32-bit Ubuntu 18.04
VPS and now the kernel doesn't boot. I had a look and indeed the
latest 32-bit linux-image-generic immediately kernel panics.
This means that if you're on 32-bit and you try to boot into it,
your VPS won't boot. Also it means that currently 32-bit Ubuntu
18.04 installs aren't possible because the installer kernel won't
boot.
I haven't yet had any reports of the same thing happening in other
versions of Ubuntu, but it might do since presumably there is some
security patch being pushed out (I'm going to take a wild stab at
32-bit KPTI protection) that is broken, so it might hit any
supported version of 32-bit Ubuntu.
The only quick way I have found to work around this at present is
to run a 64-bit kernel. Here's how you'd do that, assuming that your
VPS is currently unbootable.
xen-shell> rescue
(boot and log in to rescue VM)
$ sudo mount /dev/xvda1 /mnt
$ sudo mount --bind /dev /mnt/dev
$ sudo mount --bind /sys /mnt/sys
$ sudo mount --bind /proc /mnt/proc
$ sudo chroot /mnt /bin/bash
# dpkg --add-architecture amd64
# apt update
# apt install linux-image-generic:amd64
# exit
$ sudo halt
xen-shell> arch x86_64
xen-shell> boot
This:
1) Enables multi-arch on your VPS and says that amd64 architecture
packages are acceptable
2) Installs a 64-bit kernel
3) Boots into it
You will then be running a 64-bit kernel with a 32-bit user land. It
should work fine and continue offering you updated 64-bit kernel
packages and updates 32-bit packages for everything else.
If you were brave you could completely cross-grade to amd64 but it
is a complicated, risky and unsupported procedure.
Another workaround may be to boot into rescue and do a chroot as
above, but then downgrade the kernel package.
I will attempt to replicate the problem and report it to Ubuntu.
Cheers,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting
_______________________________________________
announce mailing list
announce(a)lists.bitfolk.com
https://lists.bitfolk.com/mailman/listinfo/announce
Hi Everyone (Andy especially)
Have any of you done a "P2V" (ha!) of your VPS into LXD/LXC? I've done some
Googling, and from what I see, it shouldn't be too difficult in my case:
the VPS is running Ubuntu 16.04.4, there's a template for that, I've plenty
of room on the "target" LXD machine for a <10GB fs.
But...
I'm wondering about the feasibility of getting a tarball of the VPS fs
(Andy?)? I've got space on the VPS in question to make a tarball of itself,
but I'm not sure that would be the best idea (writing to the very FS I'm
trying to archive, just feels wrong before I try to do it).
Thoughts/comments sought/appreciated.
Kind regards
Murray Crane
*Background*
One of my VPS is basically just used as a mailserver and slave DNS server
and a couple of other minor things. Recently I wanted to overhaul the
mailserver changing some of the software. The stuff I wanted to use was
only available as 64 bit.
This got me thinking that the VPS is littered with remains of old junk data
files etc from previous things as I have upgraded from Debian versions
dynamically rather than fresh installs, so here was an excuse to move to 64
bit.
Yes I know and understand the pros and cons.
I have studied various guides to doing this via the Debian web site and
elsewhere and know what needs to be done, but I need a small bit of advice.
My current Kernel is linux-image-4.9.110-3+deb9u1
I plan to rsync all relevant data files (maildirectories, Bind conf files,
.authorisedkeys, mysql dumps etc.) over to my home machine and redirect
mail to the backup server then nuke the VPS with a complete new install of
Debian stable and set up as a 64 bit install.
*Question*
Does the Bitfolk self-service-network-installer coe with a 64 bit option,
or do I have to install Debian stable then convert to amd64. This would
still be an easy option as there would be very little software to
convert/replace. I would need to install a multiarch capable kernel after
using the installer (and do a second Xen retart)
If this seems a naive question sorry, we all have to learn at some time.
Thanks in advance
--
Keith Williams
คืนใดมืดที่สุด จะเห็นดาวชัดที่สุด
Wondrous Thai http://www.wondrousthai.com
FCLT magazine http://issuu.com/fcltmagazine/docs/fclt_september_2014_issue_1
Farang Can Learn Thai www.farangcanlearnthai.com
Keith's Place www.keiths-place.co.uk
Tailor Made English www.tmenglish.org
Hello,
I'm afraid there's another round of security updates needed as a
flaw has been discovered in some (Xen-specific) parts of the Linux
kernel.
It's not the hypervisor this time but it still needs a kernel
upgrade on our side so the effect is basically the same, so there
will be another reboot of all servers, likely in the early hours (UK
time) of 11–13 August.
Customers will soon receive an individual email confirming the
hour-long maintenance window specific to their server(s). The actual
work is expected to take 10–30 minutes within that window.
As before we should be able to do a suspend/restore if you have
enabled that at:
<https://panel.bitfolk.com/account/config/>
Cheers,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting
_______________________________________________
announce mailing list
announce(a)lists.bitfolk.com
https://lists.bitfolk.com/mailman/listinfo/announce
