search for: udp4

...0 0 *.33138 *.* LISTEN tcp4 0 0 *.wsmserve *.* LISTEN tcp4 0 52 r10dev01.ssh dpcs0395590.care.atc-l ESTABLISHED tcp4 0 0 r10dev01.ssh dpcs0395590.care.1187 ESTABLISHED udp4 0 0 *.daytime *.* udp4 0 0 *.time *.* udp4 0 0 *.sunrpc *.* udp4 0 0 127.255.255.255.ntp *.* udp4 0 0 rs123ws255.inter.ntp *.* udp4 0 0 loopback.ntp *.* udp4 0...

...ntpd.conf File on a DC . . . ntpsigndsocket /usr/local/samba/var/lib/ntp_signd/ Now, on the FreeBSD host I see this instead: # sockstat | grep ntp root ntpd 6229 3 dgram -> /var/run/logpriv root ntpd 6229 20 udp6 *:123 *:* root ntpd 6229 21 udp4 *:123 *:* root ntpd 6229 22 udp4 192.168.8.65:123 *:* root ntpd 6229 23 udp6 ::1:123 *:* root ntpd 6229 24 udp6 fe80::1%lo0:123 *:* root ntpd 6229 25 udp4 127.0.0.1:123 *:* root samba 766...

...ot winbindd 52698 31 tcp4 10.1.200.98:59026 10.1.200.99:389 root winbindd 52698 32 tcp4 10.1.200.98:49319 10.1.200.99:1024 root smbd 52693 35 tcp4 10.1.200.98:445 *:* root smbd 52693 36 tcp4 10.1.200.98:139 *:* root nmbd 52689 16 udp4 10.1.200.98:137 *:* root nmbd 52689 17 udp4 10.1.200.98:138 *:* root nmbd 52689 18 udp4 10.1.200.98:137 *:* root nmbd 52689 19 udp4 10.1.200.98:137 *:* root nmbd 52689 20 udp4 10.1.200.98:138 *:* root nmbd 526...

...cp4 10.1.200.98:59026 10.1.200.99:389 >> root winbindd 52698 32 tcp4 10.1.200.98:49319 10.1.200.99:1024 >> root smbd 52693 35 tcp4 10.1.200.98:445 *:* >> root smbd 52693 36 tcp4 10.1.200.98:139 *:* >> root nmbd 52689 16 udp4 10.1.200.98:137 *:* >> root nmbd 52689 17 udp4 10.1.200.98:138 *:* >> root nmbd 52689 18 udp4 10.1.200.98:137 *:* >> root nmbd 52689 19 udp4 10.1.200.98:137 *:* >> root nmbd 52689 20 udp4 10.1.200.98:1...

...lead to believe that the case of the servername (HC_LIVE) is important as it shows that the names are being passed by Netbios as opposed to DNS. - Is this correct? Assuming so, I had a look at the netstat from the server an extract from "netstat -A" is shown below: f1000089c3e25600 udp4 0 0 hc_live.sing.netbi *.* f1000089c3e25400 udp4 0 0 10.70.0.80.netbios *.* f1000089c3e25300 udp4 0 0 hc_live.sing.netbi *.* f1000089c459c900 udp4 0 0 10.70.0.80.netbios *.* f1000089c6bbd800 udp4 0 0 loopback.57393 *.* f1000089c609d000 udp4 0 0 loopback.57456 *.* f1000089c3a31d00 udp4 0 0 loo...

...698 31 tcp4 10.1.200.98:59026 10.1.200.99:389 > root winbindd 52698 32 tcp4 10.1.200.98:49319 10.1.200.99:1024 > root smbd 52693 35 tcp4 10.1.200.98:445 *:* > root smbd 52693 36 tcp4 10.1.200.98:139 *:* > root nmbd 52689 16 udp4 10.1.200.98:137 *:* > root nmbd 52689 17 udp4 10.1.200.98:138 *:* > root nmbd 52689 18 udp4 10.1.200.98:137 *:* > root nmbd 52689 19 udp4 10.1.200.98:137 *:* > root nmbd 52689 20 udp4 10.1.200.98:138 *:* &gt...

...ne is home gateway/http/printserver. Recently some strange things happened as my printer all of sudden started to print stuff when nobody prints... luckily (or unluckily) it ran out of ink so I can't tell what's printed. Checked programs running, ports opened and found one unidentified: udp4 0 0 *.49152 *.* dimon@gateway ~ > sockstat | grep 49152 bind named 270 4 udp4 *:49152 *:* Now', is there any reason for bind to use this port? Googling for that subject didn't bring any results other than usualy this port is first...

...ues we see with HP systems?? The load-and-hang many of them do with syslinux.efi as discussed here?? E.g., maybe they implement this protocol a little better...? -Alan<<< It very well might. I remember your "load-and-hang"; that could be becauseHP just does not need to test their UDP4 Binding Services because bootmgfw.efi does not use that, then they might very well have a non-reported FW bug there. But how to know if it is a problem in our side or their side? who knows.. but also "who cares" is we can avoidusing EFI UDP4 Binding Services... That's why I think we...

win2k/XP clients can access this fine, but not NT clients. Samba is listening on the netbios-dgm/ns ports and there's no packet filtering: udp4 0 0 atarashii.netbios-dgm *.* udp4 0 0 atarashii.netbios-ns *.* udp4 0 0 *.netbios-dgm *.* udp4 0 0 *.netbios-ns *.* What do I need to check? Thanks, G...

...ail, everything works nicely. If I put it back into the jail, it just doesn't respond - the nmbd is running, though; sockstat output follows: root smbd 1436 18 tcp4 192.168.15.201:445 *:* root smbd 1436 19 tcp4 192.168.15.201:139 *:* root nmbd 1430 6 udp4 192.168.15.201:137 *:* root nmbd 1430 7 udp4 192.168.15.201:138 *:* root nmbd 1430 8 udp4 192.168.15.201:137 *:* root nmbd 1430 9 udp4 192.168.15.201:138 *:* root nmbd 1430 12 dgram -> /var/run/logpriv So it listens at the corr...

...ndsocket  /usr/local/samba/var/lib/ntp_signd/ > > Now, on the FreeBSD host I see this instead: > > # sockstat | grep ntp > root     ntpd       6229  3  dgram  -> /var/run/logpriv > root     ntpd       6229  20 udp6   *:123                 *:* > root     ntpd       6229  21 udp4   *:123                 *:* > root     ntpd       6229  22 udp4   192.168.8.65:123      *:* > root     ntpd       6229  23 udp6   ::1:123               *:* > root     ntpd       6229  24 udp6   fe80::1%lo0:123       *:* > root     ntpd       6229  25 udp4   127.0.0.1:123         *:* &gt...

...igndsocket /usr/local/samba/var/lib/ntp_signd/ > > Now, on the FreeBSD host I see this instead: > > # sockstat | grep ntp > root ntpd 6229 3 dgram -> /var/run/logpriv > root ntpd 6229 20 udp6 *:123 *:* > root ntpd 6229 21 udp4 *:123 *:* > root ntpd 6229 22 udp4 192.168.8.65:123 *:* > root ntpd 6229 23 udp6 ::1:123 *:* > root ntpd 6229 24 udp6 fe80::1%lo0:123 *:* > root ntpd 6229 25 udp4 127.0.0.1:123 *:* &gt...

...65535 0 0 deny ip from any to any kustik:~# sockstat -4 USER COMMAND PID FD PROTO LOCAL ADDRESS FOREIGN ADDRESS root smbd 10548 18 tcp4 10.0.1.8:445 *:* root smbd 10548 19 tcp4 10.0.1.8:139 *:* root nmbd 10542 6 udp4 *:137 *:* root nmbd 10542 7 udp4 *:138 *:* root nmbd 10542 8 udp4 10.0.1.8:137 *:* root nmbd 10542 9 udp4 10.0.1.8:138 *:* root sshd 555 3 tcp4 *:22 *:* root natd 264...

...oing package. (I cannot find anything in the log and every blocked package will be logged) My setup is, FreeBSD6 going online with ppp, NAT is done with pf and the firewall too. Asterisk is configured to bind to 0.0.0.0, so it should bind to my tun0 interface and the external IP. netstat -an says: udp4 0 0 *.4569 *.* udp4 0 0 *.5060 *.* If I call outside everything is working fine. Is this a problem with NAT or the maybe the firewall or is it necessary to change some configoptions in asterisk? Best regards, Matthias

On Thu, Jun 25, 2015 at 7:28 PM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Thu, Jun 25, 2015 at 11:54 AM, Patrick Masotta <masottaus at yahoo.com> wrote: > >> Yes I know what you mean; >> "I think" the handle of the running image (our code) has a "path" telling us where >> was laded from. That would solve this thing. > > I just

...HED tcp4 0 0 jail.smtp *.* LISTEN tcp4 0 0 jail.ssh *.* LISTEN tcp4 0 0 jail.telnet *.* LISTEN tcp4 0 0 jail.domain *.* LISTEN udp4 0 0 jail.syslog *.* udp4 0 0 jail.ntp *.* udp4 0 0 jail.domain *.* netstat: short read netstat: short read netstat: short read .....(goes on for miles and miles if i dont ^C) just in case : kmem and the kernel are linked to...

...ware for communication stuff, btw. (2) set up the UDP 'port' to communicate with (like in a separate software package for passing commands and responses back and forth). (3) use the "system" command to send messages - as an example: system("echo \"quit\"| socat - UDP4-DATAGRAM:0.0.0.0:19004") I haven't tried receiving data from that software yet... but according to the writeup on socat, it should be no problem. You can also use the socat software to redirect from one type of connection to another. (I'm studying R - both for programming/running &...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I'm using tinc to connect a couple of ipv6 capable machines using a mix of upd6, udp4, tcp6 and tcp4. Now I wanted to add an linux embedded device, which has no ipv6 support at all. Tinc did compile and configuration is fine (tested on other machine), but after connecting the embedded device to other hosts tinc instances, it suddenly crashes. The last things happening before crash a...

...4 2356 ?? I 9:24PM 0:00.00 /usr/ local/samba/sbin/smbd -D root 246 0.0 1.3 3104 1624 ?? Ss 9:24PM 0:00.05 /usr/ local/samba/sbin/nmbd -D smbclient -L SambaServer1 -U% Domain=[WORKGROUP] OS=[Unix] Server=[Samba 3.0.20] --then it lists my shares----------- netstat -an|grep 137 udp4 0 0 192.168.1.22.137 *.* udp4 0 0 *.137 *.* netstat -an|grep 445 tcp4 0 0 *.445 *.* LISTEN Any thoughts would be appreciated, Paulb

...pcap reports might help for >additional debugging (whether to find a >workaround or to find a potential bug in Syslinux)? > In my case there is not a relevant pcap file; syslinux.efi gets perfectly transferred and when it tries to get ldlinux.e64 it fails locating the Binding Service for UDP4, before aborting w/o generating any additional traffic. >_ I am guessing that these >systems are actually using UEFI x86_64. If >they are not, then this would be a potential reason for strange >behaviors regarding syslinux.efi and ldlinux.e64. > All my tests were conducted on 64...