From: Michael Richardson <mcr@sandelman.ottawa.on.ca>
To: Jeff Dike <jdike@addtoit.com>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] PATCH: Netdevice 0 -- port number patch
Date: Fri, 17 Sep 2004 22:59:24 -0400 [thread overview]
Message-ID: <7617.1095476364@marajade.sandelman.ottawa.on.ca> (raw)
In-Reply-To: Message from Jeff Dike <jdike@addtoit.com> of "Fri, 17 Sep 2004 13:43:41 EDT." <200409171743.i8HHhfid003216@ccure.user-mode-linux.org>
-----BEGIN PGP SIGNED MESSAGE-----
>>>>> "Jeff" == Jeff Dike <jdike@addtoit.com> writes:
>> This fixes the mcast device code to log the right port number.
Jeff> I don't see that the port number was ever in network order, so
Jeff> I don't see that it needs converting.
Well, it has to be in network byte order to bind() or connect() the socket.
It is placed in network byte order at line 145 of mcast_kern.c.
And, there is a byte order difference:
east:~# dmesg | grep eth
Kernel command line: root=/dev/root rootfstype=hostfs rootflags=/mara4/openswan-2/nightly/UMLPOOL/east/root rw eth0=mcast,10:00:00:dc:bc:ff,239.192.0.1,21200 eth1=mcast,10:00:00:64:64:23,239.192.1.2,31200 eth2=mcast,10:00:00:32:64:23,239.192.3.2,31210
east:~# dmesg | grep 'Net'
Netdevice 0 (10:00:00:dc:bc:ff) : mcast backend multicast adddress: 239.192.0.1:53330, TTL:1
Netdevice 1 (10:00:00:64:64:23) : mcast backend multicast adddress: 239.192.1.2:57465, TTL:1
Netdevice 2 (10:00:00:32:64:23) : mcast backend multicast adddress: 239.192.3.2:60025, TTL:1
and
marajade-[/mara4/openswan-2/nightly] mcr 1039 %bc
bc 1.06
Copyright 1991-1994, 1997, 1998, 2000 Free Software Foundation, Inc.
This is free software with ABSOLUTELY NO WARRANTY.
For details type `warranty'.
obase=16
53330
D052
21200
52D0
- --
] "Elmo went to the wrong fundraiser" - The Simpson | firewalls [
] Michael Richardson, Xelerance Corporation, Ottawa, ON |net architect[
] mcr@xelerance.com http://www.sandelman.ottawa.on.ca/mcr/ |device driver[
] panic("Just another Debian GNU/Linux using, kernel hacking, security guy"); [
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Finger me for keys
iQCVAwUBQUukhYqHRg3pndX9AQFzIgQA4P00Z6LG7CXmVzxh0EiRO6hJ7AwcxFfq
m2RTJP/T1kYEHLASshYNe83ujcSFU3aIKvcnbPP5w4oAM05zhLS4AXXdwQHyBLUP
3ytOci9Tt9dFN7wt9zl6QluDidi23af+lO6G/r55m/VRhRUmbunzuA+7ZuBLsu/N
8pFKzotZshQ=
=G/2j
-----END PGP SIGNATURE-----
-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
prev parent reply other threads:[~2004-09-18 3:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-15 22:53 [uml-devel] PATCH: Netdevice 0 -- port number patch Michael Richardson
2004-09-17 17:43 ` Jeff Dike
2004-09-18 2:59 ` Michael Richardson [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7617.1095476364@marajade.sandelman.ottawa.on.ca \
--to=mcr@sandelman.ottawa.on.ca \
--cc=jdike@addtoit.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox