> Hello Enrique,
>
> good to hear you made such good progress!

Thanks! I'm very happy

> Why do you want to use the WAN port? You could try reconfiguring the WRT
> as compdoc suggests, but the main issue I see is that the WRT is a
> router with an intergrated firewall. You are making your life alot
> harder because of that since the WRT will filter the traffic and treat
> the Endian's green zone as a red zone. What you need is a simple switch
> to "distribute" the green network to your clients.
>        Since the WRT is a router/firewall and Endian is one aswell, you will
> keep having difficulties there. For example you would want to make a
> port forward and you would have to forward the port from endian to the
> WRT and then make another forward from the WRT to the client. Using the
> LAN port on the WRT should bypass all those issues.
> (Personally I dont like having several routers/firewalls connected in a
> row because problem solving is a pain in such a scenario)

I thought connecting green nic to WRT's wan port was essential, but I
see it is not. I'm afraid I don't have a switch at home (where I'm
installing and testing everything). But I do have one at office, and
the purpose of all this "game" is to learn for installing this old PC
with Endian at office and secure everything (although there are 4 pcs
only)

> If you want to use the WAN port though, you should definetly do it as
> compdoc described and have the WRT DHCP server turned on. The Endian
> DHCP server cannot work since its connected to the WRT's WAN.

Great! will test it asap

> (Endian-WRTLAN)If you changed the config to take automatic IP, it should
> take an IP from the range of 192.168.1.30-192.168.1.50 and have as
> default gateway 192.168.1.20 and primary DNS 192.168.1.20. Just like the
> WRT gets such an IP.

I see

> (Endian-WRTWAN) If you keep Endian on the WRT's WAN, you should activate
> DHCP on the WRT and when you set to "Automatic IP" you should get an IP
> from the range you setup in WRT.

Ahh... coool

> Try setting "facebook.com" instead of "www.facebook.com" that might do
> the trick.

Thanks! will try that

------------------------------------------------------------------------------
This SF.net email is sponsored by 

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev 
_______________________________________________
Efw-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/efw-user

Reply via email to