Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

frr fails to input from /dev/stdin using -f in 9.0 #14194

Closed
2 tasks done
jfgibbins opened this issue Aug 12, 2023 · 4 comments
Closed
2 tasks done

frr fails to input from /dev/stdin using -f in 9.0 #14194

jfgibbins opened this issue Aug 12, 2023 · 4 comments
Assignees
Labels
triage Needs further investigation

Comments

@jfgibbins
Copy link

Using version 8.5 and prior the following command will add config to running instance of frr

$SUDO vtysh -f /dev/stdin <<EOF
ip router-id 10.8.88.1
EOF

config is sample...doesn't matter what commands you're trying to add

starting with 9.0 this no longer works

  • Did you check if this is a duplicate issue?
  • Did you test it on the latest FRRouting/frr master branch?

To Reproduce
see above

Versions
Ubuntu 22.04 - latest build of cloud image

@jfgibbins jfgibbins added the triage Needs further investigation label Aug 12, 2023
@choppsv1
Copy link
Contributor

qq: does normal redirecting work, or fail the same way? i.e.,

cat <<EOF | sudo vtysh
ip router-id 10.8.88.1
EOF

@jfgibbins
Copy link
Author

if I adjust yours to include a line for "conf t" it will take the command. I'm guessing cli without a parameter is defaulting to using -c for arguments, as if you were at a command prompt in vtysh.
I did notice though, when using -f as in the original post, it does oddly accept a statement for "ip route x.x.x.x/xx dest", but no other commands.

This worked quite well prior to 9.x. Has the method of usage been deprecated, or was it an "unrealized enhancement"?

Copy link

This issue is stale because it has been open 180 days with no activity. Comment or remove the autoclose label in order to avoid having this issue closed.

@frrbot
Copy link

frrbot bot commented Feb 12, 2024

This issue will be automatically closed in the specified period unless there is further activity.

@frrbot frrbot bot closed this as completed Feb 19, 2024
@frrbot frrbot bot removed the autoclose label Feb 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage Needs further investigation
Projects
None yet
Development

No branches or pull requests

2 participants