01-20-2018
I want to collect logs from different hosts, therefore I am checking is the port 514 is open or not.
10 More Discussions You Might Find Interesting
1. Linux
Hello,
I am ltrying to find the config file to modify a parameter for apache (I guess). Here, when sending mail using php web form I get a copy of all mail sent from that form, but here is a sample of what I get :
From : apache@localhost.localdomain
To : myemail@host.com
Subject : Mail ... (2 Replies)
Discussion started by: qfwfq
2 Replies
2. UNIX for Advanced & Expert Users
hello guys,
this morning when I start my pc (gentoo) I get some strange errors about localhost.
"Could not determine the server's fully qualified domain name, using 127.0.0.1 for ServerName" ... Apache
the same for my aplications, I have to use the full address of my pc instead of... (1 Reply)
Discussion started by: georgeplus
1 Replies
3. Ubuntu
Hi folks,
Ubuntu 7.04 server amd64
On running;
$ telnet localhost 106
Trying 127.0.0.1...
telnet: Unable to connect to remote host: Connection refused
$ netstat -an | grep 106
$ sudo netstat -an | grep 106
both no printout
Pls advise where shall I check and how to fix... (22 Replies)
Discussion started by: satimis
22 Replies
4. Shell Programming and Scripting
Somewhat long story:
I have a simple Perl CGI script that uses Expect to Telnet to a device and grab some data, and then spits it back to Perl for display on the Webpage.
This works for many devices I've tried, but one device just fails, it keeps rejecting the password on this device, only... (1 Reply)
Discussion started by: jondo
1 Replies
5. UNIX for Dummies Questions & Answers
I'm trying to connect to my linux server but I'm having some major problems. The server had OEL 5 installed and my local pc is running Windows XP. I'm using PuTTy to connect to the server with Xming running on my loacl machine. I login as root and run the following command -
export... (5 Replies)
Discussion started by: garethnsolomons
5 Replies
6. UNIX for Advanced & Expert Users
Hi,
I have these entries in the /etc/esolv.conf:
------------
domain xxxxxx
search yyyyyy
nameserver 127.0.0.1
nameserver aaaaaaaaaaaaaaaa
nameserver bbbbbbbbbbbbbbbb
-------------
When I use 'dig' or 'nslookup' command, like 'dig yahoo.com' it uses the localhost as the server.
I... (2 Replies)
Discussion started by: chaandana
2 Replies
7. Solaris
Hi All!
I having an issue when trying to run snmpwalk, so the following command it returns an error:
bash-3.00# /usr/sfw/bin/snmpwalk -v 2c -c public localhost sysDescr.0
Timeout: No Response from localhost
bash-3.00#
I have checked also:
bash-3.00# svcs -a | grep sma
online ... (2 Replies)
Discussion started by: fretagi
2 Replies
8. Debian
I am getting the message - waiting for localhost.
Here are some diagnostic steps I have tried ....
root@meow:/home/ethan# cat /var/www/cgi-bin/httpd.conf
ScriptAlias /cgi-bin/ /usr/lib/cgi-bin/jkj
ServerName 127.0.0.1:80
Listen xx.xx.xx.xx:80
Listen 127.0.0.1:80
... (1 Reply)
Discussion started by: Meow613
1 Replies
9. Shell Programming and Scripting
I get a "not found" error from this
localhost/choice.php
ethan@meow:~$ ping 127.0.0.1
PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data.
64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.025 ms
64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.036 m
and this
ethan@meow:~$ mysql -u... (4 Replies)
Discussion started by: Meow613
4 Replies
10. Shell Programming and Scripting
Morning and Happy New Year to all.
I am in a situation where I need to connect to a list of devices that are using either telnet or ssh.
I want to try to telnet, if I receive any of the following I want to attempt ssh :
"Connection refused"
"Connection timed out"
timeout expiration
... (3 Replies)
Discussion started by: popeye
3 Replies
LEARN ABOUT DEBIAN
sniffit
SNIFFIT(5) File Formats Manual SNIFFIT(5)
NAME
sniffit - configuration file for sniffit (name arbirtary)
DESCRIPTION
This page describes the format for the config file for sniffit (see sniffit(8) ). This file allows you to specify in great detail witch
packets should be processed by sniffit. This file also controls (or will control) some functions for the continuous logging ('-L' option).
A sniffit config file might look like (Be sure to end it with a BLANK line):
# Sniffit Sample Config file -- Brecht Claerhout
logfile /var/log/sniffit.today.log
# First select all packets!
select both mhosts 1
select both mhosts 2
# Now deselect all packets from/to those damn 'surfers'
deselect both port 80
deselect both port 8001
This file will tell sniffit to process all packets on the subnet except those FROM/TO ports 80 and 8001 (thus we don't want logs of those
mass WWW connections witch turn our logs unreadable).
GLOBAL FORMAT
The file consists of lines, lines are formed by fields, fields are separated with SPACES (NO TABS). Unix comment lines (starting with '#'
are allowed). So this gives us:
<field1> <field2> <field3> <field4> <field5>
FIELD FORMAT
<field1>
select - Sniffit will look for packets that match the following description (other fields)
deselect - Sniffit will ignore packets that match the description
logfile - change the logfile name to <field2> instead of the default 'sniffit.log'
<field2>
from - Packets FROM the host matching the following desc. are considered.
to - similar, Packets TO the....
both - similar, Packets FROM or TO the....
a filename - as an argument of 'logfile' in <field1>
<field3>
host - The (de)selection criteria involves a hostname.
port - similar, ... a portnumber
mhosts - The (de)selection criteria involves multiple-hosts, like with the wildcars in 0.3.0, but without the 'x'
<field4>
Either a hostname, a portnumber, a service name or a numbet-dot partial notation indicating multiple hosts depending on <field3>
(service names like 'ftp' are resolved as the services available present on the host that runs Sniffit, and translated into a port
nr)
<field5>
A portnumber, if <field3> was 'host' or 'mhosts' (optional, if not filled in, all ports are going to be (de)selected)
FILE INTERPRETING
The config file is interpreted SEQUENTIAL, so watch it, don't mix lines in a file. Example:
select both mhosts 100.100.12.
deselect both port 80
select both host 100.100.12.2
This file will get you the packets:
a) Send by hosts '100.100.12.*'
b) EXCEPT the WWW packets
c) BUT showing the WWW packets concerning
100.100.12.2
select both mhosts 100.100.12.
select both host 100.100.12.2
deselect both port 80
Will give you the packets (probably unwanted result):
a) Send by hosts '100.100.12.*'
b) Send from/to 100.100.12.2 (useless line)
c) deselecting all WWW packets on the subnet
AUTHOR
Brecht Claerhout <coder@reptile.rug.ac.be>
SEE ALSO
sniffit(8)
SNIFFIT(5)