Feature Request: Hostname support for BGP/other protocols

[leleobhz]

Hello,

I'm using FRR inside docker environment and inside the same docker bridge. Everything works well, but docker, to make things easier, set a hostname with the name the container with the internal IP atributed to him.

This IP address vary each time container runs and the hostname is the default way of docker images to reach each other. But FRR only supports IP address as neighbour, not supporting hostname as a valid config.

That said, its possible to deploy hostname support for neighbours in FRRouting?

Thanks!

[leleobhz]

Just for reference, I've also registered the issue #2024 related to Docker images too. I'm using the new version of the image effectively to register this issue.

[ajones-rvbd]

Looking through the cisco manual, I don't see name-lookup support for BGP. @lelobhz, do you know any routers which support this feature?

I'm also a little confused about the problem here. docker-compose let's you set the IP address of the service using something like:

services:
frr:
cap_add:
- NET_ADMIN
networks:
site1:
ipv4_address: 192.168.1.2

And by defining the network in the file below. Does that solve this issue?

[donaldsharp]

why not use interface based neighbors

[ajones-rvbd]

Currently, interfaces are not correctly ordered in docker. Though there is a patch in the works to fix that.

[ajones-rvbd]

See: moby/libnetwork#2132 for details

[leleobhz]

Hello @ajones-rvbd

Not a bad idea, although this demand a new network setup. Using networks in composer requires CAP_NET_ADMIN?

I'll try to do this way and return this issue. I think maybe a good idea include this setup in a docker-composer.yml example file too - if it works well.

Thanks!

[ajones-rvbd]

Hi @leleobhz -- NET_ADMIN was left over in the copy+paste which was from a router service, it's not necessary in order to setup the IP address...

I see what you're looking for and it makes sense, I'm still pretty new to routers and they do seem arcane to me at times -- but it also seems like if there is a simple work-around for this one, we should try to use it...

I think of the hand crafted IP addresses in docker compose as a kind of IGP -- and that, from the outside, there will be some sort of ingress translation (similar to: https://kubernetes.io/docs/concepts/services-networking/ingress/) that hopefully doesn't know about these internal addresses and references the services by "name". This is not 100% sorted out yet, though, AFAICT...

[donaldsharp]

Added as a Feature Request. https://github.com/FRRouting/frr/wiki/Feature-Requests