"tommy" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) om...
> Confusion on my part is certainly a possibility.
>
> My desired IP is what is shown below, 192.168.1.102 whenever it sees
> the IPCONFIG-indicated MAC of 32-BB-09-A3-92-64.
>
> But, what is printed on the card is MAC address 00-0D-88-55-B7-BB
> which must be in the MAC address filter.
The first 6 digits - 00-0D-88 - identify the manufacturer as D-Link (you can
look this up in a database on the IEEE public web site). This has to be the
correct MAC address for your wifi client adapter.
Your ipconfig dump does not show any wifi device. It shows an Ethernet
network bridge. The fact that I see neither Ethernet nor wifi devices is
very odd. Any laptop made in the last 5 or 10 years normally has an Ethernet
on the motherboard, whether you want it or not, so the fact that you don't
seem to have one is strange. And I would expect to see a clearly-identified
wireless device entry.
The address 32-BB-09-A3-92-64 is a locally-administered MAC address. That
means it is not a burned-in address on a real device, it is an address
created dynamically by XP for the bridge, which is a pseudo-device. It's not
associated with any vendor. Did you intentionally set up a network bridge,
or did this happen as a result of the install?
You didn't say the wifi network isn't working, so I'm going to assume that
wifi is working for you, and we're just trying to explain the MAC address
anomaly.
It is possible that the G-650 is set up something like this:
The install process inserts a network bridge between the G-650 device driver
and the TCP/IP stack. This is a software bridge ordinarily used to move
layer 2 frames directly between two network devices - for example, one
Ethernet to another, or wifi <-> Ethernet. The bridge would normally
cross-connect two two hardware device drivers. Here, there is only one
device, but you could create a fake, or null, device with the
locally-administered MAC address, build the TCP/IP stack on top of that, and
then use the bridge to mediate between the virtual wifi device with the fake
MAC address, and the real wifi device. Then the local TCP/IP stack would see
only the fake device with its fake MAC address at the bottom of its stack,
and when it sends DHCP discovery packets, it would include that address in
the IP datagrams. The 802.11 frames would continue to bear the real MAC
address, so MAC filtering would require that.
I'm just speculating here, because I've never seen this. If I'm right, I
have no idea why it would be done this way. I could certainly be wrong. I
have an AG-650, which I would have thought builds a stack the same way as
your G-650, and on my XP, ipconfig /all clearly shows a wifi device with
TCP/IP sitting directly over it. Note that a bridge might also explain why
we don't see a configured wireless device - the device is displayed only if
a TCP/IP stack is configured directly over it (I verified that by
temporarily disabling all stack elements over my Ethernet device - the entry
disappeared from ipconfig /all).
>
> -----------------------------------------------------
> Microsoft Windows XP [Version 5.1.2600]
> (C) Copyright 1985-2001 Microsoft Corp.
>
> C:\Documents and Settings\Tommy>ipconfig /all
>
> Windows IP Configuration
>
> Host Name . . . . . . . . . . . . : tlaptop
> Primary Dns Suffix . . . . . . . :
> Node Type . . . . . . . . . . . . : Hybrid
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
>
> Ethernet adapter Network Bridge:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : MAC Bridge Miniport
> Physical Address. . . . . . . . . : 32-BB-09-A3-92-64
> Dhcp Enabled. . . . . . . . . . . : Yes
> Autoconfiguration Enabled . . . . : Yes
> IP Address. . . . . . . . . . . . : 192.168.1.102
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.1.1
> DHCP Server . . . . . . . . . . . : 192.168.1.1
> DNS Servers . . . . . . . . . . . : 192.168.1.1
> Lease Obtained. . . . . . . . . . : Wednesday, February 11,
> 2004 7:56:46
> AM
> Lease Expires . . . . . . . . . . : Wednesday, February 18,
> 2004 7:56:46
> AM
>
> C:\Documents and Settings\Tommy>
> -------------------------------------------
|