Hi,
Please email freebsd-wireless@ with wireless related questions.
Try "wlandebug -i wlan0 +crypto" and see if you get encryption errors.
Unfortunately there's currently no broadcom NIC maintainer, so things
are falling behind.
adrian
___
freebsd-q
On Tue, May 08, 2012 at 03:07:04AM +1000, Ian Smith wrote:
> In freebsd-questions Digest, Vol 414, Issue 1, Message: 13
> On Sun, 06 May 2012 21:48:19 +0100 Chris Whitehouse
> wrote:
> > On 06/05/2012 17:31, Ian Smith wrote:
> > > Anton, I'm not sure what the state of the art is for multiple ne
In freebsd-questions Digest, Vol 414, Issue 1, Message: 13
On Sun, 06 May 2012 21:48:19 +0100 Chris Whitehouse wrote:
> On 06/05/2012 17:31, Ian Smith wrote:
> > Anton, I'm not sure what the state of the art is for multiple network
> > profiles for such as wireless vs wired, home and work etc,
On 06/05/2012 17:31, Ian Smith wrote:
Anton, I'm not sure what the state of the art is for multiple network
profiles for such as wireless vs wired, home and work etc, but look
around. I recall one called just 'profile' from years ago, and more
recently talk of 'failover' setups for wired/wireles
In freebsd-questions Digest, Vol 413, Issue 11, Message: 21
On Sat, 5 May 2012 19:26:00 -0400 (EDT) Chris Hill wrote:
> On Sat, 5 May 2012, Robert Bonomi wrote:
>
> > Anton Shterenlikht wrote;
>
> [snip]
>
> >> ...I still find the whole networking area perfectly impenetrable. (If
> >>
On Sat, 5 May 2012, Robert Bonomi wrote:
Anton Shterenlikht wrote;
[snip]
...I still find the whole networking area perfectly impenetrable. (If
you can recommend a really introductory book on the subject, I'd
really appreciate it.
[snip]
See also "TCP/IP Network Administration". This i
Anton Shterenlikht wrote;
> I'm afraid I understand very little
> from what you've written. Sorry
> to be such a shmuck. I've read a couple
> of books on networking, someting like
> Patterson & Hennesy (?) Networking - system
> approach (?), but I still find
> the whole networking area perfectly
On Sat, May 05, 2012 at 01:32:00PM -0500, Robert Bonomi wrote:
>
> : Anton Shterenlikht wrote:
> > On Fri, May 04, 2012 at 04:56:33PM -0500, Robert Bonomi wrote:
> > >
> > > It looks like you're missing a route.
> > >
> > > I suspect you've got a wired ethernet port, that is being conigured
> >
: Anton Shterenlikht wrote:
> On Fri, May 04, 2012 at 04:56:33PM -0500, Robert Bonomi wrote:
> >
> > It looks like you're missing a route.
> >
> > I suspect you've got a wired ethernet port, that is being conigured
> > with a default address. and the default route points -there-.
> >
> > Plea
On Sat, May 05, 2012 at 04:38:18PM +1000, Ian Smith wrote:
> On Fri, 4 May 2012 21:03:07 +0100, Anton Shterenlikht wrote:
> [..]
> > wlan0: flags=8843 metric 0 mtu 1500
> > ether 00:c0:49:58:00:fe
> > inet 192.168.1.104 netmask 0xff00 broadcast 192.168.1.255
> > nd6
On Sat, May 05, 2012 at 07:30:17AM +0800, Buganini wrote:
> how about
> `ifconfig wlan0 mode 11b`
>
> 11g sticks very soon for me and some other people.
>
> Regards,
> Buganini
seems to make no difference:
wlan0: flags=8843 metric 0 mtu 1500
ether 00:c0:49:58:00:fe
inet 192.168.
On Fri, May 04, 2012 at 04:56:33PM -0500, Robert Bonomi wrote:
>
> Anton Shterenlikht wrote:
> > I've US Robotics 5411 wireless pccard device.
> > It's identified as:
> >
> > # pciconf -lv
> > *skip*
> > siba_bwn0@pci0:3:0:0: class=0x028000 card=0x431814e4 chip=0x431814e4
> > rev=0x02 hdr=0x00
On Fri, 4 May 2012 21:03:07 +0100, Anton Shterenlikht wrote:
[..]
> wlan0: flags=8843 metric 0 mtu 1500
> ether 00:c0:49:58:00:fe
> inet 192.168.1.104 netmask 0xff00 broadcast 192.168.1.255
> nd6 options=29
> media: IEEE 802.11 Wireless Ethernet OFDM/36Mbps
how about
`ifconfig wlan0 mode 11b`
11g sticks very soon for me and some other people.
Regards,
Buganini
2012/5/5 Anton Shterenlikht :
> I've US Robotics 5411 wireless pccard device.
> It's identified as:
>
> # pciconf -lv
> *skip*
> siba_bwn0@pci0:3:0:0: class=0x028000 card=0x431814e4 chip=0x
Anton Shterenlikht wrote:
> I've US Robotics 5411 wireless pccard device.
> It's identified as:
>
> # pciconf -lv
> *skip*
> siba_bwn0@pci0:3:0:0: class=0x028000 card=0x431814e4 chip=0x431814e4
> rev=0x02 hdr=0x00
> vendor = 'Broadcom Corporation'
> device = 'BCM4318 [AirForce
I've US Robotics 5411 wireless pccard device.
It's identified as:
# pciconf -lv
*skip*
siba_bwn0@pci0:3:0:0: class=0x028000 card=0x431814e4 chip=0x431814e4 rev=0x02
hdr=0x00
vendor = 'Broadcom Corporation'
device = 'BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller'
16 matches
Mail list logo