Reputation
Top tag
Next privilege 200 Rep.
See reduced ads
Badges
9
Newest
 Custodian
Impact
~4k people reached

  • 0 posts edited
  • 0 helpful flags
  • 19 votes cast
Oct
3
accepted Filter packets sent via HTTP to a port other then 80?
Oct
3
comment Filter packets sent via HTTP to a port other then 80?
Yup, your answer combined with @nik filter did the trick. Thanks a bunch!
Oct
3
comment Filter packets sent via HTTP to a port other then 80?
I really just pasted it as is into Wireshark's filter input box, after I certainly sent a request to the server and also got a response, but nothing showed up in the main window. The IP address is rather non-spcific in my case... that's my localhost.
Oct
3
revised Filter packets sent via HTTP to a port other then 80?
added 170 characters in body; edited title
Oct
3
comment Filter packets sent via HTTP to a port other then 80?
Nope, this didn't do it. Sorry.
Oct
3
comment Filter packets sent via HTTP to a port other then 80?
@grawity Umm... I thought they were the same :) Well, Wireshark then, that's what I'm using. But if there's some way to do this via tcpdump, that's fine too, whichever gets me there.
Oct
3
asked Filter packets sent via HTTP to a port other then 80?
Jul
8
comment Get a concise list of open (listening) sockets in Fedora 17
@Paul I'm not assuming anything. The number assigned to the opened port is useful. A string alias - isn't. End of story. Sorry, I won't reply any more on this subject. I think it won't help anything / will just waste a little more of database space, hence adding to global warming :)
Jul
8
comment Get a concise list of open (listening) sockets in Fedora 17
@Paul correct information may well be garbage, if there is no way to interpret it. If I write this answer to you in Cyrilic phonetic translation - will it not be garbage to you? It most certainly will, however, it may be correct in all other aspects.
Jul
8
comment Get a concise list of open (listening) sockets in Fedora 17
@Paul I really think this argument is redundant. For me they don't match - hence garbage. Maybe someone used a string consisting of all numbers as an alias to the port number - I don't know and am not eager to find out. In the particular case of the program I'm interested in the port is printed as :shockwave2 - and that is a particularly useless piece of information.
Jul
6
accepted Get a concise list of open (listening) sockets in Fedora 17
Jul
6
comment Get a concise list of open (listening) sockets in Fedora 17
@Paul that was just an example that floated somewhere in the top results. I was using a different program to bind the socket (written by me, so I surely know what port it uses).
Jul
6
comment Get a concise list of open (listening) sockets in Fedora 17
I actually did say it's Fedora 17. yum claims there's no sockstat that it knows of, but it's not uncommon for RHEL to rename things. If only I knew this is the case... :)
Jul
6
comment Get a concise list of open (listening) sockets in Fedora 17
@terdon I can't yet :) I'd need to wait for some time. But you are welcome to post your suggestion if you like.
Jul
6
comment Get a concise list of open (listening) sockets in Fedora 17
@Paul with another program if I do then echo "some command" | nc 127.0.0.1 port-number - where I actually know what port number it listens on, I'm getting the expected message back, but that program appears in the list as listening on a completely different port.
Jul
6
comment Get a concise list of open (listening) sockets in Fedora 17
@terdon oh, I've missed the -p option. Sorry, I've been trying them from memory instead of just reading through the list of options... well... I'm sorry :) netstat -npa did what I wanted.
Jul
6
comment Get a concise list of open (listening) sockets in Fedora 17
@lserni unfortunately not. This will not print the name of the program using (binding) the socket...
Jul
6
asked Get a concise list of open (listening) sockets in Fedora 17
Jun
30
comment Moved /lib64 to /backup_lib64 using sudo, now sudo doesn't work on CentOS6.4
Well, then I'm sorry to tell you, but it seems like you have to pull some other triggers there... it doesn't look like there's a technical way to solve this.
Jun
29
comment Moved /lib64 to /backup_lib64 using sudo, now sudo doesn't work on CentOS6.4
It sounds like you didn't get much in terms of a ways out of this situation. However, have you tried su command? Perhaps it doesn't need to load any libraries (not likely, but you could still try).