|
Ticket ID: SIXXS #9962754 Ticket Status: User PoP: fihel01 - DNA Oy (Helsinki)
Blocked from TIC server, had problems to configure windows machine
![[fi]](/s/countries/fi.gif) Carmen Sandiego on Tuesday, 20 August 2013 16:02:03
Greetings!
I did succesfully configurate tunnel on my linux laptop, but had problems to get it work on my windows laptop, hence ended hammering the TIC server when tried to source the problem. I think I have found the problem to get tunneling working for my other laptop and I am asking if you kindly would inform how long I am blocked before I can try if it did work? Or if unblocking for that reason is against your policy, then unblock it for the reason I can use the tunnel on my linux configuration (tested and it is working there). I can stop trying to get it to work on my windows machine if needed.
Is there a gui version of the AICCU for windows? I am not sure if I have filled the aiccu.conf right (pasting it now):
username SMM15-SIXXS
password xxxxxxx
server tic.sixxs.net
protocol tic
ipv6_interface wi-fi
tunnel_id T127342
verbose false
daemonize true
automatic true
requiretls false
makebeats true
It seems to be filled right as far as I can tell. The ipv6-address shows in the wi-fi interface, but for whatever reason it does not work (ipv6 tests show only ipv4 available). Ipv6 DNS servers are empty though, have I missed how to configure them? (was automatic with AICCU in linux). Could the problem be so simple that I did forget to open the specific port for the TIC server? It did work instantly on my linux machine.
Well, since it already did work perfectly on my linux configuration (and without unnessesary hammering to the TIC servers, sorry for that again), I would appreciate if I would get unblocked to continue using it only on my linux machine. If not, could you please show me the mistake on my configurating/give working configuration to my windows 8.1 machine? Also I would love to try the windows configuration again firewall off and nat off from my router...
Apologizing for the hammering,
Samuel Mki
SMM15-SIXXS
Blocked from TIC server, had problems to configure windows machine
ipv6_interface wi-fi
Unless you want a special name, keeping the default ('aiccu') should work fine.
It seems you are trying to mix a tunnel with a real interface, that will not work.
but for whatever reason it does not work
It won't work as that interface is not a tunnel. The ipv6_interface clause specifies the tunnel interface used for sending the IPv6 packets.
Is there a gui version of the AICCU for windows?
There only is a very old GUI version, we do not maintain that anymore. (It was very old MFC based).
We have a new version of AICCU still in the works.
Ipv6 DNS servers are empty though, have I missed how to configure them? (was automatic with AICCU in linux).
AICCU has no idea about DNS. Thus if they got configured something else did that.
It did work instantly on my linux machine.
Was that machine connected in the same way?
Could the problem be so simple that I did forget to open the specific port for the TIC server?
Depends what your problem is and how your network looks like, where all the components fit etc.
Please do read the FAQ on firewalls though, that should likely answer your 'port' question.
I would appreciate if I would get unblocked to continue using it only on my linux machine.
Please note that a tunnel can only be used at 1 endpoint at a time.
Next to that TIC blocks are IP based. Thus if you are behind a NAT that might cause conflicts.
If not, could you please show me the mistake on my configurating/give working configuration to my windows 8.1 machine?
See above.
I am assuming though that you have a Linux machine set up. If you terminate the tunnel there, you can use 'radvd' to announce a subnet to the other computers on your network. See the FAQ for details on subnets.
Blocked from TIC server, had problems to configure windows machine
Carmen Sandiego on Tuesday, 20 August 2013 16:45:00
I am using my linux laptop on the same network and behind same nat and router. And thanks, I guess that ipv6 interface was wrong and that could have been the problem why it did not work.
Hmmm... now I feel pretty stupid, should have tried with different ipv6 interface name and using some public ipv6 nameservers. Seems that could be the problem, so could you inform how long I am blocked from trying to fix the connection?
Samuel Maki
Blocked from TIC server, had problems to configure windows machine
behind same nat and router.
In that case you either configured a DMZ or you are lucky, but typically you should use AYIYA.
using some public ipv6 nameservers.
Why do you think you need an IPv6 nameserver?
Please note that IPv4 nameservers can perfectly fine lookup A (IPv4) and AAAA (IPv6) records.
Blocked from TIC server, had problems to configure windows machine
Carmen Sandiego on Tuesday, 20 August 2013 16:55:16
Well, I have configured DMZ so it should not be a problem. I decided to use heartbeat (or try to) because AYIYA is more demanding for the server. And was just saying I should have tried using ipv6 nameserver just in case, but yeah, I am sure my isp's ipv4 nameservers can handle ipv6 records as well, was just troubleshooting.
Blocked from TIC server, had problems to configure windows machine
Carmen Sandiego on Tuesday, 20 August 2013 17:27:00
Seems the problem is found then? Because it works in the same network with the linux machine it must have been just a mistake on windows aiccu.conf. Sorry for asking, but is it possible to unblock my ip so I could try it? Or tell me how long the blocking is going to be so I do not accidently expand the block by connecting to the TIC server...
Blocked from TIC server, had problems to configure windows machine
unblock my ip so I could try it?
TIC blockages automatically expire.
You can see in the webinterface if a block is in place. (Unless you provided wrong/bad login details).
|
![[ch]](/s/countries/ch.gif)
on Tuesday, 20 August 2013 16:28:21
Posting is only allowed when you are