similar to: [Bug 401] misc. ipv4-mapped address support fix

http://bugzilla.mindrot.org/show_bug.cgi?id=401 Summary: misc. ipv4-mapped address support fix Product: Portable OpenSSH Version: -current Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: sshd AssignedTo: openssh-unix-dev at mindrot.org ReportedBy:

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

http://bugzilla.mindrot.org/show_bug.cgi?id=401 ------- Additional Comments From yoshfuji at linux-ipv6.org 2003-01-06 12:20 ------- Created an attachment (id=194) --> (http://bugzilla.mindrot.org/attachment.cgi?id=194&action=view) patch to run openssh-3.5p1 on linux-2.2 & glibc-2.2(or later) This is modified patch for openssh-3.5p1. Patch is simplified. ------- You are

Hi, openssh-1.2.2p1 seems to have 2 problems on ipv6 (and ipv4 mapped addresses). 1. "BREAKIN ATTEMPT" warnings from ipv4 node 2. X forwarding The following patche fixes them. Thanks. diff -ru openssh-1.2.2p1/canohost.c openssh-1.2.2p1-20000308/canohost.c --- openssh-1.2.2p1/canohost.c Fri Jan 14 13:45:48 2000 +++ openssh-1.2.2p1-20000308/canohost.c Wed Mar 8 00:25:18 2000 @@

Hello, I am doing some tests with asterisk on a dual-stack environment. I have some doubts regarding asterisk binding addresses on a server with 2 network cards. According to asterisk documentation: /; With the current situation, you can do one of four things:/ /; a) Listen on a specific IPv4 address. Example: bindaddr=192.0.2.1/ /; b) Listen on a specific IPv6 address.

on systems that has separate IPv4/v6 socket layer (i.e. IPv4 packet does not get routed to AF_INET6 socket) rsync --daemon would accept IPv6 sessions only. open_socket_in() tries to deal with the situation, but it was not enough. here's the patch. (it is required on all *BSDs to accept both IPv4 and IPv6 connections with --daemon mode) itojun --- ? configure.lineno ? lib/dummy

On Thu, 19 Jul 2018 15:26:28 +0200 Thomas Glanzmann via samba <samba at lists.samba.org> wrote: > Hello, > I use Samba AD in Version 4.8.3 and would like to run it on IPv4 und > IPv6 in order to be able to have Samba acting as IPv6 DNS Server. > However since I have problem with sysprep domain join as soon as Samba > advertises its own Domain Controller Hostname as IPv4 and

Hello, I use Samba AD in Version 4.8.3 and would like to run it on IPv4 und IPv6 in order to be able to have Samba acting as IPv6 DNS Server. However since I have problem with sysprep domain join as soon as Samba advertises its own Domain Controller Hostname as IPv4 and IPv6 address, I would like to tell Samba to run on both protocols but only resolve to an IPv4 address. So in short: When I

On Wed, Jul 29, 2015 at 05:34:00PM +0930, Ron wrote: > > This commit: > > > > tftp: convert IPv6-mapped IPv4 addresses to IPv4 > > > > If we receive IPv4 addresses mapped to IPv6, convert them back to IPv4 > > so that mapping scripts which use \i behave sanely. > > > > Signed-off-by: H. Peter Anvin <hpa at zytor.com> > > > >

The problem shows in the following log snippet. The numeric address of the peer (localhost in this case) is garbage. rsyncd[32671]: reverse name lookup failed rsyncd[32671]: rsync: forward name lookup for failed: Name or service not known rsyncd[32671]: rsync on debian/ from UNKNOWN (::10fa:ffbf:a426:608%5) rsyncd[32671]: wrote 616 bytes read 70 bytes total size 143069 I am using linux

Using CentOS 6.9 with IPv4 configured, and _not_ disabling IPv6 yet, we want this NFS client system to prefer the IPv4 address of a dual-stack remote NFS server, which has both A and AAAA records in DNS. Otherwise we get a minutes long pause while automounter tries to mount the IPv6 address -- I can see automounter's '/bin/mount' running, using the AAAA record of the server, until

On 07/29/2015 01:45 AM, Ron via Syslinux wrote: > > 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

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

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

http://bugzilla.mindrot.org/show_bug.cgi?id=180 djm at mindrot.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- Additional Comments From djm at mindrot.org 2002-04-26 16:55

Hi All, I'm Kendell, and I'm new to the list. I've been working on a SSH VPN client. I've noticed a possible glitch/bug with OpenSSH on various platforms (Linux and various BSD, but Windows seems to be OK for some reason.) The SSH VPN client can configure SSH tunnels using DNS names instead of IP addresses. It seems that if the client "rapidly" configures a number of

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

Jim Klimov via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> writes: > I've recently found that at least on my test box the `LISTEN *` line had > only set up an IPv4 `0.0.0.0` listener but not an IPv6 `::0` listener for > `upsd`. Interesting. On one system I checked, I have 4 explicit directives for 127.0.0.1, ::1, and the LAN on v4/v6. On another, I have an empty

Jim Klimov via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> writes: > I've recently found that at least on my test box the `LISTEN *` line had > only set up an IPv4 `0.0.0.0` listener but not an IPv6 `::0` listener for > `upsd`. Interesting. On one system I checked, I have 4 explicit directives for 127.0.0.1, ::1, and the LAN on v4/v6. On another, I have an empty