Our network service model uses /32 subnet for floating IP. (mostly to acheive floating ip mobility)
I found that floating ip is assigned with /32 mask so no problem, but the problem is quantum router's default gateway, it is assigned with actual mask.
See the example.
28: qg-fc9eb6a0-a6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether fa:16:3e:77:dd:5b brd ff:ff:ff:ff:ff:ff
inet 172.16.0.101/24 brd 172.16.0.255 scope global qg-fc9eb6a0-a6 # external gateway
inet 172.16.0.102/32 brd 172.16.0.102 scope global qg-fc9eb6a0-a6 # floating IP
inet6 fe80::f816:3eff:fe77:dd5b/64 scope link
valid_lft forever preferred_lft forever
Except that, it looks like a bug for me.
Um...what do you think so? We're using fixed version of this issue on our deploy, by the way.
Our network service model uses /32 subnet for floating IP. (mostly to acheive floating ip mobility)
I found that floating ip is assigned with /32 mask so no problem, but the problem is quantum router's default gateway, it is assigned with actual mask.
See the example.
28: qg-fc9eb6a0-a6: <BROADCAST, MULTICAST, UP,LOWER_ UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000 3eff:fe77: dd5b/64 scope link
link/ether fa:16:3e:77:dd:5b brd ff:ff:ff:ff:ff:ff
inet 172.16.0.101/24 brd 172.16.0.255 scope global qg-fc9eb6a0-a6 # external gateway
inet 172.16.0.102/32 brd 172.16.0.102 scope global qg-fc9eb6a0-a6 # floating IP
inet6 fe80::f816:
valid_lft forever preferred_lft forever
Except that, it looks like a bug for me.
Um...what do you think so? We're using fixed version of this issue on our deploy, by the way.