Hi,

I'm VERY new to openwrt, generally being a windows CE type of guy!

I have built and flashed a linksys WRT54g AP, but am having difficulty in understanding the build structure (come back platform builder....) so I can bring up the Wifi without playing with the AP command line. The offending line is shown in the title (I think)

I think I understand that the AP /etc/config/networking scripts are run when the AP boots and that these inturn are built by the general kamikaze build scripts.

I have managed to track down this line in the build_mipsel\root\lib\wifi\broadcom.sh file  and also in the
build_mipsel\linux-2.4..\broadcom\-wl-...\ipkg\wlc\libwifi\broadcom.sh directory

Both these files get re-generated by the build process.

So what is the correct way of dealing with this in OpenWRT

I have looked at the FAQ/Docs but did not find anything on this - sorry if its too obvious for these!

Regards

nick

Try $YOUR_BUILDROOT/package/broadcom-wl/files/lib/wifi/broadcom.sh.

Hope this helps,
Charlie

there's a good reason it's disabled by default. it's so that people won't just plug in the router and use it with the stock settings like a normal consumer router - which allows full access to the system via wireless with no password. you are expected to configure it at least once via the command line (or web interface if you installed one) before using it.

kevin@xen:/stuff/openwrt/trunk$ grep -R "REMOVE THIS LINE" * 2>/dev/null
docs/.svn/text-base/wireless.tex.svn-base:      # REMOVE THIS LINE TO ENABLE WIFI:
docs/wireless.tex:      # REMOVE THIS LINE TO ENABLE WIFI:
package/hostap-driver/files/lib/wifi/.svn/text-base/hostap.sh.svn-base: # REMOVE THIS LINE TO ENABLE WIFI:
package/hostap-driver/files/lib/wifi/hostap.sh: # REMOVE THIS LINE TO ENABLE WIFI:
package/madwifi/files/lib/wifi/madwifi.sh:      # REMOVE THIS LINE TO ENABLE WIFI:
package/madwifi/files/lib/wifi/.svn/text-base/madwifi.sh.svn-base:      # REMOVE THIS LINE TO ENABLE WIFI:
package/mac80211/files/lib/wifi/mac80211.sh:    # REMOVE THIS LINE TO ENABLE WIFI:
package/mac80211/files/lib/wifi/.svn/text-base/mac80211.sh.svn-base:    # REMOVE THIS LINE TO ENABLE WIFI:
package/broadcom-wl/files/lib/wifi/.svn/text-base/broadcom.sh.svn-base: # REMOVE THIS LINE TO ENABLE WIFI:
package/broadcom-wl/files/lib/wifi/broadcom.sh: # REMOVE THIS LINE TO ENABLE WIFI:

yes indeed it makes a lot of sense but it also was a pain for me when i built my first openwrt kamikaze image (used whiterussian before) and flashed it and BANG... offline. the router was on top of a building, i was having  only wireless access to it possible at that time. (the wire part was going in someone's appartment to a local network with some servers running, he was not home FOR ANOTHER BLOODY WEEK) ...

wwow... just thinking of it makes my head spin again. what a pain it was that day for me...

now... especially for the svn non release, debug versions (which i doubt will be ever used by someone not evolved enough to protect the router within the first 7 seconds of it's first run), i think it really is safe to just enable the wifi by default.

(Last edited by dlbogdan on 23 May 2008, 11:18)

While I think that disabling wifi by default is a good thing(tm), I think it would be great if the image builder offered a way to preconfigure wifi for the image so you can get working wireless (with encryption) out of the box.
(I think I read somewhere one could do it manually by placing a prefilled files/etc/config/wireless into the root directory of the openwrt-sources, but I never tried this).

Hi,

Thanks for all the replies.

It seems that the 'master' script is in trunk/package/broadcom-wl/files/lib/wifi/broadcom.sh anything you put in here gets into the scripts that are generated in the trunk/build_mipsel/...... and these get into the access point /etc/config/networking script that is run up on boot.

Thanks for the security warnings, this is for some research and is a sealed 2 box network.

I guess I was trying to make the more general point that I cant seem to find where all this sort of stuff is laid down and what the higher level of structure is. For instance if I wanted to make the http server on port 1234 or wanted to disable vlans..(from the build)  I cant believe its down to greping and trial build until you find the magic file!

Any authoritative resources in this area most welcome!

Regards

nick

You're not going to like this response, but... Perhaps this shows the need to TEST a new setup before actually putting it into service, especially in a hard-to-access location?  Anytime you're taking your hands off some equipment, whether it's a router going to the top of a roof or a laptop going to your sister, ask yourself - If this breaks in some way, what will I do?  What can I check before I allow myself to make a horrendous error? (In case you're wondering, my most-stressful case was making changes to a router in Germany while I was sitting in Texas)