I've been working on this for a week but just can't get things right!!! I
have 2 ethernet boards installed in my server eth0 and eth2. eth1 is turned
off.eth0 is connected to my Sonicwall SA going to the internet and its ip is
68.23.245.5 eth2 goes to my LAN and it's ip is 206.95.105.14. On the lan I
have 5 subnets 206.95.136.126 netmask 255.255.255.128, 206.95.105.126
netmask 255.255.255.128, 207.184.199.254 netmask 255.255.255.192,
204.125.172.190 netmask 255.255.255.192, and 206.93.151.126 netmask
255.255.255.192. My internet router is ip 68.23.245.1 the wan interface on
the Sonicwall is 68.23.245.2 the lan side of the sonicwall is 68.23.245.3
and the linux host proxy is 68.23.245.5 I would like to use the balance of
the 68.23.245.6-128 ranges of ip's on the 206.95.105.14 eth2 network on my
linux proxy. Any help would be appreciated. Also when I do make changes
using route add and restart the network service the routes seem to revert
back to what they were originally. Sorry for the length of this but I'm
trying to put out as much info as possible to get this resolved. Thanks!!!

On Tue, 01 Jul 2003 22:20:20 -0400, Jim Mainock wrote:

> I've been working on this for a week but just can't get things right!!!
> I have 2 ethernet boards installed in my server eth0 and eth2. eth1 is
> turned off.eth0 is connected to my Sonicwall SA going to the internet
> and its ip is 68.23.245.5 eth2 goes to my LAN and it's ip is
> 206.95.105.14. On the lan I have 5 subnets 206.95.136.126 netmask
> 255.255.255.128, 206.95.105.126 netmask 255.255.255.128,
> 207.184.199.254 netmask 255.255.255.192, 204.125.172.190 netmask
> 255.255.255.192, and 206.93.151.126 netmask 255.255.255.192. My
> internet router is ip 68.23.245.1 the wan interface on the Sonicwall is
> 68.23.245.2 the lan side of the sonicwall is 68.23.245.3 and the linux
> host proxy is 68.23.245.5 I would like to use the balance of the
> 68.23.245.6-128 ranges of ip's on the 206.95.105.14 eth2 network on my
> linux proxy. Any help would be appreciated. Also when I do make changes
> using route add and restart the network service the routes seem to
> revert back to what they were originally. Sorry for the length of this
> but I'm trying to put out as much info as possible to get this resolved.
> Thanks!!!

Jim, I am almost too timid to respond, but will give it a go in hopes to
help:
> eth0 is connected to my Sonicwall SA going to the internet
.... lost you right there on context. Should I know what Sonicwall SA is?
> and its ip is 68.23.245.5 eth2 goes to my LAN and it's ip is
> 206.95.105.14.
# ping -c 1 68.23.245.5
PING 68.23.245.5 (68.23.245.5) from 66.63.71.252 : 56(84) bytes of data.

--- 68.23.245.5 ping statistics ---
1 packets transmitted, 0 received, 100% loss, time 0ms

# ping -c 1 206.95.105.14
PING 206.95.105.14 (206.95.105.14) from 66.63.71.252 : 56(84) bytes of
data.

--- 206.95.105.14 ping statistics --- 1 packets transmitted, 0 received,
100% loss, time 0ms

==============>I get no connection to either of those IP addys.

My
> internet router is ip 68.23.245.1

# ping -c 1 68.23.245.1
PING 68.23.245.1 (68.23.245.1) from 66.63.71.252 : 56(84) bytes of data.
64 bytes from 68.23.245.1: icmp_seq=1 ttl=237 time=62.6 ms

--- 68.23.245.1 ping statistics ---
1 packets transmitted, 1 received, 0% loss, time 0ms rtt min/avg/max/mdev
= 62.647/62.647/62.647/0.000 ms

Your router is connected and live.

Jim, I'm no expert (at all!) I don't understand why all your LAN addys
are in the same 68.xxx.xxx.xxx range. I thought your private (LAN)
network would be on a reserved set of IP numbers, like 192.168.100.23,
(or such), or maybe 10.200.56.79, 80,81,82,83, ... etc. Think there is
another set for private use at maybe 172.xxx.xxx.xxx.

Might be all wet, but perhaps this is your issue. If you are using
public numbers for your private net, it wont work (and could get you in
trouble.) Wish I had an easy reference to give you. Look for
Networking-HOWTO, or some such, ... should give you better info.

Good luck.

Thanks, I will make the changes you are suggesting and pick up the book.

"Seth H Holmes" <sholmes@dweezil.NOSPAMFORMEroute-fu.net> wrote in message
news:slrnbg5vqr.tom.sholmes@dweezil.route-fu.net...
> In article <EjrMa.9844$BM.3005200@newssrv26.news.prodigy.com> , Jim Mainock
wrote:
> > I've been working on this for a week but just can't get things right!!!
I
> > have 2 ethernet boards installed in my server eth0 and eth2. eth1 is
turned
> > off.eth0 is connected to my Sonicwall SA going to the internet and its
ip is
> > 68.23.245.5 eth2 goes to my LAN and it's ip is 206.95.105.14. On the lan
I
> > have 5 subnets 206.95.136.126 netmask 255.255.255.128, 206.95.105.126
> > netmask 255.255.255.128, 207.184.199.254 netmask 255.255.255.192,
> > 204.125.172.190 netmask 255.255.255.192, and 206.93.151.126 netmask
> > 255.255.255.192. My internet router is ip 68.23.245.1 the wan interface
on
> > the Sonicwall is 68.23.245.2 the lan side of the sonicwall is
68.23.245.3
> > and the linux host proxy is 68.23.245.5 I would like to use the balance
of
> > the 68.23.245.6-128 ranges of ip's on the 206.95.105.14 eth2 network on
my
> > linux proxy. Any help would be appreciated. Also when I do make changes
> > using route add and restart the network service the routes seem to
revert
> > back to what they were originally. Sorry for the length of this but I'm
> > trying to put out as much info as possible to get this resolved.
Thanks!!!
>
> Since I seriously doubt you are ADP Autonet, I seriously doubt
> you should be using the IPs you say you are using on your private
> network. Please look into using RFC1918 IP address space. I
> recommend addresses in 192.168.0.0/16.
>
> cougars:~> whois -h whois.arin.net 206.95.105.126
>
> OrgName: ADP Autonet
> OrgID: AUTO
> Address: 175 Jackson Plaza
> City: Ann Arbor
> StateProv: MI
> PostalCode: 48106
> Country: US
>
> NetRange: 206.88.0.0 - 206.95.255.255
> CIDR: 206.88.0.0/13
> NetName: ADP-AUTONET
> NetHandle: NET-206-88-0-0-1
> Parent: NET-206-0-0-0-0
> NetType: Direct Allocation
> NameServer: DNS1.AUTONET.NET
> NameServer: DNS2.AUTONET.NET
> Comment: ADDRESSES WITHIN THIS BLOCK ARE NON-PORTABLE
> RegDate: 1995-08-09
> Updated: 1996-03-15
>
> TechHandle: ADP-NOC-ARIN
> TechName: ADP Autonet
> TechPhone: +1-800-521-2733
> TechEmail: techcontact@autonet.net
>
> # ARIN WHOIS database, last updated 2003-07-01 21:05
> # Enter ? for additional hints on searching ARIN's WHOIS database.
>
> cougars:~> whois -h whois.arin.net 207.184.199.254
>
> OrgName: ADP Autonet
> OrgID: AUTO
> Address: 175 Jackson Plaza
> City: Ann Arbor
> StateProv: MI
> PostalCode: 48106
> Country: US
>
> NetRange: 207.184.0.0 - 207.187.255.255
> CIDR: 207.184.0.0/14
> NetName: ADP-AUTONET96
> NetHandle: NET-207-184-0-0-1
> Parent: NET-207-0-0-0-0
> NetType: Direct Allocation
> NameServer: DNS1.AUTONET.NET
> NameServer: DNS2.AUTONET.NET
> Comment: ADDRESSES WITHIN THIS BLOCK ARE NON-PORTABLE
> RegDate: 1996-08-21
> Updated: 1999-02-10
>
> TechHandle: DH358-ARIN
> TechName: Hares, David
> TechPhone: +1-734-827-3620
> TechEmail: dhares@networktwo.net
>
> # ARIN WHOIS database, last updated 2003-07-01 21:05
> # Enter ? for additional hints on searching ARIN's WHOIS database.
>
>
> As for the rest, you MUST subnet on logical boundries. You CANNOT
> have a network
>
> 206.95.136.126/255.255.255.128
> 206.95.105.126/255.255.255.128
> 207.184.199.254/255.255.255.192
> 204.125.172.190/255.255.255.192
> 206.93.151.126/255.255.255.192
>
> These could be hosts in a network, but certainly not the subnets
> themselves. In addition, if you want several hosts on the same
> network, they need to be in *GASP* the same network.
>
> From what I'm reading here, you have absolutely no grasp of basic
> IP networking. I recommend picking up a book, O'Reiley and Associates
> publish a great TCP/IP book, and get a better understand of what
> you are doing before you foul up too much.
>
>
> --
> Seth H Holmes
>