Mine is the same as your's.
Bob Miller ([EMAIL PROTECTED]) wrote:
>
> larry price wrote:
>
> > > Anyone know what a BSSID is? That's what kismet reports, and
> > > I kind of assumed that's the access point's MAC. But is it?
> > >
> > BSSID : Basic Service Set Identifier
>
> It looks like a MAC.
On Wednesday 12 January 2005 09:25 am, Bob Miller wrote:
: larry price wrote:
: > > Anyone know what a BSSID is? That's what kismet reports, and
: > > I kind of assumed that's the access point's MAC. But is it?
: >
: > BSSID : Basic Service Set Identifier
:
: It looks like a MAC. Our home networ
larry price wrote:
> > Anyone know what a BSSID is? That's what kismet reports, and
> > I kind of assumed that's the access point's MAC. But is it?
> >
> BSSID : Basic Service Set Identifier
It looks like a MAC. Our home network has a BSSID of 00:0C:41:66:81:A8,
which is the MAC stamped on th
> On Tue, 11 Jan 2005 08:00:49 -0800, Bob Miller <[EMAIL PROTECTED]> wrote:
>
> > Anyone know what a BSSID is? That's what kismet reports, and
> > I kind of assumed that's the access point's MAC. But is it?
> >
> > Anyway, I used ifconfig, iwconfig (frustratingly), and kismet. What
> > else shou
On Tue, 11 Jan 2005 08:00:49 -0800, Bob Miller <[EMAIL PROTECTED]> wrote:
> Anyone know what a BSSID is? That's what kismet reports, and
> I kind of assumed that's the access point's MAC. But is it?
>
BSSID : Basic Service Set Identifier
> Anyway, I used ifconfig, iwconfig (frustratingly), and
> Could it have been a DHCP problem rather than a wireless problem?
>
> Was the AP made by D-Link (they have a proprietary speedup, that
> degrades for uncapable windows machines but not for the rest of the
> world)?
I am using a D-link AP at home and it works fine on all my systems.
___
Michael H. Collins wrote:
> do you do "dhcpcd eth1" or whatever your wireless device thinks it is?
Yes. Ethereal showed DHCP discover packets going out, but no replies
coming back. Unless I set them, iwconfig showed no ESSID, zero access
point, and the wrong frequency. There was an issue wher
do you do "dhcpcd eth1" or whatever your wireless device thinks it is?
Bob Miller wrote:
Lots of you are using WiFi with Linux. I am too, in certain
locations. (home and The Strand, to name two.) But when it doesn't
work, I have zero clue how to diagnose what's wrong.
This weekend, I was at a h
larry price wrote:
> Could it have been a DHCP problem rather than a wireless problem?
I don't think so. At one point, I did assign a static IP
address, and I still couldn't talk to anybody.
> Was the AP made by D-Link (they have a proprietary speedup, that
> degrades for uncapable windows mach
--- larry price <[EMAIL PROTECTED]> wrote:
> Could it have been a DHCP problem rather than a
> wireless problem?
Good point Larry. I've had these types of issues
before. More than once they've been solved by manually
assigning an IP vs. waiting for one (sniff for a bit
to see the net in use, typ
On Mon, 10 Jan 2005 22:51:18 -0800, Bob Miller <[EMAIL PROTECTED]> wrote:
> Lots of you are using WiFi with Linux. I am too, in certain
> locations. (home and The Strand, to name two.) But when it doesn't
> work, I have zero clue how to diagnose what's wrong.
>
> This weekend, I was at a hotel
Lots of you are using WiFi with Linux. I am too, in certain
locations. (home and The Strand, to name two.) But when it doesn't
work, I have zero clue how to diagnose what's wrong.
This weekend, I was at a hotel with an open access WiFi network. All
of the Windows users I was with connected to
12 matches
Mail list logo
