Re: [Sheflug] Re: Network Goes on Holiday

["Stephen J. Turnbull" <nospam [at] sk.tsukuba.ac.jp>]

>>>>> "Chris" == Chris J/#6 <sixie [at] nccnet.co.uk> writes:

    Chris> They're still both on different networks (192.168.0.0/24
    Chris> [SuSE] and 192.168.1.0/24 [Debian])...you either need to
    Chris> reconfig the Suse box so its network is 192.168.1.0/24 or
    Chris> the Debian so its 192.168.0.0/24, or change the netmask to
    Chris> 255.255.0.0 (there are other legal values but that'd
    Chris> involve be sitting down and working them out).

If they are physically on the same wire (including a NON-switching
hub) there's another option, which is simply adding routes.  There's
nothing illegal or impossible about

ifconfig eth0 1.1.1.1 netmask 255.255.255.0
# 2.2 kernels do the following automatically
# route add -net 1.1.1.0 netmask 255.255.255.0 eth0
route add -host 2.2.2.2 eth0

I just did it, it worked---before adding the 2.2.2.0 route traceroute
showed 2 hops including the gateway, afterward one hop direct to
target.  I imagine that

route add -net 2.2.2.0 netmask 255.255.255.0 eth0

would work just as well.

-- 
University of Tsukuba                Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Institute of Policy and Planning Sciences       Tel/fax: +81 (298) 53-5091
_________________  _________________  _________________  _________________
What are those straight lines for?  "XEmacs rules."
---------------------------------------------------------------------
Sheffield Linux User's Group - http://www.sheflug.co.uk
To unsubscribe from this list send mail to
- <sheflug-request [at] vuw.ac.nz> - with the word 
 "unsubscribe" in the body of the message. 

  GNU the choice of a complete generation.