Hi list,
here is a small addition. Adding and deleting the route to and from
routing table on the command line works as expected:
fw1 # route add 2001:xxxx:xxxx:xxxx::4/128 2001:xxxx:xxxx:xxxx::4 -label
geo_service
add host 2001:xxxx:xxxx:xxxx::4/128: gateway 2001:xxxx:xxxx:xxxx::4
fw# route -n show -inet6 | grep 2001:xxxx:xxxx:xxxx::4
2001:xxxx:xxxx:xxxx::4 52:01:8d:e4:fd:63 UHLch
1 23015 - 3 vlan18
2001:xxxx:xxxx:xxxx::4 2001:xxxx:xxxx:xxxx::4 UGHS
0 0 - 8 vlan18
fw1 # route del 2001:xxxx:xxxx:xxxx::4/128 2001:xxxx:xxxx:xxxx::4 -label
geo_service
del host 2001:xxxx:xxxx:xxxx::4/128: gateway 2001:xxxx:xxxx:xxxx::4
fw1# route -n show -inet6 | grep 2001:xxxx:xxxx:xxxx::4
2001:638:dfce:3000::4 52:01:8d:e4:fd:63 UHLc
0 23015 - 3 vlan18
Why can't relayd add the route to the table and what does the following
log concretely mean:
<snip>
pfe_route: failed to add gateway 2001:638:dfce:3000::4: 22 Invalid argument
<snap>
Am 28.06.23 um 16:57 schrieb Joerg Streckfuss:
> Hello,
>
> I'm trying to use the relayd router function to add host routes to the
> routing table with a route label for further processing by bgpd. The
> host ist directly connected to the firewall.
>
> relayd.conf:
>
> table <service_v6> { 2001:xxxx:xxxx:xxxx::4 }
> router "service_v6" {
> route 2001:xxxx:xxxx:xxxx::4/128
> forward to <service_v6> port 80 check tcp
> rtlabel geo_service
> }
>
> fw1# relayd -vvvd
> startup
> socket_rlimit: max open files 1024
> pfe: filter init done
> socket_rlimit: max open files 1024
> socket_rlimit: max open files 1024
> socket_rlimit: max open files 1024
> parent_tls_ticket_rekey: rekeying tickets
> hce_notify_done: 2001:xxxx:xxxx:xxxx::4 (tcp connect ok)
> host 2001:xxxx:xxxx:xxxx::4, check tcp (0ms,tcp connect ok), state
> unknown -> up, availability 100.00%
> pfe_dispatch_hce: state 1 for host 1 2001:xxxx:xxxx:xxxx::4
> sync_routes: router service_v6 route 2001:xxxx:xxxx:xxxx::4/128 gateway
> 2001:xxxx:xxxx:xxxx::4 up priority 0
> hce_notify_done: 2001:xxxx:xxxx:xxxx::4 (tcp connect ok)
> pfe_route: failed to add gateway 2001:xxxx:xxxx:xxxx::4: 22 Invalid
> argument
> hce_notify_done: 2001:xxxx:xxxx:xxxx::4 (tcp connect ok)
> hce_notify_done: 2001:xxxx:xxxx:xxxx::4 (tcp connect ok)
> hce_notify_done: 2001:xxxx:xxxx:xxxx::4 (tcp connect ok)
>
>
> The route with the route label never pops up in the routing table. With
> IPv4 addresses the setup works as expected.
>
> Any suggestions?
>
No comments:
Post a Comment