|
Problem with aiccu 2007.01.07 upgrade
![[it]](/s/countries/it.gif) Shadow Hawkins on Saturday, 13 January 2007 23:15:32
My system is a Gentoo Linux (2.6.18 kernel)
With the last update to Aiccu I 've encountered a very strange issue: with 2006.07.25 no problem at all with the default cfg, but after the upgrade I cannot ping nor the endpoint nor any other site (like sixxs.net).
The log output in /var/log/messages (Gentoo style) is exactly the same. Also the cfg used is the same.
I've tried to enable "behindnat true" (my ISP nat all the connections) option in the new cfg without success.
Anyone has any idea?
P.s.: Should I open a ticket reporting this problem?
P.P.s: The pop used is ittrn01
Problem with aiccu 2007.01.07 upgrade
![[us]](/s/countries/us.gif) Shadow Hawkins on Sunday, 14 January 2007 01:49:04
I had the same problems, apparently there are issues with some builds of the 2007.01.07 version. Best bet is to revert to the 2006.07.25 until a newer build is released.
Problem with aiccu 2007.01.07 upgrade
Shadow Hawkins on Sunday, 14 January 2007 11:53:44
Mmm, so the thing is getting really weird cause my build of Aiccu got compiled at installation time.
:'(
Problem with aiccu 2007.01.07 upgrade
Carmen Sandiego on Sunday, 14 January 2007 17:40:33
UP same problem here, 5 days without ipv6 connection.
EDIT, confirm that net-misc/aiccu-2006.07.25 (gentoo style) works great.
Problem with aiccu 2007.01.07 upgrade
Please verify the following -
1. download the version of 20070107 as linked from our website
2. build it without any patches
3. cat the configfile (you can omit the password)
4. run aiccu test
do not use vendor supplied packages for this test. Does the source from our website work as intended?
Problem with aiccu 2007.01.07 upgrade
Shadow Hawkins on Sunday, 14 January 2007 22:13:27
Ok, strange issue. Before starting I'd line to point that the cfg used is the same.
Compiling by hand the tar archive is all ok. Also starting it as daemon using the same line used in the init script.
The ebuild in gentoo is exactly the same of the provided one with the tar archive. The only difference is line added in the init file but it cannot influence at all. After all I am starting it manually without using the script so it must be something else...but what?
So with the compiled one:
start-stop-daemon --start --oknodo --quiet --exec /home/stefano/Desktop/aiccu/aiccu/unix-console/aiccu -- start
All works, but with:
start-stop-daemon --start --oknodo --quiet --exec /usr/sbin/aiccu -- start
I Can't even ping the endpoint.
Seriuously this is the diff of the ebuild bundled against the gentoo one:
SRC_URI="http://www.sixxs.net/archive/sixxs/aiccu/unix/${PN}_${PV//\./}.tar.gz"
---
SRC_URI="http://www.sixxs.net/archive/sixxs/aiccu/unix/aiccu_current.tar.gz" 7c5
< LICENSE="SixXS"
---
LICENSE="BSD" 9c7
< KEYWORDS="~amd64 ~arm ~hppa ~ppc ~x86"
---
KEYWORDS="~x86" 11,12c9
< DEPEND="net-libs/gnutls
< sys-apps/iproute2"
---
DEPEND="" 15,19d11
< src_unpack () {
< unpack ${A}
< cd ${S}
< epatch ${FILESDIR}/init-after-ntp-client.patch
< }
31c23
< doins doc/aiccu.conf
---
doins aiccu.conf
As u can see there is only one signicant line more and it simply regards the init script.
So a question arises. Considering I am running a full stable system, can be the default CFLAGS (-O2 -march=i686 -pipe) a little problematic with the compiling of aiccu? Why only since this version?
Problem with aiccu 2007.01.07 upgrade
Shadow Hawkins on Wednesday, 17 January 2007 14:01:07
Hi,
as i already explained on another Topic i had the same behaviour.
After upgrading to the latest sixxs-aiccu package for this error:
Jan 17 13:46:05 reactive sixxs-aiccu: Couldn't pass client information: Deprecated Client Detected, please upgrade to the newest version which can be found at http://www.sixxs.net/tools/aiccu/.
I can't ping either ptp endpoint or any ipv6 sites all i receive is No route to host message.
Since i'm looking that you're connected to the same TB server ittrn01 of mine i wonder if the problems that we're both suffering could be referrend to the TB italian configuration with the new sixxs-aiccu client.
What do you think?
Simone
Problem with aiccu 2007.01.07 upgrade
Shadow Hawkins on Wednesday, 17 January 2007 16:29:46
Hi All,
i finally found what the problem was referring to.
If you look at the following lines you surely find where are the problem. I found that *BSD ifconfig doesn't correctly create routing for the ipv6 next-hop.
I start the sixxs-aiccu client and receive No route to host
reactive# sixxs-aiccu start
reactive# ifconfig gif2
gif2: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1280
tunnel inet 151.48.122.114 --> 213.254.12.34
inet6 2001:1418:100:154::2 --> 2001:1418:100:154::1 prefixlen 128
reactive# ping6 irc6.eutelia.it
PING6(56=40+8+8 bytes) 2001:1418:100:154::2 --> 2001:750:2:3::22
ping6: sendmsg: No route to host
ping6: wrote irc6.eutelia.it 16 chars, ret=-1
^C
--- irc6.eutelia.it ping6 statistics ---
1 packets transmitted, 0 packets received, 100.0% packet loss
reactive# netstat -rn
Routing tables
Internet:
Destination Gateway Flags Refs Use Netif Expire
default 151.6.149.65 UGS 0 497631 tun0
127.0.0.1 127.0.0.1 UH 0 508 lo0
151.6.149.65 151.48.122.114 UH 1 0 tun0
172.16.1/28 172.16.1.2 UGS 0 75 tun1
172.16.1.2 172.16.1.1 UH 1 0 tun1
192.168.0 link#1 UC 0 0 vr0
192.168.1.15 192.168.1.15 UH 0 1486 lo1
Internet6:
Destination Gateway Flags Netif Expire
default 2001:1418:100:154::1 UGS gif2
::1 ::1 UHL lo0
2001:1418:100:154::2 link#6 UHL lo0
fe80::%lo0/64 fe80::1%lo0 U lo0
fe80::1%lo0 link#2 UHL lo0
ff01:2::/32 fe80::1%lo0 UC lo0
ff01:4::/32 link#4 UC tun0
ff01:6::/32 link#6 UC gif2
ff02::%lo0/32 fe80::1%lo0 UC lo0
ff02::%tun0/32 link#4 UC tun0
ff02::%gif2/32 link#6 UC gif2
Then if you add route for you ptp endpoint trought the interface gif2 (in my case)
reactive# route add -inet6 2001:1418:100:154::1 -iface gif2
add host 2001:1418:100:154::1: gateway gif2
reactive# ping6 irc6.eutelia.it
PING6(56=40+8+8 bytes) 2001:1418:100:154::2 --> 2001:750:2:3::22
16 bytes from 2001:750:2:3::22, icmp_seq=0 hlim=57 time=90.520 ms
^C
--- irc6.eutelia.it ping6 statistics ---
1 packets transmitted, 1 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 90.520/90.520/90.520/0.000 ms
reactive# netstat -rn
Routing tables
Internet:
Destination Gateway Flags Refs Use Netif Expire
default 151.6.149.65 UGS 0 501191 tun0
127.0.0.1 127.0.0.1 UH 0 508 lo0
151.6.149.65 151.48.122.114 UH 1 0 tun0
172.16.1/28 172.16.1.2 UGS 0 75 tun1
172.16.1.2 172.16.1.1 UH 1 0 tun1
192.168.0 link#1 UC 0 0 vr0
192.168.0.50 link#1 UHLW 1 3 vr0
192.168.1.15 192.168.1.15 UH 0 1486 lo1
Internet6:
Destination Gateway Flags Netif Expire
default 2001:1418:100:154::1 UGS gif2
::1 ::1 UHL lo0
2001:1418:100:154::1 gif2 UHLS gif2
2001:1418:100:154::2 link#6 UHL lo0
fe80::%lo0/64 fe80::1%lo0 U lo0
fe80::1%lo0 link#2 UHL lo0
ff01:2::/32 fe80::1%lo0 UC lo0
ff01:4::/32 link#4 UC tun0
ff01:6::/32 link#6 UC gif2
ff02::%lo0/32 fe80::1%lo0 UC lo0
ff02::%tun0/32 link#4 UC tun0
ff02::%gif2/32 link#6 UC gif2
reactive#
Hope this can help anybody is trying to pinpoint this issue.
Ciao
simone
Problem with aiccu 2007.01.07 upgrade
Shadow Hawkins on Wednesday, 17 January 2007 22:41:10
The problem was solved with the last (2007.01.15) update :)
One last glitch in the ebuild file if u want o correct it the next time.
"doins aiccu.conf" to be corrected in doins "doc/aiccu.conf" line 24 of the ebuild file.
Thx for all the support :)
Problem with aiccu 2007.01.07 upgrade
![[de]](/s/countries/de.gif) Shadow Hawkins on Friday, 02 March 2007 16:34:27
I've also a problem with getting default route setup correctly.
Have FreeBSD 6.2-STABLE running with sixxs-aiccu-20070115 port installed.
baby# netstat -nr -f inet6
Routing tables
Internet6:
Destination Gateway Flags Netif Expire
default 2001:a60:f000:46::1 UGS gif0
2001:a60:f000:46::1 gif0 UHLS gif0
2001:a60:f000:46::2 link#7 UHL lo0
baby# netstat -nr -f inet
Routing tables
Internet:
Destination Gateway Flags Refs Use Netif Expire
default 82.135.14.1 UGS 0 15975 tun0
82.135.14.1 82.135.14.226 UH 1 0 tun0
baby# ifconfig
gif0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1280
tunnel inet 82.135.14.226 --> 62.245.150.2
inet6 fe80::280:c8ff:fe4e:fb40%gif0 prefixlen 64 scopeid 0x7
inet6 2001:a60:f000:46::2 --> 2001:a60:f000:46::1 prefixlen 128
tun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1492
inet 82.135.14.226 --> 82.135.14.1 netmask 0xffffffff
Opened by PID 512
I've added the route from 2001:a60:f000:46::1 to gif0 manually to make it work! If you look at the PPPoE IPv4 routing, this one looks good. The PPP client sets default route (local/remote IPs) correctly.
Regards,
Dejan
|
![[ch]](/s/countries/ch.gif)
on Sunday, 14 January 2007 17:40:45
Posting is only allowed when you are