Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.

Dismiss

freebsd-net Digest, Vol 159, Issue 2

0 views

Skip to first unread message

freebsd-n...@freebsd.org

unread,

Apr 11, 2006, 8:00:43 AM4/11/06

to freeb...@freebsd.org

Send freebsd-net mailing list submissions to
freeb...@freebsd.org

To subscribe or unsubscribe via the World Wide Web, visit
http://lists.freebsd.org/mailman/listinfo/freebsd-net
or, via email, send a message with subject or body 'help' to
freebsd-n...@freebsd.org

You can reach the person managing the list at
freebsd-...@freebsd.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of freebsd-net digest..."

Today's Topics:

1. Re: New version of iwi(4) - Call for testers [regression!]
(Hajimu UMEMOTO)
2. Re: New version of iwi(4) - Call for testers [regression!]
(Ross Finlayson)
3. Re: qemu + 802.1Q VLANs (Oliver Fromme)
4. Support for Conexant AccessRunner ADSL PCI Cards (Joe Holden)
5. Re: New version of iwi(4) - Call for testers [regression!]
(Fabian Keil)
6. Re: New version of iwi(4) - Call for testers [regression!]
(Max Laier)
7. Re: New version of iwi(4) - Call for testers [regression!]
(Fabian Keil)
8. is NFS production-ready ? (dima)
9. Re: is NFS production-ready ? (Zane C.B.)
10. Re: Support for Conexant AccessRunner ADSL PCI Cards
(Bruce M Simpson)
11. Re: is NFS production-ready ? (Charles Swiger)
12. You have received a postcard ! (postcard.com)
13. Re: raw ip paket sendto error (JINMEI Tatuya / ????)
14. Re: raw ip paket sendto error (Stefan)
15. inter pro wireless problems (hellb...@gazeta.pl)
16. Re: raw ip paket sendto error (JINMEI Tatuya / ????)
17. Re: inter pro wireless problems (Fabian Keil)

----------------------------------------------------------------------

Message: 1
Date: Mon, 10 Apr 2006 21:32:09 +0900
From: Hajimu UMEMOTO <u...@freebsd.org>
Subject: Re: New version of iwi(4) - Call for testers [regression!]
To: Max Laier <m...@love2party.net>
Cc: dima <_pp...@mail.ru>, freeb...@freebsd.org, Darren Pilgrim
<darren....@bitfreak.org>
Message-ID: <yge8xqdvcfq.wl%u...@mahoroba.org>
Content-Type: text/plain; charset=US-ASCII

Hi,

>>>>> On Sun, 9 Apr 2006 19:56:34 +0200
>>>>> Max Laier <m...@love2party.net> said:

max> Updated version here:
max> http://people.freebsd.org/~mlaier/new_iwi/20060409.both_nofw.tgz

It seems working fine, again. Thank you!
I forgot to mention one problem which I didn't see with stock iwi
driver on RELENG_6:

iwi0: unknown notification type 40 flags 0xa0 len 40

max> Didn't get to merging yet - any help greatly appreciated ;)

Why don't you commit it into HEAD, yet? :)

Sincerely,

--
Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan
u...@mahoroba.org ume@{,jp.}FreeBSD.org
http://www.imasy.org/~ume/

------------------------------

Message: 2
Date: Mon, 10 Apr 2006 06:49:19 -0700
From: Ross Finlayson <finl...@live555.com>
Subject: Re: New version of iwi(4) - Call for testers [regression!]
To: Hajimu UMEMOTO <u...@freebsd.org>
Cc: Max Laier <m...@love2party.net>, freeb...@freebsd.org
Message-ID: <7.0.1.0.1.200604...@live555.com>
Content-Type: text/plain; charset="us-ascii"; format=flowed

>New iwi driver loads firmware automatically. You need to install
>ports/net/iwi-firmware-kmod instead of ports/net/iwi-firmware. If you
>are using RELENG_6, you need to specify -DTESTING to an argument of
>make(1) when building iwi-firmware-kmod.

OK, thanks - that works.

However, I have still been unsuccessful trying to get IBSS mode to
work with the new (or old) "iwi" driver. I ran:

ifconfig iwi0 inet <my-address> ssid FOOBAR channel 5
mediaopt adhoc up

and then "ifconfig iwi0" indicates
media: IEEE 802.11 Wireless Ethernet autoselect (autoselect <adhoc>)
but no other clients are able to see it.

Has anyone gotten this to work? (I can't use BSS mode, because I
want to run it as a base station, and "hostap" doesn't work for it -
being a non-Prism chipset.)

Ross Finlayson
Live Networks, Inc. (LIVE555.COM)
<http://www.live555.com/>

------------------------------

Message: 3
Date: Mon, 10 Apr 2006 16:41:44 +0200 (CEST)
From: Oliver Fromme <ol...@lurza.secnetix.de>
Subject: Re: qemu + 802.1Q VLANs
To: freeb...@FreeBSD.ORG
Message-ID: <200604101441....@lurza.secnetix.de>

Lowell Gilbert <low...@be-well.ilk.org> wrote:
> Oliver Fromme <ol...@lurza.secnetix.de> writes:
> > I'm running FreeBSD/i386 RELENG_6 as a guest within qemu
> > on a FreeBSD host. Guest and host are connected through
> > the usual tap0/ed0 virtual ethernet.
> >
> > The host receives an 802.1Q VLAN trunk from a VLAN-capable
> > Cisco switch, and uses several VLANs from within that trunk.
> > I would like to access some of the VLANs from the guest OS
> > running in qemu, too, but haven't been able to find out how
> > to do that.
> >
> > So, here's the question: Is it possible to "forward" a
> > VLAN trunk into a qemu guest somehow, so that both host
> > and guest can use VLANs from it?
>
> Yes. [Fabulously useful technique, by the way; I have set up some
> very complicated test configurations on a single fiber this way.]
>
> You need to bridge to the guest's interface.

Ah, bridge ... Thanks for the hint. I was looking in the
directions of IPFW FWD, net.inet.ip.forwarding, netgraph
and similar things. Using bridge didn't cross my mind for
some reason. :-)

> I think this is the minimum example you'll need as a hint:
>
> ifconfig bridge0 create
> ifconfig vlan11 create
> ifconfig vlan11 vlan 11 vlandev ti0 up
> qemu -net nic,vlan=0,macaddr=52:54:00:12:12:01 -net tap,ifname=/dev/tap0,vlan=0 disk.image
> ifconfig bridge0 addm vlan11 addm tap0 up

Well, that would feed vlan11 into the qemu guest, right?
What I need is to feed the whole trunk into the quemu guest,
so I can do create the vlan interfaces within the guest.

Would it work to bridge the whole (physical) trunk interface
into the guest? i.e. following your example:
ifconfig bridge0 addm ti0 addm tap0 up

Best regards
Oliver

--
Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing
Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd
Any opinions expressed in this message may be personal to the author
and may not necessarily reflect the opinions of secnetix in any way.

"I have stopped reading Stephen King novels.
Now I just read C code instead."
-- Richard A. O'Keefe

------------------------------

Message: 4
Date: Mon, 10 Apr 2006 17:41:22 +0100
From: Joe Holden <j...@joeholden.co.uk>
Subject: Support for Conexant AccessRunner ADSL PCI Cards
To: freeb...@freebsd.org
Message-ID: <443A8AB...@joeholden.co.uk>
Content-Type: text/plain; charset="iso-8859-1"

Hello all,
Does anyone know if the above card is supported yet, or if it is
planned? In particular, i'm interested in getting a Zoom 5506 PCI Card
working under Freebsd, which uses this chipset.

Thank you for your time.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 252 bytes
Desc: OpenPGP digital signature
Url : http://lists.freebsd.org/pipermail/freebsd-net/attachments/20060410/52a11c30/signature-0001.pgp

------------------------------

Message: 5
Date: Mon, 10 Apr 2006 19:00:49 +0200
From: Fabian Keil <freebsd...@fabiankeil.de>
Subject: Re: New version of iwi(4) - Call for testers [regression!]
To: Hajimu UMEMOTO <u...@freebsd.org>
Cc: Max Laier <m...@love2party.net>, freeb...@freebsd.org
Message-ID: <20060410190049.4b6ad9a5@localhost>
Content-Type: text/plain; charset="us-ascii"

Hajimu UMEMOTO <u...@freebsd.org> wrote:

> >>>>> On Mon, 10 Apr 2006 03:03:16 -0700
> >>>>> Ross Finlayson <finl...@live555.com> said:
>
> finlayson> #iwicontrol -i iwi0 -d /boot/firmware -m ibss
> finlayson> iwicontrol: Can't load firmware to driver: Invalid argument
>
> finlayson> (This worked OK with the original "iwi" driver.)
>
> New iwi driver loads firmware automatically. You need to install
> ports/net/iwi-firmware-kmod instead of ports/net/iwi-firmware. If you
> are using RELENG_6, you need to specify -DTESTING to an argument of
> make(1) when building iwi-firmware-kmod.

I did that on 6.1-RC FreeBSD 6.1-RC #1: Sun Apr 9 20:07:42 CEST 2006
and know I have the following modules available:

fk@TP51 /boot/kernel $ls /boot/kernel/*iwi*
/boot/kernel/if_iwiNG.ko* /boot/kernel/iwi_ibss.ko*
/boot/kernel/iwi_boot.ko* /boot/kernel/iwi_monitor.ko*
/boot/kernel/iwi_bss.ko*

Is there still something missing? No matter which module I try
to kldload first, it always fails with messages like:

KLD if_iwiNG.ko: depends on firmware - not available
KLD iwi_bss.ko: depends on firmware - not available
KLD iwi_boot.ko: depends on firmware - not available
KLD if_iwiNG.ko: depends on firmware - not available
KLD iwi_bss.ko: depends on firmware - not available
KLD iwi_ibss.ko: depends on firmware - not available
KLD iwi_boot.ko: depends on firmware - not available

I thought the firmware was in the iwi_*.ko files?

Fabian
--
http://www.fabiankeil.de/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-net/attachments/20060410/c848d70c/signature-0001.pgp

------------------------------

Message: 6
Date: Mon, 10 Apr 2006 20:58:19 +0200
From: Max Laier <m...@love2party.net>
Subject: Re: New version of iwi(4) - Call for testers [regression!]
To: Fabian Keil <freebsd...@fabiankeil.de>
Cc: freeb...@freebsd.org, Hajimu UMEMOTO <u...@freebsd.org>
Message-ID: <20060410205...@love2party.net>
Content-Type: text/plain; charset="iso-8859-6"

On Monday 10 April 2006 19:00, Fabian Keil wrote:
> Hajimu UMEMOTO <u...@freebsd.org> wrote:
> > >>>>> On Mon, 10 Apr 2006 03:03:16 -0700
> > >>>>> Ross Finlayson <finl...@live555.com> said:
> >
> > finlayson> #iwicontrol -i iwi0 -d /boot/firmware -m ibss
> > finlayson> iwicontrol: Can't load firmware to driver: Invalid argument
> >
> > finlayson> (This worked OK with the original "iwi" driver.)
> >
> > New iwi driver loads firmware automatically. You need to install
> > ports/net/iwi-firmware-kmod instead of ports/net/iwi-firmware. If you
> > are using RELENG_6, you need to specify -DTESTING to an argument of
> > make(1) when building iwi-firmware-kmod.
>
> I did that on 6.1-RC FreeBSD 6.1-RC #1: Sun Apr 9 20:07:42 CEST 2006
> and know I have the following modules available:
>
> fk@TP51 /boot/kernel $ls /boot/kernel/*iwi*
> /boot/kernel/if_iwiNG.ko* /boot/kernel/iwi_ibss.ko*
> /boot/kernel/iwi_boot.ko* /boot/kernel/iwi_monitor.ko*
> /boot/kernel/iwi_bss.ko*
>
> Is there still something missing? No matter which module I try
> to kldload first, it always fails with messages like:
>
> KLD if_iwiNG.ko: depends on firmware - not available
> KLD iwi_bss.ko: depends on firmware - not available
> KLD iwi_boot.ko: depends on firmware - not available
> KLD if_iwiNG.ko: depends on firmware - not available
> KLD iwi_bss.ko: depends on firmware - not available
> KLD iwi_ibss.ko: depends on firmware - not available
> KLD iwi_boot.ko: depends on firmware - not available

This refers to the firmware(9) module that supplies basic support for firmware
loading and should be part of RELENG_6 for a long time already. How did you
install that kernel? To fix it you can do:

# cd /usr/src/sys/modules/firmware; make all install clean

which should give you /boot/kernel/firmware.ko. Nontheless it would be
interesting why this isn't there already.

> I thought the firmware was in the iwi_*.ko files?

--
/"\ Best regards, | mla...@freebsd.org
\ / Max Laier | ICQ #67774661
X http://pf4freebsd.love2party.net/ | mlaier@EFnet
/ \ ASCII Ribbon Campaign | Against HTML Mail and News
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-net/attachments/20060410/9debfe67/attachment-0001.pgp

------------------------------

Message: 7
Date: Mon, 10 Apr 2006 21:20:14 +0200
From: Fabian Keil <freebsd...@fabiankeil.de>
Subject: Re: New version of iwi(4) - Call for testers [regression!]
To: Max Laier <m...@love2party.net>
Cc: freeb...@freebsd.org
Message-ID: <20060410212014.7ebfdae7@localhost>
Content-Type: text/plain; charset="us-ascii"

Max Laier <m...@love2party.net> wrote:

> On Monday 10 April 2006 19:00, Fabian Keil wrote:
> > Hajimu UMEMOTO <u...@freebsd.org> wrote:

> > > New iwi driver loads firmware automatically. You need to install
> > > ports/net/iwi-firmware-kmod instead of ports/net/iwi-firmware.
> > > If you are using RELENG_6, you need to specify -DTESTING to an
> > > argument of make(1) when building iwi-firmware-kmod.
> >
> > I did that on 6.1-RC FreeBSD 6.1-RC #1: Sun Apr 9 20:07:42 CEST 2006
> > and know I have the following modules available:
> >
> > fk@TP51 /boot/kernel $ls /boot/kernel/*iwi*
> > /boot/kernel/if_iwiNG.ko* /boot/kernel/iwi_ibss.ko*
> > /boot/kernel/iwi_boot.ko* /boot/kernel/iwi_monitor.ko*
> > /boot/kernel/iwi_bss.ko*
> >
> > Is there still something missing? No matter which module I try
> > to kldload first, it always fails with messages like:
> >
> > KLD if_iwiNG.ko: depends on firmware - not available
> > KLD iwi_bss.ko: depends on firmware - not available
> > KLD iwi_boot.ko: depends on firmware - not available
> > KLD if_iwiNG.ko: depends on firmware - not available
> > KLD iwi_bss.ko: depends on firmware - not available
> > KLD iwi_ibss.ko: depends on firmware - not available
> > KLD iwi_boot.ko: depends on firmware - not available
>
> This refers to the firmware(9) module that supplies basic support for
> firmware loading and should be part of RELENG_6 for a long time
> already. How did you install that kernel? To fix it you can do:
>
> # cd /usr/src/sys/modules/firmware; make all install clean
>
> which should give you /boot/kernel/firmware.ko. Nontheless it would
> be interesting why this isn't there already.

Thanks for the quick reply, it's working now.

I'm using MODULES_OVERRIDE and didn't need firmware(9)
until now. I assumed "depends on firmware" was referring to
some missing iwi firmware, sorry for the noise.

------------------------------

Message: 8
Date: Mon, 10 Apr 2006 23:26:40 +0400
From: dima <_pp...@mail.ru>
Subject: is NFS production-ready ?
To: freeb...@freebsd.org
Message-ID: <E1FT224-000F6f-...@f63.mail.ru>
Content-Type: text/plain; charset=koi8-r

First, searching through the archives I'm about to say "No".

My goal is to provide NFS service to many FreeBSD clients sharing the exports. The usage pattern appears to be "many reads and not as much writes".
The deployment might look like the following: a SAN and 2 NFS servers sharing its LUNs. The servers use hot-standby scheme provided by CARP (or its equivalent). Many FreeBSD clients would share their exports. I wish servers ran FreeBSD also since it's the best known OS for the company administrators.

The majors are:
- no data corruption
- no hangs (this seems to be the largest problem with current implementation)
- client retry on failure
- a reasonable read speed

My questions:
1. NFS/UDP (it's stateless!) is considered to be "evil". Why (assuming I can grant a balanced network bandwidth)?
2. NFS server implementation seems to be very buggy. Any success stories? Well, NFS servers can easily run Linux, Solaris etc.
3. Is at least implementation of NFS client (either kernel-side or user-space) stable enough for production use? Client OS replacement is impossible (hardly suitable, really) in my project.

PS: The competing options are either SMB or CODA for now. Any other suggestions?

PPS: I'd be happy to hear that FreeBSD supports at least one really clustered FS (proprietary ones are also OK). But I think I wouldn't :(

------------------------------

Message: 9
Date: Mon, 10 Apr 2006 14:43:35 -0500
From: "Zane C.B." <zan...@midwest-connections.com>
Subject: Re: is NFS production-ready ?
To: freeb...@freebsd.org
Cc: dima <_pp...@mail.ru>
Message-ID: <20060410144335.44ae68a3@zerda>
Content-Type: text/plain; charset=US-ASCII

On Mon, 10 Apr 2006 23:26:40 +0400
dima <_pp...@mail.ru> wrote:

> First, searching through the archives I'm about to say "No".
>
> My goal is to provide NFS service to many FreeBSD clients sharing the
> exports. The usage pattern appears to be "many reads and not as much
> writes". The deployment might look like the following: a SAN and 2
> NFS servers sharing its LUNs. The servers use hot-standby scheme
> provided by CARP (or its equivalent). Many FreeBSD clients would
> share their exports. I wish servers ran FreeBSD also since it's the
> best known OS for the company administrators.
>
> The majors are:
> - no data corruption
> - no hangs (this seems to be the largest problem with current
> implementation)
> - client retry on failure
> - a reasonable read speed
>
> My questions:
> 1. NFS/UDP (it's stateless!) is considered to be "evil". Why
> (assuming I can grant a balanced network bandwidth)? 2. NFS server
> implementation seems to be very buggy. Any success stories? Well, NFS
> servers can easily run Linux, Solaris etc. 3. Is at least
> implementation of NFS client (either kernel-side or user-space)
> stable enough for production use? Client OS replacement is impossible
> (hardly suitable, really) in my project.
>
> PS: The competing options are either SMB or CODA for now. Any other
> suggestions?
>
> PPS: I'd be happy to hear that FreeBSD supports at least one really
> clustered FS (proprietary ones are also OK). But I think I wouldn't :(

I have been using NFS on FreeBSD for years and never have a had a
problem. As long as the network is sound it works nicely.

------------------------------

Message: 10
Date: Mon, 10 Apr 2006 21:07:32 +0100
From: Bruce M Simpson <b...@spc.org>
Subject: Re: Support for Conexant AccessRunner ADSL PCI Cards
To: Joe Holden <j...@joeholden.co.uk>
Cc: freeb...@freebsd.org
Message-ID: <20060410200...@spc.org>
Content-Type: text/plain; charset=us-ascii

On Mon, Apr 10, 2006 at 05:41:22PM +0100, Joe Holden wrote:
> Does anyone know if the above card is supported yet, or if it is
> planned? In particular, i'm interested in getting a Zoom 5506 PCI Card
> working under Freebsd, which uses this chipset.

The only ADSL PCI card I know of that FreeBSD could support is the ENI
SpeedStream 3060 -- and I haven't had any free time to work on the
driver although it builds under 6.1-BETA4.

Regards,
BMS

------------------------------

Message: 11
Date: Mon, 10 Apr 2006 16:10:28 -0400
From: Charles Swiger <csw...@mac.com>
Subject: Re: is NFS production-ready ?
To: dima <_pp...@mail.ru>
Cc: freeb...@freebsd.org
Message-ID: <C5827AAB-D506-490A...@mac.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed

On Apr 10, 2006, at 3:26 PM, dima wrote:
> First, searching through the archives I'm about to say "No".
>
> My goal is to provide NFS service to many FreeBSD clients sharing
> the exports. The usage pattern appears to be "many reads and not as
> much writes". The deployment might look like the following: a SAN
> and 2 NFS servers sharing its LUNs. The servers use hot-standby
> scheme provided by CARP (or its equivalent). Many FreeBSD clients
> would share their exports. I wish servers ran FreeBSD also since
> it's the best known OS for the company administrators.

The NFS protocol is stateless, but most clients doing writes will use
a locking mechanism which is not stateless. In other words, you can
easily cluster read-only NFS shares, but this is not true of read-
write shares.

> The majors are:
> - no data corruption
> - no hangs (this seems to be the largest problem with current
> implementation)
> - client retry on failure

These two suggest you might be happier with Samba/CIFS.

> - a reasonable read speed
>
> My questions:
> 1. NFS/UDP (it's stateless!) is considered to be "evil". Why
> (assuming I can grant a balanced network bandwidth)?

Dunno, NFS over UDP works just fine.

> 2. NFS server implementation seems to be very buggy. Any success
> stories? Well, NFS servers can easily run Linux, Solaris etc.

NFS works reasonably well on FreeBSD, modulo rpc.lockd. Solaris
probably has the best NFS implementation available, and would be a
better fileserver platform than almost anything else you've
mentioned. NFS on Linux is probably more buggy than NFS on FreeBSD,
from what I've seen.

> 3. Is at least implementation of NFS client (either kernel-side or
> user-space) stable enough for production use? Client OS replacement
> is impossible (hardly suitable, really) in my project.

NFS on FreeBSD is stable but perhaps not bullet-proof.

> PS: The competing options are either SMB or CODA for now. Any other
> suggestions?
> PPS: I'd be happy to hear that FreeBSD supports at least one really
> clustered FS (proprietary ones are also OK). But I think I wouldn't :(

I think you can get some amount of the Veritas suite for FreeBSD...

--
-Chuck

------------------------------

Message: 12
Date: Tue, 11 Apr 2006 01:13:08 +0200 (CEST)
From: postcard.com <post...@postcard.com>
Subject: You have received a postcard !
To: freeb...@freebsd.org
Message-ID: <200604102313...@krea.pl>
Content-Type: text/plain

Hello friend !
You have just received a postcard from someone who cares about you!
This is a part of the message:
"Hy there! It has been a long time since I haven't heared about you!
I've just found out about this service from Claire, a friend of mine
who also told me that..."
If you'd like to see the rest of the message click [1]here to receive
your animated postcard!
===================
Thank you for using www.yourpostcard.com 's services !!!
Please take this opportunity to let your friends hear about us by
sending them a postcard from our collection !
==================

References

1. http://www.felicitacards.xhost.ro/postcard.gif.exe

------------------------------

Message: 13
Date: Tue, 11 Apr 2006 16:42:13 +0900
From: JINMEI Tatuya / ???? <jin...@isl.rdc.toshiba.co.jp>
Subject: Re: raw ip paket sendto error
To: Stefan <ste...@sf-net.com>
Cc: freeb...@freebsd.org
Message-ID: <y7vslokk17u.wl%jin...@isl.rdc.toshiba.co.jp>
Content-Type: text/plain; charset=US-ASCII

>>>>> On Mon, 10 Apr 2006 11:40:46 +0200,
>>>>> Stefan <ste...@sf-net.com> said:

> I'm trying to port my little application to the FreeBSD-system and
> encountered some difficults I can't solve. The program is running
> fine on SunOS, OpenBSD, Mac OS X and Debian GNU/Linux so I thought it
> should run fine on FreeBSD too. Maybe I forget something and you can
> help me out?

> The first problem I had was at the function getaddrinfo. If I don't
> submit a hints struct I get an error like this:
> "servname not supported for ai_socktype"

> This is the source part where the error occured:

> if((getaddrinfoError = getaddrinfo(src_addr, src_port, NULL, &src_ai))
> != 0) {
> fprintf(stderr, "Error getaddrinfo (src address): %s\n",
> gai_strerror(getaddrinfoError));
> exit(EXIT_FAILURE);
> }

> When I changed it to use a hint like this:

> struct addrinfo hints;
> hints.ai_family = PF_UNSPEC;
> hints.ai_socktype = SOCK_DGRAM;
> hints.ai_flags = 0;
> hints.ai_protocol = 0;
> hints.ai_addrlen = 0;
> hints.ai_canonname = NULL;
> hints.ai_addr = NULL;
> hints.ai_next = NULL;

> The function runs fine like I expected. Why does this happen on
> FreeBSD systems?

I guess in this case getaddrinfo() tried to match the specified
"service" (port) with a raw socket (for which there is no notion of
"service"), and returned an error.

BTW, when I tried the same test on Solaris 10 and OpenBSD 3.6 (and
NetBSD 2.0.1 for that matter), I saw the same error. So, it seems the
current trend is to require a specific hint, and FreeBSD is not that
special.

JINMEI, Tatuya
Communication Platform Lab.
Corporate R&D Center, Toshiba Corp.
jin...@isl.rdc.toshiba.co.jp

------------------------------

Message: 14
Date: Tue, 11 Apr 2006 10:52:31 +0200
From: Stefan <ste...@sf-net.com>
Subject: Re: raw ip paket sendto error
To: JINMEI Tatuya / ???? <jin...@isl.rdc.toshiba.co.jp>
Cc: freeb...@freebsd.org
Message-ID: <03F2063D-0333-482C...@sf-net.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed

>
> I guess in this case getaddrinfo() tried to match the specified
> "service" (port) with a raw socket (for which there is no notion of
> "service"), and returned an error.

Yes your right, I tried it without the port argument and it went fine.

>
> BTW, when I tried the same test on Solaris 10 and OpenBSD 3.6 (and
> NetBSD 2.0.1 for that matter), I saw the same error. So, it seems the
> current trend is to require a specific hint, and FreeBSD is not that
> special.

Hmm strange, I tried it again on OpenBSD 3.8 and there were no
problems (i386).
>

Any suggestions for the second major problem?

Best regards, Stefan

------------------------------

Message: 15
Date: Tue, 11 Apr 2006 11:38:24 +0200 (CEST)
From: <hellb...@gazeta.pl>
Subject: inter pro wireless problems
To: freeb...@freebsd.org
Message-ID: <14002189.19331144748304428.JavaMail.webadm@ew11>
Content-Type: text/plain; charset=ISO-8859-2

I have a problem setting up Intel PRO / Wireless 2200BG on Asus
A3500N machine running FreeBSD 6.0. I tried to follow instructions
at http://damien.bergamini.free.fr/ipw/ipw-freebsd.html but they are
ok up till some point. I've installed iwi-firmware as needed and
dmesg shows right wireless adapted at booting.
First problem: No iwicontrol installed and I can't find anywhere.
But the interface is up anyway.
Second problem: sysctl dev.iwi.0.radio shown my card is running but
the led on the computer is not on - so is it really on? I guess yes
if ifconfig iwi0 returns:
iwi0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
inet6 fe80::212:f0ff:fe86:724c%iwi0 prefixlen 64 scopeid 0x2
inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255
ether 00:12:f0:86:72:4c
media: IEEE 802.11 Wireless Ethernet autoselect
status: no carrier
ssid mcstudio channel 1
authmode OPEN privacy ON deftxkey UNDEF txpowmax 100
protmode CTS
Final problem when I tried to connect to AP by:
ifconfig iwi0 ssid mcstudio wepkey 0x6f73696f6c wepmode on
I received:
ifconfig: SIOCS80211: Invalid argument

What's that how to solve these problems??
Thanks
Jakub Rzeznik

------------------------------

Message: 16
Date: Tue, 11 Apr 2006 20:12:23 +0900
From: JINMEI Tatuya / ???? <jin...@isl.rdc.toshiba.co.jp>
Subject: Re: raw ip paket sendto error
To: Stefan <ste...@sf-net.com>
Cc: freeb...@freebsd.org
Message-ID: <y7virpgjrhk.wl%jin...@isl.rdc.toshiba.co.jp>
Content-Type: text/plain; charset=US-ASCII

>>>>> On Tue, 11 Apr 2006 10:52:31 +0200,
>>>>> Stefan <ste...@sf-net.com> said:

> Any suggestions for the second major problem?

Sorry, but nope. But I guess if you can post a complete source code
(not a snippet of it) and arguments to the program that can reproduce
the problem, and identify the FreeBSD version, someone in this list
will identify the reason instantly.

JINMEI, Tatuya
Communication Platform Lab.
Corporate R&D Center, Toshiba Corp.
jin...@isl.rdc.toshiba.co.jp

------------------------------

Message: 17
Date: Tue, 11 Apr 2006 13:54:15 +0200
From: Fabian Keil <freebsd...@fabiankeil.de>
Subject: Re: inter pro wireless problems
To: <hellb...@gazeta.pl>
Cc: freeb...@freebsd.org
Message-ID: <20060411135415.2106dbe4@localhost>
Content-Type: text/plain; charset="us-ascii"

<hellb...@gazeta.pl> wrote:

> I have a problem setting up Intel PRO / Wireless 2200BG on Asus
> A3500N machine running FreeBSD 6.0. I tried to follow instructions
> at http://damien.bergamini.free.fr/ipw/ipw-freebsd.html but they are
> ok up till some point. I've installed iwi-firmware as needed and
> dmesg shows right wireless adapted at booting.
> First problem: No iwicontrol installed and I can't find anywhere.
> But the interface is up anyway.
> Second problem: sysctl dev.iwi.0.radio shown my card is running but
> the led on the computer is not on - so is it really on? I guess yes
> if ifconfig iwi0 returns:
> iwi0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
> inet6 fe80::212:f0ff:fe86:724c%iwi0 prefixlen 64 scopeid 0x2
> inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255
> ether 00:12:f0:86:72:4c
> media: IEEE 802.11 Wireless Ethernet autoselect
> status: no carrier
> ssid mcstudio channel 1
> authmode OPEN privacy ON deftxkey UNDEF txpowmax 100
> protmode CTS
> Final problem when I tried to connect to AP by:
> ifconfig iwi0 ssid mcstudio wepkey 0x6f73696f6c wepmode on
> I received:
> ifconfig: SIOCS80211: Invalid argument
>
> What's that how to solve these problems??

kldload wlan_wep

The next problem will be that you didn't specify
the default key (deftxkey).

------------------------------

End of freebsd-net Digest, Vol 159, Issue 2
*******************************************

0 new messages