3. Why Vertex-5
We had three choices for FPGA boards:
Virtex-5,Vertex-2 & Altera
Embedded tri-mode Ethernet MAC
wrapper is available only for Virtex-5 and
Vertex-6
Because of which we used Virtex-5 board
for our project.
4. Procedure
Implemented the Tri-mode
Ethernet MAC Wrapper
Implemented the IPv4 to
IPv6 conversion algorithm
Implemented the IPv6 to
IPv4 conversion algorithm
Combine two algorithms
to get the NAT64 module
8. Header Mapping
IPv4 IPv6
Ether Type: 0x0800 Ether Type:0x86dd
DSCP, ECN Traffic class
Header Length, Total Length Payload Length
Protocol Next Header
Time to Live Hop Limit
Ipv4 address Ipv6 address
13. Issues
Virtex-5 board only has one Ethernet port
though out NAT64 server needs at least
two ports.
Virtex-5 device designs of Tri-mode
Ethernet MAC require a Verilog LRM-IEEE
1364-2005 encryption-compliant simulator
ModelSim v6.6d
Cadence Incisive Enterprise Simulator (IES) 10.2
Synopsys VCS and VCS MX 2010.06)
Butany of those simulators are not freely
available
Hinweis der Redaktion
Monahriliyapaaannn
According to the slides, given by Dr. Pasqual, there are 3 types of FPGAtri-mode Ethernet MAC wrapper is free
We have to configure the TEMAC wrapper
The generated example design for this OpenSparc board will not work if implemented and downloaded to the board as is. We must make some configuration changes in the example design so that it works on the OpenSparc board. This is the most hardest part in our project
This is the timing diagramFor each ipv4 packet received, NAt64 send ipv6 packet after delaying 36 bytesData and FCS field is delayed by (76-x) bytes
This is the timing diagramFor each ipv6 packet received, NAt64 send ipv4 packet after delaying 36 bytesData and FCS field is delayed by 16 bytes
‘Ether type’ in ethernet header is used to determine whether this packet is ipv4 or ipv6How ipv4 packets and ipv6 packets are mapped each other
There are twomethosChipScope Pro Inserter flow (which is easy)(which we use)ChipScope Pro Core Generator flow
So, the single Ethernet port has to represent IPv4 network and IPv6 networkBecause of unavailability of functional and timing simulations, we have to rely on the hardware debug tools (ChipScope Pro Analyzer and wireshark). This make the project extremely difficult and time consuming (synthesizing, implementing and generating a programming file takes lots of time )