I want to install FreeBSD on linode.

Paul Belair

New Member

Thanks: 2
Messages: 12

#1
Hello the prices have gone up at digitalocean. I found linode.com and signed up expecting to see FreeBSD. Instead of cancelling the account I thought I might find a way to install FreeBSD on a linode.

I constantly fail at doing this on my own in past and thought maybe someone here is working on it. If there is I'd appreciate knowing the configurations
 
OP
OP
P

Paul Belair

New Member

Thanks: 2
Messages: 12

#4
It was a great guide.
It didn't reboot from a terminal window untill I remembered about turning Lassie off on the control panel settings.
 

sko

Well-Known Member

Thanks: 213
Messages: 419

#5
Hello the prices have gone up at digitalocean.
What prices are you referring to? Haven't received any info about that from DO (and they seem to send out mails about every change/update they made) so I just checked the price list on the DO site but can't spot any changes...
Also linode seems to be exactly on par with DO with their pricing. Vultr is also the same except they offer less SSD space with increasing VM size (which doesn't matter if you put user data on a separate block storage...)
 
OP
OP
P

Paul Belair

New Member

Thanks: 2
Messages: 12

#6
The price of their minimal droplet $5 went up to $15 (200%). I destroyed a droplet and almost created a new one till I saw the price.
I like 'linode.com' because I don't have to destroy a linode to start over. So the price will remain the same.
 

sko

Well-Known Member

Thanks: 213
Messages: 419

#7
That's definitely not correct:

https://www.digitalocean.com/pricing/
Screenshot-2018-11-20-13-51-27.png


And when creating a droplet:
Screenshot-2018-11-20-13-54-09.png

Only thing I just recognized on my private account: the default selection for the droplet size was 4CPU/8GB, so you have to click on the arrow to the left to select one of the smaller droplets. Don't know why they changed the UI there at all (it was perfectly fine IMHO) and why it defaults to a rather big droplet size...

On DO you also don't need to destroy a droplet - just re-deploy it, restore from snapshot or deploy a new one from a snapshot. That's what I did constantly while testing something like automated deployment or my autoconfiguration/cloudinit scripts.
 
OP
OP
P

Paul Belair

New Member

Thanks: 2
Messages: 12

#8
Well yesterday that $15 droplet only had 1G ram. Today they offer it at 3G ram. And that arrow wasn't there before today.
 

sko

Well-Known Member

Thanks: 213
Messages: 419

#9
Well yesterday that $15 droplet only had 1G ram.
This would be the 1GB/3CPU/60GB droplet and it is still available.

TBH, I also was confused for a second with that new slide menu.
Instead of constantly fiddling with a working UI they should focus on useful changes/fixes, like offering BGP peering, OpenBSD images (or at least don't nuke the FS when snapshotting/backing up manually installed OpenBSD droplets) and removing the stupid "no SMTP on IPv4" restriction...
The main reason I've stayed with DO is that vultr hasn't any free capacity for block storage at their FRA DC since at least 6 months and they don't allow subdomains at their DNS...
 

trev

Aspiring Daemon

Thanks: 118
Messages: 637

#12
Nope, DO blocks outgoing connections on IPv4/Port 25; IPv6 is not blocked.
Incorrect.

From the DO support site:

How do I enable IPv6 SMTP?

We currently do not allow SMTP traffic over IPv6 as a side effect of how email black lists treat IPv6 addresses.
You can give priority to IPv4 addresses over IPv6 so that you can continue to send out email without disabling IPv6. You would do that by editing the Droplet's /etc/gai.conf file and removing the comment (#) from the following line:
Default Configuration: #precedence ::ffff:0:0/96 100
Configuration with Priority to IPv4: precedence ::ffff:0:0/96 100
As a result of which DO refunded my account balance as they confirmed this was the case.

Are you sure you are with DO? ;-)
 

sko

Well-Known Member

Thanks: 213
Messages: 419

#13
I've just checked my ticket from earlier this year - It is indeed v6/SMTP that is blocked except if you have your own /64 prefix and v4/SMTP is blocked on new accounts for the first 60 days, somehow that wasn't automatically removed on my account (>2 years old) so I opened a ticket; that's why I had v4 memorized. Sorry for causing confusion about that :confused:
 
Top