How are you using it ?
>

 >It depends on the server role. I have a line that act as a communication
gateway, and they have two NICs that work like a charm. I think that you're
having issues with some minor configuration mistake.

I expect you are right.. I hope you are right. I'm have been in IT long
enough to know I dont know everything and all is possible, but what have I
done wrong!?

As an example install set up let me run through this.

I'm implementing this as I type so it is exact. Basing it on this
http://www.gliffy.com/pubdoc/2049706/L.png I am going to use a static IP for
the WAN facing eth0 instead of DHCP

Check Module Status:
*Network **                       *YES
*Firewall* *                       *No
*Antivirus  **                    *No*
DHCP **          *                 YES
*DNS **          *                   YES*
Backup**        **                 *No*  **
Events** **          *               YES*
Logs** **          *                  YES*
Monitor** **          *              YES*
NTP**           *                   YES* **
**VPN                              *No* **
*
*Software Management**  *YES* **
**Traffic Shaping  **          *No*
**Users and Groups**        *YES* **
**Web Server**                  *No* **
**Mail               **             *No
*RADIUS  **                     *No*
**File Sharing **               *YES* **
**HTTP Proxy  **              *No*
**User Corner  **               *YES*
**Webmail  **                    *No*
**Groupware  **                *No*
**Printer Sharing**           *YES


Go to *Netwodk -> Interfaces*
eth0
Method       Static
External (WAN) Yes
IP address 192.168.2.80     (This is out of the DHCP range of the router on
the WAN)
Netmask    255.255.255.0
*
*
Press* change
*
Save and confirm

go to eth1
Method:      Static
External (WAN): NO
IP address: 192.168.4.1
Netmask:    255.255.255.0

Press* change
*
Save and confirm

Go to Network -> Gateways
                          (No records listed yet )
Add new
Enabled:        YES
Name :         TheGateway
IP address:   192.168.2.1
Interface:       eth0
Weight:          1
default:         YES

Press Add
                          (Gateway list is shown with all settings as above)
Save and confirm

Go to DHCP
select static interface     eth1 (LAN facing eth)

Defaults for common options tab:
Default gateway:           eBox
Search Domain:            Custom  [Blank]
Primary nameserver:      local eBox DNS
Secondary nameserver:  [Blank]
NTP server:                    None
Wins server:                   None
(NOTE making any changes to above default setting requires setting search
domain but its not necessary to change these. It is enough to have the DHCP
range configured to get the clients getting an IP and gateway)

go to Ranges near bottom of page
click Add new
Name:   LANRange
>From :   192.168.4.100
To :       192.168.4.200

Save and confirm
Check range in displayed in list as per settings: YES

Check LAN client is getting IP and gateway: YES
IP:                  192.168.4.199
Default Rout:   192.168.4.1
primary DNS:   192.168.4.1

on LAN client Ping 192.168.4.1: YES ping OK
on LAN client Ping 192.168.2.80: YES ping OK
on LAN client Ping 192.168.2.1: NO ping NOT OK
Test Internet.  No connection to Internet

on eBox test internet: YES connected to internet,
on eBox open administrator console and Ping 192.168.2.1: YES ping OK

on eBox run command route -n
# 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           0          0
          0 eth1
  169.168.2.0        0.0.0.0      255.255.255.0     U           0          0
          0 eth0

Go to eBox Network -> Diagnostic Tools
ping router on WAN 192.168.2.1: YES ping OK
ping a client on LAN 192.168.4.199: YES ping OK

Its the perfect firewall :-)
Nothing gets through.

Whats missing ?

Fred.
_______________________________________________
ebox-user mailing list
[email protected]
http://lists.ebox-platform.com/cgi-bin/mailman/listinfo/ebox-user

Reply via email to