On 10/27/2015 01:01 PM, Brian Rak wrote:
(Existing email got kinda messy, starting over again):
So, I'm having an issue with the kernel where if I add a bunch of
routes, I see some of them go "missing". They don't show up in the
'ip -4 route' list, but they do show up if I do 'ip -4 route get
(Existing email got kinda messy, starting over again):
So, I'm having an issue with the kernel where if I add a bunch of
routes, I see some of them go "missing". They don't show up in the 'ip
-4 route' list, but they do show up if I do 'ip -4 route get X'.
I managed to come up with a simple
On 10/26/2015 11:28 AM, Alexander Duyck wrote:
On 10/24/2015 06:32 AM, Brian Rak wrote:
On 10/23/2015 6:32 PM, Alexander Duyck wrote:
On 10/23/2015 02:34 PM, Brian Rak wrote:
I've got a weird situation here. I have a route that the kernel knows
about, but won't display via the general RTM
On 10/24/2015 06:32 AM, Brian Rak wrote:
On 10/23/2015 6:32 PM, Alexander Duyck wrote:
On 10/23/2015 02:34 PM, Brian Rak wrote:
I've got a weird situation here. I have a route that the kernel knows
about, but won't display via the general RTM_GETROUTE call, but will
display if I query for th
On 10/23/2015 6:32 PM, Alexander Duyck wrote:
On 10/23/2015 02:34 PM, Brian Rak wrote:
I've got a weird situation here. I have a route that the kernel knows
about, but won't display via the general RTM_GETROUTE call, but will
display if I query for that particular route:
# ip -4 route show |
On 10/23/2015 02:34 PM, Brian Rak wrote:
I've got a weird situation here. I have a route that the kernel knows
about, but won't display via the general RTM_GETROUTE call, but will
display if I query for that particular route:
# ip -4 route show | grep 108.61.171.x
The use of 'x' here is going
I've got a weird situation here. I have a route that the kernel knows
about, but won't display via the general RTM_GETROUTE call, but will
display if I query for that particular route:
# ip -4 route show | grep 108.61.171.x
# ip route get 108.61.171.x
108.61.171.x dev MYIF
cache
# cat /pro
