Puppy Network Wizard

Post Reply
Message
Author
Scrollon
Posts: 3
Joined: Wed 05 Aug 2015, 11:27

Puppy Network Wizard

#1 Post by Scrollon »

Hello
I'm new to Puppy and I am struggling to setup my wifi network adapter. I'm using the Puppy Network Wizard and all is fine until I try to enter the Shared Key. It contains a backslash (\) which is getting ignored. I have tried \\ but that doesn't work either. Is there a way of escaping the \ character? Can I set the shared key in another way, perhaps from the command line?
Any help would be most welcome.
Regards
Geoff

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#2 Post by rcrsn51 »

Try a different connection manager. PeasyWiFi has a similar problem with back-slashes, but it lets you manually edit the wpa_supplicant.conf file to fix it.

Or you can use \\.

Scrollon
Posts: 3
Joined: Wed 05 Aug 2015, 11:27

#3 Post by Scrollon »

I tried using \\ with no success. I will have a look at Peasy Wifi, thanks.

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#4 Post by rcrsn51 »

Sorry. I meant that PWF can use \\ instead of doing a manual edit.

User avatar
Burn_IT
Posts: 3650
Joined: Sat 12 Aug 2006, 19:25
Location: Tamworth UK

#5 Post by Burn_IT »

Does either allow inputting the key as hex??
I'm at work so I cannot look right now
"Just think of it as leaving early to avoid the rush" - T Pratchett

Scrollon
Posts: 3
Joined: Wed 05 Aug 2015, 11:27

#6 Post by Scrollon »

Hi rcrsn51

Got it! I installed PWF and tried \\ again and, as you said, it just works. Thanks very much for the very swift response.
Cheers
Geoff

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#7 Post by rcrsn51 »

Excellent.

@Burn_IT: PWF's problem with the back-slash is that either GTKdialog or the bash scripting somehow interprets it as a line break. I have yet to track down the culprit. But it gets protected by using \\.

There is a sed command involved here that appears to need a triple-back-slash to work correctly!

If you use the hex version of the passphrase instead, you would need to manually edit the .conf file in order to remove the quotes that normally surround the passphrase.

I wonder how Frisbee handles this situation.

Post Reply