search for: 6724

...01). Thanks to Matthias Klose <doko at debian.org> for reporting. * Lintian cleaning. Checksums-Sha1: 5a6c4dbdb342caa1b23b9029681bda55c781b680 2243 blktap_2.0.90-4.dsc f5c1e09e7ece3a9698827170c5155b54c04c91ce 235286 blktap_2.0.90.orig.tar.gz a0ecdcda10e4717ed1090f36fba21538fd566699 6724 blktap_2.0.90-4.debian.tar.xz Checksums-Sha256: ca3f14e3a5dd17aa9d3e93c94348ebf5a653fb719ce6309279de19d7f0285537 2243 blktap_2.0.90-4.dsc a2a46a6c114ad4041802fd805a97cb66856003f6e3c1f157907b934fdf4c40ee 235286 blktap_2.0.90.orig.tar.gz e4c4cd4b0e76e79df0b4fbdf7a2d7e51072e27a6d23b44c750e70ddd79fb...

...rying the next. So I gave a stab at implementing RFC 8305. This patch implements part of it in sshconnect.c. * It does not do section 3 (initiation of asynchronous DNS queries, a SHOULD). * It does not do section 4 (sorting of resolved destination addresses). That means it does not do the RFC 6724 address sort which is a MUST. The order is still the one from getaddrinfo(3). * It implements section 5 (initiation of asynchronous connection attempts). It paces the connection attempts 250 milliseconds appart as recommended. Once a connection attempt succeeds it cancels all other initiat...

...Sandy, Thanks! Curious. Do you have any other interfaces? ifconfig -a should show them all including loopback. What is puzzling me is that it should not even attempt to use IPv6 to reach a global address when it only has a link-local address. It should gracefully fall back to IPv4 (as per RFC 6724 or RFC 3484 depending on the kernel version). Since you have an IPv4 address and I assume an IPv4 connection, then this should work over IPv4. I'm assume that you do not have an /etc/gai.conf file installed? David ------------------------------------------------------------------------ Dr D...

...other interfaces? ifconfig -a should >> show them all including loopback. >> >> What is puzzling me is that it should not even attempt to use IPv6 to >> reach a global address when it only has a link-local address. It should >> gracefully fall back to IPv4 (as per RFC 6724 or RFC 3484 depending on >> the kernel version). Since you have an IPv4 address and I assume an IPv4 >> connection, then this should work over IPv4. >> >> I'm assume that you do not have an /etc/gai.conf file installed? >> >> David >> ------------------...

I am a complete novice in this area so please bear with me. I have installed nut version 2.6.2-1 for my debian 64bit system. I am trying to implement 'nut' for a new VIX2120 home UPS and have determined that I need the richcomm_usb driver [usb 0925:1234]. But it is not in /lib/nut although referenced in the documentation (driver.list) How do get hold of a copy? Due to ignorance I am not

...t;>>> show them all including loopback. >>>> >>>> What is puzzling me is that it should not even attempt to use IPv6 to >>>> reach a global address when it only has a link-local address. It should >>>> gracefully fall back to IPv4 (as per RFC 6724 or RFC 3484 depending on >>>> the kernel version). Since you have an IPv4 address and I assume an >>>> IPv4 >>>> connection, then this should work over IPv4. >>>> >>>> I'm assume that you do not have an /etc/gai.conf file installed? &g...

...or name resolution. Nope. See slide 9 & 10. It is common to use DNS but any IPv6 enabled name resolution method might be used (depending on the situation). > Does that mean that if you have a DNS AAAA record, then it will use IPv6? Usually, yes. BUT it is quite complex. See RFC 6724 and RFC 6555. These two RFCs do not provide the full answer. I would strongly recommend IPv6 training, such as ours (see www.ipv6training.com <http://www.ipv6training.com> ) as this is far from simple. It makes IPv6 consultants very happy though. 😉 >What about mDNS? LLMNR, mDNS (ak...

...>>>> >>>>>> What is puzzling me is that it should not even attempt to use IPv6 to >>>>>> reach a global address when it only has a link-local address. It >>>>>> should >>>>>> gracefully fall back to IPv4 (as per RFC 6724 or RFC 3484 depending >>>>>> on >>>>>> the kernel version). Since you have an IPv4 address and I assume an >>>>>> IPv4 >>>>>> connection, then this should work over IPv4. >>>>>> >>>>>> I'...

...used, 1986456k free, 890236k cached > > PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND > 1918 operador 20 0 543m 70m 21m S 14 3.7 5401:22 Radit > 1904 operador 20 0 268m 20m 13m S 6 1.1 2804:29 raditcast > 1739 operador 9 -11 180m 6724 4644 S 4 0.3 2105:52 pulseaudio > 24929 operador 20 0 4460 1924 744 S 4 0.1 11:31.26 lame > > Radit its the automatizer, raditcast is the wrapper that uses lame to > encode and makes connection to icecast2 > > > >> I don't have an immediate idea where...

...ous. Do you have any other interfaces? ifconfig -a should > show them all including loopback. > > What is puzzling me is that it should not even attempt to use IPv6 to > reach a global address when it only has a link-local address. It should > gracefully fall back to IPv4 (as per RFC 6724 or RFC 3484 depending on > the kernel version). Since you have an IPv4 address and I assume an IPv4 > connection, then this should work over IPv4. > > I'm assume that you do not have an /etc/gai.conf file installed? > > David > ----------------------------------------------...

On 4/11/2017 9:24 AM, David Holder wrote: > Hi Phil, > > NBT name resolution is IPv4 only. Samba does work over IPv6, but > NetBIOS name resolution is and always will be IPv4 only. It is a > feature of the protocol not Samba. How can this be? Everything I have read about SMB for the last 20 years or so has said that it is based entirely on NetBIOS, and has no concept even of

...g me is that it should not even attempt to use IPv6 >>>>>>>> to >>>>>>>> reach a global address when it only has a link-local address. It >>>>>>>> should >>>>>>>> gracefully fall back to IPv4 (as per RFC 6724 or RFC 3484 depending >>>>>>>> on >>>>>>>> the kernel version). Since you have an IPv4 address and I assume an >>>>>>>> IPv4 >>>>>>>> connection, then this should work over IPv4. >>>>>>...

Hey Guys, We have a central server which runs centos, most of the client machines run on windows. Does anybody know of a solution whereby we can manage antivirus for all the clients from the centos server? I know there are management consoles for managing antivirus on windows but we dont want to run a windows server.. Anybody have any ideas? Or are we just screwed and need to have a windows

...8305. This patch implements part of >> it in sshconnect.c. >> >> * It does not do section 3 (initiation of asynchronous DNS queries, a >> SHOULD). >> * It does not do section 4 (sorting of resolved destination >> addresses). That means it does not do the RFC 6724 address sort >> which is a MUST. The order is still the one from getaddrinfo(3). >> * It implements section 5 (initiation of asynchronous connection >> attempts). It paces the connection attempts 250 milliseconds appart >> as recommended. Once a connection attempt suc...

...fconfig -a should >>> show them all including loopback. >>> >>> What is puzzling me is that it should not even attempt to use IPv6 to >>> reach a global address when it only has a link-local address. It should >>> gracefully fall back to IPv4 (as per RFC 6724 or RFC 3484 depending on >>> the kernel version). Since you have an IPv4 address and I assume an >>> IPv4 >>> connection, then this should work over IPv4. >>> >>> I'm assume that you do not have an /etc/gai.conf file installed? >>> >>&...

...g me is that it should not even attempt to use IPv6 >>>>>>>> to >>>>>>>> reach a global address when it only has a link-local address. It >>>>>>>> should >>>>>>>> gracefully fall back to IPv4 (as per RFC 6724 or RFC 3484 depending >>>>>>>> on >>>>>>>> the kernel version). Since you have an IPv4 address and I assume an >>>>>>>> IPv4 >>>>>>>> connection, then this should work over IPv4. >>>>>>...

I have a following problem: The call qplot(wg, v.realtime, data=df.best.medians$gv1, colour=sp, geom="boxplot") works nice: for each value of the wg factor I get two box-plots (two levels in the sp factor) in different colours, side-by-side, centered at the wg x-axis. However, I want to separate the data belonging to different levels of the n factor, so I add the facets option:

...g loopback. >>>>> >>>>> What is puzzling me is that it should not even attempt to use IPv6 to >>>>> reach a global address when it only has a link-local address. It >>>>> should >>>>> gracefully fall back to IPv4 (as per RFC 6724 or RFC 3484 depending >>>>> on >>>>> the kernel version). Since you have an IPv4 address and I assume an >>>>> IPv4 >>>>> connection, then this should work over IPv4. >>>>> >>>>> I'm assume that you do not...

...t;>>> IPv6 >>>>>>>>>> to >>>>>>>>>> reach a global address when it only has a link-local address. It >>>>>>>>>> should >>>>>>>>>> gracefully fall back to IPv4 (as per RFC 6724 or RFC 3484 >>>>>>>>>> depending >>>>>>>>>> on >>>>>>>>>> the kernel version). Since you have an IPv4 address and I assume >>>>>>>>>> an >>>>>>>>>> I...

...t;>>> IPv6 >>>>>>>>>> to >>>>>>>>>> reach a global address when it only has a link-local address. It >>>>>>>>>> should >>>>>>>>>> gracefully fall back to IPv4 (as per RFC 6724 or RFC 3484 >>>>>>>>>> depending >>>>>>>>>> on >>>>>>>>>> the kernel version). Since you have an IPv4 address and I >>>>>>>>>> assume an >>>>>>>>>>...