How would I go about simulating a tunnel broker for a case study?

Hey everyone.

One of the final requirements in my uni's networking class is to do a short case study regarding an ipv6 solution. In my case, a tunnel broker.

Anyway, I know the basics of a tunnel broker. It uses 6in4 to allow ipv6 networks to communicate to the rest of the ipv6 world through a tunnel over an ipv4 network (please correct me, if I am wrong).

I'd just like to get some help on how I can "simulate" this on gns3/packet tracker because I am not able to use the services of Hurricane Electric, which is what I'm modelling my case study on.

Basically, what I'm getting at is what would the topology look like in GNS3/Packet Tracer? Like, how do I make a pseudo-ipv4-only ISP or something that resembles the internet in there? If it's even possible.

EDIT: My apologies if this isn't the right place to ask, I'm not even sure if I'm asking the right questions.

EDIT2: Also, I have no idea how all this actually works on the tunnel broker side.

Okay, say you've established your tunnel to the broker and now all packets not addressed to your own ipv6 network is sent to the broker. What happens then? What does the tunnel broker do with the packets you sent? How does this little logical connection get you access to the rest of the ipv6 internet?

Posted Jun 22, 2016, 10:59 AM UTC · edited

39
icebalmCCNA•

Okay, say you've established your tunnel to the broker and now all packets not addressed to your own ipv6 network is sent to the broker. What happens then? What does the tunnel broker do with the packets you sent? How does this little logical connection get you access to the rest of the ipv6 internet?

The same way any ipv4 internet provider gets you access to the rest of the ipv4 internet. They forward your packets to the appropriate network.

2
tryagainplssOP•

Ahh. And those packets are then sent back to the client through the broker again, correct?

1
icebalmCCNA•

That is correct sir.

1
tryagainplssOP•

I've got the "send your ipv6 packets to the tunnel broker so they can forward it to the appropriate network" down but I can't seem to find a good solution to routing the packets back.

I've resorted to using ipv6 eigrp in the mean time which includes my ipv6 network, the tunnel broker and my "ipv6 internet". Is there a better way to route back to my ipv6 network other than EIGRP? Cause the way I'm doing it now, my ipv6 network sees everyone else but I think how it works in actuality is I just send my packets to the broker without ever seeing any other networks in my routing table apart from the tunnel.

Here's a screenshot of what I have going so far in regards to the topology, my network here is JT-Corp (green area).

1
icebalmCCNA•

With a tunnelbroker like he.net, they're giving you IP blocks that they're advertising routes to already, so any traffic for those IP blocks goes to their networks, and then they just forward it through to your tunnel. You need to do the same on your network. The other networks need to know that to get to JT-Corp's subnet the packets need to route to that 2911 router named "Tunnel Broker". However you do that, routing protocol, static routes, etc, is up to you.

1
zlimvos•

it shouldnt be too hard to simulate the 'ipv4' internet and the 'ipv6' internet in your topology. All you need is IP connectivity between your client and the tunnel broker (i'd just put a router in between) and then ipv6 connectivity between the tunnel broker router and a server behind it (again, i'd just add a router on native ipv6 config)

Should look like this:

ipv6 Server <-ipv6--> ipv6 router <-ipv6--> TunnelBroker Router (dual stack) <-ipv4-> ipv4 router <-ipv4-> client ipv4 router <-ipv4-> client pc

1
tryagainplssOP•

Ahh. I never considered it to be that simple. Thanks a lot.

1
ThisIs_MyNameInfiniBand Master Race :P•

I'd also lower the MTU on the fake "TunnelBroker" to account for overhead.

1