similar to: [Bug 180] [PATCH] sshd sets no ToS bit on connections with IPv4-mapped IPv6 addresses

I know i'm new to the list but i'd like to propose something for tincd daemon. I'd like to mark all sockets established by a tincd process with a mark passed as an argument in the command line. What could be the purpose of this new option? The goal of this option is to be able to have several tincd process running at the same time using the same port but using different ip. In

Hi list, I just tried to add a second DC to an existing Samba4 domain using samba-tool (both hosts run latest samba4 git version). But the join failed, complaining about being unable to find a writeable DC: root at elektron:~# /opt/samba4/bin/samba-tool domain join linex.r00t.la DC Finding a writeable DC for domain 'linex.r00t.la' ERROR(exception): uncaught exception - Failed to find a

Guys, I'm facing this problem too: https://lists.samba.org/archive/samba/2013-March/172230.html I have two Samba4 AC DC, in both located in my office, dual-stacked, working like a charm. Now, I need to deploy a third DC, located within Amazon EC2, which does NOT have IPv6. But, samba-tool fails to join. How can I workaround this, without enabling a tunneled IPv6 within my EC2 ?

Take 2 at bouncing this to the rest of the original recipients through a different MTA, since mail.zytor.com refused to accept it the first time. Please re-add Jason Gunthorpe <jgg at obsidianresearch.com> and 793921 at bugs.debian.org to the CC for replies. On Wed, Jul 29, 2015 at 05:34:00PM +0930, Ron wrote: > > Hi Jason, > > On Tue, Jul 28, 2015 at 03:45:30PM -0600, Jason

List, I'm behind a dlink DSL-G604T wireless router. ssh client was hanging at: debug1: Entering interactive session. Telnet was having a similar problem to port 22, however a simple client.c I compiled was not. My java ssh client was also working. After some investigation, I noticed that the hang was after the system call: setsockopt(3, SOL_IP, IP_TOS, [16], 4) = 0 I noticed also that

Hi, The problem that setsockopt(IP_TOS) doesn't work on Cygwin is long fixed. Ages ago Microsoft changed the definition for IP_TOS when moving from winsock1 to winsock2 and IP_TOS in Cygwin didn't work all these years because nobody (that's especialy me) realized that we were still using the old winsock1 value. This has been fixed since 2005, though. Patch below. Corinna Index:

Hi, I noticed that the Type of Service bit for minimize delay is set in client->server packets only. Is this OS-specific or is there another reason for this? Here is a tcpdump of an interactive connection: 217.225.98.212.22 > 134.169.34.19.45870: P 1:49(48) ack 48 win 12008 (DF) 134.169.34.19.45870 > 217.225.98.212.22: P 48:96(48) ack 49 win 25416 (DF) [tos 0x10] 217.225.98.212.22

https://bugzilla.mindrot.org/show_bug.cgi?id=1733 Summary: Enhance support for QoS (ToS) by supporting DSCP/CS and adding option Product: Portable OpenSSH Version: 5.4p1 Platform: All OS/Version: Linux Status: NEW Severity: enhancement Priority: P2 Component: ssh AssignedTo:

Hi, I've a problem with rsync 2.6.2 and the daemon. I've installed it precisly as I did with 2.6.0 (I've tried before with 2.6.1 and was having the same problems as now with 2.6.2). When I try to a rsync --daemon command the rsync offcourse finishes, but in the log file it says 2004/05/04 21:15:10 [22369] rsyncd version 2.6.2 starting, listening on port 873 2004/05/04 21:15:10

Hi, Dear OpenSSH support, I'm writing to ask whether this bug is fixed in your openSSH 6.0. If no, do you have any plan? https://bugzilla.redhat.com/show_bug.cgi?id=640857 Regards, Carol

https://bugzilla.mindrot.org/show_bug.cgi?id=2037 Priority: P5 Bug ID: 2037 Assignee: unassigned-bugs at mindrot.org Summary: sshd Causing DNS Queries on ListenAddress when binding to IPV4 and IPV6 addresses on AIX Severity: normal Classification: Unclassified OS: AIX Reporter: caleblloyd at

According to this bugzilla entry, bug 6870 has been fixed as of at least version 3.5: https://bugzilla.samba.org/show_bug.cgi?id=6870 However, I assert that it is present in 4.2.10, which ships with Debian Jessie. On my home network (IPv4 and IPv6), a box with Samba 4.2.10 with IPv6 disabled (via sysctl), will fail to contact a DC because the IPv6 connect fails immediately before the v4

Hey guys! To make the adoption of IPv6 networks with Samba4 more smooth / robust, I think that it is vital to give to Samba4, the ability for it, to join a IPv4-Only Secondary DC, into a Dual-Stacked Primary DC. This doesn't work today. Otherwise, these days to enable IPv6 within a "Samba4 AC DC" network, it is a requirement to enable it, simultaneously, on each and every network

http://bugzilla.mindrot.org/show_bug.cgi?id=401 yoshfuji at linux-ipv6.org changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|misc. ipv4-mapped address |ipv4 mapped address (ipv4 in |support fix |ipv6) and ipv6 support fix ------- Additional

Hi, we've seen SELinux reports from our users that dovecot tried to use something that needs CAP_NET_ADMIN capability. Before enabling it, we would like to know where it originated from. I've checked the sources, but was not able to find anything that would require this capability. Do you know for what it is used? CAP_NET_ADMIN Perform various network-related operations: * interface

Hi, I have a testing multihome setup, with the default gateway being one of the links and using policy routing to honor requests for a specific link. Everything works as expected when I request a specific IP to bind to. But if I request a specific interface things fall apart in ways that I can not explain: default gw (WORKS) ---------- rabbit@Thesaurus:~$ ping -c 1 yahoo.com PING yahoo.com

On Sat, Jan 7, 2017 at 2:30 PM, Peter Moody <mindrot at hda3.com> wrote: > so I spent a bit of time looking at this and it seems like the only > way to go, at least if I want to keep it in ssh_connect_direct(), is > to use pthreads. further, it seems like getting that accepted is > something of a long shot: Sorry, pthreads is a non-starter. I would have thought that using

On 10/15/20 2:02 PM, jeremy ardley wrote: >> how/where do I configure (just) the dovecot smtp-client -> submission_relay_host to only connect IPv4? > > It appears your host has A and AAAA records in your DNS. The clients will try IPV6 first if they see an AAAA record. > > If you don't need IPV6 for your host remove the AAAA record. All connections will then only use

Thanks to everyone for a fruitful discussion, links and ideas. The result is nearing a merge at https://github.com/networkupstools/nut/pull/2013 and seems to not upset CI on any platform, including Windows (which behaves funny WRT binding to the same host:port as many times as you ask). Ultimately the chosen logic is that if there was a `LISTEN * <port>` in `upsd.conf`, the depending on

Thanks to everyone for a fruitful discussion, links and ideas. The result is nearing a merge at https://github.com/networkupstools/nut/pull/2013 and seems to not upset CI on any platform, including Windows (which behaves funny WRT binding to the same host:port as many times as you ask). Ultimately the chosen logic is that if there was a `LISTEN * <port>` in `upsd.conf`, the depending on