Internal Network Problems

[Jorge]

Hi, some of you might have remembered my post a few days ago on internal networks. I want to thank Tyr-7BE, manual_overide, triplehex, and spiff for their great responses. After all the reading and messing around I got the concepts on how to setup a internal network, but some problems came up. I was wondering if anyone else has seen this happen before and if it is a problem. Below is snips for route and ifconfig.

Ifconfig eth0:
inet addr:65.32.169.201 Bcast:65.32.169.255
Route eth0:
65.32.169.0

Why would route show a different ip than ifconfig? It does this for all my cards. Also this is for my default route.

default 6532169hfc01.ta 0.0.0.0

This is not my hostname and why would it even show a hostname? My hostname is 6532169hfc201.tampabay.rr.com.

I am having problems with setting the internal network up and I thought this might be due to all this. Any help is welcome =)

[jumpedintothefire]

OK some quick background:
65.32.169.0 is the network address
65.32.169.255 is the broadcast address
65.32.169.201 is your ip address
all address between 1-254 form one subnet.
That can change, depends on the subnet mask used.
In order to talk to anybody else on the internet, it must pass through the gateway.

6532169hfc01 is the gateway (65.32.169.1 ?)

What you are seeing are the resolved names from the dns server on the lan.
try route -n this will show ip address only and not names. It's not a problem. What problems are you having?

[Jorge]

Thank you jumpedintothefire! What kind of problems am I not having is the question, hehe. I have not got a working network up as of yet. I have a Windows 98 machine and a Linux Debian 2.2 2.2.17 machine as the gateway. This is what I try below and I never get it to work.

Windows = 192.168.1.0
Linux Gateway = 192.168.0.1
eth0 = Internet connection
eth1 = Linux Gateway
Hub
Here is how it is layed out.
Internet => eth0 => Cable Modem => Linux
Then
Windows 98 => Hub Slot 2
Hub Slot 1 => eth1

I have eth0 setup with dhcp (pump).
This is what I do for eth1.

ifconfig eth1 192.168.0.1 netmask 255.255.255.0 up

route add -host 192.168.0.1 eth1

route add -net 192.168.0.0 netmask 255.255.255.0 eth1

route add default gw 192.168.0.1

I habe ip forwarding compiled into my kernel, all the network cards work and I have my scripts setup for MASQ. What I am doing wrong is beyond me. I hope this information helps. If anyone could tell me what I am doing wrong it would be a !HUGE! help. Also I have the gateway in Windows 98 set to 192.168.0.1 and the named servers to to 65.32.1.70 / 65.32.2.130 which is in /etc/resolv.conf.

[jumpedintothefire]

:D Windows = 192.168.1.0 > Make this 192.168.1.2

:eek: Don't do this it hoses the inet connection > route add default gw 192.168.0.1

That should help

[Jorge]

Thanks Jumped. So I should make the Windows machine 192.168.1.2 and the Linux gateway machine 192.168.1.1, right?

[jumpedintothefire]

yup :)

[Jorge]

Hi, I still can not seem to get the internal network on the net. When I ping
the Windows machine (192.168.1.2) from the Windows machine, I get replies and
when I ping the Linux gateway (192.168.1.1) I get replies, but when I try
to ping a host outside, then it says "unknown host"! When I put the route in
(as I posted earlier) I can not even access the net from my Linux machine
anymore! My route table is below.

doom:/etc/pmfirewall# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.1 * 255.255.255.255 UH 0 0 0 eth1
65.32.169.0 * 255.255.255.0 U 0 0 0 eth0
192.168.1.0 * 255.255.255.0 U 0 0 0 eth1
192.168.1.0 * 255.255.255.0 U 0 0 0 eth1
default 192.168.1.1 0.0.0.0 UG 0 0 0 eth1
default 65.32.169.1 0.0.0.0 UG 0 0 0 eth0

Ifconfig is below also.

doom:~# ifconfig
eth0 Link encap:Ethernet HWaddr 00:80:13:95:42:E4
inet addr:65.32.169.201 Bcast:65.32.169.255 Mask:255.255.255.0
UP BROADCAST RUNNING MTU:1500 Metric:1
RX packets:397 errors:0 dropped:0 overruns:0 frame:0
TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
Interrupt:5 Base address:0xec00

eth1 Link encap:Ethernet HWaddr 00:60:67:08:47:F1
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:104 errors:0 dropped:0 overruns:0 frame:0
TX packets:259 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
Interrupt:10 Base address:0xef40

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:3924 Metric:1
RX packets:95 errors:0 dropped:0 overruns:0 frame:0
TX packets:95 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0

I do not know if my internal network will ever work, haha. Has anyone had
these problems before? I know one person in the world must have! Please,
any help is welcome and very much appreciated! I get nothing in syslog or
any other place concerning this either =(
At this point I am running around in circles, hehe.

[jumpedintothefire]

:eek: Don't do this it hoses the inet connection > route add default gw 192.168.0.1 :mad:

one step at a time.

the named servers to to 65.32.1.70 / 65.32.2.130 which is in /etc/resolv.conf.


OK that is half the battle, you need to either setup a forward only nameserver and point you lan clients to it. Enter the firewall's internal ip in the clients dns search order. Or just enter the ip's that you put in the /etc/resolv.conf in each of your lan machines.

[Jorge]

Hi again =) I did not do
route add default gw 192.168.0.1
I should have said that on my post =/
I did route add default gw 192.168.1.1
Should I not even add a default gw and leave the external (eth0) as the default?
Do I really have to setup a named server? I was under the impression I could use my isp's named servers =( Well I am going to go have a few more cracks at this, heh. I hope it will work this time, but I will not setup the named server unless you or another person says I have to. Thanks allot =)

[Jorge]

Hey I got it up! Thank you jumpedintothefire! I see what you were saying and the STUPID mistake I was doing. Again thank you for all your help =)