|
||||||||||
Routed /48: 2001:470:d39d::/48 Routed /64: 2001:470:1f15:158c::/64 This is the config, I got from tunnelbroker.net But I have not configured the routed /48 part on my side at all. (the /48 part was optional at tunnelbroker.net) It seems I have missed a digit, somewhere during copy/pasting - (the part where you were assuming x::1) I'll try to setup Sixxs again, since they have a Windows Client too - that way I can try in between the office, and my home. At the office I don't have a monowall yet (have to wait 60 days, before I start working there :) - and am not going to do experiments at my current job) Thank you for your testing though... but since I'm completely new to ipv6, I don't want to take your time too much ;) Steve Bertrand schreef: > Michel Servaes wrote: > >> 2001:470:1f15:158c:d7d:bd6:5ff3:6988 is the IP of my computer, behind monowall. >> > > I can not ping that. > > >> 2001:470:1f14:158c::2/64 is the assigned client IPv6 address >> > > I can ping that. > > >> , in being the server 2001:470:1f14:158c::1/64 >> > > I can ping that. > > >> 2001:470:1f15:158c:: to the LAN side of monowall. >> > > I can not ping that (assuming that the m0n0 is x::1) > > >> Ugh, I hate those new addresses... IPv4 was easy to remember. This is akward :-) >> > > The numbering scheme will come naturally after some time ;) > > >> Thanks again, for testing - this helps me getting it running, and understanding it >> > > No problem. > > It appears as though the m0n0wall is not allowing IPv6 traffic to cross > from the WAN side to the LAN side. > > How was your tunnel space allocated? I'm not familiar with how the > tunnel providers are assigning/routing space. > > Do they route you 2001:470:1f15::/48 over the 2001:470:1f14:158c::/64 > tunnel? > > Steve > |