Replies: 13 comments 3 replies
-
|
Can you describe a bit your topology, configuration, and the whole scope of messages received/sent? |
Beta Was this translation helpful? Give feedback.
-
Hello: I am his friend; in fact this frr does not have any neighbors;
|
Beta Was this translation helpful? Give feedback.
-
|
How are you starting zebra and what does your configuration look like. I am not seeing this locally so I need proper recreation steps. |
Beta Was this translation helpful? Give feedback.
-
I started frr through systemctl restart frr.service The configuration is as follows Current configuration: |
Beta Was this translation helpful? Give feedback.
-
My system is centos7.8 A special situation that may help you is to ping the local ipv6 address Thank you very much for your reply |
Beta Was this translation helpful? Give feedback.
-
|
Can you show also /etc/frr/daemons file? |
Beta Was this translation helpful? Give feedback.
-
|
here is the # This file tells the frr package which daemons to start.
#
# Sample configurations for these daemons can be found in
# /usr/share/doc/frr/examples/.
#
# ATTENTION:
#
# When activating a daemon for the first time, a config file, even if it is
# empty, has to be present *and* be owned by the user and group "frr", else
# the daemon will not be started by /etc/init.d/frr. The permissions should
# be u=rw,g=r,o=.
# When using "vtysh" such a config file is also needed. It should be owned by
# group "frrvty" and set to ug=rw,o= though. Check /etc/pam.d/frr, too.
#
# The watchfrr, zebra and staticd daemons are always started.
#
bgpd=no
ospfd=no
ospf6d=yes
ripd=no
ripngd=no
isisd=no
pimd=no
ldpd=no
nhrpd=no
eigrpd=no
babeld=no
sharpd=no
pbrd=no
bfdd=no
fabricd=no
vrrpd=no
pathd=no
#
# If this option is set the /etc/init.d/frr script automatically loads
# the config via "vtysh -b" when the servers are started.
# Check /etc/pam.d/frr if you intend to use "vtysh"!
#
vtysh_enable=yes
zebra_options=" -A 127.0.0.1 -s 90000000 -f /etc/frr/zebra.conf"
bgpd_options=" -A 127.0.0.1 -f /etc/frr/bgpd.conf"
ospfd_options=" -A 127.0.0.1 -f /etc/frr/ospfd.conf"
ospf6d_options=" -A ::1 -f /etc/frr/ospf6d.conf"
ripd_options=" -A 127.0.0.1"
ripngd_options=" -A ::1"
isisd_options=" -A 127.0.0.1"
pimd_options=" -A 127.0.0.1"
ldpd_options=" -A 127.0.0.1"
nhrpd_options=" -A 127.0.0.1"
eigrpd_options=" -A 127.0.0.1"
babeld_options=" -A 127.0.0.1"
sharpd_options=" -A 127.0.0.1"
pbrd_options=" -A 127.0.0.1"
staticd_options="-A 127.0.0.1"
bfdd_options=" -A 127.0.0.1"
fabricd_options="-A 127.0.0.1"
vrrpd_options=" -A 127.0.0.1"
pathd_options=" -A 127.0.0.1"
# configuration profile
#
#frr_profile="traditional"
#frr_profile="datacenter"
#
# This is the maximum number of FD's that will be available.
# Upon startup this is read by the control files and ulimit
# is called. Uncomment and use a reasonable value for your
# setup if you are expecting a large number of peers in
# say BGP.
#MAX_FDS=1024
# The list of daemons to watch is automatically generated by the init script.
##watchfrr_options=""
# To make watchfrr create/join the specified netns, use the following option:
##watchfrr_options="--netns"
# This only has an effect in /etc/frr/<somename>/daemons, and you need to
# start FRR with "/usr/lib/frr/frrinit.sh start <somename>".
# for debugging purposes, you can specify a "wrap" command to start instead
# of starting the daemon directly, e.g. to use valgrind on ospfd:
# ospfd_wrap="/usr/bin/valgrind"
# or you can use "all_wrap" for all daemons, e.g. to use perf record:
# all_wrap="/usr/bin/perf record --call-graph -"
# the normal daemon command is added to this at the end. |
Beta Was this translation helpful? Give feedback.
-
This file tells the frr package which daemons to start.Sample configurations for these daemons can be found in/usr/share/doc/frr/examples/.ATTENTION:When activating a daemon for the first time, a config file, even if it isempty, has to be present and be owned by the user and group "frr", elsethe daemon will not be started by /etc/init.d/frr. The permissions shouldbe u=rw,g=r,o=.When using "vtysh" such a config file is also needed. It should be owned bygroup "frrvty" and set to ug=rw,o= though. Check /etc/pam.d/frr, too.The watchfrr, zebra and staticd daemons are always started.bgpd=no If this option is set the /etc/init.d/frr script automatically loadsthe config via "vtysh -b" when the servers are started.Check /etc/pam.d/frr if you intend to use "vtysh"!vtysh_enable=yes configuration profile#frr_profile="traditional" This is the maximum number of FD's that will be available.Upon startup this is read by the control files and ulimitis called. Uncomment and use a reasonable value for yoursetup if you are expecting a large number of peers insay BGP.#MAX_FDS=1024 The list of daemons to watch is automatically generated by the init script.##watchfrr_options="" To make watchfrr create/join the specified netns, use the following option:##watchfrr_options="--netns" This only has an effect in /etc/frr//daemons, and you need tostart FRR with "/usr/lib/frr/frrinit.sh start ".for debugging purposes, you can specify a "wrap" command to start insteadof starting the daemon directly, e.g. to use valgrind on ospfd:ospfd_wrap="/usr/bin/valgrind"or you can use "all_wrap" for all daemons, e.g. to use perf record:all_wrap="/usr/bin/perf record --call-graph -"the normal daemon command is added to this at the end. |
Beta Was this translation helpful? Give feedback.
-
|
Is there any method to get |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
I found it was [root@localhost wh]# ip6tables -t raw -L -n -v
Chain PREROUTING (policy ACCEPT 1994K packets, 140M bytes)
pkts bytes target prot opt in out source destination
442 24400 DROP icmpv6 * * fe80::/16 ::/0 ipv6-icmptype 133
Chain OUTPUT (policy ACCEPT 13038 packets, 891K bytes)
pkts bytes target prot opt in out source destinationIs my kernel config error? |
Beta Was this translation helpful? Give feedback.
-
|
I have rechecked: the |
Beta Was this translation helpful? Give feedback.
-
|
Maybe it is an zebra or kernel bug, because there is the code to filter RS packages, and it blocked in kernel's Line 891 in 21aa863 |
Beta Was this translation helpful? Give feedback.
-
|
I confirm that this error occurred in this environment:
All RS(Router Solicitation) packages will blocked in zebra's |
Beta Was this translation helpful? Give feedback.
-
|
I think we should always recv RS, no matter RA is enable or not. We can just drop RS, when RA is false. @donaldsharp |
Beta Was this translation helpful? Give feedback.
-
|
This problem is very serious, if we only use BGP with ipv6-forward enabled. Since there will no configure in zebra.conf about RS/RA. All RS(Router Solicitation) packets will be blocked in zebra's recv-q. |
Beta Was this translation helpful? Give feedback.
-
Describe the bug
Screenshots
Versions
OS Version:
CentOS7.8、CentOS8
FRR Version:
quaager 2.07、frr9.1、frr9.0
Beta Was this translation helpful? Give feedback.
All reactions