eBox as http proxy
 

Hi,

I am trying to configure an eBox to act as an http proxy but having trouble using that proxy on client computers to browse internet.

The ifconfig on ebox returns the following:

eBox141:~# ifconfig
eth0 Link encap:Ethernet HWaddr 00:0c:29:ee:64:f2
inet addr:10.45.48.108 Bcast:10.45.255.255 Mask:255.255.0.0
inet6 addr: fe80::20c:29ff:feee:64f2/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:90045 errors:0 dropped:0 overruns:0 frame:0
TX packets:226 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:7043548 (6.7 MB) TX bytes:35150 (34.3 KB)
Interrupt:16 Base address:0x2024

eth1 Link encap:Ethernet HWaddr 00:0c:29:ee:64:fc
inet addr:192.168.122.158 Bcast:192.168.122.255 Mask:255.255.255.0
inet6 addr: fe80::20c:29ff:feee:64fc/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1123 errors:0 dropped:0 overruns:0 frame:0
TX packets:781 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:949754 (927.4 KB) TX bytes:92267 (90.1 KB)
Interrupt:16 Base address:0x20a4

eth0 is on the internal lan with the client from which I want to access the internet
eth1 is can access internet all right.

The ifconfig on a client returns

eth0 Link encap:Ethernet HWaddr 00:0C:29:46:58:7F
inet addr:10.45.48.102 Bcast:10.45.255.255 Mask:255.255.0.0
inet6 addr: fe80::20c:29ff:fe46:587f/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:16014030 errors:0 dropped:0 overruns:0 frame:0
TX packets:835276 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1297106653 (1237.0 Mb) TX bytes:738158694 (703.9 Mb)


I configured the Firefox on the client to use eBox's ip address/port in the proxy settings but I still can't get on the internet.



Side note 1:

eBox is on a vmware workstation 7. It is eBox 1.4.1
eBox has two virtual nics (above) - one is NAT (eth1) and the other is bridged (eth0)

Side note 2:
the client is on vmware ESXi 4.0. It's an openSUSE 11.2.

I may have found the source of the problem. I'll post it later.

Well. With the eBox, the changes saved don't mean they are automatically enabled. I just had to enable HTTP proxy module in the Modules Status and it all worked just fine.