xboxscene.org forums

Author Topic: [wip][30 Days=success/failure] Porting Either Lwip/wattcp 16  (Read 143 times)

Mios∞ft

  • Archived User
  • Full Member
  • *
  • Posts: 119
[wip][30 Days=success/failure] Porting Either Lwip/wattcp 16
« on: March 29, 2008, 05:37:00 PM »

Just started a serious approach that I am going to create a simple PC(server app) <-> Xbox1(listener) TCP sockets based; in 30 days. cool.gif

Will report progress as I achieve something noteworthy.  tongue.gif
Logged

ressurectionx

  • Archived User
  • Hero Member
  • *
  • Posts: 2778
[wip][30 Days=success/failure] Porting Either Lwip/wattcp 16
« Reply #1 on: March 30, 2008, 06:45:00 AM »

Hey man.  I'm a dummy and I don't even know what that is or what it does, but it's great to see other coders out there.  Good luck on your project.

~Rx
Logged

Mios∞ft

  • Archived User
  • Full Member
  • *
  • Posts: 119
[wip][30 Days=success/failure] Porting Either Lwip/wattcp 16
« Reply #2 on: April 02, 2008, 02:54:00 PM »

Just wondering:

Can TCP work without ICMP and ARP?   huh.gif

I am not very deep into how protocols work.
Logged

Mios∞ft

  • Archived User
  • Full Member
  • *
  • Posts: 119
[wip][30 Days=success/failure] Porting Either Lwip/wattcp 16
« Reply #3 on: April 08, 2008, 02:56:00 PM »

Is this Fragmentation support really required? For now, Can I get that crap out of the source?
[would it cause a huge hit in performance?]

What about intel16 and intel stuff, is it required? big endian <-> little endian conversion... Is it required?

Thanks  biggrin.gif
Logged

openxdkman

  • Archived User
  • Hero Member
  • *
  • Posts: 550
[wip][30 Days=success/failure] Porting Either Lwip/wattcp 16
« Reply #4 on: April 09, 2008, 01:16:00 PM »

pc & xbox1 are intel based
that means your get least significant byte first in structure if you just declare the area in the structure as a long (or longword, or dword or u32 whatever). it's of course a possible source of mistake.
if rfc tells msb (most significan byte) first then that's mean you have to reverse bytes order.

but the worst trap is when compiler decides (without telling you) to add padding bytes in structure to align stuff...

with a packet analyser you can discover such horrible mess.

there are also compilations directive that prevent compiler to touch your structure definition.

I turned fragmentation off also with my first attempts. Then I put it back but never verified what it did.
Probably doesn't change a lots... but I may be wrong.


Logged