OpenSolaris

Printable Version Enter a New Search
Bug ID 6773428
Synopsis flowadm add-flow accept "-a remote_ip=1", "remote_ip=99999999" and "remote_ip=1.1"
State 10-Fix Delivered (Fix available in build)
Category:Subcategory network:flowadm
Keywords crossbow
Responsible Engineer Girish Moodalbail
Reported Against
Duplicate Of
Introduced In solaris_nevada
Commit to Fix snv_107
Fixed In snv_107
Release Fixed solaris_nevada(snv_107)
Related Bugs
Submit Date 19-November-2008
Last Update Date 28-January-2009
Description 
The flowadm(1M) manpage clearly states the following semantics for the "local_ip or remote_ip" attribute:

local_ip or remote_ip:
	Identifies a network flow by the local IP address. <value> must be a IPv4 address in dotted-decimal notation or an IPv6 address in colon-separated notation.

However, from the following examples we see that is not true and IP address checking is not done correctly.

bash-3.2# flowadm add-flow -l e1000g3 -a remote_ip=99999999 flow3
bash-3.2# flowadm add-flow -l e1000g3 -a remote_ip=1.1 flow4
bash-3.2# flowadm add-flow -l e1000g3 -a remote_ip=1 flow5
bash-3.2# flowadm show-flow
FLOW        LINK        IP ADDR                        PROTO  PORT    DSFLD
flow5       e1000g3     RMT:0.0.0.1/32                 --     --      --
flow4       e1000g3     RMT:1.0.0.1/32                 --     --      --
flow3       e1000g3     RMT:5.245.224.255/32           --     --      --
bash-3.2# flowadm add-flow -l e1000g3 -a remote_ip=9999999999999999999999999999999999999 flow6
bash-3.2# flowadm show-flow
FLOW        LINK        IP ADDR                        PROTO  PORT    DSFLD
flow6       e1000g3     RMT:255.255.255.255/32         --     --      --
flow5       e1000g3     RMT:0.0.0.1/32                 --     --      --
flow4       e1000g3     RMT:1.0.0.1/32                 --     --      --
flow3       e1000g3     RMT:5.245.224.255/32           --     --      --
Work Around 
N/A
Comments 
N/A