similar to: Settings for safe interop between Samba and NFS

Test both the TLS enabled and fallback paths. nbd-server doesn't appear to support TLS at all, and qemu-nbd is known not to allow fallback to unencrypted, and therefore it only makes sense to test nbdkit at the moment. --- .gitignore | 4 ++++ TODO | 3 --- interop/Makefile.am | 54 +++++++++++++++++++++++++++++++++++++++++++++ interop/interop.c | 30

This neutral refactoring adds -DTLS_MODE. We can in future change the requested TLS mode, but not in this commit. It also checks that nbd_get_tls_negotiated returns true after connecting, when the requested mode was set to LIBNBD_TLS_REQUIRE. --- interop/Makefile.am | 4 ++++ interop/interop.c | 26 ++++++++++++++++++++------ 2 files changed, 24 insertions(+), 6 deletions(-) diff --git

On Fedora 29, nbdkit-devel at 1.10.4 is too old for any of the tests/Makefile.am actions to run, but this also means we don't create any tls pki/ or keys.psk files that we then want to reuse during qemu testing, as evidenced by 'make check' failures such as: FAIL: interop-qemu-nbd-tls-certs ================================ qemu-nbd: Unable to access credentials

The test interop-qemu-nbd-tls-certs frequently fails on slow (32 bit) machines in Fedora Koji. (Is crypto slow on these already overloaded machines?) As we cannot wait for a signal when qemu-nbd is ready start serving, we have to use a sleep. The current sleep is 5 seconds, which is not long enough. Making the sleep longer would work but is inconsiderate for people using faster machines.

https://bugzilla.mindrot.org/show_bug.cgi?id=2639 Bug ID: 2639 Summary: PuTTY interop tests broken Product: Portable OpenSSH Version: 7.3p1 Hardware: All OS: Linux Status: NEW Severity: normal Priority: P5 Component: Regression tests Assignee: unassigned-bugs at mindrot.org

On 9/17/19 5:35 PM, Richard W.M. Jones wrote: > This neutral refactoring adds -DTLS_MODE. We can in future change the > requested TLS mode, but not in this commit. > > It also checks that nbd_get_tls_negotiated returns true after > connecting, when the requested mode was set to LIBNBD_TLS_REQUIRE. > --- > interop/Makefile.am | 4 ++++ > interop/interop.c | 26

We're setting up a connection with Level3's voip system and when we use Asterisk or make or recv calls we get an initial pulsing noise. Level3's Interop team explains that's their RTP extension headers and Asterisk apparently doesn't know what to do with it. He said we need to either ignore or of course let the traffic pass. Has anyone heard of this before? I understand the

Has anyone done interop testing with Level 3 and Asterisk. If so, would you be willing to share your experiences. Gene -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20050308/061aea35/attachment.htm

Does anybody know how big a presence Asterisk and/or Digium will make at Networld Interop this year? I have a part-time guy that is building an Asterisk system for us (in a proof of concept fashion before we do a full switch to it) that I would like to take, but I don't want to waste his time if it is going to just be a "yeah, try our product" booth and not something he

On 9/17/19 5:35 PM, Richard W.M. Jones wrote: > Test both the TLS enabled and fallback paths. > > nbd-server doesn't appear to support TLS at all, and qemu-nbd is known > not to allow fallback to unencrypted, and therefore it only makes > sense to test nbdkit at the moment. > --- > .gitignore | 4 ++++ > +interop_nbdkit_tls_certs_allow_enabled_SOURCES =

Dear all, I have a SUN server running as ClearCase view-server and am using Samba for Interop. Today I updated Samba from 3.0.21c to 3.0.24 and now I cannot mount/start my views from windows!! MVFS error log on my windows client gives "{8 pid/tid 49800000c58/85fdf178} MvfsFsNotification: Unsupported filesystem type (6)" Samba logs don't show any error... Trying other

On Sun, Dec 07, 2014 at 05:35:37PM +0100, Johann Hartwig Hauschild wrote: > > I just had a look at the kernel-docs and the discussion here in november. > This issue should not be happening if I build a pre-3.3-kernel with > CONFIG_RELOCATABLE=y, CONFIG_EFI=y and CONFIG_EFI_STUB=y, right? Those are allready at those values at

Hi everybody, I've connected Asterisk 1.2.5 (libpri 1.2.2, zaptel 1.2.4, Linux 2.6.13.2) to an Avaya-Tenovis PBX via a PRI/E1-line. Calls from SIP-phones via * to the PBX work fine. However, incoming calls to * only result in: -- XXX Missing handling for mandatory IE 24 (cs0, Channel Identification) XXX -- which seems to be an * problem, because a Windows-fax-machine works fine on a PRI

Hi all, I spent the past days reading the mailing list archive, but still I have some questions to ask. Moreover, a detailed report of what I attempted can be useful for others. Goal: having a remote SMB or NFS share, mount it locally and re-share it using SAMBA. The remote SMB/NFS share will _not_ be directly used by users; it will be used only through the local samba "proxy". NT

Hello, I set up NFSv4 server. To make sure I set vfs.nfsd.server_min_nfsvers=4. I can check its version, for example, by tcpduming and then I can see in wireshark lines like: Network File System Program Version: 4 V4 Procedure: COMPOUND.... .... is there any easier way to check its version? I see there is nfsstat -e option which shows delegs and locks. But all other ones are combined with nfsv3

Am 07.12.2014 schrieb Geert Stappers: > On Sun, Dec 07, 2014 at 05:35:37PM +0100, Johann Hartwig Hauschild wrote: > > > > I just had a look at the kernel-docs and the discussion here in november. > > This issue should not be happening if I build a pre-3.3-kernel with > > CONFIG_RELOCATABLE=y, CONFIG_EFI=y and CONFIG_EFI_STUB=y, right? > > Those are allready at

On 11/20/20 1:26 PM, Michael B Allen wrote: > Thanks for the inputs but my problem has nothing to do with NFS. Do you think that because you saw "krbupdate" in /etc/services? The problem you've described is definitely an NFSv3 problem.? The connections causing the client to hang are portmap connections. They're dynamic, and don't necessarily conform to /etc/services.

https://bugs.freedesktop.org/show_bug.cgi?id=73200 Priority: medium Bug ID: 73200 Assignee: nouveau at lists.freedesktop.org Summary: vdpau-GL interop fails due to different screen objects Severity: normal Classification: Unclassified OS: All Reporter: ystreet00 at gmail.com Hardware: Other

Hello all... I''m migrating a nfs server from linux to solaris, and all clients(linux) are using read/write block sizes of 8192. That was the better performance that i got, and it''s working pretty well (nfsv3). I want to use all the zfs'' advantages, and i know i can have a performance loss, so i want to know if there is a "recomendation" for bs on nfs/zfs, or

I have an NFS server and NFS client separated by a firewall. Both servers are FreeBSD 7.1. Server configuration: nfs_server_enable="YES" nfs_server_flags="-t -n 4" rpcbind_enable="YES" mountd_flags="-r -p 737" mountd_enable="YES" The firewall allows tcp and udp to port 111, but only tcp to ports 2049 and 737 (configured for mountd, see above).