sergiotarxz/nuttx
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
589bb56bcb
nuttx/net/route/net_initroute.c

63 lines
2.0 KiB
C
Raw Normal View History

Partial implementation of a simple network routing table.
2013-10-02 02:55:20 +02:00
/****************************************************************************
Addes support for read-only routing tables. Prior to this change, routing tables were only support in RAM and had to be initialized with explicit logic to add the necessary routes to the routing table. With this change, routes may be defined in the pre-initialized, read-only routing table provided by the board-specific logic This would be particularly useful, for example, in the case where there is only a single network adaptor and you want all output packets to go to the single adaptor in all cases. So for that behavior you could add a read-only routing table to the board-specific long that contains a single entry, the default route: 0.0.0.0/0. Squashed commit of the following: net/route: RAM and ROM routing tables build correctly in all IPv4 and IPv6 configurations. net/route: Verify IPv6 ROM route build; Make number of ROM routes a variable, not a configuration item. net/route: Add initial support for ROM-base, read-only routing tables. net/route: Adjust and generalize some structures, rename some functions, and add configuration and build support that will eventually support read-only routing tables. net/route: Some initial though experiments on use of a fixe, read-only routing table
2017-09-28 17:04:31 +02:00
* net/route/net_initroute.c
Partial implementation of a simple network routing table.
2013-10-02 02:55:20 +02:00
*
net: Author Gregory Nutt: update licenses to Apache Gregory Nutt has submitted the SGA and we can migrate the licenses to Apache. Signed-off-by: Alin Jerpelea <alin.jerpelea@sony.com>
2021-02-19 12:45:37 +01:00
* Licensed to the Apache Software Foundation (ASF) under one or more
* contributor license agreements. See the NOTICE file distributed with
* this work for additional information regarding copyright ownership. The
* ASF licenses this file to you under the Apache License, Version 2.0 (the
* "License"); you may not use this file except in compliance with the
* License. You may obtain a copy of the License at
Partial implementation of a simple network routing table.
2013-10-02 02:55:20 +02:00
*
net: Author Gregory Nutt: update licenses to Apache Gregory Nutt has submitted the SGA and we can migrate the licenses to Apache. Signed-off-by: Alin Jerpelea <alin.jerpelea@sony.com>
2021-02-19 12:45:37 +01:00
* http://www.apache.org/licenses/LICENSE-2.0
Partial implementation of a simple network routing table.
2013-10-02 02:55:20 +02:00
*
net: Author Gregory Nutt: update licenses to Apache Gregory Nutt has submitted the SGA and we can migrate the licenses to Apache. Signed-off-by: Alin Jerpelea <alin.jerpelea@sony.com>
2021-02-19 12:45:37 +01:00
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
* WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
* License for the specific language governing permissions and limitations
* under the License.
Partial implementation of a simple network routing table.
2013-10-02 02:55:20 +02:00
*
****************************************************************************/
/****************************************************************************
* Included Files
****************************************************************************/
#include <nuttx/config.h>
Addes support for read-only routing tables. Prior to this change, routing tables were only support in RAM and had to be initialized with explicit logic to add the necessary routes to the routing table. With this change, routes may be defined in the pre-initialized, read-only routing table provided by the board-specific logic This would be particularly useful, for example, in the case where there is only a single network adaptor and you want all output packets to go to the single adaptor in all cases. So for that behavior you could add a read-only routing table to the board-specific long that contains a single entry, the default route: 0.0.0.0/0. Squashed commit of the following: net/route: RAM and ROM routing tables build correctly in all IPv4 and IPv6 configurations. net/route: Verify IPv6 ROM route build; Make number of ROM routes a variable, not a configuration item. net/route: Add initial support for ROM-base, read-only routing tables. net/route: Adjust and generalize some structures, rename some functions, and add configuration and build support that will eventually support read-only routing tables. net/route: Some initial though experiments on use of a fixe, read-only routing table
2017-09-28 17:04:31 +02:00
#include "route/ramroute.h"
Add support for an in-memory routing table cache in order to improve performance when the routing table is retained in a file. The cache holds the most recently used routing table entries and so can eliminate some file access. Squashed commit of the following: net/route: Flush in cache when any entry is deleted from the routing table. When a router matching an IP address is found, add the routing table entry to the cache. net/route: Add utility functions to manage an in-memory cache to improve performance when use a file-based routing table.
2017-09-29 20:04:45 +02:00
#include "route/cacheroute.h"
NET: Move routing table functions to net/route
2014-06-26 21:02:08 +02:00
#include "route/route.h"
Partial implementation of a simple network routing table.
2013-10-02 02:55:20 +02:00
Addes support for read-only routing tables. Prior to this change, routing tables were only support in RAM and had to be initialized with explicit logic to add the necessary routes to the routing table. With this change, routes may be defined in the pre-initialized, read-only routing table provided by the board-specific logic This would be particularly useful, for example, in the case where there is only a single network adaptor and you want all output packets to go to the single adaptor in all cases. So for that behavior you could add a read-only routing table to the board-specific long that contains a single entry, the default route: 0.0.0.0/0. Squashed commit of the following: net/route: RAM and ROM routing tables build correctly in all IPv4 and IPv6 configurations. net/route: Verify IPv6 ROM route build; Make number of ROM routes a variable, not a configuration item. net/route: Add initial support for ROM-base, read-only routing tables. net/route: Adjust and generalize some structures, rename some functions, and add configuration and build support that will eventually support read-only routing tables. net/route: Some initial though experiments on use of a fixe, read-only routing table
2017-09-28 17:04:31 +02:00
#ifdef CONFIG_NET_ROUTE
Partial implementation of a simple network routing table.
2013-10-02 02:55:20 +02:00
/****************************************************************************
* Public Functions
****************************************************************************/
/****************************************************************************
Addes support for read-only routing tables. Prior to this change, routing tables were only support in RAM and had to be initialized with explicit logic to add the necessary routes to the routing table. With this change, routes may be defined in the pre-initialized, read-only routing table provided by the board-specific logic This would be particularly useful, for example, in the case where there is only a single network adaptor and you want all output packets to go to the single adaptor in all cases. So for that behavior you could add a read-only routing table to the board-specific long that contains a single entry, the default route: 0.0.0.0/0. Squashed commit of the following: net/route: RAM and ROM routing tables build correctly in all IPv4 and IPv6 configurations. net/route: Verify IPv6 ROM route build; Make number of ROM routes a variable, not a configuration item. net/route: Add initial support for ROM-base, read-only routing tables. net/route: Adjust and generalize some structures, rename some functions, and add configuration and build support that will eventually support read-only routing tables. net/route: Some initial though experiments on use of a fixe, read-only routing table
2017-09-28 17:04:31 +02:00
* Name: net_init_route
Partial implementation of a simple network routing table.
2013-10-02 02:55:20 +02:00
*
* Description:
Addes support for read-only routing tables. Prior to this change, routing tables were only support in RAM and had to be initialized with explicit logic to add the necessary routes to the routing table. With this change, routes may be defined in the pre-initialized, read-only routing table provided by the board-specific logic This would be particularly useful, for example, in the case where there is only a single network adaptor and you want all output packets to go to the single adaptor in all cases. So for that behavior you could add a read-only routing table to the board-specific long that contains a single entry, the default route: 0.0.0.0/0. Squashed commit of the following: net/route: RAM and ROM routing tables build correctly in all IPv4 and IPv6 configurations. net/route: Verify IPv6 ROM route build; Make number of ROM routes a variable, not a configuration item. net/route: Add initial support for ROM-base, read-only routing tables. net/route: Adjust and generalize some structures, rename some functions, and add configuration and build support that will eventually support read-only routing tables. net/route: Some initial though experiments on use of a fixe, read-only routing table
2017-09-28 17:04:31 +02:00
* Initialize to the routing table
Partial implementation of a simple network routing table.
2013-10-02 02:55:20 +02:00
*
Standardization of some function headers.
2018-03-13 16:52:27 +01:00
* Input Parameters:
Addes support for read-only routing tables. Prior to this change, routing tables were only support in RAM and had to be initialized with explicit logic to add the necessary routes to the routing table. With this change, routes may be defined in the pre-initialized, read-only routing table provided by the board-specific logic This would be particularly useful, for example, in the case where there is only a single network adaptor and you want all output packets to go to the single adaptor in all cases. So for that behavior you could add a read-only routing table to the board-specific long that contains a single entry, the default route: 0.0.0.0/0. Squashed commit of the following: net/route: RAM and ROM routing tables build correctly in all IPv4 and IPv6 configurations. net/route: Verify IPv6 ROM route build; Make number of ROM routes a variable, not a configuration item. net/route: Add initial support for ROM-base, read-only routing tables. net/route: Adjust and generalize some structures, rename some functions, and add configuration and build support that will eventually support read-only routing tables. net/route: Some initial though experiments on use of a fixe, read-only routing table
2017-09-28 17:04:31 +02:00
* None
Partial implementation of a simple network routing table.
2013-10-02 02:55:20 +02:00
*
* Returned Value:
Addes support for read-only routing tables. Prior to this change, routing tables were only support in RAM and had to be initialized with explicit logic to add the necessary routes to the routing table. With this change, routes may be defined in the pre-initialized, read-only routing table provided by the board-specific logic This would be particularly useful, for example, in the case where there is only a single network adaptor and you want all output packets to go to the single adaptor in all cases. So for that behavior you could add a read-only routing table to the board-specific long that contains a single entry, the default route: 0.0.0.0/0. Squashed commit of the following: net/route: RAM and ROM routing tables build correctly in all IPv4 and IPv6 configurations. net/route: Verify IPv6 ROM route build; Make number of ROM routes a variable, not a configuration item. net/route: Add initial support for ROM-base, read-only routing tables. net/route: Adjust and generalize some structures, rename some functions, and add configuration and build support that will eventually support read-only routing tables. net/route: Some initial though experiments on use of a fixe, read-only routing table
2017-09-28 17:04:31 +02:00
* None
Partial implementation of a simple network routing table.
2013-10-02 02:55:20 +02:00
*
****************************************************************************/
Addes support for read-only routing tables. Prior to this change, routing tables were only support in RAM and had to be initialized with explicit logic to add the necessary routes to the routing table. With this change, routes may be defined in the pre-initialized, read-only routing table provided by the board-specific logic This would be particularly useful, for example, in the case where there is only a single network adaptor and you want all output packets to go to the single adaptor in all cases. So for that behavior you could add a read-only routing table to the board-specific long that contains a single entry, the default route: 0.0.0.0/0. Squashed commit of the following: net/route: RAM and ROM routing tables build correctly in all IPv4 and IPv6 configurations. net/route: Verify IPv6 ROM route build; Make number of ROM routes a variable, not a configuration item. net/route: Add initial support for ROM-base, read-only routing tables. net/route: Adjust and generalize some structures, rename some functions, and add configuration and build support that will eventually support read-only routing tables. net/route: Some initial though experiments on use of a fixe, read-only routing table
2017-09-28 17:04:31 +02:00
void net_init_route(void)
Partial implementation of a simple network routing table.
2013-10-02 02:55:20 +02:00
{
Addes support for read-only routing tables. Prior to this change, routing tables were only support in RAM and had to be initialized with explicit logic to add the necessary routes to the routing table. With this change, routes may be defined in the pre-initialized, read-only routing table provided by the board-specific logic This would be particularly useful, for example, in the case where there is only a single network adaptor and you want all output packets to go to the single adaptor in all cases. So for that behavior you could add a read-only routing table to the board-specific long that contains a single entry, the default route: 0.0.0.0/0. Squashed commit of the following: net/route: RAM and ROM routing tables build correctly in all IPv4 and IPv6 configurations. net/route: Verify IPv6 ROM route build; Make number of ROM routes a variable, not a configuration item. net/route: Add initial support for ROM-base, read-only routing tables. net/route: Adjust and generalize some structures, rename some functions, and add configuration and build support that will eventually support read-only routing tables. net/route: Some initial though experiments on use of a fixe, read-only routing table
2017-09-28 17:04:31 +02:00
#if defined(CONFIG_ROUTE_IPv4_RAMROUTE) || defined(CONFIG_ROUTE_IPv6_RAMROUTE)
net_init_ramroute();
Complete implementation of the IPv6 routing logic. From Max Neklyudov.
2015-05-13 15:22:02 +02:00
#endif
This commit adds support for routing tables in files in a file system. This might be useful for customized, per-unit routing tables. There are two issues with it however: 1. Reading from file system on a per packet basis could be slow. I think it probably should have a small, in-memory cache of most frequently used routes for good problem. 2. Currently the delroute logic is disabled due to a problem with the design. NuttX does not currently support truncate(). Therefore, it is not possible to delete entries from the routing table file. In this current implementation, that leaves the last entry intact at the end of the file. An alternative design might include a tag on each record to indicate if the record is valid or not. That would work but would add complexity to the other routing table functions. The existing implementation is available for testing purposes only if CONFIG_EXPERIMENTAL=y. Squashed commit of the following: net/route: The current delroute design depends on file truncation. However, NuttX does not currently support truncate. Alternative, more complex designs are possible but not implemented. At present the file routing table are otherwise functional but the delroute logic is disabled via CONFIG_EXPERIMENTAL. Enable it only if you plan to fix it. net/route: Fix some issues with locking routing table files. net/route: Add partial implementation of delroute for the case where the routing table is in a file. net/route: Add support for seeking to positions in the routing table. net/route: Add net_addroute_ipv4/6() using a file-based routing table. net/route: Add net_foreach_ipv4/4() using a file-based routing table. net/route: Initial build, configuration, and fs utilies to support routing tables in a file.
2017-09-29 16:33:36 +02:00
Add support for an in-memory routing table cache in order to improve performance when the routing table is retained in a file. The cache holds the most recently used routing table entries and so can eliminate some file access. Squashed commit of the following: net/route: Flush in cache when any entry is deleted from the routing table. When a router matching an IP address is found, add the routing table entry to the cache. net/route: Add utility functions to manage an in-memory cache to improve performance when use a file-based routing table.
2017-09-29 20:04:45 +02:00
#if defined(CONFIG_ROUTE_IPv4_CACHEROUTE) || defined(CONFIG_ROUTE_IPv6_CACHEROUTE)
net_init_cacheroute();
#endif
Complete implementation of the IPv6 routing logic. From Max Neklyudov.
2015-05-13 15:22:02 +02:00
}
Partial implementation of a simple network routing table.
2013-10-02 02:55:20 +02:00
Addes support for read-only routing tables. Prior to this change, routing tables were only support in RAM and had to be initialized with explicit logic to add the necessary routes to the routing table. With this change, routes may be defined in the pre-initialized, read-only routing table provided by the board-specific logic This would be particularly useful, for example, in the case where there is only a single network adaptor and you want all output packets to go to the single adaptor in all cases. So for that behavior you could add a read-only routing table to the board-specific long that contains a single entry, the default route: 0.0.0.0/0. Squashed commit of the following: net/route: RAM and ROM routing tables build correctly in all IPv4 and IPv6 configurations. net/route: Verify IPv6 ROM route build; Make number of ROM routes a variable, not a configuration item. net/route: Add initial support for ROM-base, read-only routing tables. net/route: Adjust and generalize some structures, rename some functions, and add configuration and build support that will eventually support read-only routing tables. net/route: Some initial though experiments on use of a fixe, read-only routing table
2017-09-28 17:04:31 +02:00
#endif /* CONFIG_NET_ROUTE */
Reference in New Issue Copy Permalink