Make floating IP fully featured (send & receive)
Currently Floating IP feature is of very very limited usefulness. I can connect to web and FTP resources but UDP ones fail. Presently a droplet has no way to send data from it's floating IP address, which means it fails in some areas.
I would like to see the floating IP system get boosted up a bit to make the floating IP an additional IP on the droplet, so that it will act as a fully additional IP on the droplet. Thus, it will allow that IP to be fully utilized and provide more scenarios where the Floating IP system is useful.
-
Guest
- Sep 11 2018
- Needs review
Related ideas
IP address can be used to change the name of the Wi-Fi, control the number of devices that are connected at a time to the network and much more. We shall see the things that uses the IP address 192.168.1.254 in the router below.
192.168.1.254
192.168.0.1
Attachments Open full size
Attachments Open full size
Attachments Open full size
You can already do this by binding to the secondary ip address on the eth0 interface, in my case this is a 10.x.x.x address. That's what the floating IP is bound to on the hypervisor.
Attachments Open full size
This is really needed otherwise floating IPs seem rather pointless.
For hosting websites with a mail server (which I would have thought a lot of users would be doing) this rules out floating IPs and it would be a really good use case being able to quickly switch to a backup server (a few mins of downtime) vs changing all the DNS records and waiting for propagation (hours of downtime). With DNS on floating IP and outgoing mail sent from the other IP, as reverse lookups would fail your mail server is blacklisted in no time.
It is possible to send out traffic via the secondary IP but only if the service allows you to bind to this network:
curl --interface SECOND_IPÂ https://ipinfo.io/ip
What would be better would be to be able to set the default outgoing IP where you could switch between them.
Attachments Open full size
Urgent: Floating IP should also be used on OUTGOING traffic like SMTP
You cannot use 1 IP for half of the services and use another for the rest
Our sysadmin says: "this is just a flaw in their design"
dnswl.org says "Having multiple records in regards to mailing usually leads nowhere, except to trouble."
You cannot send email using IP 1, but receive it on IP 2, set up a server on IP 2 and expect mail servers to treat this as "safe"
So in you quest to prevent spam - you are 10 points behind because when you use 2 IP's and do not respect the floating IP for outgoing traffic then you are 10 points behind when email is concerned and almost immediately flagged for spam
PLEASE FULLY APPLY the Floating IP to ==ALL== IN and all OUT traffic
Attachments Open full size
+1
Attachments Open full size
Please!
Attachments Open full size
+1
Attachments Open full size