|
Problem after ip change
![[pl]](/s/countries/pl.gif) Shadow Hawkins on Tuesday, 01 April 2008 11:41:06
=========================================================================
ADMIN EDIT: The problem has been fixed in AICCU with the entry: "Don't use a connected UDP socket for AYIYA and heartbeat traffic", new version of which for linux/etc will be released later on
=========================================================================
Hello,
I've got problem with my tunnel after dynamic ip change. I use Heartbeat tunnel and everything works fine until ip change; then i lose connection and I can't set it back. I can't ping or receive any other packets.
ifconfig:
eth0 Link encap:Ethernet HWaddr 00:50:FC:3A:77:DD
inet addr:192.168.1.101 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::250:fcff:fe3a:77dd/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:7084890 errors:0 dropped:0 overruns:0 frame:0
TX packets:6716477 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1557544203 (1485.3 Mb) TX bytes:2721735842 (2595.6 Mb)
Interrupt:5 Base address:0xe000
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:7422 errors:0 dropped:0 overruns:0 frame:0
TX packets:7422 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3082362 (2.9 Mb) TX bytes:3082362 (2.9 Mb)
sixxs Link encap:UNSPEC HWaddr C0-A8-01-65-05-08-50-70-00-00-00-00-00-00-00-00
inet6 addr: 2001:6a0:147::1/128 Scope:Global
inet6 addr: 2001:6a0:200:69::2/64 Scope:Global
inet6 addr: fe80::c0a8:165/64 Scope:Link
UP POINTOPOINT RUNNING NOARP MTU:1280 Metric:1
RX packets:9236 errors:0 dropped:0 overruns:0 frame:0
TX packets:8998 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2434063 (2.3 Mb) TX bytes:1037843 (1013.5 Kb)
route:
2001:6a0:147::1 via :: dev sixxs metric 256 expires 21249600sec mtu 1280 advmss 1220 hoplimit 4294967295
2001:6a0:200:69::/64 via :: dev sixxs metric 256 expires 21248875sec mtu 1280 advmss 1220 hoplimit 4294967295
fe80::/64 dev eth0 metric 256 expires 21248311sec mtu 1500 advmss 1220 hoplimit 4294967295
fe80::/64 via :: dev sixxs metric 256 expires 21248875sec mtu 1280 advmss 1220 hoplimit 4294967295
default via 2001:6a0:200:69::1 dev sixxs metric 1024 expires 21248875sec mtu 1280 advmss 1220 hoplimit 4294967295
I guess that second /128 address in sixxs interface can be a problem but I don't know how to configure it proper way to acquire my revDNS on host.
z
Thanks for help!
Problem after ip change
![[si]](/s/countries/si.gif) Shadow Hawkins on Sunday, 30 March 2008 20:04:19
What (operating) system do you run your tunnel on ?
What tool starts it ? Aiccu ? How is it configured ?
Did you perform any other additional configuration ?
Problem after ip change
Shadow Hawkins on Sunday, 30 March 2008 23:35:33
I run tunnel on linux. It's started with aiccu
conf:
username *******
password *******
ipv6_interface sixxs
tunnel_id T14490
verbose true
daemonize true
automatic true
requiretls false
defaultroute true
makebeats true
No additional configuration expect adding that /128 address: ip a a 2001:6a0:147::1/128 dev sixxs
Problem after ip change
Shadow Hawkins on Monday, 31 March 2008 12:43:17
Does it work without the additional address ?
Why exactly are you adding it ? You can't just assign any address to an interface.
Problem after ip change
Shadow Hawkins on Monday, 31 March 2008 15:16:49
I think it worked but I'm not 100% sure, I will check that as soon as I can... Basically additional ip is used for my own revDNS which I can't have with standard tunnel address.
Problem after ip change
Shadow Hawkins on Monday, 31 March 2008 20:08:37
You can not just make up an address and assign it to an interface. It is like making up, that 123456 is your phone number and entering it into your mobile phone. It wont work.
Problem after ip change
Shadow Hawkins on Monday, 31 March 2008 23:25:11
Hmm, I think I didn't clear it up enough. That address is from my subnet prefix assigned by sixxs. I added one /128 from it to make it default address for sixxs interface. Basically:
Tunnel: 2001:6a0:200:69::2/64
Subnet: 2001:6a0:147::/48
2001:6a0:147::1/128 works as deprecated address which is "outgoing address".
Problem after ip change
Shadow Hawkins on Tuesday, 01 April 2008 17:10:21
Well, that is wrong.
Did you read the FAQ ?
You need to manually add an address from the subnet to the other interface, that connects to your other hosts.
Problem after ip change
Shadow Hawkins on Tuesday, 01 April 2008 17:11:37
... that would be eth0 in your case.
And it must have a prefix of /64, not /128.
Problem after ip change
Shadow Hawkins on Tuesday, 01 April 2008 18:50:11
Ok, fist of all I know how to configure subnet... but put aside all that earlier disscussion cuz U seem like u didn't read my postes. So lets start from begining.
Question:
Is it possible to use subnet address instead of tunnel address? I read in other thread that it's possible by adding /128 address which make it default address https://noc.sixxs.net/forum/?msg=setup-230468
But U clearly have other opinion on that subject so please explain it to me.
Problem after ip change
Shadow Hawkins on Thursday, 03 April 2008 12:25:51
Ah, that clears it up. Sorry for the confusion.
|
Posting is only allowed when you are