Displaying 20 results from an estimated 500 matches similar to: "Bug#793921: tftpd-hpa: IPv6 address cannonization breaks IPv4"
2015 Aug 07
0
Bug#793921: tftpd-hpa: IPv6 address cannonization breaks IPv4
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
2012 Nov 21
3
ip6tables REJECT target 3s timeout
Hi,
I am trying to get ipv6 firewall running. I did a very simple ip6tables
rules and noticed very long running yum updates. I think that happened
because firewall is dropping outgoing packets to port 80. Well, I
thought to mitigate the issue and changed outgoing from drop to reject.
Now I try manually
# strace telnet 2a02:180:ffff:1::551f:b966 80
...
connect(3, {sa_family=AF_INET6,
2009 Jan 12
1
Rsync crash
Hello,
I'm using an rsync server on a Linux packages repository (deb packages)
to sync all mirrors.
The mirrors sync every 10 minutes. Most of the time, there is nothing to
sync, except a timestamp file, so the sync is pretty fast.
Anyway, after it has been working well for some time (between 2 and
24hours), the rsync daemon crashes. It is still running but seems to
retry something
2016 Oct 13
3
Bug 6870 resurfaced in Samba 4.2.10
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
2007 May 19
7
Puppet Trac throwing errors again for documentation pages
Hi,
https://reductivelabs.com/trac/puppet/wiki/DocumentationStart
https://reductivelabs.com/trac/puppet/wiki/PuppetIntroduction
https://reductivelabs.com/trac/puppet/wiki/PuppetMasters
https://reductivelabs.com/trac/puppet/wiki/PuppetBestPractice
- Max
2014 Jul 21
2
Feature Request: Ability to join a IPv4-Only DC, into a Dual-Stacked "Samba4 AC DC" PDC.
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
2014 Jul 18
1
Samba DC join fails - IPv4/IPv6 issue
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 ?
2013 Mar 10
1
Samba DC join fails - IPv4/IPv6 issue
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
2004 May 04
2
rsync 2.6.2 --daemon Problem
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
2016 May 31
2
[Bug 1071] New: nftables: set does not work within inet table with option flags interval
https://bugzilla.netfilter.org/show_bug.cgi?id=1071
Bug ID: 1071
Summary: nftables: set does not work within inet table with
option flags interval
Product: nftables
Version: unspecified
Hardware: x86_64
OS: All
Status: NEW
Severity: normal
Priority: P5
Component: nft
2015 Aug 06
0
Bug#793921: tftpd-hpa: IPv6 address cannonization breaks IPv4
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>
> >
> >
2016 Oct 17
2
Bug 6870 resurfaced in Samba 4.2.10
Hi,
So I did some digging into the source code, and I think I've found the
issue. Around line 120 of source3/libads/cldap.c:
for (i=0; i<num_servers; i++) {
NTSTATUS status;
status = cldap_socket_init(state->cldap,
NULL, /* local_addr */
state->servers[i],
&state->cldap[i]);
if (tevent_req_nterror(req, status)) {
return tevent_req_post(req, ev);
2006 Jan 11
2
Linux 4.2p1 crash during reverse name lookup
4.0p1 and 4.2p1 are affected for me, I'm using Linux based around a FC2
build (~2 years old).
I'm trying to login with password authentication from psftp.exe (part of
PuTTY) but it.
Maybe this bug isn't with OpenSSH itself but a supporting library, I
would appreciate your assistance in tracking down the problem.
I have tried getting a 'core' file out of SSH with
2008 Aug 11
0
rsync failure with error 12
I am running rsync over a VPN. The connection has been stable for some
time, but recently it has started failing. I am including the strace of
the failure below. Basically, the client disconnects typically with an
error 12. I have 3 other clients using the same openvpn/rsync
configuration, and those are stable, so I am fairly confident this is
something on this particular link.
The
2011 Nov 12
5
[Bug 1950] New: sshd tries to bind over and over to ::1 for several seconds
https://bugzilla.mindrot.org/show_bug.cgi?id=1950
Bug #: 1950
Summary: sshd tries to bind over and over to ::1 for several
seconds
Classification: Unclassified
Product: Portable OpenSSH
Version: 5.9p1
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
2000 Jan 17
1
pre27 compilation fails on Sol7 box
Something strange happens when I compile the pre27 SSH:
ocal/ssh//include -DETCDIR=\"/usr/local/ssh//etc\" \
-DSSH_PROGRAM=\"/usr/local/ssh//bin/ssh\" \
-DSSH_ASKPASS_DEFAULT=\"/usr/local/ssh//libexec/ssh/ssh-askpass\" \
-DHAVE_CONFIG_H -c atomicio.c
In file included from includes.h:106,
from atomicio.c:26:
fake-socket.h:30: parse error before
2013 Nov 08
1
Rsync hanging, even with timeout and contimeout specified
Here's the details and some debugging I did for starters, but I have no
idea where to proceed from here. Help please? Command to reproduce should
be in the strace output below.
-Dan
P.S. Sorry for sending this a few times; I think only one will make it
through to the list since I wasn't subscribed initially.
$ rsync --version
rsync version 3.1.0 protocol version 31
Copyright (C)
2004 Jun 06
1
Daemon + ipv6 bug report
Hi all.
I'm just reporting some strange (fatal) behaviour when running
rsync --daemon on an IPv6-enabled box. It gets a fatal error
when trying to bind to the same address twice.
strace output:
bind(4, {sa_family=AF_INET6, sin6_port=htons(873), inet_pton(AF_INET6, "::", &sin6_addr), sin6_flowinfo=0, sin6_scope_id=0}, 28) = 0
bind(5, {sa_family=AF_INET, sin_port=htons(873),
2016 Oct 14
0
Bug 6870 resurfaced in Samba 4.2.10
Hai,
Did you check if ifconfig still shows ipv6 adresses. ( even ::1 )
Can you check that.
I have several with ipv6 on and severel only ipv4.
As of 4.1.17+ i didnt see this happing here. Now on 4.4.5
I think you have forgotten something.
Greetz,
Louis
> -----Oorspronkelijk bericht-----
> Van: samba [mailto:samba-bounces at lists.samba.org] Namens Rebecca Gellman
> via samba
2017 Jan 29
2
[PATCH tftpd-hpa] tftpd: don't use AI_CANONNAME and AI_ADDRCONFIG to resolve addresses for bind
AI_CANONNAME is only relevant when the resulting official name is used,
which is not the case in tftpd for the address to bind to. Also
AI_ADDRCONFIG isn't helpful. This flag is good for sockets used to
connect(2) somewhere. But for listening sockets it makes tftpd fail to
start when -a 0.0.0.0:69 is passed and no network device is up yet.
This addresses Debian bug