We help IT Professionals succeed at work.

Check out our new AWS podcast with Certified Expert, Phil Phillips! Listen to "How to Execute a Seamless AWS Migration" on EE or on your favorite podcast platform. Listen Now

x

Route Problems with a Socks Proxy Server

hbrady
hbrady asked
on
Medium Priority
319 Views
Last Modified: 2010-03-18
Linux Red Hat 5.0 Multi Homed Proxy server.
Socks5 Proxy server installed
SocksCap32 TPC/IP shim run on client PC’s
Internal NIC address = 192.168.5.2

Internal Network Sub’ed into 2 Networks seperated by Routers and a T1 superpath.  Proxy server is on 192.168.5.0 subnet (Router address is 192.168.5.1).  Other subnet  is 192.168.6.0

External NIC address = 204.211.78.240 (Connected to a Cable Modem and Road Runner) Road Runner upstream router is 204.211.78.1

Current problem : Internal clients can not connect to host 192.168.5.2 for e-mail or Romstar.com when running “Socksified”.  The server refuses the connection.  External address browsing works fine.

When you try to ping www.romstar.com or 192.168.5.2 at the console you get “Network is unreachable”

Have tried :

Route add –net 127.0.0.0  result=“Network Unreachable”
Tried route del “on almost all entries and the Route Table comes back the same after reboot”
Tried changing DomainName in network file to “maine.rr.com” (Was Romstar.com). result=no change

Current etc/sysconfig/network

NETWORKING=yes
FORWARD_IPV4=no
HOSTNAME=tt022nfc
DOMAINNAME=maine.rr.com
GATEWAYDEV=eth0
GATEWAY=204.211.78.1




Current etc/sysconfig/static-routes

eth0 net 0.0.0.0 netmask 255.255.255.0 gw 204.211.78.1
eth0 net 204.211.78.0 netmask 255.255.255.0 gw 204.211.78.1
eth1 net 192.168.5.0 netmask 255.255.255.0 gw 192.168.5.1
eth1 net 192.168.6.0 netmask 255.255.255.0 gw 192.168.5.1


Current Output when “route” is run

Destination Gateway Genmask Flags Metric Ref Use Iface

204.211.78.0 204.211.78.1 255.255.255.0 UG 0 0 3 Eth0
204.211.78.0 *            255.255.255.0 U  0 0 0 Eth0
default      204.211.78.1 255.255.255.0      UG 0 0 0 Eth0
192.168.5.0  192.168.5.1  255.255.255.0 UG 0 0 30Eth1
192.168.5.0  *            255.255.255.0 U  0 0 0 Eth1
192.168.6.0  192.168.5.1  255.255.255.0 UG 0 0 14 Eth1
default      204.211.78.1 0.0.0.0       UG 0 0 50 Eth0
Comment
Watch Question

Author

Commented:
Edited text of question
Unlock this solution with a free trial preview.
(No credit card required)
Get Preview

Author

Commented:
You are right; however, the reason I do not want to hit activate on it is that the IP address is blank.  Here is how it reads :

Interface       IP address      Proto   OnBoot  Active
lo                              none            inactive
eth0            204.211.78.240  none    yes     active
eth1            192.168.5.1    none    yes     active

When I try to edit to lo line it states that the local loop back can not be changed; however, if I hit activate what ip address will it try ? Thanks !
I've heard things like this... Always is due to some missing information... Just compare in /etc/sysconfig/network-scripts the definition of ifcfg-lo and ifcfg-eth0. Maybe the first has some data missing...

Author

Commented:
Thanks marcelofr, you nailed this one !
Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a free trial preview!

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.