Express.js req.ip is returning ::ffff:127.0.0.1

by

::ffff: is a subnet prefix for IPv4 (32 bit) addresses that are placed inside an IPv6 (128 bit) space. IPv6 is broken into two parts, the subnet prefix, and the interface suffix. Each one is 64 bits long, or, 4 groups of 4 hexadecimal characters.

In IPv6, you are allowed to remove leading zeros, and then remove consecutive zeros, meaning ::ffff: actually translates to 0000:0000:ffff:0000, this address has been designated as the IPv4 to IPv6 subnet prefix, so any IPv6 processor will understand it’s working with an IPv4 address and handle it accordingly.

In the near future, IP addresses will all be IPv6, this is because we are nearly out of numbers (4.2 billion, minus some space for misc. purposes) in the IPv4 address space.

IPv6 allows for a much larger space. “340 undecillion ought to be
enough for anyone” – Bill Gates speaking on IPv6.

It is important to start addressing IP addresses using the IPv6 namespace and therefore include the ::ffff: in your code because in the future there will be real hexadecimal data between those colons. If you strip it off for aesthetic reasons, your code will break when it switches to an IPv6 network or it’s confronted with an IPv6 address.

Some networks are currently running IPv6 and you will soon be confronted with IPv6 IP addresses; make the leap now or risk breaking your code in the future.

The TL;DR (short) version of the matter is: Everything is working fine. Don’t change it, it’s the IPv6 version of an IPv4 address.

IPv4
IPv6

If you want to make your code compatible with IPv6, all you have to do is check for the ::ffff: prefix… if it exists, remove it and process the remainder as IPv4… if ::ffff: doesn’t exist, it’s an IPv6 address and needs to be processed as such.
You can double-check by seeing if periods are in the string, if so, it’s IPv4.

Keep in mind for everything but adjustments you need to make to IP addresses, you’re just recording the IP, right? It’s going to be important to the parser and log aggregates to expect ::ffff:127.0.0.1 and such in the future. Unless you need to alter an IP, just leave it as what you receive.

More Related Contents:

  1. Push items into mongo array via mongoose
  2. How to share sessions with Socket.IO 1.x and Express 4.x?
  3. How can I set NODE_ENV=production on Windows?
  4. What does body-parser do with express?
  5. How to include route handlers in multiple files in Express? [duplicate]
  6. How to redirect 404 errors to a page in ExpressJS?
  7. Node/Express file upload
  8. npm WARN package.json: No repository field
  9. socket.io and session?
  10. How to modify the nodejs request default timeout time?
  11. What is the difference between res.end() and res.send()?
  12. Express next function, what is it really for?
  13. Redirecting to previous page after authentication in node.js using passport.js
  14. Mongoose update without callback
  15. What does middleware and app.use actually mean in Expressjs?
  16. POST request not allowed – 405 Not Allowed – nginx, even with headers included
  17. Use a variable in a Jade include
  18. How to send a pdf file from Node/Express app to the browser
  19. What is the difference between res.send and res.write in express?
  20. What is best way to handle global connection of Mongodb in NodeJs
  21. Call a “local” function within module.exports from another function in module.exports?
  22. Model.find() returns empty in mongoose [duplicate]
  23. Difference between `npm start` & `node app.js`, when starting app?
  24. How can I get Express.js to 404 only on missing routes?
  25. Unable to Change Favicon with Express.js
  26. How to use socket.io in express routes?
  27. Express Router undefined params with router.use when split across files
  28. Connect or Express middleware to modify the response.body [closed]
  29. CORS-enabled server not denying requests
  30. Using multiple parameters in URL in express

Leave a Comment