Comcast router and Apache

[JamieCoy]

Tonight I replaced Comcast modem with a new modem Comcast sent me. Since it has built-in wireless capability, I had to switch my Airport Express into bridge mode. I had been easily using the Airport Express to forward to port 8102 for my web site, www.heartfullofdirt.

The interface on the Comcast modem is a bit different, but I did open port 8102 on it using the local 10.0.0.7 address as static in my TCP/IP preferences. I confirmed that this port is indeed open.

I cannot open my web site, however. I'm not using Port Triggering, just Port Forwarding. The start and end ports are both 8102 for both TCP and UDP. My Apache config also has a "listen" for port 8102, and still it's a no go.

I really want to get this fixed and would appreciate your input. Thanks.

[Lewis]

Post by JamieCoy
Tonight I replaced Comcast modem with a new modem Comcast sent me. Since it has built-in wireless capability, I had to switch my Airport Express into bridge mode. I had been easily using the Airport Express to forward to port 8102 for my web site, www.heartfullofdirt.
The interface on the Comcast modem is a bit different, but I did open port 8102 on it using the local 10.0.0.7 address as static in my TCP/IP preferences. I confirmed that this port is indeed open.

Can you load http://127.0.0.1:8102/ from your local machine?

[Norman Peelman]

Post by JamieCoy
Tonight I replaced Comcast modem with a new modem Comcast sent me. Since it has built-in wireless capability, I had to switch my Airport Express into bridge mode. I had been easily using the Airport Express to forward to port 8102 for my web site, www.heartfullofdirt.
The interface on the Comcast modem is a bit different, but I did open port 8102 on it using the local 10.0.0.7 address as static in my TCP/IP preferences. I confirmed that this port is indeed open.
I cannot open my web site, however. I'm not using Port Triggering, just Port Forwarding. The start and end ports are both 8102 for both TCP and UDP. My Apache config also has a "listen" for port 8102, and still it's a no go.
I really want to get this fixed and would appreciate your input. Thanks.

Works from here... HFOD band.

[Kees Nuyt]

On Thu, 25 Jul 2013 06:14:00 -0400, Norman Peelman

Post by Norman Peelman

Post by JamieCoy
Tonight I replaced Comcast modem with a new modem Comcast sent me. Since it has built-in wireless capability, I had to switch my Airport Express into bridge mode. I had been easily using the Airport Express to forward to port 8102 for my web site, www.heartfullofdirt.
The interface on the Comcast modem is a bit different, but I did open port 8102 on it using the local 10.0.0.7 address as static in my TCP/IP preferences. I confirmed that this port is indeed open.
I cannot open my web site, however. I'm not using Port Triggering, just Port Forwarding. The start and end ports are both 8102 for both TCP and UDP. My Apache config also has a "listen" for port 8102, and still it's a no go.
I really want to get this fixed and would appreciate your input. Thanks.

Works from here... HFOD band.

Works from here too, http://www.heartfullofdirt.com/ on port 80.
By now, you probably found out you didn't want to forward WAN-IP
port 8102 to LAN_IP port 8102, but rather forward WAN-IP port 80
to LAN_IP port 8102.

It is possible you can't address http://www.heartfullofdirt.com/
from within your LAN, because the modem would have to perform
auto-loopback for that to happen. A possible solution for that is
to configure an http proxy in your browser. That proxy server has
to be outside your LAN.

HTH

[Norman Peelman]

Post by Kees Nuyt
On Thu, 25 Jul 2013 06:14:00 -0400, Norman Peelman

Post by Norman Peelman

Post by JamieCoy
Tonight I replaced Comcast modem with a new modem Comcast sent me. Since it has built-in wireless capability, I had to switch my Airport Express into bridge mode. I had been easily using the Airport Express to forward to port 8102 for my web site, www.heartfullofdirt.
The interface on the Comcast modem is a bit different, but I did open port 8102 on it using the local 10.0.0.7 address as static in my TCP/IP preferences. I confirmed that this port is indeed open.
I cannot open my web site, however. I'm not using Port Triggering, just Port Forwarding. The start and end ports are both 8102 for both TCP and UDP. My Apache config also has a "listen" for port 8102, and still it's a no go.
I really want to get this fixed and would appreciate your input. Thanks.

Works from here... HFOD band.

Works from here too, http://www.heartfullofdirt.com/ on port 80.
By now, you probably found out you didn't want to forward WAN-IP
port 8102 to LAN_IP port 8102, but rather forward WAN-IP port 80
to LAN_IP port 8102.
It is possible you can't address http://www.heartfullofdirt.com/
from within your LAN, because the modem would have to perform
auto-loopback for that to happen. A possible solution for that is
to configure an http proxy in your browser. That proxy server has
to be outside your LAN.
HTH

My last router (netgear) did auto-loopback just fine... my current
router (netgear) does not. I just added entries to my hosts file to
accommodate.