On Wed, Dec 04, 2002 at 11:49:56PM -0800, Michelle Storm wrote:
> > So, let me make sure I have this clear.
> > My Current system: Linux dragon 2.4.19-k7 #1 Tue Nov 19 03:01:13 EST 2002 i686 AMD Athalon GNU/Linux
> >
> > On Linux Box:
> > -------------
> > 1) if I don't already have it installed. Install the package: iproute
> > 2) do from #: ip addr add 192.168.0.20 brd + dev eth0
> >
> > On Windows XP box:
> > ------------------
> > 1) Do you know how to add multiple IP's to NIC on XP (tell me how on
> > Win2k and I can probably figure it out on XP.) <-- never knew about
> > this.
> > 2) add: 192.168.0.30 to XP nick
> >
> > Then just tell the computers to look for IP: <other computers 192.168.0.?? address?
>
> Something is missing. I found out how to set the XP box up to have an
> Alternate (PRIVATE) networking address. But I don't know if I did
> everything I had to do on my Linux box.
>
> rtnetlink reports that I've added teh 192.168.0.20, and I can ping
> myself with that IP, but I can't ping the other computer, and vice
> versus.
Hmm. On the linux box, `ip addr ls dev eth0' will show the ip addresses bound
to eth0. For example, here's the output of that command for the
internal interface on my firewall, which has two ipv4 addresses:
nnorman@argonath:~ $ ip addr ls dev eth1
4: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100
link/ether 00:02:e3:02:dc:be brd ff:ff:ff:ff:ff:ff
inet 192.168.0.1/24 brd 192.168.0.255 scope global eth1
inet 192.168.0.2/32 scope global eth1
inet6 fe80::202:e3ff:fe02:dcbe/10 scope link
Likewise, I think `ipconfig /all' (typed at a command prompt) on the
XP box should show you some info about IP there.
Next step: check the ARP cache on each box to see if they know about
each other. `arp' on the linux box will do; you're looking for an
entry like
192.168.0.30 ether 00:02:E3:02:DC:BE
where the MAC address is the address of the XP box. I believe XP has
an arp command as well (I might as well confess at this point that I
no longer have a win2k system at my desk, so this is all from memory
as far as windows goes).
As long as both systems are using addresses from net 192.168.0.0/24
(i.e. with a 255.255.255.0 netmask), it should work. No routes are
needed since this is a local subnet.
If it's still not working I'd start to suspect the switch. In your
previous email you said each PC connected to the switch was oin a
seperate subnet. Does the switch support VLANs, and if so, is each
port in a seperate VLAN? Do you have access to the management of the
switch (if it is in fact manageable?) If, on the other hand, the
switch is some el cheapo thing, just power cycle it: I've seen cheap
switches get really confused at times, which is why I avoid them.
Some more thoughts:
It might be worth trying the private addresses as the only (primary)
address on each PC.
It might be worth burning a CD-R/CD-RW and using sneakernet,
especially if the network games go long.
HTH,
--
Nathan Norman - Incanus Networking mailto:nnorman@incanus.net
What's needed is a certification system that separates those who
can barely regurgitate what they crammed over the last few weeks
from those who command secret ninja networking powers.
Attachment:
pgpWqP256tIX6.pgp
Description: PGP signature