OpenSolaris

Printable Version Enter a New Search
Bug ID 4085089
Synopsis add a feature to enable 'snooping' of the loopback traffic
State 10-Fix Delivered (Fix available in build)
Category:Subcategory kernel:tcp-ip
Keywords clearview | kevlar | rtiq_reviewed | tibcoperf
Responsible Engineer Phil Kirk
Reported Against 2.8 , 5.7 , s10 , s10_54 , s10_63 , s297_fcs
Duplicate Of
Introduced In sunos_2.0
Commit to Fix snv_103
Fixed In snv_103
Release Fixed solaris_nevada(snv_103)
Related Bugs 4195614 , 6616754 , 6760922 , 6764012 , 6764020 , 6764023 , 6764199 , 6770479 , 6770744 , 6774464 , 6777013 , 6784207 , 6787370 , 6789874 , 6791375 , 6794914 , 6806687 , 6847389 , 6847403 , 6858912 , 6867658 , 6867662 , 6884202 , 6886324 , 6894207 , 5097626 , 4821256
Submit Date 9-October-1997
Last Update Date 2-November-2009
Description 
i'll leave this rfe deliberately vague as i don't have
too great a preference as to how this is implemented.

what my customer would like (& what would be extremely
useful for troubleshooting purposes) is the ability to
'snoop' (in some way) loopback ip traffic

the sort of thing that springs to mind would be some sort
of /dev/lo pseudo device that supports dlpi (or at least
the subset that snoop uses). the ability to snoop all ip
traffic via this (as opposed to just that intended for
loopback) would also be cool as a timesaver on multihomed
m/cs & also for diagnosing disparities between what ip
sees/sends & what the data links (/dev/le etc) see

maybe there could be a way of switching this capability
on/off (could be automatic whenever anything snoops it)
so it doesn't cause a hit in performance under normal
operation
Work Around 
N/A
Comments 
N/A