IPv6 "Jubmo Payload" Broadcast sample for Visual Basic .Net?

  • Thread starter Thread starter gregory_may
  • Start date Start date
G

gregory_may

First the research links:

IPv6 spec (look for 'jumbo payload'):
http://www.cs-ipv6.lancs.ac.uk/ipv6/documents/rfcs/archive/rfc1883.txt

IPv6 Sample C# Client/Server
http://www.codeproject.com/csharp/ipv6.asp

I am developing an application where I need to broadcast information to
clients. I have hit a 64K limit in UDP broadcasting. I am not exited
about coding around this problem. It appears IPv4 uses a 2 byte length in
the header of the message which translates to a 64K Message limit.

It looks like IPv6 may get around this 64K message size problem by using a
"Jumbo Payload" (check out the IPv6 spec link), it could save me a good deal
of coding headache if I can get a IPv6 Broadcast to work with Jumbo
Payloads.

I need help answering the following questions:
* Can I use .Net IPv6 broadcast in place of IPv4 UDP broadcast? It looks
like the IPv6 structure will broadcast properly on IPv4 equipment for the
same subnet.
* Does the .Net implementation of IPv6 implement "Jumbo Payloads" so I can
get around my 64K message length problem?
* Does anyone know how to do a IPv6 broadcast in VB.Net. (Got a sample?)

I could not find any .Net samples working with IPv6 broadcast. An example
of VB.Net doing a IPv6 broadcast would be ideal, but a C# broadcast sample
would be ok too.

Thanks so much!

Greg.
 
Hi Gregory,

I am reviewing the issue and I am researching the issue.
I will get back and update you with new information ASAP.

Have a nice day!

Best regards,

Peter Huang
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.
 
I got this from the IPv6 Group:
I am developing an application where I need to broadcast information to
clients. I have hit a 64K limit in UDP broadcasting. I am not exited
about coding around this problem. It appears IPv4 uses a 2 byte length in
the header of the message which translates to a 64K Message limit.

It looks like IPv6 may get around this 64K message size problem by using a
"Jumbo Payload" (check out the IPv6 spec link), it could save me a good
deal
of coding headache if I can get a IPv6 Broadcast to work with Jumbo
Payloads.
Click to expand...

The "jumbo payload" option is designed for very high speed networks that
support frame sizes larger than 64K, for example HIPPI and Fibre Channel.
Most networks support only a much smaller frame size, 1536 bytes on classic
Ethernet networks, 9KB on Gigabit Ethernet networks. Unless you work in a
computer center equipped with a very high speed network, you probably cannot
benefit from the jumbo payload.
I need help answering the following questions:
* Can I use .Net IPv6 broadcast in place of IPv4 UDP broadcast? It looks
like the IPv6 structure will broadcast properly on IPv4 equipment for the
same subnet.
Click to expand...

Yes. IPv6 multicast to the IPv6 "all nodes and routers" address will have
the same effect as IPv4 broadcast.
* Does the .Net implementation of IPv6 implement "Jumbo Payloads" so I can
get around my 64K message length problem?
Click to expand...

No. See above.
* Does anyone know how to do a IPv6 broadcast in VB.Net. (Got a sample?)

I could not find any .Net samples working with IPv6 broadcast. An example
of VB.Net doing a IPv6 broadcast would be ideal, but a C# broadcast sample
would be ok too.
Click to expand...

Basically, the behavior is the same as for IPv4 multicast: create an IPv6
UDP socket, bind to the port number you are listening to, and then subscribe
to the multicast group.

-- Christian Huitema
 
Back
Top