Routing

[sss]

ok.. the big tower on the LEFT is an access point ... it has a dhcp server giving ip's on the 192.168.0.* range


the router on the other side is running in CLIENT mode(IE wireless clients cannot connect to it, it IS a wireless client), it is obtaining its wirelss ip address (192.168.033 from the big tower)

on the lan side the router has its own dhcp assigining 192.168.1.* address.. all the lan pc's get their address from this...

so far so good... now how should the routing be setup for this so that lan pc's can see other computers connected on the main tower

[sss]

http://img62.imageshack.us/img62/127/image10vk.jpg

[sss]

also the lan part of the router is 192.168.1.1... and that is what the gateway is for all lan clients!

[stoke]

I'd setup the PC's at home to get their ip address from the router and the router's DHCP server should set the default gateway on them machines to 192.168.1.1 [router's LAN ip].

Then the router must take care of all your local network traffic, routing all requests to 192.168.1.* back inside your network, and any other requests it must route through to the AP on 192.168.0.* it must look after.

i.e. You have no choice nor control.

[sss]

well yes.. so far so good

[stoke]

I don't get it ... what is your question ?

Do you want to change what the router does ?
It seems like you're pretty stuck with what it does by default and if you can configure it further ... oh .. I get it ... you've got all this harware lying at home that you also want to use and possibly use the same router with that HW ?

[sss]

well at first... the tower and the pc's could not see each other.. but they magically fixed themselves now... they sorted out their own routing

but


i dont understand their routing tables and what they mean!

[stoke]

um ...

http://www.informit.com/articles/article.asp?p=24375&rl=1 = A really good "intro" how-to on Routing and all the components.

http://www.pacificnet.net/~bbruce/route_main.htm = When a PC has 2 Network cards, how to use routing to control the 2 cards and who gets to see what.

The above 2 links should get you to a stage where you can start hexperimenting.

[sss]

ok.. network setup... bf2 ping is 60ms :)

real speed is about 60KB a second

and uncapped :)

[SaintMg]

well at first... the tower and the pc's could not see each other.. but they magically fixed themselves now... they sorted out their own routing

:rofl: i have had some very strange occurances with network's and routers , like i have no idea what to do and how they work just plug this in there that here and turn on . some time non of my pc can see the network other time i can read from a pc but no write access or my favourite when pc A can acess pc B but pc B cant see pc A but can see the server :confused:

[TG]

Networks should be left to the sorcerers (like me) who understand the arcane rituals and spells to invoke to get it working properly.



LIFE!!!! I GAVE IT LIFE!!!!!

[sss]

man i have one hectic question.. that i dont think anyone could answer!

[gus]

If it is a question nobody can answer, then it must involve women. If it is a network question, then surely somebody will have an answer. :D

[sss]

ok heres how it works.... i setup my router to have a static ip

of 196.x.x.x <--- this is my internet public static ip
gateway 196.x.x.x

this 196 network i am on i am not to sure what the deal is with it but my router is wirelessley connected to it.. anyway they prioritize bandwidth and all that... so i ping games.saix.co.za and get a ping of 200ms

i remove my static ip and reconnect to the network
i get DHCP'd a 192.168.0.X address
my gateway also changes to something like that.. now i cant browse anymore.. dns doesnt work either.


BUT

i can ping my old gateway 196.x.x.x
i can ping games.saix.co.za aswell..

PING is the only thing that works.. and now my ping is also 40ms

my route is obviously different... ping works.. but actual traffic does not..... why is this??

[sss]

i need to work out how my ping is going through.. then setup my dns and gateway accordingly so that normal traffic can go aswell.. but how do u work it out?

[stoke]

Ping runs on a protocol called ICMP and is usually controlled completely seperately from the other protocols.

What is means is that THEY are blocking you in this modified configuration.

[sss]

so now i need to write some fancy stuff to encapsulate all my data inside a icmp packet.. transmit that to some external server that extracts it and then makes a connection on my behalf... excellent... i'll hop on it right away!

[stoke]

LOLLIES .... ICMP is waaay too small to be useful for anything other than a Howzit.

But .. then again .. you can size it at any time ... hmmm ...

Do this:
ping -f -l 2048 www.google.co.za = packet 2048 bytes big not allowed to fragment itself ...

Usually the network will not be able to send a ICMP packet that big without chopping it into smaller parts.

Dangit.

[edit: I can get away with a packet size of 1216 on this IS ADSL network.]

[sss]

i get stuck just under 900 bytes

but its not like i'm gonna actually attempt the thingy above... too much work with no payload

[gus]

You must NOT have a 196.x.x.x address for the gateway address for your router. This will be somebody else's public IP address, so using it internally in your network will mess you up. The 192.168.x.x ones are the right range to use, which is why DHCP gives you one like that. Is your router sitting inside your network? In that case, it must have a valid network address for the network it attaches too and then have a 192.168.x.x. (or an address in another non-routable range) address for your little private network, which is then the gatewy address for your PC. Also, make sure that the same range is not used on both sides of the network, i.e. if the rest of the network maybe use 192.168.0.x, then make sure your more private network behind the router for example use 192.168.1.x. As you have done in the drawing at the top of the thread. You may need to change the DHCP setup on the router to hand out IP addresses in the right range for your little network and set valid DNS addresses there.

The reason why you can ping your old gateway is probably because you are actually pinging the real owner of that 196.x.x.x IP address.

ICMP is basically designed to pass IP error messages, so is not really suitable for tunneling data.

You are getting into low level TCP/IP stuff, so you might want to consider buying this book:
http://www.kalahari.net/bk/product.asp?toolbar=none&sku=28370659&format=detail
(Not specifically from Kalahari, but I guess you can shop around yourself.)

[sss]

sorry.. i probably should of mentiond this is purely the external network.

not my internal network hence the 196. ips...

my connections is like this


(me + computer 1 + computer 2 ) at home --> 196.1.1.* --> router (wirelessly to isp ) 196.*.*.* STATIC ... or DHCP to 192.* , --> isp tower


its like the isp's wireless router is both on a internet network and private network!

all my internal network is 192.1.1.* stuff permanently

[sss]

woo R941 for a book.. i'll go use google some more.. hasnt failed me yet!! :)

[gus]

Good books are expensive.

A router has two IP addresses, one for each network it attaches too, which it routes between. The book mentioned above has a whole chapter on routing, I think. (OK, I have checked in the book and it indeed has a whole chapter on routing.)