search

freebsd / freebsd-wifi-build

freebsd-wifi-build
142 stars 59 forks source link

Config Overview #104

Open ebichu opened 7 years ago

ebichu commented 7 years ago

Ok so I've RTFM:d a lot but I'm still a bit confused about the best practice with regards to configuration. In my case I've got an TP-Link TL-WDR3600.

Should I just build an unedited .bin-file, log on with telnet, make changes, cfg_save and be done with it? Or should I make the changes in the mfsroot?

Does it matter, which would be the easier way? At the moment I just want the basics; I.E. ipfw, nat, dnsmasq, dropbear with WAN as WAN and yellow as ethernet.

kevans91 commented 7 years ago

Hi,

To start with, I would flash the default mfsroot and make your changes afterwards as you've initially suggested. My line of reasoning is as follows:

1.) The defaults work, give you access by default 2.) Assuming you're completely new to this, you'll likely end up changing things around quite a bit 3.) If you build from a version of freebsd-wifi-build as of ea5ac953bac1fef0ac804e0327b72dc9126c361b (7 days ago), then you can use the recovery fallback for the WDR3600 (hold down WPS button during boot, will bypass initial cfg_load and load defaults from the mfsroot)

Of course, if you're familiar with the intricacies of the underlying etherswitch you're playing with, then the above may not really matter. YMMV

erikarn commented 7 years ago

Hiya,

Yes, you edit /etc/defaults/rc.conf, set the user/root password, then 'cfg_save' and reboot.

Yeah, maybe we should have default config profiles. ;)

-adrian

On 26 December 2016 at 08:54, ebichu notifications@github.com wrote:

Ok so I've RTFM:d a lot but I'm still a bit confused about the best practice with regards to configuration. In my case I've got an TP-Link TL-WDR3600.

Should I just build an unedited .bin-file, log on with telnet, make changes, cfg_save and be done with it? Or should I make the changes in the mfsroot?

Does it matter, which would be the easier way? At the moment I just want the basics; I.E. ipfw, nat, dnsmasq, dropbear with WAN as WAN and yellow as ethernet.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/freebsd/freebsd-wifi-build/issues/104, or mute the thread https://github.com/notifications/unsubscribe-auth/ABGl7SCmWJVslUpNNwXmM0bVaZt0Yl1Bks5rL_E-gaJpZM4LV2Qq .

ebichu commented 7 years ago

@kevans91 It's been awhile since I've tinkered with networking and such in FreeBSD and haven't gotten that much time for this project atm so yeah, the first solution seems as the most reasonable thing to do.

@erikarn Hehe would be nice. ;) I believe this would be somewhat on topic (most efficient configuration/efficiency :P); Have you tried emulating a WDR3600-img with qemu? And if so, do I need to think about anything other than the standard setup; i.e. as per the docs?

ebichu commented 7 years ago

Ok so I did manage to configure pretty much everything using the cfg_save-path but am still a bit confused about etherswitch. Should it be used to make the yellow ports behave as regular ethernet ports? (as per my scenario where I want the router to behave pretty much as stock atm)?

And in that case I thought about this: https://lists.freebsd.org/pipermail/freebsd-mips/2015-October/004113.html :)