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

FastNetMon /32 Blackhole Issue with Gateway IP #1031

Open
vahidajorloo opened this issue Dec 12, 2024 · 2 comments
Open

FastNetMon /32 Blackhole Issue with Gateway IP #1031

vahidajorloo opened this issue Dec 12, 2024 · 2 comments

Comments

@vahidajorloo
Copy link

Hi Pavel,

I am facing an issue with FastNetMon and /32 blackhole announcements. Assume we have two IP addresses:

192.168.1.1 on the interface VLAN (SVI) as the gateway.
192.168.1.2 on the server in the same VLAN.

When I run the following command:
/usr/bin/fastnetmon_api_client ban 192.168.1.2 (the server ip)

It works as expected, and everything is fine.

However, when I run:

/usr/bin/fastnetmon_api_client ban 192.168.1.1 (the gateway IP, directly connected to the router)

nothing happens, and the IP is still reachable, even though I can see it in the BGP advertised table to the upstream peer.

Is there anything I can do to fix this issue?

@pavel-odintsov
Copy link
Owner

Hello!

Thank you for report.

I do not think that it related with FastNetMon as it's more about routing policy.

@pavel-odintsov
Copy link
Owner

Can you see that BGP announces are correctly created in both cases? If so then it's clearly BGP policy specific issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants