[Expired for aiccu (Ubuntu) because there has been no activity for 60
days.]
** Changed in: aiccu (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1261653
T
** Changed in: aiccu (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1261653
Title:
aiccu can not route, looses route
To manage notifications about this bug
Joni-Pekka,
in short:
would you please be so kind, and start "sudo tcpdump -i wlan0 -s 1514 -w
aiccu.tcpdump tcp port 3874 or udp port 3740 or udp port 5072 or proto 41 or
icmp" in one terminal and "ping6 -c5 heise.de" in an other.
After the ping6 finishes, type ctrl-c in the tcpdump-terminal t
> THEN TCPDUMP STOPS WHEN GIVING RESTART AICCU DUE SIXXS DROPS OUT
What do you mean with this sentence? Can you rephrase it? (possibly with
interpunction and possibly also in lowercase?)
It sounds like you are restarting things, why?
Note that, as stated on the contact page mentioned in a previo
hi,
One reason found, that was at evneing ifconfig wlan2 down and
at morning ifconfig wlan up,... that stops trafic trough sixxs,...
This is fixed to give restart aiccu after ifconfig wlan up .
Also got new Huawei driver that gives staedy trafic to ppp0.
Still ther have been mystery stops rando
> joni@mpi2:~$ sudo tcpdump -i sixxs
Dumping the tunneling interface will only show the traffic that goes
into the tunnel.
For any kind of tunneling protocol you need to look at the interface
that the tunneling happens over.
Also, using hostname resolving makes it difficult to see what is really
tcpdump:
- IPÅV6 dispeared
- started tcpdump
- ping6 ipv6.google.com started
joni@mpi2:~$ sudo tcpdump -i sixxs
Password:
tcpdump: WARNING: sixxs: no IPv4 address assigned
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on sixxs, link-type RAW (Raw IP), captur
I do next dump both IPV6 and IPV4 trafic if that brings more!
Any other ideas,... let's wait when IPV6 drops again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1261653
Title:
aiccu can not route,
So, I do not see difrence at sixxs interface after restarting aiccu, sixxs
interface
repair's, resets somthing at kernel routing,... correct ???
It can be incoming packets are not coming to ping6 even PC receives,...
ping6 out put is here :
joni@mpi2:~$ ping6 ipv6.google.com
PING ipv6.google.co
> I mean protocol level timeing, response time, missing packets,...
AICCU can do little about high latency or missing packets.
As for 'timing' except for the requirement that hosts are NTP synced, there is
no timing, AYIYA/proto-41 are lossless protocols, the tunneled protocols (eg
TCP) will tak
once a day, twice a day,... basically I use IPV4 from intranet so can
I can not note when it happens,...
Yes, ntps,...
I mean protocol level timeing, response time, missing packets,...
Basically aiccu should not change iptables, and shorewall dose it
only ones when it have started,...,... there
> Problem to supply any usefull is that it dose not happen every days
and sometimes twice
Then collect the information when the problem happens. How do you mean
that the problem happens 'twice'?
> Most likely this somekind of timeing / protocol,... related problem,
Unless your local system
Problem to supply any usefull is that it dose not happen every days and
sometimes
twice
Most likely this somekind of timeing / protocol,... related problem,
there have been same kind of reports but those have been negled
or system has started to work whitout explanation.
Doing dump is not v
> Joni-Pekka, would you please be so kind, and post the output of "sudo
> /usr/sbin/aiccu autotest" ?
> Best would be twice: One before changed IP and one after at least 2 minutes
> after connection is broken.
That does not do anything useful. The 'autotest' mode sets up the tunnel
again and thu
> If operator could block AYIA I belive aiccu did not start !
Even if AYIYA is blocked (or otherwise caused to be broken), AICCU can
still start.
This as AICCU fetches it's configuration using the TIC protocol, which
is independent of the tunnel protocol used afterwards (proto-41,
optionally with
Joni-Pekka, would you please be so kind, and post the output of "sudo
/usr/sbin/aiccu autotest" ?
Best would be twice: One before changed IP and one after at least 2 minutes
after connection is broken.
Thanks in advance.
--
You received this bug notification because you are a member of Ubuntu
If operator could block AYIA I belive aiccu did not start !
Restarting is not due aiccu is down or not running,...
reason or another it hangs ,... sudo restart aiccu
start's incoming ipv6 trafic, ping6 send's packages
while aiccu/tunnel is hangig but no response nor error!!!
So IPV4 is w
> Technical detail is that fact operator changes IP time to time as well
> there can missing pacets due operator switches radio mode of conection
> between GRPS-UMTS-HSPA,
That is not a *technical* detail, that is merely a description of the
problem that you are seeing.
As stated, the AYIYA a
Technical detail is that fact operator changes IP time to time as well
there can missing pacets due operator switches radio mode of conection
between GRPS-UMTS-HSPA,
If I do not restart aiccu connection dose not come back but if
do restart then it comes back immediately.
Software:
http://kur
> AICCU dose not dedetect changes so it can not receive data, IPV4 network
> works but it can have brakes and IP can change,... conection is lost at IPV6
> to incoming direction and aiccu dose not find it.
>From this sentence I understand you claim that AICCU does not handle
IPv4 address changes,
20 matches
Mail list logo
