Results 1 to 5 of 5
Hi All,
When ever we run ifconfig command it gives you the detail of
eth1 ................................
.............................
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
now if i have some application ...
- 01-28-2009 #1Just Joined!
- Join Date
- Nov 2008
- Location
- PUNE
- Posts
- 72
ifconfig help
Hi All,
When ever we run ifconfig command it gives you the detail of
eth1 ................................
.............................
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
now if i have some application servers running on
127.0.0.3 and 127.0.0.4
how am i suppose to see that
Is that(ifconfig command's) data gets store in some file because when i run packet sniffer it never shows me the desired IP addresses packet sniffing
, i.e. 127.0.0.3 or 127.0.0.4 i am using wireshark packet sniffer by the way but it only shows the 127.0.0.1 only or the NAT address that is 192.168.0.1 bla bla bla 
any idea about it?
- 01-28-2009 #2
The netstat command will show you every single port being used.
See the man pages for the correct syntax and usage but the command is basically run as:
Code:netstat -a
Code:netstat -t
I do not respond to private messages asking for Linux help, Please keep it on the forums only.
All new users please read this.** Forum FAQS. ** Adopt an unanswered post.
- 01-29-2009 #3Just Joined!
- Join Date
- Nov 2008
- Location
- PUNE
- Posts
- 72
Hi Mike,
Thanks for your reply
actually i not looking for specifically port its actually my concern is packet sniffing which is coming to specific IP address( 127.0.0.3 or 127.0.04 ) and i can do that only when it is available through command ifconfig
but while passing this command it never shows the IP my system is using(i.e. 127.0.0.3 and 127.0.0.4 and bla bla bla related to loop back only 127.0.0.1 is visible through this command
)
Sorry for posting confusing post if it is.........
- 01-30-2009 #4Just Joined!
- Join Date
- Jan 2009
- Location
- holland
- Posts
- 12
Hi ,am new to the netstat in linux so i dunno that now but from logical newbie point of view u could try to set and sniff range scan maby in wireshark or as commands like 127.0.0.1 to 127.0.0.255 sniff sniff
further i dunno cause am noob @ linux..
- 01-30-2009 #5Just Joined!
- Join Date
- Nov 2008
- Location
- PUNE
- Posts
- 72
Problem with the wireshark is that when you start it, It automatically picks up the running IP's sniffing you just have to select out of provided options you cant add on your own

like what ifconfig does
i tried to scan file sbin/ifconfig
but couldn't understand much any ways mine research is on let me see how far i can reach


Reply With Quote