On Sat, 03 Jul 1999, champ wrote:
> power:/ # ip ad li
> 1: lo: <LOOPBACK,UP> mtu 3924 qdisc noqueue
> link/LOOPBACK 00:00:00:00:00:00 brd 00:00:00:00:00:00
> inet 127.0.0.1/8 scope host lo
> inet 127.0.0.1/32 scope global lo
> 5: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast
> link/ETHER 48:54:e8:27:b4:ee brd ff:ff:ff:ff:ff:ff
> inet 10.0.0.95/24 brd 10.0.0.255 scope global eth0
> 6: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast
> link/ETHER 00:50:04:68:2d:6b brd ff:ff:ff:ff:ff:ff
> inet 10.0.1.95/24 brd 10.0.1.255 scope global eth1
> power:/ # ip ro li
> 10.0.0.0/24 dev eth0 proto kernel scope link src 10.0.0.95
> 10.0.1.0/24 dev eth1 proto kernel scope link src 10.0.1.95
> default via 10.0.0.1 dev eth0
> power:/ # ping 10.0.0.255
> PING 10.0.0.255 (10.0.0.255): 56 data bytes
> ping: sendto: Permission denied
> ping: wrote 10.0.0.255 64 chars, ret=-1
>
>
Because it is used in DoS attacks. if someone wants to attack you computer,
they forge your IP and broadcast ping a large network as much as possible. You
receive all the replys, and probably go pear shaped, while the network becomes
heavily congested with all those pings. Not good at all. So most TCP/IP stacks
(including) have broadcast ping disabled to prevent it being used in DoS
attacks.
Hope this helps
Beau Kuiper
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
