Re: Home Network won't work

From: timk (timk_at_harbornet.com)
Date: 09/08/03


Date: Sun, 07 Sep 2003 21:33:33 -0700

Bit Twister wrote:
> On Sun, 07 Sep 2003 20:45:27 -0700, timk wrote:
>
>>Help - can't get the home network setup correctly!
>>
>>I am trying to setup a home network/firewall machine. I have loaded
>>RedHat 9.0 on this machine. It is connected to a cable router on eth0
>>and a single dual-boot PC on eth1 (eventually it will be connected to a
>>hub - once it is working).
>
>
> Go ahead and cable through hub. If not, you need a crossover cable
> nic to nic.
>

Okay, but what is the difference? Is there something special about a
crossover cable?

>
>>I can get the network machine to boot-up and see the internet. It also
>>obtains (dynamically) an ip-address from my ISP.
>>
>>The problem is that I can not get the home side PC (either in windows or
>>linux) to work.
>
>
> in /etc/sysctl.conf
> net.ipv4.ip_forward = 0 <==== set = 1
>

Yeah, it is set to 1. Any other suggestions I can try? I still don't
understand the route stuff below...

>
>>The route and ifconfig give some different results then I have seen and
>>I am not sure how to fix? Any ideas?
>>
>>Specifically, the inet and Bcast addresses are different, WHY?:
>>inet: 123.151.60.244
>>Bcast: 123.151.63.255
>>
>>Also, the route has an entry I do not know where it is coming from, any
>>ideas? How dow I remove it?
>>Destination Gateway Genmask Flags Metric Ref Use Iface
>>169.254.0.0 * 255.255.0.0 U 0 0 0 eth1
>>
>>Here is the full-output...
>>ifconfig eth0:
>>eth0 Link encap:Ethernet HWaddr 00:26:54:07:F5:18
>> inet addr:123.151.60.244 Bcast:123.151.63.255 Mask:255.255.252.0
>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>> RX packets:424836 errors:139 dropped:0 overruns:1 frame:206
>> TX packets:6657 errors:0 dropped:0 overruns:0 carrier:0
>> collisions:0 txqueuelen:100
>> RX bytes:34687028 (33.0 Mb) TX bytes:536985 (524.3 Kb)
>> Interrupt:5 Base address:0xc000
>>
>>ifconfig eth1:
>>eth1 Link encap:Ethernet HWaddr 00:E0:18:DD:41:E7
>> inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
>> UP BROADCAST MULTICAST MTU:1500 Metric:1
>> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>> TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
>> collisions:0 txqueuelen:100
>> RX bytes:42540 (41.5 Kb) TX bytes:504 (504.0 b)
>> Interrupt:11 Base address:0x6000
>>
>>and finally route:
>>Kernel IP routing table
>>Destination Gateway Genmask Flags Metric Ref Use
>>Iface
>>192.168.1.0 * 255.255.255.0 U 0 0 0 eth1
>>123.151.60.0 * 255.255.252.0 U 0 0 0 eth0
>>169.254.0.0 * 255.255.0.0 U 0 0 0 eth1
>>127.0.0.0 * 255.0.0.0 U 0 0 0 lo
>>default 123.151.60.1 0.0.0.0 UG 0 0 0 eth0
>>



Relevant Pages

  • help needed with www access and router setup problem
    ... hub, before I started experimenting with two physical routers. ... the WAN and NIC cables to a D-Link router. ... web (could not resolve internet addresses). ... When I ran route, I got this: ...
    (comp.os.linux.networking)
  • help needed with www access and router setup problem
    ... hub, before I started experimenting with two physical routers. ... the WAN and NIC cables to a D-Link router. ... web (could not resolve internet addresses). ... When I ran route, I got this: ...
    (linux.redhat.install)
  • Re: Connect 2 client vpns through 1 vpn server
    ... Routing is basically a two-way process. ... The 192.168.0.0/16 is a bundled route. ... If the traffic belongs to another branch, the central site ... to the central site (or hub). ...
    (microsoft.public.windows.server.networking)
  • Re: Connect 2 client vpns through 1 vpn server
    ... The 192.168.0.0/16 is a bundled route. ... that every 192.168 address will be sent through the VPN tunnel. ... If the traffic belongs to another branch, the central site ... to the central site (or hub). ...
    (microsoft.public.windows.server.networking)
  • Re: yet another boring trip report part 3
    ... Differing interpretations of 'okay', I guess, but I ... Great route, eh? ... a final, attention-getting slab ...
    (rec.climbing)