Re: Problem with Cable Moden & Router.




Mark Healey wrote:
On Sat, 06 Jan 2007 10:06:21 -0800, Tarkin wrote:



And it still can be. But you need your
router's address. For example, a
typical router has an address of
192.168.1.1- unless you have enabled
security restrictions within the router
itself, you can assign your box an
adress of say, 192.168.1.200,
and the router will recognize it
as a valid part of "it's" network.

That is good to know. I'll have to look into that.

If your box is the only one attached
to the router (why did you buy it
in the first place?)

Several reasons.

1) To do really big backups. It seems that it would be easier to just use
a garage sale PC to store files rather than hassling with removable media.
I don't have room for any more hard drives.

2) I have a cheapo netcam I'd like to hook up to the peep hole on my front
door so I can see who is there without making the inevitable noise going
to the door.


You still need to setup the router
to correctly get the IP from your
ISP. You also need to add the
router's address, as a gateway,
to your routing tables.

You're still touching base with
c.o.l, so I assume you have access
to Google, and ReHat's site. You need
to brush up on basic network
concepts, and consult RedHat for
the appropriate startup scripts.

This is where I get confused. I don't know what a gateway is or dies or
what routing tables are. I also clueless about subnet masks.

The only reason I wanted to use DHCP was name servers. If I have a static
setup and my ISP changes their nameservers frequently, I'd always be
manually changing them.

--
Mark Healey
marnkews ãt healeyopolis döt com

From my experience (Comcast), they
don't change. Mine haven't in years.
If I am having connection issues, I
can tell if the cable link is down
by pinging the IP's of both
the primary and secondary
server. If they're both down,
I'm SOL :^(

The term 'gateway' is what it implies-
a 'gate', or a point of entry/exit for
traffic coming from one network to
another. In this case, your router is
acting as a gateway form your home
network (Linux Box + File Server +
SecCam), to the ISP's network.

So, the routing tables are like GPS
way-points. They mark specific
locations between packet origin
and packet destination.

Try this as root:
route add -net default netmask default gw 192.168.1.1 dev eth0
(IFF your router's address is 192.168.1.1, of course).

This should be the first entry in your routing tables.
It specifies that the default host (0.0.0.0, the
current host in the current network) should send
and receive all traffic on interface eth0 via
the gateway at 192.168.1.1 (your router).

The next entry will specify that all broadcast
traffic (in this example, all machines who have
an address of 192.168.1.xxx) should be routed
by the default host (again, as root) :
route add -net 192.168.1.0 netmask 255.255.255.0 dev eth0

That should get you up and networked, as long as:
1)There are no glaring hardware problems
2)There are no glaring kernel issues
3)Your router's address is 192.168.1.1

This should work even if you change from
dhcp to static and back, as long as you
give yourself a valid network address
that matches your routers scheme, i.e.
192.168.1.some#-not-zero-or-one .
If you're camera and file server are going
to use dhcp, but the Linux box is
going to have a static addy, use
something beyond what most routers
will use if they are reset (i.e. .100 to
..254; I have several Linux boxen
so I've made them 192.168.1.200,
..201, .202, etc... to separate them
from the dhcp-ed Windows boxen
my Dad uses).

Really, though, a few good
books/HOWTO's/man pages/
websites should really be in your
future. One weekend should be
all it takes, and you'll even understand
netmasking!!

HTH,
Tarkin

.



Relevant Pages

  • Re: [SLE] connection redundancy
    ... which is the router just this side of the ... >>because it's own gateway is still up. ... You'll also need three network cards to put into this Linux box. ... your internal LAN can route packets to the Internet. ...
    (SuSE)
  • Re: Cant access secure Web pages
    ... and which need to be contacted via the Default Gateway. ... The Default Gateway being the software process that does the network ... Gateway (as set up by your ISP's DHCP packet to the router), ... me so I can send it directly (to the MAC address discovered by ARP). ...
    (uk.comp.sys.mac)
  • Re: way OT: route table
    ... The default gateway is at 192.168.16.1. ... or the gateway does not lie on the same network as the ... The private router is set up to pass all ... >your access router has an interface on ...
    (microsoft.public.backoffice.smallbiz2000)
  • Re: please advise - problem with routing
    ... Actually, these are HOST addresses, not NETWORK addresses. ... I will assume that this means from the 192.168.1.x/24 subnet you can ... your Internet Router, and not related to routing between the two internal ... Gateway using Interface 192.168.1.12. ...
    (microsoft.public.windows.server.networking)
  • Re: Adding a route question
    ... Do I have my network cards gateways configured correctly? ... Subnet mask 255.255.255.0 ... With one router it is ... > gateway" so no static routes need to be manually ADDED. ...
    (microsoft.public.win2000.networking)