Thanks Rado,
The diagram included that Gateway setting just because it was the most
recent thing I had tried. Its now as you describe (the way I would expect it
to be also)
So yes you are right .. All my LAN traffic should go through eBox like this:
http://www.gliffy.com/pubdoc/2049706/L.png
I notice that although the client has a normal looking output for the
command *route -*n
Like this:*
*
*# route -n*
Kernel IP routing table
*Destination Gateway Genmask Flags Metric Ref Use
Iface*
192.168.4.0 0.0.0.0 255.255.255.0 U 1 0
0 eth0
169.255.0.0 0.0.0.0 255.255.0.0 U 1000 0
0 eth0
0.0.0.0 192.168.4.1 0.0.0.0 UG 0
0 0 eth0
The eBox server only has this result !! :
*# route -n*
Kernel IP routing table
*Destination Gateway Genmask Flags Metric Ref Use
Iface*
192.168.4.0 0.0.0.0 255.255.255.0 U 1 0
0 eth1
169.168.2.0 0.0.0.0 255.255.255.0 U 1 0
0 eth0
I dont know a lot about how to read this especially in the context of eBox
yet, but I have learned when it looks out of place.
Is there not supposed to be at least one record with a gateway setting in
it?
In this case perhaps two extra records like this :
Destination Gateway Genmask Flags Metric Ref Use
Iface
0.0.0.0 192.168.4.1 0.0.0.0 UG 0
0 0 eth1
0.0.0.0 192.168.2.1 0.0.0.0 UG 0
0 0 eth0
This really is an out of the box clean install, so providing there is no
secret setting I dont know about, this should be plug and play!
Perhaps I have a package enabled thats causing a problem ! Or i'm missing a
package! I have completely reinstalled countless times with slightly
different configurations to test that but it should not be necessary.
Can you suggest the smallest package set to enable for this setup ?
Oh! and if a package is installed but not enabled will that have any
influence? e.g. Firewall or DNS.. I think it should not but!, there is
always a *but*.
Thanks again.
3poFred
> 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
>
_______________________________________________
ebox-user mailing list
[email protected]
http://lists.ebox-platform.com/cgi-bin/mailman/listinfo/ebox-user
