Are you using a router with nat or just plain old router in a box?? I would just bind apache to port 8080 and bind squid to all 80 ports in the machine. It will be much simpler to understand and maintain. Eliezer On 07/17/2013 12:47 PM, jc.yin wrote: > Okay I'm assuming that, after seeing this, my public ip hasn't been properly > set up with the local server? Should inet addr be my public IP? > > > eth0 Link encap:Ethernet HWaddr c4:2c:03:21:ca:80 > inet addr:192.168.1.45 Bcast:192.168.1.255 Mask:255.255.255.0 > inet6 addr: fe80::c62c:3ff:fe21:ca80/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:740367 errors:0 dropped:0 overruns:0 frame:0 > TX packets:612985 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:509918363 (509.9 MB) TX bytes:475908750 (475.9 MB) > Interrupt:23 > > eth1 Link encap:Ethernet HWaddr 60:33:4b:09:4f:69 > inet6 addr: fe80::6233:4bff:fe09:4f69/64 Scope:Link > UP BROADCAST MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:14627 > TX packets:0 errors:72 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) > Interrupt:21 > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > inet6 addr: ::1/128 Scope:Host > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:5894 errors:0 dropped:0 overruns:0 frame:0 > TX packets:5894 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:1504276 (1.5 MB) TX bytes:1504276 (1.5 MB) > > > > > > -- > View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-Reverse-Proxy-cannot-open-ports-tp4661107p4661130.html > Sent from the Squid - Users mailing list archive at Nabble.com. >
