[Samba] Update
David Holder
david.holder at erion.co.uk
Mon Mar 2 10:20:34 MST 2015
Hi Roland,
It will be useful to see the resolv.conf. However, I don't think that
this is a name resolution issue as it is clear that git.samba.org is
being resolved to at least the v6 address. If that works then A & AAAA
records should be returned to the resolver regardless of the transport
used. There must be something else going on as well.
Could try
host -t a git.samba.org
and
host -t aaaa git.samba.org
Just to be prove it...
David
------------------------------------------------------------------------
Dr David Holder CEng FIET MIEEE
Erion Ltd, An Cala, Inverkirkaig, Lochinver, Sutherland, IV27 4LR, UK
Reception: +44 (0)1422 207000
Direct Dial: +44 (0)131 2026317
http://www.erion.co.uk
Registered in England and Wales. Registered Number 3521142
Registered Office: Newtons, 49 Coniscliffe Road, Darlington, County
Durham, DL3 7EH, UK
VAT Number: GB 698 3633 78
On 02/03/2015 17:08, Rowland Penny wrote:
> On 02/03/15 16:45, sandy.napoles at eccmg.cupet.cu wrote:
>> root at samba:/home/samba-master# git pull
>> error: Failed to connect to 2001:638:603:d06e::80:230: Network is
>> unreachable while accessing http://git.samba.org/samba.git/info/refs
>> fatal: HTTP request failed
>> root at samba:/home/samba-master#
>>
>>
>>
>>> On 02/03/15 16:21, sandy.napoles at eccmg.cupet.cu wrote:
>>>> My OS is Debian 7 and I only writte git pull
>>>>
>>>>> On 02/03/15 15:05, sandy.napoles at eccmg.cupet.cu wrote:
>>>>>> ifconfig -a
>>>>>> eth0 Link encap:Ethernet HWaddr 00:0c:29:82:ec:80
>>>>>> inet addr:172.18.68.8 Bcast:172.18.68.31
>>>>>> Mask:255.255.255.224
>>>>>> inet6 addr: fe80::20c:29ff:fe82:ec80/64 Scope:Link
>>>>>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>>>>>> RX packets:107940 errors:0 dropped:0 overruns:0 frame:0
>>>>>> TX packets:109315 errors:0 dropped:0 overruns:0
>>>>>> carrier:0
>>>>>> collisions:0 txqueuelen:1000
>>>>>> RX bytes:14394078 (13.7 MiB) TX bytes:20253880
>>>>>> (19.3 MiB)
>>>>>>
>>>>>> lo Link encap:Local Loopback
>>>>>> inet addr:127.0.0.1 Mask:255.0.0.0
>>>>>> inet6 addr: ::1/128 Scope:Host
>>>>>> UP LOOPBACK RUNNING MTU:16436 Metric:1
>>>>>> RX packets:252 errors:0 dropped:0 overruns:0 frame:0
>>>>>> TX packets:252 errors:0 dropped:0 overruns:0 carrier:0
>>>>>> collisions:0 txqueuelen:0
>>>>>> RX bytes:38555 (37.6 KiB) TX bytes:38555 (37.6 KiB)
>>>>>>
>>>>>>
>>>>>> ip -f inet6 route
>>>>>> fe80::/64 dev eth0 proto kernel metric 256
>>>>>>
>>>>>>
>>>>>>
>>>>>>> Thanks. No other interfaces (ifconfig -a)?
>>>>>>>
>>>>>>> Also output of
>>>>>>>
>>>>>>> ip -f inet6 route
>>>>>>>
>>>>>>> would be useful.
>>>>>>>
>>>>>>> David
>>>>>>> ------------------------------------------------------------------------
>>>>>>>
>>>>>>> Dr David Holder CEng FIET MIEEE
>>>>>>>
>>>>>>> Erion Ltd, An Cala, Inverkirkaig, Lochinver, Sutherland, IV27
>>>>>>> 4LR, UK
>>>>>>>
>>>>>>> Reception: +44 (0)1422 207000
>>>>>>>
>>>>>>> Direct Dial: +44 (0)131 2026317
>>>>>>>
>>>>>>> http://www.erion.co.uk
>>>>>>>
>>>>>>>
>>>>>>> Registered in England and Wales. Registered Number 3521142
>>>>>>> Registered Office: Newtons, 49 Coniscliffe Road, Darlington, County
>>>>>>> Durham, DL3 7EH, UK
>>>>>>> VAT Number: GB 698 3633 78
>>>>>>>
>>>>>>> On 02/03/2015 14:26, sandy.napoles at eccmg.cupet.cu wrote:
>>>>>>>> in /etc/gai.conf all is coment
>>>>>>>>
>>>>>>>>> Hi 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 David Holder CEng FIET MIEEE
>>>>>>>>>
>>>>>>>>> Erion Ltd, An Cala, Inverkirkaig, Lochinver, Sutherland, IV27
>>>>>>>>> 4LR,
>>>>>>>>> UK
>>>>>>>>>
>>>>>>>>> Reception: +44 (0)1422 207000
>>>>>>>>>
>>>>>>>>> Direct Dial: +44 (0)131 2026317
>>>>>>>>>
>>>>>>>>> http://www.erion.co.uk
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Registered in England and Wales. Registered Number 3521142
>>>>>>>>> Registered Office: Newtons, 49 Coniscliffe Road, Darlington,
>>>>>>>>> County
>>>>>>>>> Durham, DL3 7EH, UK
>>>>>>>>> VAT Number: GB 698 3633 78
>>>>>>>>>
>>>>>>>>> On 02/03/2015 13:10, sandy.napoles at eccmg.cupet.cu wrote:
>>>>>>>>>> eth0 Link encap:Ethernet HWaddr d0:27:88:64:e4:01
>>>>>>>>>> inet addr:172.18.70.100 Mask:255.255.255.224
>>>>>>>>>> inet6 addr: fe80::d227:88ff:fe64:e401/64
>>>>>>>>>> Scope:Link
>>>>>>>>>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>>>>>>>>>> RX packets:1413908 errors:0 dropped:0 overruns:0
>>>>>>>>>> frame:0
>>>>>>>>>> TX packets:447039 errors:0 dropped:0 overruns:0
>>>>>>>>>> carrier:0
>>>>>>>>>> collisions:0 txqueuelen:1000
>>>>>>>>>> RX bytes:1693689457 (1.5 GiB) TX bytes:52974612
>>>>>>>>>> (50.5
>>>>>>>>>> MiB)
>>>>>>>>>> Interrupt:43 Base address:0xc000
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> traceroute6 git.samba.org
>>>>>>>>>> traceroute to git.samba.org (2001:638:603:d06e::80:230), 30 hops
>>>>>>>>>> max,
>>>>>>>>>> 80
>>>>>>>>>> byte packets
>>>>>>>>>> connect: Network is unreachable
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> Hi Sandy,
>>>>>>>>>>>
>>>>>>>>>>> Please can you provide the output from an *i**fconfig -a*
>>>>>>>>>>> command?
>>>>>>>>>>>
>>>>>>>>>>> This should give an idea of what is going on. Turning off IPv6
>>>>>>>>>>> will
>>>>>>>>>>> not
>>>>>>>>>>> be necessary if you can find the actual cause of the problem.
>>>>>>>>>>>
>>>>>>>>>>> You would not get this error message if you only have a link
>>>>>>>>>>> local
>>>>>>>>>>> address configured on your interface. You must have some
>>>>>>>>>>> form of
>>>>>>>>>>> global
>>>>>>>>>>> address.
>>>>>>>>>>>
>>>>>>>>>>> Also, the IPv6 address is that of git.samba.org not samba.org.
>>>>>>>>>>> You
>>>>>>>>>>> could
>>>>>>>>>>> try:
>>>>>>>>>>>
>>>>>>>>>>> *traceroute6 git.samba.org.*
>>>>>>>>>>>
>>>>>>>>>>> Best Regards,
>>>>>>>>>>> David
>>>>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>>>>
>>>>>>>>>>> Dr David Holder CEng FIET MIEEE
>>>>>>>>>>>
>>>>>>>>>>> Erion Ltd, An Cala, Inverkirkaig, Lochinver, Sutherland, IV27
>>>>>>>>>>> 4LR,
>>>>>>>>>>> UK
>>>>>>>>>>>
>>>>>>>>>>> Reception: +44 (0)1422 207000
>>>>>>>>>>>
>>>>>>>>>>> Direct Dial: +44 (0)131 2026317
>>>>>>>>>>>
>>>>>>>>>>> http://www.erion.co.uk
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Registered in England and Wales. Registered Number 3521142
>>>>>>>>>>> Registered Office: Newtons, 49 Coniscliffe Road, Darlington,
>>>>>>>>>>> County
>>>>>>>>>>> Durham, DL3 7EH, UK
>>>>>>>>>>> VAT Number: GB 698 3633 78
>>>>>>>>>>>
>>>>>>>>>>> On 28/02/2015 18:38, Reindl Harald wrote:
>>>>>>>>>>>> Am 28.02.2015 um 19:13 schrieb sandy.napoles at eccmg.cupet.cu:
>>>>>>>>>>>>> I do not working with ipv6, I have disable, but I have the
>>>>>>>>>>>>> same
>>>>>>>>>>>>> error,
>>>>>>>>>>>>> I
>>>>>>>>>>>>> can read in internet that this ipv6 ip
>>>>>>>>>>>>> 2001:638:603:d06e::80:230:
>>>>>>>>>>>>> belong
>>>>>>>>>>>>> to url samba.org....
>>>>>>>>>>>>>
>>>>>>>>>>>>> If I try to connect to this url using some navegator I
>>>>>>>>>>>>> connected
>>>>>>>>>>>>> perfect....but when I run git pull using command line I
>>>>>>>>>>>>> can not
>>>>>>>>>>>>> connect..
>>>>>>>>>>>> the question is *how* did you disable ipv6 - when ifconfig
>>>>>>>>>>>> shows
>>>>>>>>>>>> a
>>>>>>>>>>>> "link local" ipv6 address the stack is *not* entirely disabled
>>>>>>>>>>>>
>>>>>>>>>>>> [root at srv-rhsoft:~]$ ifconfig eth0
>>>>>>>>>>>> eth0: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST> mtu
>>>>>>>>>>>> 1500
>>>>>>>>>>>> ether 24:be:05:1a:c0:27 txqueuelen 100
>>>>>>>>>>>> (Ethernet)
>>>>>>>>>>>> RX packets 2460 bytes 577531 (563.9 KiB)
>>>>>>>>>>>> RX errors 0 dropped 0 overruns 0 frame 0
>>>>>>>>>>>> TX packets 8722 bytes 1981928 (1.8 MiB)
>>>>>>>>>>>> TX errors 0 dropped 0 overruns 0 carrier 0
>>>>>>>>>>>> collisions 0
>>>>>>>>>>>> device interrupt 20 memory 0xf7e00000-f7e20000
>>>>>>>>>>>>
>>>>>>>>>>>>>> Am 28.02.2015 um 15:37 schrieb sandy.napoles at eccmg.cupet.cu:
>>>>>>>>>>>>>>> Hello list, Iam using samba4 as Domain Controller my verion
>>>>>>>>>>>>>>> Version
>>>>>>>>>>>>>>> 4.3.0pre1-GIT-068f9e2, but I have a little problem when I
>>>>>>>>>>>>>>> going
>>>>>>>>>>>>>>> to
>>>>>>>>>>>>>>> update
>>>>>>>>>>>>>>> using GIT PULL I have this error
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> error: Failed to connect to 2001:638:603:d06e::80:230:
>>>>>>>>>>>>>>> Network
>>>>>>>>>>>>>>> is
>>>>>>>>>>>>>>> unreachable while accessing
>>>>>>>>>>>>>>> http://git.samba.org/samba.git/info/refs
>>>>>>>>>>>>>>> fatal: HTTP request failed
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> some body can helpme
>>>>>>>>>>>>>> do you have working ipv6?
>>>>>>>>>>>>>> if not disable it via sysctl.conf
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> net.ipv6.conf.all.disable_ipv6=1
>>>>>>>>>>>>>> net.ipv6.conf.default.disable_ipv6=1
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> that above is most likely because the link-local address if
>>>>>>>>>>>>>> the
>>>>>>>>>>>>>> ipv6
>>>>>>>>>>>>>> stack is enabled and some piece of software thinks it's
>>>>>>>>>>>>>> useable
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> To unsubscribe from this list go to the following URL and
>>>>>>>>>>>>>> read
>>>>>>>>>>>>>> the
>>>>>>>>>>>>>> instructions: https://lists.samba.org/mailman/options/samba
>>>>>>>>>>> --
>>>>>>>>>>> To unsubscribe from this list go to the following URL and read
>>>>>>>>>>> the
>>>>>>>>>>> instructions: https://lists.samba.org/mailman/options/samba
>>>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> To unsubscribe from this list go to the following URL and read
>>>>>>>>> the
>>>>>>>>> instructions: https://lists.samba.org/mailman/options/samba
>>>>>>>>>
>>>>>>> --
>>>>>>> To unsubscribe from this list go to the following URL and read the
>>>>>>> instructions: https://lists.samba.org/mailman/options/samba
>>>>>>>
>>>>> OK, nobody seems to have asked this yet, what OS and how are you
>>>>> trying
>>>>> to update git, just what are you typing into the terminal ?
>>>>>
>>>>> Rowland
>>>>>
>>>>> --
>>>>> To unsubscribe from this list go to the following URL and read the
>>>>> instructions: https://lists.samba.org/mailman/options/samba
>>>>>
>>> OK, so you cd into the samba directory that you previously built samba4
>>> in (presumably samba-master) and typed 'git pull'.
>>>
>>> If I do the same on my debian wheezy DC, I get this:
>>>
>>> root at dc01:~/samba-master# git pull
>>> remote: Counting objects: 4622, done.
>>> remote: Compressing objects: 100% (1904/1904), done.
>>> remote: Total 3053 (delta 2436), reused 1373 (delta 1083)
>>> Receiving objects: 100% (3053/3053), 554.51 KiB, done.
>>> Resolving deltas: 100% (2436/2436), completed with 472 local objects.
>>> From git://git.samba.org/samba
>>> 87c5795..e2ed224 master -> origin/master
>>> 6e1ba4c..5f5a01e v3-6-stable -> origin/v3-6-stable
>>> 3be3266..4395552 v4-0-stable -> origin/v4-0-stable
>>> f9693a1..2722ad6 v4-0-test -> origin/v4-0-test
>>> 1e682c3..492c673 v4-1-stable -> origin/v4-1-stable
>>> c4e46cd..d2c9373 v4-1-test -> origin/v4-1-test
>>> c88a4f4..6c9d254 v4-2-stable -> origin/v4-2-stable
>>> 77d8786..f645571 v4-2-test -> origin/v4-2-test
>>> * [new tag] samba-4.0.25 -> samba-4.0.25
>>> * [new tag] samba-4.1.17 -> samba-4.1.17
>>> * [new tag] samba-4.2.0rc5 -> samba-4.2.0rc5
>>> From git://git.samba.org/samba
>>> * [new tag] ldb-1.1.20 -> ldb-1.1.20
>>> * [new tag] samba-3.6.25 -> samba-3.6.25
>>> * [new tag] tevent-0.9.23 -> tevent-0.9.23
>>> Updating 87c5795..e2ed224
>>>
>>> and so on
>>>
>>> So there must be a difference between your setup and mine, but what ??
>>>
>>> Rowland
>>>
>>> --
>>> To unsubscribe from this list go to the following URL and read the
>>> instructions: https://lists.samba.org/mailman/options/samba
>>>
>>
>
> OK, what have you got in /etc/resolv.conf ?
> If it points to your DC, what are your forwarders ?
>
> Rowland
>
>
>
More information about the samba
mailing list