SCOUG Logo


Next Meeting: Sat, TBD
Meeting Directions


Be a Member
Join SCOUG

Navigation:


Help with Searching

20 Most Recent Documents
Search Archives
Index by date, title, author, category.


Features:

Mr. Know-It-All
Ink
Download!










SCOUG:

Home

Email Lists

SIGs (Internet, General Interest, Programming, Network, more..)

Online Chats

Business

Past Presentations

Credits

Submissions

Contact SCOUG

Copyright SCOUG



warp expowest
Pictures from Sept. 1999

The views expressed in articles on this site are those of their authors.

warptech
SCOUG was there!


Copyright 1998-2024, Southern California OS/2 User Group. ALL RIGHTS RESERVED.

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.

The Southern California OS/2 User Group
USA

SCOUG-HELP Mailing List Archives

Return to [ 27 | May | 2007 ]

>> Next Message >>


Date: Sun, 27 May 2007 00:22:13 -0700
From: "Steven Levine" <steve53@earthlink.net >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: route unreachable

In <001-37245946-14384.024@seadog.reno.nv.us>, on 05/26/07
at 11:24 PM, "Jon Harrison" said:

Hi,

>What could be the reason for route failure?

Since the hardware is good, operator malfunction is a likely culprit.

>The setup.cmd is correct but route fails.

If the failing route command is in setup.cmd, the above does not compute.
:-)

A typical valid setup.cmd would be

route -fh
arp -f
ifconfig lo 127.0.0.1
ifconfig lan0 192.168.10.3 netmask 255.255.255.0
ifconfig lan0 mtu 1492
route add default 192.168.10.251
ipgate off

>From the commandline I enter route add default '192.168.1.10 -hopcount
>1' and it fails.

Define fails. Do you get an error message?

FWIW, I would enter this as just

route add default 192.168.1.10

assuming that your router is 192.168.1.10.

>I cannot ping either, it fails.

This is expected. No routee. No pingee.

>I've changed tcpcfg to match my network.

Are you sure? It would help if you listed the ip addressed you think you
should be using.

>I've created a hosts file (which shouldn't effect my
>inablility to ping ip addr).

True. This just allows you to connect by name without running a dns
server.

Steven

--
----------------------------------------------------------------------
"Steven Levine" MR2/ICE 3.00 beta 05 #10183 eCS/Warp/DIY/14.103a_W4 etc.
www.scoug.com irc.ca.webbnet.info #scoug (Wed 7pm PST)
----------------------------------------------------------------------

=====================================================

To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".

For problems, contact the list owner at
"postmaster@scoug.com".

=====================================================


>> Next Message >>

Return to [ 27 | May | 2007 ]



The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA

Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS RESERVED.

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.