Filtering Source Addresses on gw-internet

In response to the many requests and comments on this list for all
NetworkOps to install filtering to prevent IP spoofing attacks . . .

On my internet router (gw-internet) I had set up filtering to attempt to
block all outgoing source addresses that do not have my network
(a.b.c.0/24) as their source some time ago.

Then, I had to modify the acl 120 to prevent
the default route for our internal network from leaking the occasional
packet with an RFC 1597 private destination address out to our ISP. (We
use Cisco 11.2 NAT to hide several medium sized networks behind a couple
af legit IPs. I took another spare router, and slapped 1.1.1.1/8 on a
secondary interface, and tried to ping out, and my acl seems to be O.k.

I'm just trying to be responsible for my users (some of whom are
@ unsupervised and remote sites via dialup & ISDN) and prevent any
other network ops from experiencing problems caused by ignorant /
malicious users that may find their way onto my network !

Any comments / suggestions / improvements / warning / something I have
missed ??? Thanks !

gw-internet#show access-lists 120
Extended IP access list 120
    deny ip any 10.0.0.0 0.255.255.255 log
    deny ip any 172.16.0.0 0.0.255.255 log
    deny ip any 172.17.0.0 0.0.255.255 log
    deny ip any 192.168.0.0 0.0.255.255 log
    permit ip a.b.c.0 0.0.0.255 any (27429 matches)
    deny ip any any log

gw-internet#
%SEC-6-IPACCESSLOGDP: list 120 denied icmp 1.1.1.1 -> 205.161.206.4 (8/0),
1 packet
ICMP: dst (205.161.206.4) administratively prohibited unreachable sent to
1.1.1.1
ICMP: dst (205.161.206.4) administratively prohibited unreachable sent to
1.1.1.1
ICMP: dst (205.161.206.4) administratively prohibited unreachable sent to
1.1.1.1
ICMP: dst (205.161.206.4) administratively prohibited unreachable sent to
1.1.1.1
ICMP: dst (205.161.206.4) administratively prohibited unreachable sent to
1.1.1.1

Line 2 and 3 could be replaced by
deny ip any 172.16.0.0 0.15.255.255 log

which would block all 172.16.0.0-172.31.0.0 as per the RFC.

You might also want to block 127.0.0.0.

GK

Much thanks to everyone for their input. Greg, since you have "Cisco" in your
email address, any comment on whether sending packets to a null interface is a
quicker / more efficient way blocking unwanted traffic ? gw-internet is a
little old 68030, with 1MB RAM.

-----BEGIN PGP SIGNED MESSAGE-----

>gw-internet#show access-lists 120
>Extended IP access list 120
> deny ip any 10.0.0.0 0.255.255.255 log
> deny ip any 172.16.0.0 0.0.255.255 log
> deny ip any 172.17.0.0 0.0.255.255 log
> deny ip any 192.168.0.0 0.0.255.255 log
> permit ip a.b.c.0 0.0.0.255 any (27429 matches)
> deny ip any any log

Line 2 and 3 could be replaced by
deny ip any 172.16.0.0 0.15.255.255 log

which would block all 172.16.0.0-172.31.0.0 as per the RFC.

You might also want to block 127.0.0.0.

GK

-----BEGIN PGP SIGNATURE-----
Version: PGP for Personal Privacy 5.0
Charset: noconv

iQEVAwUBM/DBxW384++etaQJAQGlwAgAoVjoB5EZCaYjzvmwWaVeO5zOPTipegDE
0TX2Xg2L5yIClAeiWD4f0T4E4jCH5BtSwoitlu9fcHlsPo4VRwOutQssIJHL+sUR
Ps1NEot6pwOu+slCwklLhqVwyouv0UHI0Fxal5aCM65X+WNH8+5HvE9g4uBQp8A6
o6HzM++69FKwg8pdQ82HNnjToVZxsqwH41HNSHC0HjLvJG+uZPBFlzLEdnvkNSRg
fikSERpnZAa+QzpTRjtTcK3XC2DEYGAi0wifn9mbyRav9xenzvNl+rUV5Fg/jbFS
jDFhiLFJc/7o3Y5+9HoA9keBEqeFMle86BGjX09C1FKLtPnVhTwSpQ==
=ZNYx
-----END PGP SIGNATURE-----

Linux.