On Monday 08 July 2002 04:29, Jethro Cramp wrote:
Steve - thanks for the comments.
Sure! Routing is basically simple. But we tend to make it more complex than it needs. I did not make up what I said. More than likely somthing else is wrong. Do this to me off list and we'll share the result when you are up: run on every computer on your lan; su domainname -f >/tmp/landebug.log ifconfig >>/tmp/netdebug.log netstat -nr >>/tmp/netdebug.log cat /etc/hosts >>/tmp/netdebug.log cat /etc/resolv.conf >>/tmp/netdebug.log ps afx >>/tmp/netdebug.log chown your_user_name /tmp/netdebug.log Then mail each to me and maybe with a note of what you want that computer to do. No, you do not need different subnets for hubs. They don't care. (IP less.) Routers needs different subnets, that's what routers were made for. (Heck, chcck into your local Barnes and Noble and take a look at a hard cover book called TCP/IP Illustrated, Volume 1 by Stevens. Spend half an hour reading about routing and you'll get it. It has a nice test network on the front cover which is used in each example. Maybe bring a notebook too for notes. Better yet buy it.) You may of course have turned on the firewall and are not even listening on the port.
On Monday 08 July 2002 12:23, steve wrote:
<snip>
In my little corner I have my desktop connected to the office network (through 192.168.0.50/eth1) and I can connect to the other computers and the internet fine.
I probably should have mentioned that my two computers are (of course) running SuSE
<snip> You can not ping across two different networks like that.
I was trying to ping from the laptop to the desktop and vice versa - that should be on the same two networks.
To reach different networks you need to have a router to connect the two. The router has one nic on each network and table entries showing which nic can route what traffic.
LAN1---[eth0 ROUTER eth1]---LAN2
If LAN1 is 192.168.15.0 and LAN2 is 192.268.0.0, you could make eth0 192.168.15.1 and eth1 192.168.0.1.
Make your netmask 255.255.255.0 on all.
This is what I was trying to achieve with my desktop being the router. I had set it up exactly as you described but with my desktop in the place of 'ROUTER'.
Your routing table should have 192.168.15.0 with 192.168.0.1 as the route (UG - Up and Gateway) and 192.168.0.0 with 192.168.15.1 (UG).
I'm not clear on where you have the Internet, but the machine which is the gateway out would have let's say 24.24.24.1 as the default gateway. This means when it does not know where the packet goes (i.e. destination not one of the 192.x.x.x.) send it out through it.
Now you could probably make things a lot easier by setting up a network at home on the same network as at work. Make sure you grab an address which is available on both. I.e. there's no need to have seperate subnets for each hub.
Anything for an easy life. I tried setting up like this:
laptop eth0 192.168.0.51
desktop eth0 192.168.0.49 (this is to the hub connecting to the laptop) eth1 192.168.0.50 (this is to the office hub, which the rest of the machines are connected to).
To me this doesn't feel right and I still can't get the laptop and desktop to ping one another. Surely if I am using two separate hubs they have to be on different nets?
ip route reveals:
[laptop] 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.51 default via 192.168.0.1 dev eth0
[desktop] 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.49 192.168.0.0/24 dev eth1 proto kernel scope link src 192.168.0.50 127.0.0.0/9 dev l0 scope link default via 192.168.0.1 dev eth0
At the end of this I wonder if you have a firewall?
NMP - 'Not My Problem'. The rest of the 'office' is somebody else's and I only need to connect with their network to get a broadband connection and share a printer. I have a firewall on 'desktop' which I'm going to check + strengthen once I have it and laptop talking together. I fully expect the window machines to burn in the fire of hades at any moment.
Jethro
-- Steve _____________________________________________________________ HTML in e-mail is not safe. It let's spammers know to spam you, and sets you up for online attack through IE 4.5 and above. Using HTML in e-mail promotes it as safe to the uninitiated.