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_add_ramroute.c
|
2013-10-02 02:55:20 +02:00
|
|
|
*
|
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
|
2013-10-02 02:55:20 +02:00
|
|
|
*
|
2021-02-19 12:45:37 +01:00
|
|
|
* http://www.apache.org/licenses/LICENSE-2.0
|
2013-10-02 02:55:20 +02:00
|
|
|
*
|
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.
|
2013-10-02 02:55:20 +02:00
|
|
|
*
|
|
|
|
****************************************************************************/
|
|
|
|
|
|
|
|
/****************************************************************************
|
|
|
|
* Included Files
|
|
|
|
****************************************************************************/
|
|
|
|
|
|
|
|
#include <nuttx/config.h>
|
|
|
|
|
|
|
|
#include <stdint.h>
|
2017-08-10 17:14:31 +02:00
|
|
|
#include <string.h>
|
2013-10-02 02:55:20 +02:00
|
|
|
#include <errno.h>
|
2013-10-05 20:05:51 +02:00
|
|
|
#include <debug.h>
|
|
|
|
|
2014-07-05 00:38:51 +02:00
|
|
|
#include <nuttx/net/net.h>
|
2014-07-05 03:13:08 +02:00
|
|
|
#include <nuttx/net/ip.h>
|
2014-07-05 00:38:51 +02:00
|
|
|
|
2013-10-05 20:05:51 +02:00
|
|
|
#include <arch/irq.h>
|
2013-10-02 02:55:20 +02:00
|
|
|
|
2024-04-09 15:07:57 +02:00
|
|
|
#include "netlink/netlink.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"
|
2014-06-26 21:02:08 +02:00
|
|
|
#include "route/route.h"
|
2013-10-02 02:55:20 +02:00
|
|
|
|
2017-09-28 17:23:03 +02:00
|
|
|
#if defined(CONFIG_ROUTE_IPv4_RAMROUTE) || defined(CONFIG_ROUTE_IPv6_RAMROUTE)
|
2013-10-02 02:55:20 +02:00
|
|
|
|
|
|
|
/****************************************************************************
|
|
|
|
* Public Functions
|
|
|
|
****************************************************************************/
|
|
|
|
|
|
|
|
/****************************************************************************
|
2017-08-10 17:14:31 +02:00
|
|
|
* Name: net_addroute_ipv4 and net_addroute_ipv6
|
2013-10-02 02:55:20 +02:00
|
|
|
*
|
|
|
|
* Description:
|
|
|
|
* Add a new route to the routing table
|
|
|
|
*
|
2018-03-13 16:52:27 +01:00
|
|
|
* Input Parameters:
|
2013-10-02 02:55:20 +02:00
|
|
|
*
|
|
|
|
* Returned Value:
|
|
|
|
* OK on success; Negated errno on failure.
|
|
|
|
*
|
|
|
|
****************************************************************************/
|
|
|
|
|
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_ROUTE_IPv4_RAMROUTE
|
2017-08-10 17:14:31 +02:00
|
|
|
int net_addroute_ipv4(in_addr_t target, in_addr_t netmask, in_addr_t router)
|
2013-10-02 02:55:20 +02:00
|
|
|
{
|
2017-08-11 00:18:06 +02:00
|
|
|
FAR struct net_route_ipv4_s *route;
|
2013-10-05 20:05:51 +02:00
|
|
|
|
|
|
|
/* Allocate a route entry */
|
|
|
|
|
2017-08-10 17:14:31 +02:00
|
|
|
route = net_allocroute_ipv4();
|
2013-10-05 20:05:51 +02:00
|
|
|
if (!route)
|
|
|
|
{
|
2016-06-11 23:50:49 +02:00
|
|
|
nerr("ERROR: Failed to allocate a route\n");
|
2013-10-05 20:05:51 +02:00
|
|
|
return -ENOMEM;
|
|
|
|
}
|
2013-10-02 02:55:20 +02:00
|
|
|
|
2017-07-08 21:03:58 +02:00
|
|
|
/* Format the new routing table entry */
|
2013-10-02 02:55:20 +02:00
|
|
|
|
2015-01-16 20:01:08 +01:00
|
|
|
net_ipv4addr_copy(route->target, target);
|
|
|
|
net_ipv4addr_copy(route->netmask, netmask);
|
|
|
|
net_ipv4addr_copy(route->router, router);
|
2017-08-11 00:18:06 +02:00
|
|
|
net_ipv4_dumproute("New route", route);
|
2013-10-05 20:05:51 +02:00
|
|
|
|
|
|
|
/* Get exclusive address to the networking data structures */
|
|
|
|
|
2016-12-03 23:28:19 +01:00
|
|
|
net_lock();
|
2013-10-02 02:55:20 +02:00
|
|
|
|
|
|
|
/* Then add the new entry to the table */
|
|
|
|
|
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
|
|
|
ramroute_ipv4_addlast((FAR struct net_route_ipv4_entry_s *)route,
|
|
|
|
&g_ipv4_routes);
|
2016-12-03 23:28:19 +01:00
|
|
|
net_unlock();
|
2024-04-09 15:07:57 +02:00
|
|
|
|
|
|
|
netlink_route_notify(route, RTM_NEWROUTE, AF_INET);
|
2013-10-05 20:05:51 +02:00
|
|
|
return OK;
|
2013-10-02 02:55:20 +02:00
|
|
|
}
|
2015-05-13 15:22:02 +02:00
|
|
|
#endif
|
|
|
|
|
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_ROUTE_IPv6_RAMROUTE
|
2017-08-10 17:14:31 +02:00
|
|
|
int net_addroute_ipv6(net_ipv6addr_t target, net_ipv6addr_t netmask,
|
|
|
|
net_ipv6addr_t router)
|
2015-05-13 15:22:02 +02:00
|
|
|
{
|
|
|
|
FAR struct net_route_ipv6_s *route;
|
|
|
|
|
|
|
|
/* Allocate a route entry */
|
|
|
|
|
|
|
|
route = net_allocroute_ipv6();
|
|
|
|
if (!route)
|
|
|
|
{
|
2016-06-11 23:50:49 +02:00
|
|
|
nerr("ERROR: Failed to allocate a route\n");
|
2015-05-13 15:22:02 +02:00
|
|
|
return -ENOMEM;
|
|
|
|
}
|
|
|
|
|
2017-07-08 21:03:58 +02:00
|
|
|
/* Format the new routing table entry */
|
2015-05-13 15:22:02 +02:00
|
|
|
|
|
|
|
net_ipv6addr_copy(route->target, target);
|
|
|
|
net_ipv6addr_copy(route->netmask, netmask);
|
|
|
|
net_ipv6addr_copy(route->router, router);
|
2017-08-11 00:18:06 +02:00
|
|
|
net_ipv6_dumproute("New route", route);
|
2015-05-13 15:22:02 +02:00
|
|
|
|
|
|
|
/* Get exclusive address to the networking data structures */
|
|
|
|
|
2016-12-03 23:28:19 +01:00
|
|
|
net_lock();
|
2015-05-13 15:22:02 +02:00
|
|
|
|
|
|
|
/* Then add the new entry to the table */
|
|
|
|
|
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
|
|
|
ramroute_ipv6_addlast((FAR struct net_route_ipv6_entry_s *)route,
|
|
|
|
&g_ipv6_routes);
|
2016-12-03 23:28:19 +01:00
|
|
|
net_unlock();
|
2024-04-09 15:07:57 +02:00
|
|
|
|
|
|
|
netlink_route_notify(route, RTM_NEWROUTE, AF_INET6);
|
2015-05-13 15:22:02 +02:00
|
|
|
return OK;
|
|
|
|
}
|
|
|
|
#endif
|
2013-10-02 02:55:20 +02:00
|
|
|
|
2017-09-28 17:23:03 +02:00
|
|
|
#endif /* CONFIG_ROUTE_IPv4_RAMROUTE || CONFIG_ROUTE_IPv6_RAMROUTE */
|