SCOUG-HELP Mailing List Archives

>> Next Message >>

Date:	Tue, 9 Dec 2008 09:51:40 -0800
From:	"Steven Levine" <steve53@earthlink.net >
Reply-To:	scoug-help@scoug.com
To:	scoug-help@scoug.com
Subject:	SCOUG-Help: ecs peer2peer problem

Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

In <001-cc893c49-38500.070@seadog.reno.nv.us>, on 12/07/08
at 06:43 PM, "Jon Harrison" said:

Hi,

>I had it working briefly so I now know that even with a MAC of 0 it will
>work and that I'm not wasting my time.

I recall you saying that before.

>I now think that the xwLan
>utility is my problem, either with the way I have set it up or just the
>way it works with static IP's.

If may very well be the case. I've had my own issues with llaecs. For
example the dummy address it assigns to the wireless interface when it is
not connected causes syslog packets to go the backhole.

>The problem seems to be with the way
>xwlan switches between wired & wireless using a script and the values I
>am using for the script.

Since you are using static IPs, what you can do is experiment with
ifconfig until you get a working setup and then implement the results in
your scripts. The attached might give you some ideas to experiment with.

Since your wired interface is lan1, it would start with

route -f
arp -f
ifconfig lan1 down
ifconfig lan1 delete
ifconfig lan0 down
ifconfig lan0 delete

which should get rid of all the cruft. Then configure the wired interface
with

ifconfing lan1 ...
route add default ...

and check if that is sufficient to result the LAN issue.

>Xwlan doc's say to not define the wireless device in tcpip config program
>(tcpcfg2.cmd). So I have lan0 as not configured because when I do a
>netstat the wireless nic shows up as the first adapter. Lan1 is my
>wired config. BUT, whether running wireless or wired, netstat -n shows
>all activity is on lan0.

This does not sound like what you want to happen, This might be an llaesc
issue or something else.

You could try reconfiguring so the the wired interface is on the first
interface. The tcp/ip bindings will look like

[tcpip_nif]
DriverName = TCPIP$
Bindings = W8086X101E_nif,W8086X4220_nif

where W8086X101E_nif is the wired adapter.

>That doesn't seem correct to me but I don't
>know what llaecs

It assignes a locally administered address (i.e lla) to the inactive
interface. They say this is to avoid disabled interfaces from confusing
the LAN components, but as I've noted, it can cause its own set of
problems.

Steven

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

File attachment: ifcfg.cmd

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

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".

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

Return to [ 09 | December | 2008 ]

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.