search for: connectionless

...me host? If yes, probably you have to do > some sort of SNAT... > Thanks for the responses, I've just re-read man smb.conf and bind interfaces only mentions smbd and nmbd. Perhaps winbind ignores it. I am now guessing but it looks like winbind happily chatters CLDAP over UDP which is connectionless by definition but when it switches to TCP for LDAP it: * Opens a local socket which is on a "real" interface and sends that out, the VPN sends it and becomes the source IP * The SYN-ACK comes back (the other end doesn't care) * An RST is sent because there is no listening socket on t...

...ad around 500 entries in it - not sure that would have any effect on things. During the attack, the kernel logged a bunch of these: ip_conntrack: table full, dropping packet - Possibly the result of connection tracking? Does netfilter even track UDP "connections"? I thought UDP was connectionless. Is the only workaround for cases like this just to have larger connection tracking values in the kernel? Does that help with the ksoftirqd CPU use? Or is it best in this case to just not have it track connection state for DNS traffic at all and just forward the packets along? How is the idea...

Hello, I have used socketConnection to connect to a TCP server. I havent figured out a way to do the same with a UDP server. i.e I have a server listening on 9000, communicating via UDP. I would like to , from R, send packets to this server, This does not work u <- socketConnection('localhost',9000) Error in socketConnection("localhost", 9000, blocking = F) : cannot open

...to understand how netfilter works before filing a bug report. The described behaviour is perfectly normal. The 'nat' table is traversed for every _first_ packet of a connection. You can delete all nat rules, but already-established connections will remain active (and NATed). Due to the connectionless operation of UDP, we cannot tell UDP sessions apart if they use the same (scrip,srcport,dstip,dstport) tuple. Apart from that, your -t nat -I PREROUTING -j DROP rule will also only consider the first packet of every connection. It seems like you have some misunderstanding about the semantics....

...aptured (1736 bits) on interface 0 Ethernet II, Src: Vmware_72:06:06 (00:0c:29:72:06:06), Dst: Vmware_06:a9:58 (00:0c:29:06:a9:58) Internet Protocol Version 4, Src: 192.168.1.12 (192.168.1.12), Dst: 192.168.1.41 (192.168.1.41) User Datagram Protocol, Src Port: ldap (389), Dst Port: 65146 (65146) Connectionless Lightweight Directory Access Protocol LDAPMessage searchResEntry(3) "<ROOT>" [1 result] messageID: 3 protocolOp: searchResEntry (4) searchResEntry objectName: attributes: 1 item PartialAttributeList...

...ernet Protocol Version 4, *Src: 10.50.50.35, Dst: 10.50.50.85* *User Datagram Protocol*,*Src Port: 60549, Dst Port: 389* ??? Source Port: 60549 ??? Destination Port: 389 ??? Length: 99 ??? Checksum: 0x7950 [unverified] ??? [Checksum Status: Unverified] ??? [Stream index: 0] ??? [Timestamps] *Connectionless Lightweight Directory Access Protocol* ??? LDAPMessage searchRequest(10556) "<ROOT>" baseObject ??????? messageID: 10556 ??????? protocolOp: searchRequest (3) ??????????? searchRequest ??????????????? baseObject: ??????????????? scope: baseObject (0) ??????????????? derefAlia...

Hello I wonder how I could get my linux box to serve logins to a Windows Me box. At the moment samba is running but I cannot access home dirs (No user log on). Since ME (wireless card DWL+G520) accesses an AP (DI 624 - 192.168.0.1 + ADSL) and the card manager comes up at end of the booting process, I have no idea how to get a user log on box (To be honest I don't know if this is

...ection attempts will be rejected. This makes Asterisk unable to process TCP SIP traffic. Note that this only affects TCP/TLS, since UDP is connectionless. Also note that this does not affect chan_sip. Resolution PJProject has a compile-time constant that controls the maximum number of TCP connections that can be handled. Those...

...and, depending on the workload, result in a decent reduction in SMB requests from clients. Netlogon Ping over LDAP and LDAPS --------------------------------- Samba must query domain controller information via simple queries on the AD rootdse's netlogon attribute. Typically this is done via connectionless LDAP, using UDP on port 389. The same information is also available via classic LDAP rootdse queries over TCP. Samba can now be configured to use TCP via the new "client netlogon ping protocol" parameter to enable running in environments where firewalls completely block port 389 or UDP tr...

...and, depending on the workload, result in a decent reduction in SMB requests from clients. Netlogon Ping over LDAP and LDAPS --------------------------------- Samba must query domain controller information via simple queries on the AD rootdse's netlogon attribute. Typically this is done via connectionless LDAP, using UDP on port 389. The same information is also available via classic LDAP rootdse queries over TCP. Samba can now be configured to use TCP via the new "client netlogon ping protocol" parameter to enable running in environments where firewalls completely block port 389 or UDP tr...

...and, depending on the workload, result in a decent reduction in SMB requests from clients. Netlogon Ping over LDAP and LDAPS --------------------------------- Samba must query domain controller information via simple queries on the AD rootdse's netlogon attribute. Typically this is done via connectionless LDAP, using UDP on port 389. The same information is also available via classic LDAP rootdse queries over TCP. Samba can now be configured to use TCP via the new "client netlogon ping protocol" parameter to enable running in environments where firewalls completely block port 389 or UDP tr...

...and, depending on the workload, result in a decent reduction in SMB requests from clients. Netlogon Ping over LDAP and LDAPS --------------------------------- Samba must query domain controller information via simple queries on the AD rootdse's netlogon attribute. Typically this is done via connectionless LDAP, using UDP on port 389. The same information is also available via classic LDAP rootdse queries over TCP. Samba can now be configured to use TCP via the new "client netlogon ping protocol" parameter to enable running in environments where firewalls completely block port 389 or UDP tr...

*Dear All, I run the below tcp dump on my asterisk server tcpdump -i eth0 -n -s0 -v udp port 5060 I got the following result 20:29:48.596867 IP (tos 0x10, ttl 64, id 0, offset 0, flags [DF], proto 17, length: 373) SIP_PROXY_IP.5060 > Asterisk_IP.5060: UDP, length 345 What i need to know please what TTL means specifically and what is the best value og TTL and what is the lengh vale mean

diff -u -r -N openssh-2.9p1/channels.c openssh-2.9p1-ajf.1/channels.c --- openssh-2.9p1/channels.c Tue Apr 17 14:14:35 2001 +++ openssh-2.9p1-ajf.1/channels.c Wed Jun 6 23:25:36 2001 @@ -1815,13 +1815,25 @@ /* * getaddrinfo returns a loopback address if the hostname is * set to NULL and hints.ai_flags is not AI_PASSIVE + * + * Oh yeah? Setting hostname to NULL and hints.ai_flags to +

Hi, The last couple of days I''ve been trying to get back on the wxRuby-horse however I''ve ran into some problems while compiling/testing the subversion sources. Mind, the 1.9.2 official release works fine. Absolutely no problems whatsoever. The first hurdle was that the rake install target doesn''t work. It fails on rakewx.rb:145. Looking into it I found that

On Tuesday 22 March 2016 19:05:24 Richard W.M. Jones wrote: > This tedious workaround avoids a 0.26 second pause when using sgabios > (the Serial Graphics Adapter). It's basically a workaround for buggy > code in sgabios, but much easier than fixing the assembler. > --- > src/conn-socket.c | 32 +++++++++++++++++++++++++++++++- > 1 file changed, 31 insertions(+), 1

...and, depending on the workload, result in a decent reduction in SMB requests from clients. Netlogon Ping over LDAP and LDAPS --------------------------------- Samba must query domain controller information via simple queries on the AD rootdse's netlogon attribute. Typically this is done via connectionless LDAP, using UDP on port 389. The same information is also available via classic LDAP rootdse queries over TCP. Samba can now be configured to use TCP via the new "client netlogon ping protocol" parameter to enable running in environments where firewalls completely block port 389 or UDP tr...

...and, depending on the workload, result in a decent reduction in SMB requests from clients. Netlogon Ping over LDAP and LDAPS --------------------------------- Samba must query domain controller information via simple queries on the AD rootdse's netlogon attribute. Typically this is done via connectionless LDAP, using UDP on port 389. The same information is also available via classic LDAP rootdse queries over TCP. Samba can now be configured to use TCP via the new "client netlogon ping protocol" parameter to enable running in environments where firewalls completely block port 389 or UDP tr...

Dear all My laptop running Arch Linux is domain joined to the office AD domain. I run winbind locally (smb.conf below.) I can use Kerberos and cifs with autofs to make Windows shares appear on demand. pam_winbind etc just works. Lovely. I then fire up my laptop road-warrior VPN - I need to appear to be coming from the office for a lot of my customers. At this point my AD connection stops

Hi, I am looking networking together about 1000-2000 sites across the country. I've been looking through these mailing lists. Saw the thread from the person who had 1000+ running on Amazon, and how they essentially stripped all security out of it. Also know that the ChaosVPN uses tinc, for at least 130+ sites although I'm a bit fuzzy on the details for it. Are there any other cases of