I was reading about traffic shaping & policing and the acronyms in the book they were as clear as mud, but now Ive written them down and understand them they are really really simple. I put a few formulas on for them aswell, but havnt checked them so please correct me if im wrong, oh and I have presumed that you are attempting to traffic shape to the CIR.
Tc – This is a time interval in milliseconds when a Committed Burst (Bc) can get sent. Usually Tc = Bc / CIR
Bc – Committed Burst this is the amount of data in bits which can bet sent every Tc. Usually Bc = CIR / Tc
Be – Excess Burst is the number of bits the Bc can be exceed by if no data has been sent if no data has been sent in previous Tcs. EDIT: As commented by Jeriel Atienza the formula is Be = (Ar – CIR) * Tc/1000
CIR – Committed Information Rate this is the bandwidth of a link or VC in bps which the Service Provider guarantees to provide. Quite often the CIR is lower than the full capabilities of a link which is the main reason why traffic should be shaped & policed. CIR = Bc * Tc
Shaped Rate – This is the rate of the traffic which is being shaped in bps, it normally matches the CIR. Usually CIR = Shaped Rate!
Tuesday, November 10, 2009
Monday, November 9, 2009
Wednesday, November 4, 2009
Another Proposed Solution for Static Route Over FR issue
Hello Everyone,
Here is an another proposed solution by me for my previous Static Routes over FR issue post. I was just trying to grab someone GRE concepts so I thought to lab up that scenario again and try to fix it with GRE keepalives this time. Although you might see different ip addressing this time, but I have attached "sh ip int b" output to simplify that for you.
Just as a side note - GRE keepalives can be enabled on one side and it will work fine. It's not like serial or Ethernet keepalives which are to be enabled on both sides.
http://deepakarora1984.blogspot.com/2008/12/static-route-issue-over-frame-relay.html
R1
---
R1(config)#do term len 0
R1(config)#do sh run
Building configuration...
Current configuration : 1171 bytes
!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname R1
!
boot-start-marker
boot-end-marker
!
!
no aaa new-model
memory-size iomem 5
!
!
no ip cef
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
interface Loopback1
ip address 100.100.100.1 255.255.255.0
!
interface Tunnel0
ip address 150.0.0.1 255.0.0.0
keepalive 1 3
tunnel source Serial0/0
tunnel destination 1.1.1.1
!
interface Serial0/0
ip address 1.1.1.0 255.255.255.254
encapsulation frame-relay
serial restart-delay 0
!
interface Serial0/1
ip address 2.2.2.0 255.255.255.254
serial restart-delay 0
!
interface Serial0/2
no ip address
shutdown
serial restart-delay 0
!
interface Serial0/3
no ip address
shutdown
serial restart-delay 0
!
ip http server
ip forward-protocol nd
ip route 3.3.3.0 255.255.255.0 2.2.2.1
ip route 200.200.200.0 255.255.255.0 150.0.0.2
ip route 200.200.200.0 255.255.255.0 2.2.2.1 10
!
!
!
access-list 101 permit ip 150.0.0.0 0.255.255.255 200.0.0.0 0.255.255.255
!
!
!
control-plane
!
!
!
!
!
!
!
!
!
line con 0
line aux 0
line vty 0 4
!
!
end
R1(config)#
R1(config)#do sh ip int b
Interface IP-Address OK? Method Status Prot
ocol
Serial0/0 1.1.1.0 YES manual up up
Serial0/1 2.2.2.0 YES manual up up
Serial0/2 unassigned YES unset administratively down down
Serial0/3 unassigned YES unset administratively down down
Loopback0 10.0.0.1 YES manual up up
Loopback1 100.100.100.1 YES manual up up
Tunnel0 150.0.0.1 YES manual up up
R1(config)#
R1(config)#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
S 200.200.200.0/24 [1/0] via 150.0.0.2
1.0.0.0/31 is subnetted, 1 subnets
C 1.1.1.0 is directly connected, Serial0/0
2.0.0.0/31 is subnetted, 1 subnets
C 2.2.2.0 is directly connected, Serial0/1
100.0.0.0/24 is subnetted, 1 subnets
C 100.100.100.0 is directly connected, Loopback1
3.0.0.0/24 is subnetted, 1 subnets
S 3.3.3.0 [1/0] via 2.2.2.1
10.0.0.0/24 is subnetted, 1 subnets
C 10.0.0.0 is directly connected, Loopback0
C 150.0.0.0/8 is directly connected, Tunnel0
R1(config)#
---------------------------------------------------
R2
---
R2(config)#do term len 0
R2(config)#do sh run
Building configuration...
Current configuration : 1097 bytes
!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname R2
!
boot-start-marker
boot-end-marker
!
!
no aaa new-model
memory-size iomem 5
!
!
no ip cef
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
interface Loopback1
ip address 200.200.200.1 255.255.255.0
!
interface Tunnel0
ip address 150.0.0.2 255.0.0.0
keepalive 1 3
tunnel source Serial0/0
tunnel destination 1.1.1.0
!
interface Serial0/0
ip address 1.1.1.1 255.255.255.254
encapsulation frame-relay
serial restart-delay 0
!
interface Serial0/1
ip address 3.3.3.1 255.255.255.254
serial restart-delay 0
!
interface Serial0/2
no ip address
shutdown
serial restart-delay 0
!
interface Serial0/3
no ip address
shutdown
serial restart-delay 0
!
ip http server
ip forward-protocol nd
ip route 2.2.2.0 255.255.255.0 3.3.3.0
ip route 100.100.100.0 255.255.255.0 150.0.0.1
ip route 100.100.100.0 255.255.255.0 3.3.3.0 10
!
!
!
!
!
!
control-plane
!
!
!
!
!
!
!
!
!
line con 0
line aux 0
line vty 0 4
!
!
end
R2(config)#
R2(config)#do sh ip int brief
Interface IP-Address OK? Method Status Prot
ocol
Serial0/0 1.1.1.1 YES manual up up
Serial0/1 3.3.3.1 YES manual up up
Serial0/2 unassigned YES unset administratively down down
Serial0/3 unassigned YES unset administratively down down
Loopback0 20.0.0.1 YES manual up up
Loopback1 200.200.200.1 YES manual up up
Tunnel0 150.0.0.2 YES manual up up
R2(config)#
R2(config)#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 200.200.200.0/24 is directly connected, Loopback1
1.0.0.0/31 is subnetted, 1 subnets
C 1.1.1.0 is directly connected, Serial0/0
2.0.0.0/24 is subnetted, 1 subnets
S 2.2.2.0 [1/0] via 3.3.3.0
100.0.0.0/24 is subnetted, 1 subnets
S 100.100.100.0 [1/0] via 150.0.0.1
3.0.0.0/31 is subnetted, 1 subnets
C 3.3.3.0 is directly connected, Serial0/1
20.0.0.0/24 is subnetted, 1 subnets
C 20.0.0.0 is directly connected, Loopback0
C 150.0.0.0/8 is directly connected, Tunnel0
R2(config)#
-----------------------------------------------------------------
R3
---
R3#term len 0
R3#sh run
Building configuration...
Current configuration : 825 bytes
!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname R3
!
boot-start-marker
boot-end-marker
!
!
no aaa new-model
memory-size iomem 5
!
!
no ip cef
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
interface Serial0/0
ip address 2.2.2.1 255.255.255.254
no ip route-cache
serial restart-delay 0
!
interface Serial0/1
ip address 3.3.3.0 255.255.255.254
no ip route-cache
serial restart-delay 0
!
interface Serial0/2
no ip address
shutdown
serial restart-delay 0
!
interface Serial0/3
no ip address
shutdown
serial restart-delay 0
!
ip http server
ip forward-protocol nd
ip route 100.100.100.0 255.255.255.0 2.2.2.0
ip route 200.200.200.0 255.255.255.0 3.3.3.1
!
!
!
!
!
!
control-plane
!
!
!
!
!
!
!
!
!
line con 0
line aux 0
line vty 0 4
!
!
end
R3#
R3#sh ip int brief
Interface IP-Address OK? Method Status Prot
ocol
Serial0/0 2.2.2.1 YES manual up up
Serial0/1 3.3.3.0 YES manual up up
Serial0/2 unassigned YES unset administratively down down
Serial0/3 unassigned YES unset administratively down down
R3#
R3#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
S 200.200.200.0/24 [1/0] via 3.3.3.1
2.0.0.0/31 is subnetted, 1 subnets
C 2.2.2.0 is directly connected, Serial0/0
100.0.0.0/24 is subnetted, 1 subnets
S 100.100.100.0 [1/0] via 2.2.2.0
3.0.0.0/31 is subnetted, 1 subnets
C 3.3.3.0 is directly connected, Serial0/1
R3#
Here is an another proposed solution by me for my previous Static Routes over FR issue post. I was just trying to grab someone GRE concepts so I thought to lab up that scenario again and try to fix it with GRE keepalives this time. Although you might see different ip addressing this time, but I have attached "sh ip int b" output to simplify that for you.
Just as a side note - GRE keepalives can be enabled on one side and it will work fine. It's not like serial or Ethernet keepalives which are to be enabled on both sides.
http://deepakarora1984.blogspot.com/2008/12/static-route-issue-over-frame-relay.html
---
R1(config)#do term len 0
R1(config)#do sh run
Building configuration...
Current configuration : 1171 bytes
!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname R1
!
boot-start-marker
boot-end-marker
!
!
no aaa new-model
memory-size iomem 5
!
!
no ip cef
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
interface Loopback1
ip address 100.100.100.1 255.255.255.0
!
interface Tunnel0
ip address 150.0.0.1 255.0.0.0
keepalive 1 3
tunnel source Serial0/0
tunnel destination 1.1.1.1
!
interface Serial0/0
ip address 1.1.1.0 255.255.255.254
encapsulation frame-relay
serial restart-delay 0
!
interface Serial0/1
ip address 2.2.2.0 255.255.255.254
serial restart-delay 0
!
interface Serial0/2
no ip address
shutdown
serial restart-delay 0
!
interface Serial0/3
no ip address
shutdown
serial restart-delay 0
!
ip http server
ip forward-protocol nd
ip route 3.3.3.0 255.255.255.0 2.2.2.1
ip route 200.200.200.0 255.255.255.0 150.0.0.2
ip route 200.200.200.0 255.255.255.0 2.2.2.1 10
!
!
!
access-list 101 permit ip 150.0.0.0 0.255.255.255 200.0.0.0 0.255.255.255
!
!
!
control-plane
!
!
!
!
!
!
!
!
!
line con 0
line aux 0
line vty 0 4
!
!
end
R1(config)#
R1(config)#do sh ip int b
Interface IP-Address OK? Method Status Prot
ocol
Serial0/0 1.1.1.0 YES manual up up
Serial0/1 2.2.2.0 YES manual up up
Serial0/2 unassigned YES unset administratively down down
Serial0/3 unassigned YES unset administratively down down
Loopback0 10.0.0.1 YES manual up up
Loopback1 100.100.100.1 YES manual up up
Tunnel0 150.0.0.1 YES manual up up
R1(config)#
R1(config)#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
S 200.200.200.0/24 [1/0] via 150.0.0.2
1.0.0.0/31 is subnetted, 1 subnets
C 1.1.1.0 is directly connected, Serial0/0
2.0.0.0/31 is subnetted, 1 subnets
C 2.2.2.0 is directly connected, Serial0/1
100.0.0.0/24 is subnetted, 1 subnets
C 100.100.100.0 is directly connected, Loopback1
3.0.0.0/24 is subnetted, 1 subnets
S 3.3.3.0 [1/0] via 2.2.2.1
10.0.0.0/24 is subnetted, 1 subnets
C 10.0.0.0 is directly connected, Loopback0
C 150.0.0.0/8 is directly connected, Tunnel0
R1(config)#
---------------------------------------------------
R2
---
R2(config)#do term len 0
R2(config)#do sh run
Building configuration...
Current configuration : 1097 bytes
!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname R2
!
boot-start-marker
boot-end-marker
!
!
no aaa new-model
memory-size iomem 5
!
!
no ip cef
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
interface Loopback1
ip address 200.200.200.1 255.255.255.0
!
interface Tunnel0
ip address 150.0.0.2 255.0.0.0
keepalive 1 3
tunnel source Serial0/0
tunnel destination 1.1.1.0
!
interface Serial0/0
ip address 1.1.1.1 255.255.255.254
encapsulation frame-relay
serial restart-delay 0
!
interface Serial0/1
ip address 3.3.3.1 255.255.255.254
serial restart-delay 0
!
interface Serial0/2
no ip address
shutdown
serial restart-delay 0
!
interface Serial0/3
no ip address
shutdown
serial restart-delay 0
!
ip http server
ip forward-protocol nd
ip route 2.2.2.0 255.255.255.0 3.3.3.0
ip route 100.100.100.0 255.255.255.0 150.0.0.1
ip route 100.100.100.0 255.255.255.0 3.3.3.0 10
!
!
!
!
!
!
control-plane
!
!
!
!
!
!
!
!
!
line con 0
line aux 0
line vty 0 4
!
!
end
R2(config)#
R2(config)#do sh ip int brief
Interface IP-Address OK? Method Status Prot
ocol
Serial0/0 1.1.1.1 YES manual up up
Serial0/1 3.3.3.1 YES manual up up
Serial0/2 unassigned YES unset administratively down down
Serial0/3 unassigned YES unset administratively down down
Loopback0 20.0.0.1 YES manual up up
Loopback1 200.200.200.1 YES manual up up
Tunnel0 150.0.0.2 YES manual up up
R2(config)#
R2(config)#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 200.200.200.0/24 is directly connected, Loopback1
1.0.0.0/31 is subnetted, 1 subnets
C 1.1.1.0 is directly connected, Serial0/0
2.0.0.0/24 is subnetted, 1 subnets
S 2.2.2.0 [1/0] via 3.3.3.0
100.0.0.0/24 is subnetted, 1 subnets
S 100.100.100.0 [1/0] via 150.0.0.1
3.0.0.0/31 is subnetted, 1 subnets
C 3.3.3.0 is directly connected, Serial0/1
20.0.0.0/24 is subnetted, 1 subnets
C 20.0.0.0 is directly connected, Loopback0
C 150.0.0.0/8 is directly connected, Tunnel0
R2(config)#
-----------------------------------------------------------------
R3
---
R3#term len 0
R3#sh run
Building configuration...
Current configuration : 825 bytes
!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname R3
!
boot-start-marker
boot-end-marker
!
!
no aaa new-model
memory-size iomem 5
!
!
no ip cef
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
interface Serial0/0
ip address 2.2.2.1 255.255.255.254
no ip route-cache
serial restart-delay 0
!
interface Serial0/1
ip address 3.3.3.0 255.255.255.254
no ip route-cache
serial restart-delay 0
!
interface Serial0/2
no ip address
shutdown
serial restart-delay 0
!
interface Serial0/3
no ip address
shutdown
serial restart-delay 0
!
ip http server
ip forward-protocol nd
ip route 100.100.100.0 255.255.255.0 2.2.2.0
ip route 200.200.200.0 255.255.255.0 3.3.3.1
!
!
!
!
!
!
control-plane
!
!
!
!
!
!
!
!
!
line con 0
line aux 0
line vty 0 4
!
!
end
R3#
R3#sh ip int brief
Interface IP-Address OK? Method Status Prot
ocol
Serial0/0 2.2.2.1 YES manual up up
Serial0/1 3.3.3.0 YES manual up up
Serial0/2 unassigned YES unset administratively down down
Serial0/3 unassigned YES unset administratively down down
R3#
R3#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
S 200.200.200.0/24 [1/0] via 3.3.3.1
2.0.0.0/31 is subnetted, 1 subnets
C 2.2.2.0 is directly connected, Serial0/0
100.0.0.0/24 is subnetted, 1 subnets
S 100.100.100.0 [1/0] via 2.2.2.0
3.0.0.0/31 is subnetted, 1 subnets
C 3.3.3.0 is directly connected, Serial0/1
R3#
Wednesday, October 21, 2009
Incase You Want To Verify That Some Website Is Really Down Or It's Unreachable From You Network - Cool Tool To Verify This
Friday, October 16, 2009
Frame Relay LMI - In General
Frame Relay Local Management Interface (LMI) is a set of enchantments to frame relay, originally agreed upon in 1990 by a consortium consisting of Cisco, Digital Equipment Corporation (DEC), Northern Telecom, and StrataCom. Eventually ANSI and CCITT came along created standard versions but most vendors support both standard version alongside the one defined by the consortium.
There are very few differences between them, mainly Cisco LMI type use the DLCI of 1023 and also DLCI number between 16 and 1007 for usable DLCI number and the ANSI & ITU(q933a) standard use a DLCI of 0 and usable DLCI numbers between 16 and 976. The LMI type can be changed on the frame relay enabled interface with the command;
- Inverse ARP – to find out the layer 3 address of device on the other end of the DLCI so you dont need to static map it or similar
- Signalling of Virtual Circuit status messages, therefore if a PVC becomes unreachable all nodes along its path can be aware of this failure so data can be prevented from being sent to indirect failures.
- Multicasting – This extension allows multicast groups to be used over frame relay networks, the higher DLCI numbers reserved by the LMI type are used for this
- Globally signficiant DLCIs – Brilliant!
- Retro flow control with XON/XOFF if the applications using the Frame Relay network know understand FECNs and BECNs
By default LMI messages are sent every 10 seconds, and every sixth message a full status message will be sent which contains more detailed information about each VC, the interface will fail if the interfaces does not receive an LMI message 3 times the hello time, so 30 seconds. You cant actually turn off LMI but you can disable the keepalives with the highly ambiguous command;
There are very few differences between them, mainly Cisco LMI type use the DLCI of 1023 and also DLCI number between 16 and 1007 for usable DLCI number and the ANSI & ITU(q933a) standard use a DLCI of 0 and usable DLCI numbers between 16 and 976. The LMI type can be changed on the frame relay enabled interface with the command;
Router(config-if)#frame-relay lmi-type ?
cisco
ansi
q933aThe LMI messages messages sent between Routers and Frame Relay switches provide the the following additional features;- Inverse ARP – to find out the layer 3 address of device on the other end of the DLCI so you dont need to static map it or similar
- Signalling of Virtual Circuit status messages, therefore if a PVC becomes unreachable all nodes along its path can be aware of this failure so data can be prevented from being sent to indirect failures.
- Multicasting – This extension allows multicast groups to be used over frame relay networks, the higher DLCI numbers reserved by the LMI type are used for this
- Globally signficiant DLCIs – Brilliant!
- Retro flow control with XON/XOFF if the applications using the Frame Relay network know understand FECNs and BECNs
By default LMI messages are sent every 10 seconds, and every sixth message a full status message will be sent which contains more detailed information about each VC, the interface will fail if the interfaces does not receive an LMI message 3 times the hello time, so 30 seconds. You cant actually turn off LMI but you can disable the keepalives with the highly ambiguous command;
Router(config-if)#frame-relay lmi-n391dte ?
<1-255> event Finally you can check the status of LMI with the command;Router#sh frame lmi
LMI Statistics for interface Serial1/0 (Frame Relay DTE) LMI TYPE = CISCO
Invalid Unnumbered info 0 Invalid Prot Disc 0
Invalid dummy Call Ref 0 Invalid Msg Type 0
Invalid Status Message 0 Invalid Lock Shift 0
Invalid Information ID 0 Invalid Report IE Len 0
Invalid Report Request 0 Invalid Keep IE Len 0
Num Status Enq. Sent 18 Num Status msgs Rcvd 0
Num Update Status Rcvd 0 Num Status Timeouts 18
Last Full Status Req 00:00:03 Last Full Status Rcvd never Finally pretty much every command on the interface beings with frame-relay;Router(config-if)#frame-relay ?
accounting Special accounting instruction
address-reg ELMI address registration
broadcast-queue Define a broadcast queue and transmit rate
class Define a map class on the interface
congestion-management Enable Frame Relay congestion management
de-group Associate a DE group with a DLCI
fragment Enable end-to-end fragmentation for all PVCs
fragmentation Adaptive fragmentation
PROXY ARP - In General
The command no ip proxy-arp was one of those things which I saw in IOS configs and wasn’t to sure what proxy arp is used for or why it exists. Proxy ARP is where a router will respond on behalf of another device, it was used heavily in networks before the days of DHCP & default gateways where a host would ARP for an address that wasn’t on its subnet (modern networks just send the packets to the default gateway instead of arping for the address), the router on the local network would then act as a “proxy” and respond on behalf of the device outside of the subnet.
Proxy ARP isn’t used if hosts are set with default gateways or have routing intelligence, setting a default gateway instead of using proxy ARP is a much better option. Using Proxy ARP instead of a default gateway results in higher ARP traffic & the ARP tables of the hosts get very large as they maintain an IP/MAC binding for every single address the communicate with.
Subscribe to:
Posts (Atom)
