Hey all -

I have a server (firewall, http/s, pop/imap/smtp, ftp, Samba, CUPS, ssh) set up as follows:

(eth1) 192.168.1.1 ---> Wired network (6 machines)
(eth0) 64.x.y.z ---> Internet
(eth2) 192.168.88.1 ---> Linksys WRT54G WAP/router


The WRT54G is set up as follows:
External IP: 192.168.88.2
Internal IP: 192.168.56.254
Internal net: 192.168.56.0/24 (dhcp)
Running 128-bit WEP
MAC table enabled


All's well on the wired internal network (eth1). Everyone can get out, and all internal services (CUPS, Samba) are accessible.

On the wireless network, the router's DHCP server works, and I'm able to get out to the Internet (ping, http, ftp, ssh, etc.) without any problems. However, I can't get CUPS on a laptop to talk to the CUPS server on the three-homed machine; nor will a Windows laptop pick up anything from the Samba server. I'm sure this is a configuration problem on the WRT54G. The cupsd.conf and smb.conf files are set up to allow browsing on the 192.168.88.x network. I disabled the internal firewall on the WRT54G, and configured my firewall script on the server to allow everything to and from the 192.168.88.x network.

The router's configuration allows port-forwarding, but not to the entire internal network (specific machines with static IPs only). I have the WRT54G set up as a "gateway"; if I change it to "router" I can't get out to the Internet at all (but of course, I could have set up the routing table incorrectly).

Anyone have a setup like this working right and can give me a clue as to how to get CUPS and Samba browsing to work across the WAP?

Much appreciated - Bob

Can't help you with the router problem. I just wanted to ask why you didn't just replace eth2 in your "firewall" with a wireless card? It would make what you're doing a whole lot easier.

I finally fixed it by just plugging the internal side of the router (along with the rest of my wired internal network) into eth1, essentially setting it up as a WAP only. Everything works now. I was trying to be TOO efficient doing it the other way.

Bob

That's not a solution. Now your neighbors have access to your internal network

WEP and the MAC filtering table are still enabled; tried getting on with a different wireless NIC or without the WEP key, couldn't. So it's as secure (so to speak) as it was before; granted, WEP and MAC filtering aren't the greatest defenses, but they're better than nothing.

No, it's not as secure as it was because before you had a host between your wireless and everything else. Now you don't.

The WEP will keep some people out, as will the MAC ACLs, but with a high gain antenna and a couple days time to snarf packets -- since they've got your MAC and cracked your keys -- someone who knows what they're doing will be in your network the first time you turn your laptop off.

It probably won't happen, but I thought you'd like to know.

Funny that we should cross paths.

But I have the exact same problem as you do with a new Linksys WRT54G router.
I called linksys and they assured me that there is no problems with there routers.

I setup two boxes, one Linux FC11 and one box Windows XP and both computers can ping the Printer but can't print with Cups or Windows.

I know the settings are correct because I used a 2Wire783 router with primary setup and they both printed to Printer.

So I'm convinced it's the Linksys Router. and Linux and Windows has problem of printing.

What did you finally do to get network printing.