search

wladwm / ban2bgp

BGP Intrusion prevention system
MIT License
2 stars 1 forks source link

Issue with connection with 10.0.0.1 #1

Closed ResearchIntern98 closed 11 months ago

ResearchIntern98 commented 1 year ago

Hi, We were trying to run ban2bgp! On doing cargo run only this gets printed: Listening on http://0.0.0.0:8080 A process to port 179 also opens! But Connecting to 10.0.0.1:179 does not print? We made point to point to a route with ubuntu machine keeping ip addresses as mentioned!

Earlier we had to change tokio-util = "0.6.6" to tokio-util = { version = "0.6.6", features = ["full"] } to overcome build error in Cargo.toml

wladwm commented 1 year ago

Hi.

It should connect to your BGP router specified in ban2bgp.ini as peers=10.0.0.1 AS65535 Listen port was specified as listen=0.0.0.0:1179 - port 1179, not 179! Because you can not listen at port below 1024 if you're not root.

ResearchIntern98 commented 1 year ago

With or without sudo with 1179 or 179, it is not connecting to 10.0.0.1

wladwm commented 1 year ago

Could you please show your ban2bgp.ini ? I will try to test

ResearchIntern98 commented 1 year ago

[main] httplisten=0.0.0.0:8080 listen=0.0.0.0:1179 nexthop=198.18.0.1 communities=666:666 peers=10.0.0.1 AS65535 duration=3600 skiplist=10.0.0.0/24

wladwm commented 1 year ago

Could you please replace content by following and try again?

[main] httplisten=0.0.0.0:8080 listen=0.0.0.0:1179 nexthop=198.18.0.1 communities=666:666 peers=peer_r1 duration=3600 skiplist=10.0.0.0/24

[peer_r1] peer=10.0.0.1 as=65535 mode=blackhole

ResearchIntern98 commented 1 year ago

Doing this change in ban2bgp.ini solved the issue! Advertised routes are added, but not getting removed after duration defined! Why?

wladwm commented 1 year ago

Please update ban2bgp and rebuild. When routes should expire please check on main page (http://...:8080) presence of these routes.

wladwm commented 11 months ago

Seems that problem was solved any way...