Alexander Dalloz wrote:
Why shall it be possible to access the net from the webserver? Is it not sufficient if the webserver respond to HTTP request from the net? Or does even that not work? Then you have a wrong setup with your firewall/router.
The webserver responds to http request with no problem.
Check the output of "route", check the firewalling/port forwarding rules on the firewall/router, be sure the NIC, the cable and the switch port are ok (no errors in the output of ifconfig).
Output from route:
[root@localhost root]# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
123.123.123.0 * 255.255.255.0 U 0 0 0 eth0
169.254.0.0 * 255.255.0.0 U 0 0 0 eth0
127.0.0.0 * 255.0.0.0 U 0 0 0 lo
default 123.123.123.254 0.0.0.0 UG 0 0 0 eth0
Output from ifconfig:
[root@localhost root]# ifconfig
eth0 Link encap:Ethernet HWaddr 00:10:4B:27:1E:1A
inet addr:123.123.123.240 Bcast:123.123.123.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:83061 errors:83 dropped:0 overruns:0 frame:129
TX packets:37705 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:8443843 (8.0 Mb) TX bytes:8538271 (8.1 Mb)
Interrupt:10 Base address:0x1000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:1032 errors:0 dropped:0 overruns:0 frame:0
TX packets:1032 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:77868 (76.0 Kb) TX bytes:77868 (76.0 Kb)I don't have access to the router. It's owned by the ISP and we don't know the password(It wasn't my idea), so
I am at their mercy for now.
Thanks, Elam
