Should the tunnel work with Mac OS X v10.4.9 and PPC?
Shadow Hawkins on Friday, 11 May 2007 23:21:31
Hi there!
I'm able to make my tunnel work on Ubuntu Feisty, but not on my Mac OS X v10.4.9 PowerPC machine.
The system.log looks like this after running the aiccu test command:
May 11 00:12:04 powerbook aiccu: [tun-start] Couldn't set interface tun0's TUNSIFHEAD to enabled: Invalid argument (22)\n
May 11 00:12:04 powerbook aiccu: Tunnel Setup Failed\n
And my ifconfig looks like this:
powerbook:~ root# ifconfig
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
inet 127.0.0.1 netmask 0xff000000
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=1<UP> mtu 1280
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
ether 00:11:24:72:3c:f0
media: autoselect (none) status: inactive
supported media: none autoselect 10baseT/UTP <half-duplex> 10baseT/UTP <full-duplex> 10baseT/UTP <full-duplex,hw-loopback> 100baseTX <half-duplex> 100baseTX <full-duplex> 100baseTX <full-duplex,hw-loopback>
en1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet6 fe80::211:24ff:fe8c:ddf3%en1 prefixlen 64 scopeid 0x5
inet 192.168.0.100 netmask 0xffffff00 broadcast 192.168.0.255
ether 00:11:24:8c:dd:f3
media: autoselect status: active
supported media: autoselect
fw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 2030
lladdr 00:11:24:ff:fe:72:3c:f0
media: autoselect <full-duplex> status: inactive
supported media: autoselect <full-duplex>
tap0: flags=8842<BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
ether 74:61:70:00:00:00
closed
tun0: flags=8850<POINTOPOINT,RUNNING,SIMPLEX,MULTICAST> mtu 1500
closed
And here's a cleaned up version what tcpdump -Ans 1500 -i en1 prints during the "aiccu test" command. Looks like that everything should work:
200 SixXS TIC Service on noc.sixxs.net ready (http://www.sixxs.net)
client TIC/draft-00 AICCU/2007.01.15-console-darwin Darwin/8.9.0
200 Client Identity accepted
get unixtime
200 1178902752
username JLM3-SIXXS
200 Choose your authentication challenge please
challenge md5
200 ____________________________________
authenticate md5 ________________________________
200 Succesfully logged in using md5 as JLM3-SIXXS (Jari Lammi) from 217.119.47.119
btunnel show T11548
201 Showing tunnel information for T11548
TunnelId: T11548
Type: ayiya
IPv6 Endpoint: 2001:14b8:100:1d4::2
IPv6 POP: 2001:14b8:100:1d4::1
IPv6 PrefixLength: 64
Tunnel MTU: 1280
POP Id: fihel01
IPv4 Endpoint: ayiya
IPv4 POP: 62.78.96.38
UserState: enabled
AdminState: enabled
Password: ________________________________
Heartbeat_Interval: 60
202 Done
QUIT That's what I get
200 Thank you for using this SixXS Service
The routing table looks like this:
Routing tables
Internet:
Destination Gateway Flags Refs Use Netif Expire
default 192.168.0.254 UGSc 22 27 en1
127 localhost UCS 0 0 lo0
localhost localhost UH 11 20265 lo0
169.254 link#5 UCS 0 0 en1
192.168.0 link#5 UCS 1 0 en1
192.168.0.100 localhost UHS 0 1 lo0
192.168.0.254 0:4:ed:24:bd:f UHLW 21 17 en1 1151
Internet6:
Destination Gateway Flags Netif Expire
localhost link#1 UHL lo0
localhost Uc lo0
localhost link#1 UHL lo0
link#5 UC en1
powerbook.local 0:11:24:8c:dd:f3 UHL lo0
ff01:: localhost U lo0
ff02::%lo0 localhost UC lo0
ff02::%en1 link#5 UC en1
But still ping6 fails:
powerbook:~ root# ping6 2001:14b8:100:1d4::2
ping6: UDP connect: No route to host
powerbook:~ root# ping6 2001:14b8:100:1d4::1
ping6: UDP connect: No route to host
Jari Lammi
Should the tunnel work with Mac OS X v10.4.9 and PPC?
Shadow Hawkins on Saturday, 12 May 2007 20:22:04
I did a full recompile for both the universal binary version of the tun and then aiccu. After fixing the ownership parameters it started to work without any problems now:
tun0: flags=8851<UP,POINTOPOINT,RUNNING,SIMPLEX,MULTICAST> mtu 1280
inet6 fe80::211:24ff:fe72:3cf0%tun0 prefixlen 64 scopeid 0x7
inet6 2001:14b8:100:1d4::2 --> 2001:14b8:100:1d4::1 prefixlen 128
open (pid 505)
As I installed the prebuilt binary, the ifconfig showed tun0 there already before the aiccu even starting it. I think the problem was related with that. But anyway, aiccu really works on my PowerBook G4, just wanted to let you know that it's possible in case somebody other would wonder that at a later time.
Issue solved. 8-)
Should the tunnel work with Mac OS X v10.4.9 and PPC?
Shadow Hawkins on Wednesday, 27 June 2007 20:31:05
Hi,
I've been trying to get this to work but seems I'm unsuccessfull. Can you tell me what ownership permissions you did change?
Should the tunnel work with Mac OS X v10.4.9 and PPC?
Jeroen Massar on Thursday, 28 June 2007 01:36:18
Try: "sudo -i bash"
And then execute "aiccu". Providing the output of "aiccu test" when the configuration file has specified "verbose true" and "daemonize false" will give you quite some details already.
Posting is only allowed when you are logged in. |