Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.
# ip route get 1.2.3.4
anycast 1.2.3.4 dev eth0  src 5.6.7.8

and the question is how does it know the address is an anycast ? (which apparently is true).

UPDATED:

Present as anycast route:

root@hv2 ~ # ip route get 1.2.3.4
anycast 1.2.3.4 dev eth0  src 5.6.7.8 
    cache 

but not visible in list:

root@hv2 ~ # ip route list|grep 1.2.3.4|wc -l
0

but it's possible to delete it, and than it back to normal (no anycast anymore):

root@hv2 ~ # ip route del anycast 1.2.3.4 dev eth0
root@hv2 ~ # ip route get 1.2.3.4
1.2.3.4 via 5.6.7.8 dev eth0  src 9.10.11.12 
    cache 
share|improve this question
    
Unicast and anycast addresses are not allocated separately. This address can be used as either depending on how you configure it. But how did you end up with one IP address belonging in Australia and another belonging in Germany? That's like opposite sides of the planet. –  kasperd Jul 9 at 16:01
    
I can tell you how but.. can you tell me first where the anycast word came from on the ip route get output ? –  pawel7318 Jul 9 at 18:31

2 Answers 2

up vote 3 down vote accepted
+50

If you look at the iproute2 gitweb, you'll see it's showing the status of the RTN_ANYCAST bit set on the kernel routing structure. If you cross-reference that with the kernel source (rtnetlink.h) you'll see the following comment:

    RTN_ANYCAST,            /* Accept locally as broadcast,
                               but send as unicast */

If you check the manual page, you'll see the anycast status of an address is determined by configuration (in particular, adding the anycast keyword when you specify the address to be added). According to man 8 ip:

   IFADDR := PREFIX | ADDR peer PREFIX [ broadcast ADDR ] [ anycast ADDR ]
           [ label STRING ] [ scope SCOPE-ID ]

   ...
           anycast   -   _not  implemented_  the  destinations are anycast
           addresses assigned to this host.  They are mainly equivalent to
           local with one difference: such addresses are invalid when used
           as the source address of any packet.

From the first part of the manual, it states that when you specify the address, you can instruct the stack that it's an anycast address. Without checking the kernel source code, I imagine that when you add an anycast address, the anycast bit gets propagated to a corresponding routing table entry that would be created when the address is added.

I'm not sure if the "not implemented" part is entirely correct, because it looks like iproute2 is indeed passing the anycast flags into the system calls. So it seems like if anycast is supported by the kernel, it should work. But I haven't tested it, so I don't know about that.

share|improve this answer
    
The address was added by my teammate, than he asked me to look at it as it didn't worked and I'm pretty sure he didn't used anycast keyword with ip addr add. Because we had to make it work we moved to another IP and from that time 1.2.3.4 from the example is not presend on ip addr, ip route or config file and the ip route get still give us same output with the anycast in it. Please tell me if I should extend the question with some command's outputs to provide more details. –  pawel7318 Jul 12 at 11:27
    
@pawel7318 it might be helpful to show the full output of ip -4 route and ip -4 addr in your question. And clarify what you mean when you say the address "doesn't work". (What, specifically, isn't working? What troubleshooting steps have you tried? Also, what Linux distribution are you using?) –  Mike Jul 13 at 4:33
    
it didn't reply for any SYN package but.. as it was recognized as anycast it could be that "such addresses are invalid when used as the source address of any packet" rule applied to it. As I said the address it not set on any interface or route now. We don't own the address anymore and still ip route get shows me that it's an anycast. –  pawel7318 Jul 16 at 8:28
    
@pawel7318, it seems like the address is marked anycast but you didn't intend that. Is that correct? what Linux distribution are you using? Can you post your network configuration files? If you restart your networking subsystem (or use the supported way to bounce your interfaces) does the problem go away? As a last resort, does rebooting affect the problem? –  Mike Jul 16 at 19:36
    
It's Debian. We have dedicated servers at Hetzner.de and we ordered 'faillover address' which can be easily moved from one box to another via web-based mgmt. panel or trigered via their API. Than we placed it on the box with simple ip addr add. We had some problems to make it work (as I described above) but as we've noticed that we'll need more we ordered another subnet that works same way. From that point we don't own that IP and it was never added to /etc/network/interfaces or any other file. Even after ip addr del 1.2.3.4/32 dev eth0 I still have that magic puzzle. –  pawel7318 Jul 16 at 21:09

From the man page for ip-route, under the "ip route get" section:

Note that this operation is not equivalent to ip route show. show shows existing routes. get resolves them and creates new clones if necessary. Essentially, get is equivalent to sending a packet along this path

You can show anycast routes with the command ip route show type anycast.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.