search for: tcp4

...d by www:www.. If I got a lot of users connecting to my server on port 80, will thier requests ever be answered by the root fork or the www:www forks? --- snip --- [root@ninja:~]# sockstat -l4p80 USER COMMAND PID FD PROTO LOCAL ADDRESS FOREIGN ADDRESS www httpd 18149 3 tcp4 *:80 *:* www httpd 18148 3 tcp4 *:80 *:* www httpd 18147 3 tcp4 *:80 *:* www httpd 14055 3 tcp4 *:80 *:* www httpd 14054 3 tcp4 *:80 *:* www httpd 140...

...domain master = No dns proxy = No wins server = WINS1, WINS2 ldap ssl = no passdb expand explicit = No admin users = is81301, ds066 [/dano] path = /tmp guest ok = Yes When I do a netstat -a, I do not see ports 137 or 139 listed: tcp4 0 0 *.daytime *.* LISTEN tcp 0 0 *.ftp *.* LISTEN tcp4 0 0 *.ssh *.* LISTEN tcp 0 0 *.telnet *.* LISTEN tcp4...

...still want to chroot Dovecot. I noticed that there are some options in the dovecot.conf that are intended for this. Unfortunately online resources on how to do that can't be found on google. Although I'm running the server as user dovecot. I still do have this: dovecot pop3-login 491 1 tcp4 10.0.1.4:995 *:* dovecot pop3-login 490 1 tcp4 10.0.1.4:995 *:* dovecot pop3-login 489 1 tcp4 10.0.1.4:995 *:* dovecot imap-login 488 1 tcp4 10.0.1.4:993 *:* dovecot imap-login 487 1 tcp4 10.0.1.4:993 *:* dovecot imap-login 486...

..."zoneli" state and is already a bug report on http://www.freebsd.org/cgi/query-pr.cgi?pr=106317 But after more investigation, I found there are lots of TCP Connections in FIN_WAIT_1 and never close. # netstat -an | grep FIN_WAIT_1 | wc -l 823 # netstat -an | grep FIN_WAIT_1 | head tcp4 0 273 192.168.1.1.80 61.62.121.195.64739 FIN_WAIT_1 tcp4 0 13448 192.168.1.1.80 163.22.44.102.58775 FIN_WAIT_1 tcp4 0 33304 192.168.1.1.80 163.32.61.253.2273 FIN_WAIT_1 tcp4 0 48416 192.168.1.1.80 24.78.35.230.61059 FIN_WAI...

...rce4/nbt_server/interfaces.c:228(nbtd_add_socket) >>>> Failed to bind to 127.0.162.1:137 - NT_STATUS_ADDRESS_ALREADY_ASSOCIATED >> check where has port 137 occupied > There is nothing listening on 137 > > [root at smb4-2 ~ (master)]# netstat -an | grep -i listen > tcp4 0 0 192.168.18.162.22 *.* LISTEN > tcp4 0 0 192.168.216.162.22 *.* LISTEN > tcp4 0 0 *.10000 *.* LISTEN Try it like this: netstat -an | grep -i LISTEN | grep nmb Rowland

...les dns networks: files #passwd: compat #passwd_compat: nis shells: files services: compat services_compat: nis protocols: files rpc: files group: files winbind user: files winbind # sockstat -4 USER COMMAND PID FD PROTO LOCAL ADDRESS FOREIGN ADDRESS root winbindd 52698 26 tcp4 10.1.200.98:37794 10.1.200.99:445 root winbindd 52698 28 tcp4 10.1.200.98:37794 10.1.200.99:445 root winbindd 52698 30 tcp4 10.1.200.98:59691 10.1.200.99:389 root winbindd 52698 31 tcp4 10.1.200.98:59026 10.1.200.99:389 root winbindd 52698 32 tcp4 1...

...DR.ARPA" { type master; allow-query { any; }; file "master/localhost.rev"; }; . . . 4.netstat -an or sockstat -4 result: ns# netstat -an Active Internet connections (including servers) Proto Recv-Q Send-Q Local Address Foreign Address (state) tcp4 0 48 122.254.1x.x.22 122.254.93.23.58663 ESTABLISHED tcp4 0 0 122.254.1x.x.63442 130.94.149.166.5999 TIME_WAIT tcp4 0 0 122.254.1x.x.22 122.254.93.23.54514 ESTABLISHED tcp4 0 0 122.254.1x.x.49853 128.205.32.21.5999 ESTABLISHED tc...

...t >> services_compat: nis >> protocols: files >> rpc: files >> >> group: files winbind >> user: files winbind >> >> # sockstat -4 >> USER COMMAND PID FD PROTO LOCAL ADDRESS FOREIGN >> ADDRESS >> root winbindd 52698 26 tcp4 10.1.200.98:37794 10.1.200.99:445 >> root winbindd 52698 28 tcp4 10.1.200.98:37794 10.1.200.99:445 >> root winbindd 52698 30 tcp4 10.1.200.98:59691 10.1.200.99:389 >> root winbindd 52698 31 tcp4 10.1.200.98:59026 10.1.200.99:389 >> root winbindd...

...ening on ports 80 > and >>443? You've verified with 'netstat -finet -a' that this is the case? > >Yes: > ># netstat -finet -a >Active Internet connections (including servers) >Proto Recv-Q Send-Q Local Address Foreign Address > (state) >tcp4 0 0 192.168.1.109.ssh 192.168.1.107.3502 > ESTABLISHED >tcp4 0 52 192.168.1.109.ssh 192.168.1.107.2266 > ESTABLISHED >tcp4 0 0 *.poppassd *.* > LISTEN >tcp4 0 0 *.ftp *...

...>>>>>> Failed to bind to 127.0.162.1:137 - NT_STATUS_ADDRESS_ALREADY_ASSOCIATED >>>> check where has port 137 occupied >>> There is nothing listening on 137 >>> >>> [root at smb4-2 ~ (master)]# netstat -an | grep -i listen >>> tcp4 0 0 192.168.18.162.22 *.* LISTEN >>> tcp4 0 0 192.168.216.162.22 *.* LISTEN >>> tcp4 0 0 *.10000 *.* LISTEN >> Try it like this: >> >> netstat -an |...

Dear W.D. Do you understand that by adding the rules into kernel space numbered from zero to sixty five thousand five hundred thirty four you may alter the behavior of the rule number sixty five thousand five hundred thirty five can you please define and list the goals you are trying to achieve by altering default rule in the terms you can both explain and understand. ----- Original Message

...; shells: files > services: compat > services_compat: nis > protocols: files > rpc: files > > group: files winbind > user: files winbind > > # sockstat -4 > USER COMMAND PID FD PROTO LOCAL ADDRESS FOREIGN > ADDRESS > root winbindd 52698 26 tcp4 10.1.200.98:37794 10.1.200.99:445 > root winbindd 52698 28 tcp4 10.1.200.98:37794 10.1.200.99:445 > root winbindd 52698 30 tcp4 10.1.200.98:59691 10.1.200.99:389 > root winbindd 52698 31 tcp4 10.1.200.98:59026 10.1.200.99:389 > root winbindd...

On Wed, July 22, 2020 21:47, Andrew Bartlett wrote: > Are you using DLZ_BIND9? There is a bug where it doesn't know the locking rules for those files. No. I am using the internal dns service. > Otherwise, work out which commend it is waiting on (the child) and > what lock that is waiting on (lslocks on linux is what I used to > debug this stuff). There does not appear to be

# netstat -an | grep LISTEN tcp4 0 0 *.32785 *.* LISTEN tcp4 0 0 130.238.4.133.22 *.* LISTEN What in ?@# is 32785 ?? # lsof ... sshd 11152 root 5u IPv4 0x7003ded8 0t0 TCP *:32785 (LISTEN) sshd 11152 root 6u IPv4 0x7004ded8 0t0 TCP xx...

Hi peeps, After compiling ipfw into the new 6.2 kernel, and typing "ipfw list", all I get is: "65535 deny ip from any to any" From reading the docs, this might indicate that this is the default rule. (I am certainly protected this way--but can't be very productive ;^) ) By the way, when I run "man ipfw" I get nothing. Using this instead:

...~/WIP-perl/portsend.pl -a localmirror_1 -p 1111 in the mirror, out the jail : : Verify that the client side of the tunnel is bound to a single : address. : root# netstat -a Active Internet connections (including servers) Proto Recv-Q Send-Q Local Address Foreign Address (state) tcp4 0 0 localjail_1.3521 localjail_1.2222 TIME_WAIT tcp4 0 0 localmirror_1.3520 localmirror_1.1111 TIME_WAIT tcp4 0 0 localjail_1.2222 *.* LISTEN tcp4 0 0 localmirror_1.1111 *.* LISTEN tcp4 0 0 l...

Hi, Im using dovecote as my IMAP interface. However i do have a lot of imap instances. its only 7 user using the system as i get this. please advice. 1230 ? S 0:00 imap-login 1309 ? S 0:00 imap-login 1387 ? S 0:00 imap-login 1388 ? S 0:00 imap-login 1389 ? S 0:00 imap-login 1390 ? S 0:00 imap-login 1391 ? S

...t sure what to look for really. i rebuilt the world on the host with exactly the same sources as the jail, all is sync. --> With putty's logging feature i managed to grab this : netstat Active Internet connections Proto Recv-Q Send-Q Local Address Foreign Address (state) tcp4 0 52 jail.ssh ALyon-209-2-1-2..2484 ESTABLISHED tcp4 0 0 jail.smtp *.* LISTEN tcp4 0 0 jail.ssh *.* LISTEN tcp4 0 0 jail.telnet *.* LISTEN tcp4...

...e: >>> ../../source4/nbt_server/interfaces.c:228(nbtd_add_socket) >>> Failed to bind to 127.0.162.1:137 - NT_STATUS_ADDRESS_ALREADY_ASSOCIATED > check where has port 137 occupied There is nothing listening on 137 [root at smb4-2 ~ (master)]# netstat -an | grep -i listen tcp4 0 0 192.168.18.162.22 *.* LISTEN tcp4 0 0 192.168.216.162.22 *.* LISTEN tcp4 0 0 *.10000 *.* LISTEN > why is your localhost at 127.0.162.1? This problem is occurring in a FreeBSD...

...ps { port = 9999 } process_min_avail = 3 service_count = 0 vsz_limit = 1 G } But I am not seeing any listeners on port 9999 - root at ns(1001)# netstat -an | grep 9999 Using sockstat on FreeBSD: root at ns(1002)# sockstat | grep dovecot | grep tcp root dovecot 34800 15 tcp4 *:4190 *:* root dovecot 34800 37 tcp4 127.0.0.1:143 *:* root dovecot 34800 38 tcp6 ::1:143 *:* I have mail_debug = yes, but I don't see any failures. What is the best way to debug why I am not seeing this port number? Thanks, Patrick...