Author Topic: Shes Dead, Jim .... But .... Thats Impossible. (Read 5013 times)

Miami_Bob · « **on:** February 09, 2005, 10:55:40 pm »

I posted first over in Security and Networking

https://www.oesf.org/forums/index.php?showtopic=10590

but ony have 22 reads and no feed back after about 4 days.

Since I have some new info that might indicate the problem is related to Cacko v1.22, decided to post over here this time.

The original was:
-----------------------------------------------------------
IFCONFIG HELP?

Its probably something simple that I'm overlooking but ......

C860
Cacko v1.22
Ambicom WL1100C-CF 802.11b

$ su
# ifconfig eth0 hw ether xx:xx:xx:xx:xx:xx
SIOCSIFHWADDR: Invalid argument
#

# ifconfig eth0 down
#
# ifconfig eth0
eth0 (info)
#

[looks like eth0 is not taken down?]

# ifconfig eth0 hw ether xx:xx:xx:xx:xx:xx
SIOCSIFHWADDR: Invalid argument
#

# macchanger -s eth0
Current MAC: xx:xx:xx:xx:xx:xx (Ambicom, Inc)

# macchanger -a eth0
Current MAC: xx:xx:xx:xx:xx:xx (Ambicom, Inc)
ERROR: Can't change MAC: Interface up or not permission: Invalid argument.
#

# macchanger -s wifi0
Current MAC: xx:xx:xx:xx:xx:xx (Ambicom, Inc)

# macchanger -a wifi0
Current MAC: xx:xx:xx:xx:xx:xx (Ambicom, Inc)
ERROR: Can't change MAC: Interface up or not permission: Invalid argument.
#

Other posts have said "The above ifconfig worked on almost every linux system I've tried." & indicated that this works on the Zaurus. What am I missing here (G)?

Fell free to berate me harshly for my failure to recognize that which is probably IOTTMCO, just, please, enlighten me (G)!

TIA!
-----------------------------------------------------------

The new info is that all the above work fine under OZ/Opie v3.5.2 (although multiple other major problems preclude my going to that OS as a solution). So I copied some of the files in /etc/pcmcia/ to the Cacko v1.22 system.

I got wifi0 & wlan0 (instead of eth0) using the hostap drivers, just as OZ/Opie does HOWEVER, I get the same warning with iwconfig using either set up, which is:

"Warning: Driver for device wifi0 recommend version 18 of Wireless Extension, but has been compiled with version 15, therefore some driver features may not be available ...

I think that this may be the source of the macchanger & ifconfig problems. Hot fix A does not change the behavior.

Solutions? Suggestion? Feedback? Bricks, boots & rotten vegies? (G)

Go ahead; *I* can take it!

maslovsky · « **Reply #1 on:** February 10, 2005, 04:15:12 am »

Quote

# ifconfig eth0 hw ether xx:xx:xx:xx:xx:xx
SIOCSIFHWADDR: Invalid argument

That's because CF card is suspended. Try to do that when you card is connected or trying to connect.

Miami_Bob · « **Reply #2 on:** February 10, 2005, 04:30:26 pm »

Quote

That's because CF card is suspended. Try to do that when you card is connected or trying to connect.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=66399\"][{POST_SNAPBACK}][/a][/div]

Ahhhhh! I stand in awe of your extensive knowledge, sir!

Question once again. If the card is connected or attempting connection, this works (and so does macchanger). The new MAC is retained when the connection (or attempt to connect) is aborted.

However, when the next time the card attempts another connection, the hardware MAC is reentered.

Can the card be brought out of suspend mode by means other than trying to connect? Ie; so the new MAC is not lost?

I have another, some what related observation/question which I'll post here as the next "reply".

THANKS!

Miami_Bob · « **Reply #3 on:** February 10, 2005, 04:40:50 pm »

Over visiting an old friend earlier today & he wanted to see my C860 link into their house router (Linksys) & network. It failed to connect. I took a bunch of friendly abuse (he is a Wind-ho$e fanatic).

I could connect to their *neighbor's* Linksys router with out trouble (yes, we had permission). The only difference that we could tell was that the SSID of his house system had a space in between 2 words while the neighbor's did NOT. The C860 network app just refuses to recognise the space bar at all in the SSID diaglog box.

We couldn't test this hypothesis by changing the SSID of his house router, because he does not own the hardware (a roommate does) and did not know the (changed) user id & password.

However, I also failed to connect with the local free WAP at a Gables cafe, which *also* had a space between 2 words in the SSID. It seems to fit the pattern. My Sharp v1.2 JP NANDs (& higher) show the same inability to enter a space.

How can I show up my Wind-ho$e loving heretical porcine amigo? (G)

THANKS!

maslovsky · « **Reply #4 on:** February 10, 2005, 11:29:53 pm »

Quote

Can the card be brought out of suspend mode by means other than trying to connect? Ie; so the new MAC is not lost?

If youre intention is to change MAC address, you can put commands into one of the pcmcia scripts, which create network connection, for example /etc/pcmcia/network. Find the start() section and put your commands there. When this script is executed, the card is resumed, so it should work.

Regarding space in ESSID - that's a known problem with Sharp network applets. You can try to edit configuration files manualy after creating a connection and change ESSID there. The two files you need to check are /home/zaurus/Applications/Network/WLANX.conf (X is a number) and /etc/pcmcia/wlan-ng.conf (find a section corresponding to your connection)

Miami_Bob · « **Reply #5 on:** February 11, 2005, 07:04:39 pm »

maslovsky -

Thank you again for sharing your knowledge & experience.

I often take on odd "projects" (like the MAC changes) as if they were test questions in a text book. The ones that work easily go into the "tool box" but the ones that do NOT work easily become the best learning experiences.

However, I know my own limitations so when something becomes frustrating after I have tried to work I out on my own for a while without success, I go to the masters for my enlightenment (G).

By this method I increase my own wisdom.

One more, if might impose. Why does

#cardctl resume

leave the CF still in suspend mode? Intuitively, it would seem that this should bring it to the ready state. What am I not seeing here?

<< Regarding space in ESSID - that's a known problem with Sharp network applets. >>

Rats. And here I thought that I might have discovered something "new" on my own (G).

THANKS! once again -

padishah_emperor · « **Reply #6 on:** February 12, 2005, 06:26:10 am »

Quote

How can I show up my Wind-ho$e loving heretical porcine amigo? (G)

LOL! You don't need to, his love for that 'thing' does the job quite well.

maslovsky · « **Reply #7 on:** February 12, 2005, 06:00:00 pm »

Quote

#cardctl resume

leave the CF still in suspend mode? Intuitively, it would seem that this should bring it to the ready state. What am I not seeing here?

Yes, it does resume the card, but it goes into suspend almost immidiately. I think there are Sharp's patches in the kernel to the pcmcia code, which keep cards suspended most of the time. Probably for power saving reasons.

The best for you will be to add your code to the networking scripts because they are exeucuted when card is resumed, so they should work.

Miami_Bob · « **Reply #8 on:** February 12, 2005, 08:14:51 pm »

Quote

LOL! You don't need to, his love for that 'thing' does the job quite well.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=66713\"][{POST_SNAPBACK}][/a][/div]

Ahhh! Very good to see your handle again! Welcome back (G).

Miami_Bob · « **Reply #9 on:** February 12, 2005, 08:20:24 pm »

Quote

Yes, it does resume the card, but it goes into suspend almost immidiately. I think there are Sharp's patches in the kernel to the pcmcia code, which keep cards suspended most of the time. Probably for power saving reasons.

The best for you will be to add your code to the networking scripts because they are exeucuted when card is resumed, so they should work.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=66769\"][{POST_SNAPBACK}][/a][/div]

Ahhhh. I was begining to suspect something like that. Noticed that when I use the rear power button to turn the C860 back on with the CF WiFi card still in, the light on the card comes on briefly then blinks for a short time before going back off.

Thank you again, sir Maslovsky! This is a very educational little project for me & your insight is much appreciated! I will do more study before bothering you with more questions (G).

maslovsky · « **Reply #10 on:** February 13, 2005, 09:15:53 am »

Thank you too - it's always nice to deal with curious people, whoc don't just say "hey nothing works"

Miami_Bob · « **Reply #11 on:** February 13, 2005, 05:58:31 pm »

Quote

Thank you too - it's always nice to deal with curious people, whoc don't just say "hey nothing works"
[div align=\"right\"][a href=\"index.php?act=findpost&pid=66839\"][{POST_SNAPBACK}][/a][/div]

Thanks (Blush). Even when things DO work OK, I have this long standing, bad habit of needing to understand how & why. Taking stuff appart just to see whats inside & find out if I can put 'em back together so they work again (or do something different). Darwin must have been right at least regarding some of us - descended from orangutans (who couldn't spell either!)

But I do have a grand record as a "mine sweeper". If there IS a bug in something, I WILL somehow manage to trigger it. A "gift" that I would as soon not have received (G).

THANKS! And, when you need something tested to distruction, don't hesitate to holler!

maslovsky · « **Reply #12 on:** February 14, 2005, 08:39:56 am »

Quote

THANKS! And, when you need something tested to distruction, don't hesitate to holler!
[div align=\"right\"][a href=\"index.php?act=findpost&pid=66894\"][{POST_SNAPBACK}][/a][/div]

OK, will keep that in mind

News:

Author Topic: Shes Dead, Jim .... But .... Thats Impossible. (Read 5013 times)