Solved

eigrp not working properly

Posted on 2013-12-16
21
240 Views
Last Modified: 2014-01-12
I could ping PC0 from my firewall. Now when I shut down port fa0/2 on core1, the ping stops. From my understanding, eigrp load balance between the two links, so why when fa0/2 went down, it did not send the traffic to fa0/2 of core2.

The attached diagram has all the eigrp info.

Appreciate all the inputs.

Thanks
net-diagram.JPG
0
Comment
Question by:leblanc
  • 11
  • 10
21 Comments
 
LVL 50

Expert Comment

by:Don Johnston
ID: 39723795
It's hard to tell from the diagram...

What device has the IP address 192.168.16.9?
0
 
LVL 1

Author Comment

by:leblanc
ID: 39724678
Sorry. 192.168.16.9 is on the 3560 end. See updated diagram.
net-diagram-v2.JPG
0
 
LVL 50

Expert Comment

by:Don Johnston
ID: 39724758
Please post the output of a "sh ip route" from the three 3560's.
0
 
LVL 1

Author Comment

by:leblanc
ID: 39724997
BEFORE SHUTDOWN OF INTERFACE BETWEEN CORE1 & 3560

3560x#sh ip ro

Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP

       D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area

       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2

       E1 - OSPF external type 1, E2 - OSPF external type 2

       i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2

       ia - IS-IS inter area, * - candidate default, U - per-user static route

       o - ODR, P - periodic downloaded static route

 

Gateway of last resort is 192.168.16.10 to network 0.0.0.0

 

     192.168.254.0/32 is subnetted, 1 subnets

C       192.168.254.254 is directly connected, Loopback0

D    192.168.50.0/24 [90/284160] via 192.168.16.6, 00:15:25, Ethernet1/1

                     [90/284160] via 192.168.16.2, 00:15:25, Ethernet1/0

     192.168.16.0/30 is subnetted, 3 subnets

C       192.168.16.8 is directly connected, Ethernet1/2

C       192.168.16.0 is directly connected, Ethernet1/0

C       192.168.16.4 is directly connected, Ethernet1/1

D    192.168.1.0/24 [90/284160] via 192.168.16.6, 00:15:27, Ethernet1/1

                    [90/284160] via 192.168.16.2, 00:15:27, Ethernet1/0

D    192.168.19.0/24 [90/284160] via 192.168.16.6, 00:15:27, Ethernet1/1

                     [90/284160] via 192.168.16.2, 00:15:27, Ethernet1/0

S*   0.0.0.0/0 [1/0] via 192.168.16.10

 

3560x#sh ip eigrp topo

IP-EIGRP Topology Table for AS(1)/ID(192.168.254.254)

Codes: P - Passive, A - Active, U - Update, Q - Query, R - Reply,

       r - reply Status, s - sia Status

 

P 0.0.0.0/0, 1 successors, FD is 281600

        via Rstatic (281600/0)

P 192.168.50.0/24, 2 successors, FD is 284160

        via 192.168.16.2 (284160/28160), Ethernet1/0

        via 192.168.16.6 (284160/28160), Ethernet1/1

P 192.168.1.0/24, 2 successors, FD is 284160

        via 192.168.16.2 (284160/28160), Ethernet1/0

        via 192.168.16.6 (284160/28160), Ethernet1/1

P 192.168.16.8/30, 1 successors, FD is 281600

        via Connected, Ethernet1/2

P 192.168.16.0/30, 1 successors, FD is 281600

        via Connected, Ethernet1/0

P 192.168.19.0/24, 2 successors, FD is 284160

        via 192.168.16.2 (284160/28160), Ethernet1/0

        via 192.168.16.6 (284160/28160), Ethernet1/1

P 192.168.16.4/30, 1 successors, FD is 281600

        via Connected, Ethernet1/1

 

3560x#sh ip ro

Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP

       D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area

       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2

       E1 - OSPF external type 1, E2 - OSPF external type 2

       i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2

       ia - IS-IS inter area, * - candidate default, U - per-user static route

       o - ODR, P - periodic downloaded static route

 

Gateway of last resort is 192.168.16.10 to network 0.0.0.0

 

     192.168.254.0/32 is subnetted, 1 subnets

C       192.168.254.254 is directly connected, Loopback0

D    192.168.50.0/24 [90/284160] via 192.168.16.6, 00:19:23, Ethernet1/1

                     [90/284160] via 192.168.16.2, 00:19:23, Ethernet1/0

     192.168.16.0/30 is subnetted, 3 subnets

C       192.168.16.8 is directly connected, Ethernet1/2

C       192.168.16.0 is directly connected, Ethernet1/0

C       192.168.16.4 is directly connected, Ethernet1/1

D    192.168.1.0/24 [90/284160] via 192.168.16.6, 00:19:26, Ethernet1/1

                    [90/284160] via 192.168.16.2, 00:19:26, Ethernet1/0

D    192.168.19.0/24 [90/284160] via 192.168.16.6, 00:19:26, Ethernet1/1

                     [90/284160] via 192.168.16.2, 00:19:26, Ethernet1/0

S*   0.0.0.0/0 [1/0] via 192.168.16.10

 

 

 

 

 

3750core1#sh ip ro

Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP

       D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area

       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2

       E1 - OSPF external type 1, E2 - OSPF external type 2

       i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2

       ia - IS-IS inter area, * - candidate default, U - per-user static route

       o - ODR, P - periodic downloaded static route

 

Gateway of last resort is 192.168.16.1 to network 0.0.0.0

 

C    192.168.50.0/24 is directly connected, Vlan25

     192.168.16.0/30 is subnetted, 3 subnets

D       192.168.16.8 [90/307200] via 192.168.16.1, 00:18:56, Ethernet2/0

C       192.168.16.0 is directly connected, Ethernet2/0

D       192.168.16.4 [90/307200] via 192.168.16.1, 00:18:31, Ethernet2/0

C    192.168.1.0/24 is directly connected, Vlan10

C    192.168.19.0/24 is directly connected, Vlan200

D*EX 0.0.0.0/0 [170/307200] via 192.168.16.1, 00:

 

3750core1#sh ip eigrp topo

IP-EIGRP Topology Table for AS(1)/ID(192.168.50.2)

Codes: P - Passive, A - Active, U - Update, Q - Query, R - Reply,

       r - reply Status, s - sia Status

 

P 0.0.0.0/0, 1 successors, FD is 307200

        via 192.168.16.1 (307200/281600), Ethernet2/0

P 192.168.50.0/24, 1 successors, FD is 28160

        via Connected, Vlan25

P 192.168.1.0/24, 1 successors, FD is 28160

        via Connected, Vlan10

P 192.168.16.8/30, 1 successors, FD is 307200

        via 192.168.16.1 (307200/281600), Ethernet2/0

P 192.168.16.0/30, 1 successors, FD is 281600

        via Connected, Ethernet2/0

P 192.168.19.0/24, 1 successors, FD is 28160

        via Connected, Vlan200

P 192.168.16.4/30, 1 successors, FD is 307200

        via 192.168.16.1 (307200/281600), Ethernet2/0

 

3750core1#sh ip ro

Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP

       D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area

       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2

       E1 - OSPF external type 1, E2 - OSPF external type 2

       i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2

       ia - IS-IS inter area, * - candidate default, U - per-user static route

       o - ODR, P - periodic downloaded static route

 

Gateway of last resort is 192.168.16.1 to network 0.0.0.0

 

C    192.168.50.0/24 is directly connected, Vlan25

     192.168.16.0/30 is subnetted, 3 subnets

D       192.168.16.8 [90/307200] via 192.168.16.1, 00:19:32, Ethernet2/0

C       192.168.16.0 is directly connected, Ethernet2/0

D       192.168.16.4 [90/307200] via 192.168.16.1, 00:19:07, Ethernet2/0

C    192.168.1.0/24 is directly connected, Vlan10

C    192.168.19.0/24 is directly connected, Vlan200

D*EX 0.0.0.0/0 [170/307200] via 192.168.16.1, 00:19:32, Ethernet2/0

----------------------------------------------------

AFTER SHUTDOWN OF INTERFACE BETWEEN CORE1 & 3560

3750core1#sh ip ro

Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP

       D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area

       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2

       E1 - OSPF external type 1, E2 - OSPF external type 2

       i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2

       ia - IS-IS inter area, * - candidate default, U - per-user static route

       o - ODR, P - periodic downloaded static route

 

Gateway of last resort is not set

 

C    192.168.50.0/24 is directly connected, Vlan25

C    192.168.1.0/24 is directly connected, Vlan10

C    192.168.19.0/24 is directly connected, Vlan200

--------------

3750core1#sh ip eigrp topo

IP-EIGRP Topology Table for AS(1)/ID(192.168.50.2)

Codes: P - Passive, A - Active, U - Update, Q - Query, R - Reply,

       r - reply Status, s - sia Status

 

P 192.168.50.0/24, 1 successors, FD is 28160

        via Connected, Vlan25

P 192.168.1.0/24, 1 successors, FD is 28160

        via Connected, Vlan10

P 192.168.16.0/30, 1 successors, FD is 281600

        via Connected, Ethernet2/0

P 192.168.19.0/24, 1 successors, FD is 28160

        via Connected, Vlan200

---------

3560x#sh ip ro ei

D    192.168.50.0/24 [90/284160] via 192.168.16.6, 00:02:07, Ethernet1/1

D    192.168.1.0/24 [90/284160] via 192.168.16.6, 00:02:07, Ethernet1/1

D    192.168.19.0/24 [90/284160] via 192.168.16.6, 00:02:07, Ethernet1/1

-------------

3560x#sh ip eigrp topo

IP-EIGRP Topology Table for AS(1)/ID(192.168.254.254)

Codes: P - Passive, A - Active, U - Update, Q - Query, R - Reply,

       r - reply Status, s - sia Status

 

P 0.0.0.0/0, 1 successors, FD is 281600

        via Rstatic (281600/0)

P 192.168.50.0/24, 1 successors, FD is 284160

        via 192.168.16.6 (284160/28160), Ethernet1/1

P 192.168.1.0/24, 1 successors, FD is 284160

        via 192.168.16.6 (284160/28160), Ethernet1/1

P 192.168.16.8/30, 1 successors, FD is 281600

        via Connected, Ethernet1/2

P 192.168.16.0/30, 1 successors, FD is 281600

        via Connected, Ethernet1/0

P 192.168.19.0/24, 1 successors, FD is 284160

        via 192.168.16.6 (284160/28160), Ethernet1/1

P 192.168.16.4/30, 1 successors, FD is 281600

        via Connected, Ethernet1/1

-----------

 

3750core2#sh ip ro eigrp

     192.168.16.0/30 is subnetted, 3 subnets

D       192.168.16.8 [90/307200] via 192.168.16.5, 00:28:38, Ethernet2/0

D       192.168.16.0 [90/307200] via 192.168.16.5, 00:28:11, Ethernet2/0

D*EX 0.0.0.0/0 [170/307200] via 192.168.16.5, 00:28:38, Ethernet2/0

----------

3750core2#sh ip eigrp topo

IP-EIGRP Topology Table for AS(1)/ID(192.168.50.3)

Codes: P - Passive, A - Active, U - Update, Q - Query, R - Reply,

       r - reply Status, s - sia Status

 

P 0.0.0.0/0, 1 successors, FD is 307200

        via 192.168.16.5 (307200/281600), Ethernet2/0

P 192.168.50.0/24, 1 successors, FD is 28160

        via Connected, Vlan25

P 192.168.1.0/24, 1 successors, FD is 28160

        via Connected, Vlan10

P 192.168.16.8/30, 1 successors, FD is 307200

        via 192.168.16.5 (307200/281600), Ethernet2/0

P 192.168.16.0/30, 1 successors, FD is 307200

        via 192.168.16.5 (307200/281600), Ethernet2/0

P 192.168.19.0/24, 1 successors, FD is 28160

        via Connected, Vlan200

P 192.168.16.4/30, 1 successors, FD is 281600

        via Connected, Ethernet2/0
0
 
LVL 50

Expert Comment

by:Don Johnston
ID: 39725003
In the future, please use the code feature when posting output.
0
 
LVL 50

Expert Comment

by:Don Johnston
ID: 39725030
I didn't see the routing table of Core2 before shutting down the 3560-Core1 link.

According to this:

3750core2#sh ip ro eigrp
     192.168.16.0/30 is subnetted, 3 subnets
D       192.168.16.8 [90/307200] via 192.168.16.5, 00:28:38, Ethernet2/0
D       192.168.16.0 [90/307200] via 192.168.16.5, 00:28:11, Ethernet2/0
D*EX 0.0.0.0/0 [170/307200] via 192.168.16.5, 00:28:38, Ethernet2/0

Open in new window

Core2 is not connected to the 192.168.1.0/24 network even though the topology table says it is.

Are these real switches or is this packet tracer???
0
 
LVL 1

Author Comment

by:leblanc
ID: 39725528
This is GNS3.
The only connection between core1 and core2 is a trunk.
0
 
LVL 50

Expert Comment

by:Don Johnston
ID: 39725541
The only connection between core1 and core2 is a trunk.

I didn't ask about that. (and it's not relevant). What is relevant is that Core2 must have a connection to the 192.168.1.0 network. Need to see the routing table for Core2 when everything is up.

And GNS3 is a router emulator. The 3560 is a switch. Unless something has changed, GNS simulates switches. Which means that they may not accurately reflect the actual behavior of the device.
0
 
LVL 1

Author Comment

by:leblanc
ID: 39725655
3750core2#sh ip route
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
       D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
       E1 - OSPF external type 1, E2 - OSPF external type 2
       i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
       ia - IS-IS inter area, * - candidate default, U - per-user static route
       o - ODR, P - periodic downloaded static route

Gateway of last resort is 192.168.16.5 to network 0.0.0.0

C    192.168.50.0/24 is directly connected, Vlan25
     192.168.16.0/30 is subnetted, 3 subnets
D       192.168.16.8 [90/307200] via 192.168.16.5, 00:06:59, Ethernet2/0
D       192.168.16.0 [90/307200] via 192.168.16.5, 00:06:41, Ethernet2/0
C       192.168.16.4 is directly connected, Ethernet2/0
C    192.168.1.0/24 is directly connected, Vlan10
C    192.168.19.0/24 is directly connected, Vlan200
D*EX 0.0.0.0/0 [170/307200] via 192.168.16.5, 00:06:58, Ethernet2/0

Open in new window


Yes. I name it 3560 but it is actually a router in GNS3. See attached for the net diagram in GNS3. The diagram before was made in Packet Tracer from my friend and I don't have Packet Tracer. So I rebuilt the lab in GNS3
net-diagram-gns3.JPG
0
 
LVL 50

Expert Comment

by:Don Johnston
ID: 39725707
The 192.168.1.0 network is in the routing table of Core2 when everything is up but it's not there when the link between the 3560 and Core1 is disabled.  Curious...

Shut the 3560-Core1 link down, wait 3 minutes and then show the routing tables of the three devices and post the output please.
0
Why You Should Analyze Threat Actor TTPs

After years of analyzing threat actor behavior, it’s become clear that at any given time there are specific tactics, techniques, and procedures (TTPs) that are particularly prevalent. By analyzing and understanding these TTPs, you can dramatically enhance your security program.

 
LVL 1

Author Comment

by:leblanc
ID: 39727559
3750core1(config-if)#do sh ip route
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
       D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
       E1 - OSPF external type 1, E2 - OSPF external type 2
       i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
       ia - IS-IS inter area, * - candidate default, U - per-user static route
       o - ODR, P - periodic downloaded static route

Gateway of last resort is not set

C    192.168.50.0/24 is directly connected, Vlan25
C    192.168.1.0/24 is directly connected, Vlan10
C    192.168.19.0/24 is directly connected, Vlan200

3750core2#sh ip ro
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
       D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
       E1 - OSPF external type 1, E2 - OSPF external type 2
       i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
       ia - IS-IS inter area, * - candidate default, U - per-user static route
       o - ODR, P - periodic downloaded static route

Gateway of last resort is 192.168.16.5 to network 0.0.0.0

C    192.168.50.0/24 is directly connected, Vlan25
     192.168.16.0/30 is subnetted, 3 subnets
D       192.168.16.8 [90/307200] via 192.168.16.5, 16:31:37, Ethernet2/0
D       192.168.16.0 [90/307200] via 192.168.16.5, 16:31:20, Ethernet2/0
C       192.168.16.4 is directly connected, Ethernet2/0
C    192.168.1.0/24 is directly connected, Vlan10
C    192.168.19.0/24 is directly connected, Vlan200
D*EX 0.0.0.0/0 [170/307200] via 192.168.16.5, 16:31:37, Ethernet2/0

3560x#sh ip ro
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
       D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
       E1 - OSPF external type 1, E2 - OSPF external type 2
       i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
       ia - IS-IS inter area, * - candidate default, U - per-user static route
       o - ODR, P - periodic downloaded static route

Gateway of last resort is 192.168.16.10 to network 0.0.0.0

     192.168.254.0/32 is subnetted, 1 subnets
C       192.168.254.254 is directly connected, Loopback0
D    192.168.50.0/24 [90/284160] via 192.168.16.6, 02:35:20, Ethernet1/1
     192.168.16.0/30 is subnetted, 3 subnets
C       192.168.16.8 is directly connected, Ethernet1/2
C       192.168.16.0 is directly connected, Ethernet1/0
C       192.168.16.4 is directly connected, Ethernet1/1
D    192.168.1.0/24 [90/284160] via 192.168.16.6, 02:35:20, Ethernet1/1
D    192.168.19.0/24 [90/284160] via 192.168.16.6, 02:35:22, Ethernet1/1
S*   0.0.0.0/0 [1/0] via 192.168.16.10

Open in new window

0
 
LVL 50

Expert Comment

by:Don Johnston
ID: 39733802
Looks like it's working fine. Did you change something?
0
 
LVL 1

Author Comment

by:leblanc
ID: 39734201
It did not work.
0
 
LVL 50

Expert Comment

by:Don Johnston
ID: 39734235
Okay... You say that EIGRP is not working properly.

With the 3560-Core1 link down, the routing table of the 3560 looks like this:
     192.168.254.0/32 is subnetted, 1 subnets
C       192.168.254.254 is directly connected, Loopback0
D    192.168.50.0/24 [90/284160] via 192.168.16.6, 02:35:20, Ethernet1/1
     192.168.16.0/30 is subnetted, 3 subnets
C       192.168.16.8 is directly connected, Ethernet1/2
C       192.168.16.0 is directly connected, Ethernet1/0
C       192.168.16.4 is directly connected, Ethernet1/1
D    192.168.1.0/24 [90/284160] via 192.168.16.6, 02:35:20, Ethernet1/1  <----------
D    192.168.19.0/24 [90/284160] via 192.168.16.6, 02:35:22, Ethernet1/1
S*   0.0.0.0/0 [1/0] via 192.168.16.10

Open in new window

Forwarding 192.168.1.0 traffic to Core2.

The Core2 routing table looks like this:
C    192.168.50.0/24 is directly connected, Vlan25
     192.168.16.0/30 is subnetted, 3 subnets
D       192.168.16.8 [90/307200] via 192.168.16.5, 16:31:37, Ethernet2/0
D       192.168.16.0 [90/307200] via 192.168.16.5, 16:31:20, Ethernet2/0
C       192.168.16.4 is directly connected, Ethernet2/0
C    192.168.1.0/24 is directly connected, Vlan10  <-------------------
C    192.168.19.0/24 is directly connected, Vlan200
D*EX 0.0.0.0/0 [170/307200] via 192.168.16.5, 16:31:37, Ethernet2/0

Open in new window

Directly connected to 192.168.1.0 network through the VLAN10 interface like it does when everything is working.

 So why are you saying EIGRP is not working properly? If you are unable to get traffic from the 3560 to the 192.168.1.0 network, I think there is something else not working. Maybe VLAN10 is not correctly configured on the Core2 router?
0
 
LVL 1

Author Comment

by:leblanc
ID: 39736251
This is what I did. I did a continuous ping from the fw to 192.168.1.100. The I shut down e2/0 on core1. The fw could not longer ping 192.168.1.100. Looking at the routing table, it has the correct routes. But it looks like EIGRP did not route the packets to core2 as it should. That is what I am trying to understand.
0
 
LVL 50

Expert Comment

by:Don Johnston
ID: 39736349
If the traffic is not getting to the destination and there is a route to the network in the routing table, then it's not a routing protocol problem. Could be an ACL, could be an asymmetric routing issue.

With everything working, do a traceroute and determine the path being taken. You should be both routes in use.
0
 
LVL 1

Accepted Solution

by:
leblanc earned 0 total points
ID: 39736371
traceroute from 3560X shows that it is taking the correct path (192.168.16.6) to 192.168.1.100. But it just dies at core2.

I just found out that there were some passive-interface vlan10 in eigrp. That is why it could not communicate with 192.168.1.100 because eigrp was not advertise on vlan10. Go figure.

Thanks for your inputs.
0
 
LVL 50

Assisted Solution

by:Don Johnston
Don Johnston earned 500 total points
ID: 39736615
That would only prevent EIGRP from forming neighbor relationships with routers on the VLAN10 interface.   Based on your diagram, it appears that switch1 is a layer-2 switch.

But the GW is for PC-PT is showing as 192.168.1.1... which isn't anywhere on the diagram.  

So that may have something to do with your problem.
0
 
LVL 1

Author Comment

by:leblanc
ID: 39736832
switch1 is a layer2 switch.
192.168.1.1 is the virtual IP address for hsrp implemented in core1 and core2.
When I removed the passive commands in EIGRP, the ping starts working again. So you are saying that it is not the passive commands that causes the ping to fail. Correct?
0
 
LVL 50

Expert Comment

by:Don Johnston
ID: 39737024
And this is the problem with troubleshooting when you only get a small part of the picture. :-)

Having the VLAN10 interface passive would be a standard approach. Why that allows it to work is hard to say without seeing the configs of all the devices and having an accurate topology diagram.
0
 
LVL 1

Author Closing Comment

by:leblanc
ID: 39774520
Shutdown passive interface seems to fix the issue.
0

Featured Post

Why You Should Analyze Threat Actor TTPs

After years of analyzing threat actor behavior, it’s become clear that at any given time there are specific tactics, techniques, and procedures (TTPs) that are particularly prevalent. By analyzing and understanding these TTPs, you can dramatically enhance your security program.

Join & Write a Comment

Suggested Solutions

Short answer to this question: there is no effective WiFi manager in iOS devices as seen in Windows WiFi or Macbook OSx WiFi management, but this article will try and provide some amicable solutions to better suite your needs.
When it comes to security, there are always trade-offs between security and convenience/ease of administration. This article examines some of the main pros and cons of using key authentication vs password authentication for hosting an SFTP server.
Get a first impression of how PRTG looks and learn how it works.   This video is a short introduction to PRTG, as an initial overview or as a quick start for new PRTG users.
This video gives you a great overview about bandwidth monitoring with SNMP and WMI with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're looking for how to monitor bandwidth using netflow or packet s…

743 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

15 Experts available now in Live!

Get 1:1 Help Now