Kelley Law wrote:
Thanks Frank,
All the connections are plugged in correctly.
The DSL is connect to the WAN on the router and the Airport is connected to one of the 4 LAN ports.
The problem was / is that I couldn't find the bridge mode on the Airport config tool. I found that the Airport Java Configurator gave access to bridge mode. And NAT and DHCP is turned off, with the the router handling this.
Now wireless is able to see computers on the LAN but not the other way. This is really odd...
On Jul 28, 2004, at 7:46 PM, Frank Keeney wrote:
Kelley,
Many of the Router / Access Points are designed for connecting to the
Internet as a "firewall". On these types of devices there is normally an
Ethernet port labeled "WAN" or "Internet", this port is designed for a
direct connection to a DSL or Cable Modem. Do _not_ use this port if you are
attempting to allow full access between the wired and wireless networks. Use
one of the other ports for the Ethernet or wired side of the network.
As described above, you are not using any of the router functions and should
allow access between wired and wireless.
Frank Keeney http://www.wlanparts.com
-----Original Message----- On Behalf Of Kelley Law
I was asked to look at a friends network, and seem to have run into a small problem.
The wired computer can see the wireless but not visa versa. They are using a using a Network Everywhere router NT041 with a Airport Extreme connected to it.
Any ideas on how to get the wireless computers to see the wired? I have turned off NAT and DHCP on the Airport but can't seem to find the bridging function.
Also does any know about the Network Everywhere router, I see it is a Linksys. I am wondering if the firmware can me changed like the WRT54G?
What operating system is on each on the machines? What IP address is being used for each? I assume that the following diagram is correct?
+-----+ | DSL | +--+--+ | V (WAN port) +------+ | linksys | (provides NAT and DHCP) +--------+ | | |--------> +--------+ | | | Airport | --------------> wireless Computer (1) | | +-------+ | |----------> Wired Computer (1) |------------> Wired Computer (2)
I don't know much about airport, but I beleive that he needs to be a DHCP server for all of the wireless machines, especially so that he can be the gateway for them back to the linksys. The airport gateway gets his network address from the linksys,
and I'm not sure how the wireless computers are getting their addresses. (especially since they have to use the airport device as a gateway, and since it is a router, how does he know where to send messages. Or does AIRPORT always relay all messages to both the wired lan and to the wireless lan?)
With two DHCP servers, you have to avoid addressing conflicts, and for most operating systems, the machines must be on the same subnet to "see" each other using the NetBEUI protocol. Maybe you should consider having the Linksys issue addresses in the range of " 2 to 128", and the Airport issue addresses "129 to 254". I don't know if this will work, however, because I have a gut feel that the two segments need to me on separate subnets. I'm sure somebody on the LIST will correct me if I'm wrong.... <grin>
I have a similar network, but am using linksys wireless rather than airport. (I no longer have any MAC's.)
My wireless machines are in the 192.168.Y.xxx subnet network, and the wired machines are in the 192.168.Z.xxx subnet.
Each of these subnets uses a netmask of 255.255.255.0 Because NetBEUI "mesages" are not sent across subnet boundries, Windows "Network Neighborhood" does not display the machines in the other subnet, but can talk to them, when they are directly addressed.
/s/ Bill Turner, wb4alm
