Configuring IP source guard
Overview
IP source guard (IPSG) prevents spoofing attacks by using an IPSG binding table to match
legitimate packets. It drops packets that do not match the table. IPSG is a per-interface packet filter.
Configuring the feature on one interface does not affect packet forwarding on another interface.
The IPSG binding table can include global and interface-specific bindings. IPSG first uses the
interface-specific bindings to match packets. If no match is found, IPSG uses the global bindings.
The bindings fall into the following types:
•
IP.
•
MAC.
•
IP-MAC.
•
IP-VLAN.
•
MAC-VLAN.
•
IP-MAC-VLAN.
IPSG bindings can be static or dynamic.
•
Static bindings—Configured manually. Global IPSG supports only static IP-MAC bindings. For
more information about global static IPSG bindings, see
•
Dynamic bindings—Generated based on information from other modules. For more
information about dynamic bindings, see
As shown in
Figure 116 Diagram for the IPSG feature
Valid host
1.1.1.1
Invalid host
Static IPSG bindings
Static IPSG bindings are configured manually. They are suitable for scenarios where few hosts exist
on a LAN and their IP addresses are manually configured. For example, you can configure a static
IPSG binding on an interface that connects to a server. This binding allows the interface to receive
packets only from the server.
Static IPSG bindings on an interface implement the following functions:
•
Filter incoming IPv4 or IPv6 packets on the interface.
•
Cooperate with ARP detection in IPv4 for user validity checking.
For information about ARP detection, see
Static IPSG bindings can be global or interface-specific.
Figure
116, IPSG forwards only the packets that match an IPSG binding.
IPSG bindings
1.1.1.1
...
Configure the IP source guard
feature on the interface
"Static IPSG
"Dynamic IPSG
bindings."
IP network
"Configuring ARP attack
400
bindings."
protection."
Need help?
Do you have a question about the FlexNetwork 5510 HI Series and is the answer not in the manual?