I am wanting to know this too. Is this setting just automatically set with this firmware?
Nope it's still broken, so need to use a sleep loop in the startup script to set it every 30 seconds
Also, where has SAMBA gone? It's not under NAS any more after enabling USB support and USB storage support. I haven't connected a drive yet.
Plus, why is there now a "SPUTNIK Powered" logo at the top of the GUI? I don't have it enabled.
** Update **
The 5GHz only channel also seems more unstable in this build - can't hold a connection above 300MBit for very long unlike previous builds which were fine. Have tried a variety of power settings and even changed the eth2 interference value, but nothing helps.
just try the 17949 standard mega build, it successfully mount the optware partition.. yeah!
-----
Disk Info
--- /dev/discs/disc0/disc
Block device, size 1000 MiB (1048576000 bytes)
DOS/MBR partition map
Partition 1: 512 MiB (536870912 bytes, 1048576 sectors from 2048)
Type 0x83 (Linux)
Ext3 file system
Volume name "Optware"
UUID 42770D79-761D-4D4E-8850-FC9021248904 (DCE, v4)
Volume size 512 MiB (536870912 bytes, 131072 blocks of 4 KiB)
Partition 2: 64 MiB (67108864 bytes, 131072 sectors from 1050624)
Type 0x82 (Linux swap / Solaris)
Linux swap, version 2, subversion 1, 4 KiB pages, little-endian
Swap size 63.99 MiB (67100672 bytes, 16382 pages of 4 KiB)
Partition 3: 423 MiB (443547648 bytes, 866304 sectors from 1181696)
Type 0x0B (Win95 FAT32)
FAT32 file system (hints score 5 of 5)
Volume size 422.2 MiB (442662912 bytes, 108072 clusters of 4 KiB)
Volume name ""
Status: Mounted on /opt
Status: Not mounted
-----
just a stupid question, how could I know if the swap partition is used? _________________ Belkin N600 Play Max HD F7D4301v1
thanks Fractal. any chance of a openvpn_small compile as well? seems like brainslayer has abandoned his regular builds, and we have many E1000 customers who may benefit.
Sorry for the delay... however, after compiling mega the bins are 7.835 megs I am going to have ascott check them before I post....
2nd... compiling NMBD makes the bin 7.9mb which is no go, will have to figure out how to trim them down
-Fractal
Do a NV60/64 as all the routers in this range has 16MB or more of flash. Only the older Mega devices have only 8MB. The currently Linksys flash is 12MB which includes IPV6 and all that jazz.
Sorry for the delay... however, after compiling mega the bins are 7.835 megs I am going to have ascott check them before I post....
2nd... compiling NMBD makes the bin 7.9mb which is no go, will have to figure out how to trim them down
-Fractal
Do a NV60/64 as all the routers in this range has 16MB or more of flash. Only the older Mega devices have only 8MB. The currently Linksys flash is 12MB which includes IPV6 and all that jazz.
You are right. Only the nv routers like e4200 can go above 7.5 mb. I will try a roll with alot of goodies for those. I am on my iPad right now as I am traveling. Also I can roll VPN builds. Ascott confirmed working bin this am so he may post updated mega with samba.
This forum has been very active lately so if I missed a request please let me know. My main focus has been USB auto fix and that seems working in most situations, this has been broken since June. Again thanks everyone for testing.
Posted: Tue Nov 29, 2011 23:14 Post subject: Mega bins with samba no nmbd
Hello,
Attached is a mega nv60k bin for testing rev 17949 with 17841 reverted, in order to test the fix for the USB automount problem for ext2/3 type file systems. (the fix is revert 17841)
Fractal's traveling and asked me to post these after testing myself. I tested with an e2k and an e3k. Samba is in this one. nmbd is not. These bins were kind of big but seem to work okay. We left nmbd out, for now, until we can get the size down further.
lawleo: cool, thanks
kt_haddock: fractal said he will try to do nmbd next.
taomyn: these do not have wl interference mode 2 by default. what's your setup for applying interference mode? I thought you would just need to do that once at boot-up and you're good. will you explain what you're doing/seeing more.
barryware, basmaf: thanks. are you using kong's method? cat /tmp/disktype.dump . We're testing with a typical "optware" type setup. First partition is ext2 /opt and 2nd part is swap, that's all. we're mounting swap via optware init scripts triggered from rc_startup. We're not using kong's patches and method of partition labels though kong's work was mighty useful to us while testing - we're just trying to get usb working like it was - automounts the first part to /opt, whether it's ext2/3, vfat. Swap we're handling our own way and not sure if it's the generally favored solution.
The current hypothesis we're testing is that the addition of ext4 support and checkin 17841 broke USB support (or is at least one problem with USB support since 17349).
I'm working on a preprocessor-based solution to submit to brainslayer as a patch for the USB problem.
Posted: Wed Nov 30, 2011 6:58 Post subject: Re: Mega bins with samba no nmbd
ascott wrote:
taomyn: these do not have wl interference mode 2 by default. what's your setup for applying interference mode? I thought you would just need to do that once at boot-up and you're good. will you explain what you're doing/seeing more.
As I understood it from testing a previous Fractal build, 17806 I think, it was discovered that setting this to 2 fixed the majority of the 2.4GHz issues people were having and that it was added to the new builds as a default. I then tested this but found that although it was initially set to 2 at start-up, subsequent changes to other settings through the GUI would reset this back to 0. Hence I now have to place the following in my start-up script:
Code:
while [ 1 ]; do wl -i eth1 interference 2; sleep 30; done &
Posted: Wed Nov 30, 2011 15:31 Post subject: Re: Mega bins with samba no nmbd
Taomyn wrote:
As I understood it from testing a previous Fractal build, 17806 I think, it was discovered that setting this to 2 fixed the majority of the 2.4GHz issues people were having and that it was added to the new builds as a default. I then tested this but found that although it was initially set to 2 at start-up, subsequent changes to other settings through the GUI would reset this back to 0. Hence I now have to place the following in my start-up script:
Code:
while [ 1 ]; do wl -i eth1 interference 2; sleep 30; done &
I have an E4200.
Taomyn, I get it. Thanks. That makes sense. It sounds like that when you apply changes to the network, it brings down and up the interface again, which loses the setting. This makes me think that setting interference mode should be done from the networking services routines: when an interface is brought up, check a nvram variable for interference mode and turn it on if it's set.
We were thinking we were going to put this setting into a init script, but now I see that's not going to work. I'll take a look at adding it in networking services and see if I can formulate a patch to submit. I'm thinking this might be something the dd-wrt devs would want to add to their UI: setting interference mode nvram variables that are picked up from networking services.
Are you saying here that the bins on page 6 have samba? That is the build I am testing.