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
In the case of IOS, Batfish crashes when executing Bi-directional Reachability to the IP address after NAT. #8859
Comments
Can you attach server-side logs (docker logs) to this issue? |
Hi, I tried this out and did not have any issues. Can you post more about the network you're using? Here's mine: https://gist.github.com/dhalperi/2db8b46ebff98eb4d3fbb97aed823af3 |
Hello, thank you for your reply. Please confirm. logs↓ |
Thanks for that repro. After fixing a few bugs ( bf.q.bidirectionalReachability(
pathConstraints=PathConstraints(startLocation='dev5'),
headers=HeaderConstraints(srcIps= '10.0.45.5', dstIps='20.0.12.1', srcPorts='32875', dstPorts='22')
).answer().frame() and got
That checks out. |
Logging Slack discussion with @anothermattbrown :
|
[Problem]
In the case of IOS, Batfish crashes when executing Bi-directional Reachability to the IP address after NAT.
[Topology]
dev3's NAT settings convert 10.0.12.1 to 20.0.12.1.
[Config] ※Minimum Config
・ dev1
・ dev2
・ dev3
・ dev4
・ dev5
[Result]
・ Bi-directional Reachability Forward
・ Bi-directional Reachability Reverse
・ Bi-directional Reachability(dev5->dev1)
In the case of IOS, Batfish crashes when executing Bi-directional Reachability from 10.0.45.5 to 20.0.12.1 after NAT.
The text was updated successfully, but these errors were encountered: