DigitalOcean home
  • Droplets
  • Spaces
  • Kubernetes
  • Tools & Integrations
  • One-click Apps
  • API Documentation
  • Community
  • Tutorials
  • Q&A
  • Projects
  • Meetups
  • Customers
  • Pricing
  • Docs
  • Support
  • DigitalOcean home
  • Products
    • Droplets

      Scalable compute services.

    • Spaces

      Simple object storage.

    • Kubernetes

      Run managed Kubernetes clusters.

    • Tools & Integrations

      Automate your infrastructure.

    • One-click Apps

      Deploy pre-built applications.

    • API Documentation
  • Customers
  • Community
    • Community Overview

      Connect, share and learn

    • Tutorials

      DevOps and development guides

    • Questions & Answers

      Development and systems Q&A

    • Projects

      Community-built integrations

    Get Involved
    Write for DOnations
    Join us at a Meetup
    Featured Post
    An Introduction to Kubernetes

    by Justin Ellingwood

  • Pricing
  • Docs
  • Support
    • Documentation

    • Contact Support

    • Network Status

  • Home /
  • DO-I-858 /
  • New idea
15 Vote

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
Floating IPs
  • Comments (9)
  • Votes (15)
  • Attach files
  • ramkumarr 45 commented
    30 Dec, 2020 05:48am

    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

  • Guest commented
    21 Oct, 2020 08:29am
    https://192-168-i-i.com/brands/ my website will help you more
    ×

    Attachments Open full size

  • Guest commented
    21 Oct, 2020 01:26am
    https://192-168-i-i.com/ip-address/192-168-x-x/ my website will help you more
    ×

    Attachments Open full size

  • Guest commented
    20 Nov, 2019 10:25pm

    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

  • Robin Wilson commented
    19 May, 2019 11:11pm

    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

  • Guest commented
    11 Sep, 2018 04:27pm

    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

  • Guest commented
    11 Sep, 2018 04:27pm

    +1

    ×

    Attachments Open full size

  • Guest commented
    11 Sep, 2018 04:27pm

    Please!

    ×

    Attachments Open full size

  • Guest commented
    11 Sep, 2018 04:27pm

    +1

    ×

    Attachments Open full size

Log in / Sign up

Identify yourself with your email address

Subscribe

You won't be notified about changes to this idea.

Related ideas

DigitalOcean home

© 2018 DigitalOcean, LLC. All rights reserved.
Proudly made in NY

  • Twitter
  • Facebook
  • Instagram
  • YouTube
  • LinkedIn
  • Glassdoor
Company
About
Leadership
Blog
Careers
Partner Network
Referral Program
Events
Press
Legal & Security
Products
Droplets
Spaces
Kubernetes
Tools & Integrations
One-click Apps
API
Pricing
Documentation
Release Notes
Community
Tutorials
Meetups
Q&A
Write for DOnations
Droplets for Demos
Hatch
Shop Swag
Research Program
Currents Research
Open Source
Support
Contact Support
FAQ
Network Status