SEO
vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
01-16-2008, 07:07 PM
| ||||
| ||||
 lanscan vs. netstat -in Hi All, Can anyone explain why the command "netstat -in" does not list the lan1 card (see below) that gets listed when I do a lanscan? This is on HP-UX 11.2. Thanks in advance. #> /usr/sbin/lanscan Hardware Station Crd Hdw Net-Interface NM MAC HP-DLPI DLPI Path Address In# State NamePPA ID Type Support Mjr# 0/1/2/0 0x0011855F12A2 0 UP lan0 snap0 1 ETHER Yes 119 0/1/2/1 0x0011855F12A3 1 UP lan1 snap1 2 ETHER Yes 119 #> netstat -in Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll lan0 1500 192.233.54.128 192.233.54.176 94265339 0 65169816 0 0 lo0 4136 127.0.0.0 127.0.0.1 2494042 0 2494571 0 0      |
|
01-16-2008, 07:07 PM
| ||||
| ||||
| Re: lanscan vs. netstat -in Anthony LaMark <anthony@excsoftware.com> wrote: > Can anyone explain why the command "netstat -in" does not list the > lan1 card (see below) that gets listed when I do a lanscan? This is > on HP-UX 11.2. Thanks in advance. As netstat is operating at the IP level (more or less) it will only show those interfaces with an IP address - ie those which have been ifconfig'd. Lanscan is operating at a lower level and will show all the physical interfaces regardless of ifconfig status. Also, lanscan, by showing only physical (or rather what would look like physical to the transport) interfaces will not show things like "lan0:1" or "lan1:2" - it knows nothing about them as they exist only in the "mind" of IP and above  (similarly for lo0)It all comes down to layers rick jones -- The computing industry isn't as much a game of "Follow The Leader" as it is one of "Ring Around the Rosy" or perhaps "Duck Duck Goose." - Rick Jones these opinions are mine, all mine; HP might not want them anyway... feel free to post, OR email to raj in cup.hp.com but NOT BOTH... |
Linear Mode
