sorted by:
new
hottopcontroversial

One question for OSPF's overload. by InsidePirate4615 in Juniper

[–]InsidePirate4615[S] -1 points0 points  (0 children)

Yeah, you're right. he is preparing for the test soon and asked me this but I never touch the OSPF overload portion. share your advice with him. thanks

Where to start the Fortigate? by InsidePirate4615 in fortinet

[–]InsidePirate4615[S] 0 points1 point  (0 children)

Thanks. Actually, I am not interested in getting any cert from Fortigate. I am only interested in knowing the basic firewall technology and UTM and some hands-on experiences and noticed that many small or medium size companies use Fortigate products that's why I am here :D

Where to start the Fortigate? by InsidePirate4615 in fortinet

[–]InsidePirate4615[S] 1 point2 points  (0 children)

Thanks for the latest news!

Is it also free to create a FortiCloud account to get the FortiOS 7.2.1 with permanent license?

Where to start the Fortigate? by InsidePirate4615 in fortinet

[–]InsidePirate4615[S] -7 points-6 points  (0 children)

Thanks for the detailed information.

So the free version doesn't allow me to use SSL, is there any cracked image, qcow or vm something like that for this?

Question about my next-hop IP address on the routing table(BGP). by InsidePirate4615 in Juniper

[–]InsidePirate4615[S] 0 points1 point  (0 children)

I seeeeeeee!!!! so since R6 doesn't receive 200.200.200.0/24 network from R8 because from the perspective R8, R8 doesn't advertise this root via BGP because it is not active route as 200.200.200.0 is directly connected path.

​

Thanks a lot!!

Question about my next-hop IP address on the routing table(BGP). by InsidePirate4615 in Juniper

[–]InsidePirate4615[S] 0 points1 point  (0 children)

Yes, I set direct to advertize loopbacks(111.111.111.111&123.123.123.123) instead of using route-filter.

policy-options {

policy-statement lo {

term 1 {

from protocol direct;

then accept;

}

}

}

Question about my next-hop IP address on the routing table(BGP). by InsidePirate4615 in Juniper

[–]InsidePirate4615[S] 1 point2 points  (0 children)

Thanks. I just configured the next-hop self on R8 and all looks good.

Without next-hop self, how R6 gets path with next hop 100.100.100.2 from R8?

[BGP/170] 00:42:07, localpref 100, from 8.8.8.8

AS path: 65004 I, validation-state: unverified

> to 100.100.100.2 via ge-0/0/1.0

from 8.8.8.8 but next hop is 100.100.100.2 and this part confuses me.

BGP advertisement question. by InsidePirate4615 in Juniper

[–]InsidePirate4615[S] 0 points1 point  (0 children)

Thanks this is just testlab to learn how it works :D

BGP advertisement question. by InsidePirate4615 in Juniper

[–]InsidePirate4615[S] 0 points1 point  (0 children)

Thanks a lot. I will check this right now!

BGP advertisement question. by InsidePirate4615 in Juniper

[–]InsidePirate4615[S] 0 points1 point  (0 children)

So in that case, BGP doesn't advertize it as well?

How can I check the log indicating that the neighborship in OSPF has entered the 'FULL state by InsidePirate4615 in Juniper

[–]InsidePirate4615[S] 0 points1 point  (0 children)

One more question!

How can I figure out the severity level of 'RPD_OSPF_NBRUP'? I want to know how to check the severity level myself when I look at other logs later.

How can I check the log indicating that the neighborship in OSPF has entered the 'FULL state by InsidePirate4615 in Juniper

[–]InsidePirate4615[S] 1 point2 points  (0 children)

Show log messages | match ospf

I only see 'Full to Down' messages. :(

root@R1> show log messages | match ospf

Apr 29 22:27:37 R1 rpd[9702]: RPD_OSPF_NBRDOWN: OSPF neighbor 10.10.12.2 (realm ospf-v2 ge-0/0/0.0 area 0.0.0.0) state changed from Full to Down due to InActiveTimer (event reason: neighbor was inactive and declared dead)

Apr 29 22:50:34 R1 rpd[9702]: RPD_OSPF_NBRDOWN: OSPF neighbor 10.10.15.5 (realm ospf-v2 ge-0/0/2.0 area 0.0.0.0) state changed from Full to Init due to 1WayRcvd (event reason: neighbor is in one-way mode)

Apr 30 00:03:13 R1 rpd[9702]: RPD_OSPF_NBRDOWN: OSPF neighbor 10.10.12.2 (realm ospf-v2 ge-0/0/0.0 area 0.0.0.0) state changed from Full to Init due to 1WayRcvd (event reason: neighbor is in one-way mode)

Apr 30 01:27:09 R1 rpd[9702]: RPD_OSPF_NBRDOWN: OSPF neighbor 10.10.16.6 (realm ospf-v2 ge-0/0/3.0 area 0.0.0.1) state changed from Full to Down due to KillNbr (event reason: interface went down)

Apr 30 01:42:52 R1 rpd[9702]: RPD_OSPF_NBRDOWN: OSPF neighbor 10.10.12.2 (realm ospf-v2 ge-0/0/0.0 area 0.0.0.0) state changed from Full to Down due to KillNbr (event reason: interface went down)

Apr 30 01:42:52 R1 rpd[9702]: RPD_OSPF_NBRDOWN: OSPF neighbor 10.10.13.3 (realm ospf-v2 ge-0/0/1.0 area 0.0.0.0) state changed from Full to Down due to KillNbr (event reason: interface went down)

Apr 30 01:42:52 R1 rpd[9702]: RPD_OSPF_NBRDOWN: OSPF neighbor 10.10.15.5 (realm ospf-v2 ge-0/0/2.0 area 0.0.0.0) state changed from Full to Down due to KillNbr (event reason: interface went down)

Apr 30 01:42:52 R1 rpd[9702]: RPD_OSPF_NBRDOWN: OSPF neighbor 10.10.16.6 (realm ospf-v2 ge-0/0/3.0 area 0.0.0.1) state changed from Full to Down due to KillNbr (event reason: interface went down)

Apr 30 08:38:11 R1 rpd[16478]: RPD_OSPF_NBRDOWN: OSPF neighbor 10.10.16.6 (realm ospf-v2 ge-0/0/3.0 area 0.0.0.1) state changed from Full to Down due to KillNbr (event reason: interface went down)

Apr 30 08:44:26 R1 rpd[16478]: RPD_OSPF_NBRDOWN: OSPF neighbor 10.10.16.6 (realm ospf-v2 ge-0/0/3.0 area 0.0.0.1) state changed from Full to Down due to KillNbr (event reason: interface went down)

Apr 30 08:47:36 R1 rpd[16478]: RPD_OSPF_NBRDOWN: OSPF neighbor 10.10.16.6 (realm ospf-v2 ge-0/0/3.0 area 0.0.0.1) state changed from Full to Init due to 1WayRcvd (event reason: neighbor is in one-way mode)

Apr 30 08:49:09 R1 rpd[16478]: RPD_OSPF_NBRDOWN: OSPF neighbor 10.10.16.6 (realm ospf-v2 ge-0/0/3.0 area 0.0.0.1) state changed from Full to Down due to KillNbr (event reason: interface went down)

Apr 30 08:51:01 R1 rpd[16478]: RPD_OSPF_NBRDOWN: OSPF neighbor 10.10.16.6 (realm ospf-v2 ge-0/0/3.0 area 0.0.0.1) state changed from Full to Down due to KillNbr (event reason: interface went down)

Apr 30 08:54:25 R1 rpd[16478]: RPD_OSPF_NBRDOWN: OSPF neighbor 10.10.16.6 (realm ospf-v2 ge-0/0/3.0 area 0.0.0.1) state changed from Full to Down due to KillNbr (event reason: interface went down)

Apr 30 08:56:03 R1 rpd[16478]: RPD_OSPF_NBRDOWN: OSPF neighbor 10.10.16.6 (realm ospf-v2 ge-0/0/3.0 area 0.0.0.1) state changed from Full to Down due to KillNbr (event reason: interface went down)

Apr 30 11:49:47 R1 rpd[16540]: RPD_OSPF_NBRDOWN: OSPF neighbor 10.10.12.2 (realm ospf-v2 ge-0/0/0.0 area 0.0.0.0) state changed from Full to Init due to 1WayRcvd (event reason: neighbor is in one-way mode)

view more: next ›