What file does pclos use to determine lan or ethernet?

[leirob007]

I've been using pclos with no troubles for several years ( since mandrake sold out )and have never had a problem until now.
I can't get my sharing to work. I've read all I can find in here and there seems to be a lot of folks having the same trouble.
no LAN device configured.
but I have 2 ethernets
I have nameservers
I have dns and dhcp bind squid and everything else I can think of working.
shorewall up or down makes no difference has been made.
I went old school and edited the host file  the resolv.conf and fixed the messed up addresses in iptables.
now devices connect to eth1 get a " connect " but can't get any traffic.
I figure there is something hidden in there somewhere i am overlooking.
ifconfig:

eth0      Link encap:Ethernet  HWaddr 00:80:AD:76:4C:F0  
          inet addr:192.168.1.97  Bcast:255.255.255.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1384 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1879 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:661499 (645.9 KiB)  TX bytes:312522 (305.1 KiB)
          Interrupt:10 Base address:0x1400

eth1      Link encap:Ethernet  HWaddr 00:08:A1:9D:D4:88  
          inet addr:192.168.0.1  Bcast:192.168.0.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1197 errors:0 dropped:0 overruns:0 frame:0
          TX packets:304 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:92068 (89.9 KiB)  TX bytes:43578 (42.5 KiB)
          Interrupt:5 Base address:0x1800

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:325 errors:0 dropped:0 overruns:0 frame:0
          TX packets:325 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:61004 (59.5 KiB)  TX bytes:61004 (59.5 KiB)

route :
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.1.0     *               255.255.255.0   U     10     0        0 eth0
192.168.0.0     *               255.255.255.0   U     10     0        0 eth1
link-local      *               255.255.0.0     U     10     0        0 eth0
link-local      *               255.255.0.0     U     10     0        0 eth1
default         launchmodem     0.0.0.0         UG    10     0        0 eth0

resolv.conf:
nameserver 192.168.1.254
nameserver 192.168.0.1
search launchmodem.com
( search automatically picked up from dsl modem )

hosts:
cat /etc/hosts
127.0.0.1        localhost.localdomain localhost
192.168.0.1        leirob007.org

I know I must be overlooking something.
Can anyone help?
I'll be glad to supply any and all info needed to resolve this issue..  then maybe I can help some other unfortunate soul with it.
Thank you for your consideration,
Robert
Upon further tinkering. I have the web servers ( http and ftp and ssh) available from inside and outside the local network,
just no port forwarding

[leirob007]

Solution Found  .... Easy as 1-2-3
In case this happens to stay here I hope this helps someone else.

The trick is in the flow. So this is what worked for me:

1 you must set up both your NICs properly.
         static if at all possible intranet(local) must be static. internet can be dhcp

2  goto your Personal Firewall Setup
    you MUST select what you want to connect to your server!
    IF you have everything selected your PCLOS system is smart enough to know your too crazy to run a server
    NOW you get a new screen!
    un-check the box with your INSIDE LOCAL INTRANET eth1 in my case
    Be sure the INTERNET WWW or Informtion Highway IS CHECKED
    Ain't that just too cool !
3 Now we get to pop over to the INTERNET CONNECTION SHARING department and breeze right through it


Now that said.
I wonder why they took out that really cool feature in the older versions.
You remember that popped up a little box that said " You have selected eth0. would you like to configure eth1 as your network now? "

we were spoiled.. people
thats all that is wrong.
simple as that.
I started in 93 when it was difficult. took me a year and a half to get an x-server to run on a junk pc
distro's like PCLoS have spoiled us rotten
and for security reasons we need to take a step back
also before we all forget what the basics are.
My hat is off to them.
I appreciate the lesson it served
Robert

[menotu]

Thanks for posting your solution.