I have the following configuration. When I mention an E-smith or SME server, that is a Red Hat Linux server acting as Gateway for my network. The Linksys Router is connected to the inside port of my Linux Box. Connected at the WAN port and the Router is Gateway mode. I have turned off all security on the router.
E-smith server - 192.168.0.25 - connects to Linksys Router - Wan Interface.
Linksys Router Lan is 192.168.1.1
I need to get to 192.168.1.200 from the outside interface on the E-smith
192.168.1.200 is hardwired to the router through a switch. I also put .200 on the DMZ.
I cannot ping 192.168.1.1 from the server even though I added the network to the routing table.
I also turned off the firewall functions of the Linksys Router and put 192.168.1.200 on DMZ just to be doubly sure.
But since I cannot ping the router what does it matter?
My routing table on the e-smith is:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
68.80.190.0 * 255.255.255.0 U 0 0 0 eth1
192.168.1.0 maxserver.maxwe 255.255.255.0 UG 0 0 0 eth0
192.168.0.0 * 255.255.255.0 U 0 0 0 eth0
127.0.0.0 * 255.0.0.0 U 0 0 0 lo
default ubr03-a-rtr.chr 0.0.0.0 UG 0 0 0 eth1
[root@maxserver root]#
Everyone on 192.168.1.0 sees 192.168.0.25 just fine - I can see network shares.
Why can't I ping the 192.168.1.0 network?
Joined: 20 Jan 2004
Posts: 53
Location: Philadelphia Suburbs - USA
PostPosted: 16 Jan 2006 05:12 Post subject: Reply with quote Edit/Delete this post Delete this post
This is a Linksys 54G router. In Gateway mode. I could change it to Router mode as it really isn't a gateway device although it works fine on this network as a gateway device. The E-smith is the true gateway device.
My issue is that I am in Thailand and my client is Philadephia and I'm not sure what will happen to the connection beyond the Linksys Router if I put it in router mode.
I turned off all security on the Linksys router. It should respond to a ping from the SME from eth0 to the Wan port but does not.
Ping is the key - why can't I ping 192.168.1.1 or .200 especially since I have .200 on the DMZ?
Linux and Microsoft Networking
howardbloom at pc-man.com
E-smith server - 192.168.0.25 - connects to Linksys Router - Wan Interface.
Linksys Router Lan is 192.168.1.1
I need to get to 192.168.1.200 from the outside interface on the E-smith
192.168.1.200 is hardwired to the router through a switch. I also put .200 on the DMZ.
I cannot ping 192.168.1.1 from the server even though I added the network to the routing table.
I also turned off the firewall functions of the Linksys Router and put 192.168.1.200 on DMZ just to be doubly sure.
But since I cannot ping the router what does it matter?
My routing table on the e-smith is:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
68.80.190.0 * 255.255.255.0 U 0 0 0 eth1
192.168.1.0 maxserver.maxwe 255.255.255.0 UG 0 0 0 eth0
192.168.0.0 * 255.255.255.0 U 0 0 0 eth0
127.0.0.0 * 255.0.0.0 U 0 0 0 lo
default ubr03-a-rtr.chr 0.0.0.0 UG 0 0 0 eth1
[root@maxserver root]#
Everyone on 192.168.1.0 sees 192.168.0.25 just fine - I can see network shares.
Why can't I ping the 192.168.1.0 network?
Joined: 20 Jan 2004
Posts: 53
Location: Philadelphia Suburbs - USA
PostPosted: 16 Jan 2006 05:12 Post subject: Reply with quote Edit/Delete this post Delete this post
This is a Linksys 54G router. In Gateway mode. I could change it to Router mode as it really isn't a gateway device although it works fine on this network as a gateway device. The E-smith is the true gateway device.
My issue is that I am in Thailand and my client is Philadephia and I'm not sure what will happen to the connection beyond the Linksys Router if I put it in router mode.
I turned off all security on the Linksys router. It should respond to a ping from the SME from eth0 to the Wan port but does not.
Ping is the key - why can't I ping 192.168.1.1 or .200 especially since I have .200 on the DMZ?
Linux and Microsoft Networking
howardbloom at pc-man.com