This is truely odd, especially that you can ping the external interface from
an internal client, that means forwarding is working! Though that doesn't
necessarily mean that the masqing is working. Still make sure that the rule
for masq'ing is set, the only one that should be there for testing purposes
is
/sbin/ipchains -A forward -s 192.168.0-j MASQ
that will masq everything internal go anywhere.
Also pipe your route table to a file and paste here, and ifconfig...those
might point to something, but it seems to me at this point that masq'ing
isn't enabled =(
Quote:> If I can't get it running tomorrow I may have to try using a windows based
> solution, though I'm none too keen on that idea.
> If any of you are on this newsgroup tomorrow you will probably see
> progressively more desperate messages posted from me!
We'll get this thing runin man, don't you worry =) Unfortunately though, I
won't be on again until Monday night probably, but I'm sure Dean will think
of something
Good Luck!
-Dave T.
> Alas no, I haven't got it working.
> If I set the default route as the Linux machine's local network address,
> route still shows the BT router's IP as the default gateway
> (192.168.254.254)
> I have tried removing this manually and am told it is a non-existent
> process.
> etc/sysconfig/network has
> GATEWAY="192.168.82.2"
> GATEWAYDEV="eth0"
> FORWARD_IPV4="yes"
> Forwarding was disabled in etc/sysctl.conf but enabling it made no
> difference.
> I can ping the linux box's local net IP on eth1 and the DHCP assigned IP
on
> eth0 from the clients but not the BT router or the web.
> Trying to think of any other info I can tell you that may help as I am
going
> back in tomorrow to try and sort it and am not feeling overly confident.
> eth0 gets it's IP assigned dynamically by the BT router in the form
> 192.168.254.x
> All the local network IP's are static
> All local subnet masks are 255.255.255.0 (not sure about the BT router)
> Most clients log on to the Alpha OpenVMS box as a named domain (i.e. log
> onto NT domain is checked in windows networking)
> and use DEC Pathworks to map to drives on the Alpha.
> Haven't tried it on one of the non-Pathworks clients yet - could it be
this
> that is interfering with the routing?
> Thanks for the suggestions so far.
> If I can't get it running tomorrow I may have to try using a windows based
> solution, though I'm none too keen on that idea.
> If any of you are on this newsgroup tomorrow you will probably see
> progressively more desperate messages posted from me!
> Dom
> > Hey,
> > I must have miss typed something...I'm going back now to check why were'
> not
> > on the same page
> > . . .
> > I think I see where it happened, I said that you put the gatewaydev in
the
> > /etc/sysconfig/network-scripts/ifcfg-(internalnic) instead of
> > /etc/sysconfig/network. On another note regarding ip forwarding,
though,
> I
> > still have all these files in /proc/sys/net/ipv4
> > conf ip_local_port_range
> tcp_max_syn_backlog
> > icmp_destunreach_rate ip_masq_debug
> > tcp_retrans_collapse
> > icmp_echo_ignore_all ip_masq_udp_dloose tcp_retries1
> > icmp_echo_ignore_broadcasts ip_no_pmtu_disc tcp_retries2
> > icmp_echoreply_rate ipfrag_high_thresh tcp_rfc1337
> > icmp_ignore_bogus_error_responses ipfrag_low_thresh tcp_sack
> > icmp_paramprob_rate ipfrag_time tcp_stdurg
> > icmp_timeexceed_rate neigh tcp_syn_retries
> > ip_always_defrag route tcp_syncookies
> > ip_autoconfig tcp_fin_timeout tcp_timestamps
> > ip_default_ttl tcp_keepalive_probes
> tcp_window_scaling
> > ip_dynaddr tcp_keepalive_time
> > ip_forward tcp_max_ka_probes
> > and my network file is
> > NETWORKING=yes
> > HOSTNAME="xxx.xxx.xxx"
> > GATEWAY=""
> > GATEWAYDEV=""
> > FORWARD_IPV4="no"
> > Still interresting to see that my machine routes fine while
> > FORWARD_IPV4="no" and the /etc/sysctl.conf file is
> > # Disables packet forwarding
> > net.ipv4.ip_forward = 0
> > # Enables source route verification
> > net.ipv4.conf.all.rp_filter = 1
> > # Disables automatic defragmentation (needed for masquerading, LVS)
> > net.ipv4.ip_always_defrag = 0
> > # Disables the magic-sysrq key
> > kernel.sysrq = 0
> > and finally the /proc/sys/net/ipv4/ip_forward file
> > 1
> > which is the only place it says to forward packets! I'm not doing this
to
> > say, 'In your face Dean' lol, just giving evidence that the ip_forward
> file
> > isn't ignored on MY configuration, thats all =)
> > Either way, I haven't seen a post from Dom here letting us know that he
> got
> > it working and what the problem was...
> > -Dave T.
> > > Hi Dave,
> > > > The ip_forward file is not ignored, just depends on the version
linux
> > > > you're running. Personally running rh6.2 w/2.2.19 kernel and still
> use
> > the
> > > > ip_forward file...still try this file for forwarding =)
> > > Hmm, interesting, the version of Redhat 6.2 did this in my
> > > /etc/sysconfig/network file:
> > > cat /etc/sysconfig/network
> > > NETWORKING=yes
> > > # FORWARD_IPV4 removed; see /etc/sysctl.conf
> > > HOSTNAME=xxx.xxx.xxx.xxx
> > > DOMAINNAME=xxx.xxx.xxx.xxx
> > > GATEWAY=xxx.xxx.xxx.xxx
> > > GATEWAYDEV=eth0
> > > See ya
> > > Dean Thompson
> > > --
+____________________________+____________________________________________+
> > > | Dean Thompson | E-mail -
> > |
> > > | Bach. Computing (Hons) | ICQ - 45191180
> > |
> > > | PhD Student | Office - <Off-Campus>
> > |
> > > | School Comp.Sci & Soft.Eng | Phone - +61 3 9903 2787 (Gen. Office)
> > |
> > > | MONASH (Caulfield Campus) | Fax - +61 3 9903 1077
> > |
> > > | Melbourne, Australia |
> > |
+----------------------------+--------------------------------------------+
by