Limi's Sphere of Influence

The current BeBox routers have issues with UDP as the timeouts on the sockets are too large. Some games and software create excessive numbers of UDP sockets which then cause issues with the routers ability to handle connections. You can't adjust the setting for the UDP timeout through the web interface easily, so here are the instructions to modify it...

1. Browse to... http://192.168.1.254/cgi/b/bandr/?ce=1&be=0&l0=0&l1=1&tid=BACKUP_RESTORE and login
2. Select 'Backup Configuration Now...' and save the file
3. Open up the file you just downloaded 'user.ini' in your favorite text editor
4. Search for... appconfig application=GAME(UDP) ...and you should see 3 lines which look like...
   
   appconfig application=GAME(UDP) trace=enabled timeout=60
appconfig application=CONE(UDP) trace=enabled timeout=300
appconfig application=LOOSE(UDP) trace=enabled timeout=300


5. Change the timeout value to '3' for all of these
6. Now search for... timerconfig timer=udpidle
7. Change the value from '65' to '3'
8. Save the file, and then upload it into the router via the 'Restore saved configuration'

After that your router should restart and your UDP timeout problems should be fixed.

I found this fix on another site, so just re-posting it here to preserve it for anyone who might need it.

It seem's a couple of times now i've needed the ability to create empty GIT branches in a repository so that I could seperate some code. Be that documentation or just seperate parts of a project, it's very useful (and saves having to create another repo). But everytime I need it I can never remember the commands to run, and the results that Google brings back usually are for old versions or the commands have changed. So, mainly for my own reference, this is how to create a completely empty branch in GIT...

git symbolic-ref HEAD refs/heads/newbranchnamehere
git rm --cached *
rm *

At this point put in or create your new files, then add them as you usually would and commit and push.

git add a.rb
git commit -m 'insert witty commit message here'
git push origin newbranchnamehere

A little while ago I started to re-write one of my gems, however, because it was such a drastic re-write, development was done in a brand new branch. So no code existed on this new branch. Finally came to the point where I decided to switch the old gem out for the new one on GitHub, and instantly ran into problems. I couldn't really just merge the development branch into master, as it wasn't originally based off master, so this is what I did...

1. On the GitHub repo, set the default branch to be the 'dev' branch.
2. Rename the local branches
   
   git branch -m master legacy
git branch -m dev master
   
   
3. Delete the remote master branch on GitHub.
   
   git push origin :master
   
   
4. Push up the new master to GitHub.
   
   git push origin master:refs/heads/master
   
   
5. Push up the old legacy code to GitHub.
   
   git push origin legacy:refs/heads/legacy
   
   
6. On the GitHub repo, change the default branch back to 'master'
7. Finally, Delete the old remote dev branch on GitHub.
   
   git push origin :dev
   
   

So now you should have the old master branch in a new branch called 'legacy' and the new 'dev' branch as master. Done and done!