On 03/31/2010 04:05 AM, Network Messenger wrote:
Thanks for the reply Rado,
Ok a Picture says a thousand words.
This is the gliffy diagram http://www.gliffy.com/publish/2049706/
Its just a diagram of what the layout looks like.
Its got to be something simple.
No Firewall means no ports closed.
DHCP is working OK both to the client and to the WAN connection eth0
of eBox
When I put a check in External WAN for eth0 I get a gateway record
created with 192.168.2.1 as the IP. It is Enabled and set to default.
I have tried also setting the Default Gateway in the DHCP section to
refer to the gateway record so its set to Configured Ones =
DHCP-gw-eth0 instead of eBox
So on the client I now get a Gateway of 192.168.2.1 instead of
192.168.4.1 but its not helping. I still cant ping 192.168.2.1 or
anything on the internet.
The picture looks pretty clean, but:
your router is on different segment than your laptop. Your laptop has to
have your ebox as a gateway (and your ebox has to have default route set
to router's IP address). Try to set it up that way. Btw, what are your
netmasks on both ebox interfaces?
The flow of your packets should follow this route:
router <-> ebox <-> lan
Unless you have netmask like 255.255.0.0, your lan computers won't be
able to see router directly. (and, broadening your netmask is not a
solution, what you really want is to have all your traffic go trough
ebox, am I right?)
Rado
_______________________________________________
ebox-user mailing list
[email protected]
http://lists.ebox-platform.com/cgi-bin/mailman/listinfo/ebox-user
