determine ip and mac frame header information for a data packe

Determine Ip And Frame Header Information For A Data Packe Full Details In

Did you know that 100 Base-T actually runs at 125 megabaud Yep that 100 meg ethernet card of yours is actually clocked at 125 Megabit.

The rules for the P N subforum have been updated to prohibit ad hominem or personal attacks against other posters.

Determine Ip And Frame Header Information For A Data Packe Full Details In

See the full details in the post Politics and News Rules Guidelines.

For a better experience, please enable JavaScript in your browser before proceeding.

So I looked at IP specifications, and the IP spec also has sourcedest fields and data fields.

My guess is that ethernet frames can only be read within the network, and have to be translated to IP format before being unleashed on the internet.

First off some definitions: A packet is from layer three and up.

This does not include the datalink layer (very important) A frame is the actual bit level encapsulation of a packet.

In order for any two nodes on a single network (ethernet, frame-relay, token-ring, hdlc, FDDI, what ever the actual network type is) to communicate they have to agree upon what datalink layer protocol to use.

Again, plug in a token ring network card into an ethernet network and surprise.no talkie-talkie.

The real magic happens when a PACKET (ip headertcp headerapplication data) crosses a router.

The intelligence of the router is what allows this packet to traverse different network types.

This is why you can communicate with a web server in Hong Kong and not care about the intermediate systems in between.

So in answer to your question - ethernet frames can only be read by ethernet nodes.

These quot;framesquot; are NOT translated into IP format before being unleashed on the internet, rather hey are already IP packets.

These packets (L3 and above) are just quot;reframedquot; into different L2 hearders with L2 source and destination addresses changed.

L2, or Layer 2 is the ones and zeros (and they are directly proportional to the voltage., aka, the physical layer), and, finally, for this explanation, L3, or Layer 3, is framing, encapsulation, et al., or how the ones and zeros are interpreted.

The thing that fscks this explanation up is that ethernet is an L1, L2, protocol.

Really Id say IP, or TCPIP is an L3 protocol, but IP itself is L3, and its an unreliable protocol.believe it or not.

Its a connectionless state.

And, if Im wrong I apologize, but Im a bit buzzed right now so bear with me.

The Voltage is not directly perpotional (I suck at spelling) to the Ones and Zeros in binary.

You will have encoding methods over the line itself, which are then converted into the Ones and Zeros.

I belive Ethernet uses the Manchester Encoding, and Fast Ethernet and Gig Ethernet use a different form of encoding (I forget which one, might even be manchester) that are actually a 5 to 4 relationship, where 5 voltage differentials are equilivant to 4 zeros and ones.

This is best and commonly seem on T1 lines, where you can have AMID4 encoding that will steal 1 bit out of every 8 bits on the wire, or the ESF8BZ1 that will add an addiotional bit every 192 bits.

Determine Ip And Mac Frame Header Information For A Data Packe