[HowTo] Install and configure Oleg's firmware

[al37919]

My problem is that I installed OLEG 2.0.1.5 firmware (from forums discussions I found that should be a good choice instead Oleg 3.0.2.6).

where did you found so advanced "Oleg's" firmwares?
To the best of my knowledge, the last Oleg's firmware titled 1.9.2.7-10

[adrianio]

where did you found so advanced "Oleg's" firmwares?
To the best of my knowledge, the last Oleg's firmware titled 1.9.2.7-10

From this web page top link "Firmware Wizard" ->> asus->wl500gpv2. Link to asus wl500gpv2 download directory -> http://files.wl500g.info/asus/wl500gpv2/firmware/

[al37919]

it is asus original.

If you wish to get real Oleg's firmware, it is available here: http://oleg.wl500g.info/

For wl500gPv2 better take last version from here: http://oleg.wl500g.info/pre10a/ It seems to be very close to the next bugfix release.

[adrianio]

it is asus original.

If you wish to get real Oleg's firmware, it is available here: http://oleg.wl500g.info/

For wl500gPv2 better take last version from here: http://oleg.wl500g.info/pre10a/ It seems to be very close to the next bugfix release.

Very fast answer! Thank you! You've just got maximum points !!!
I read first page maybe hundreds times, but I did not think to click the link in the bottom of page! Bad for me!
Again, thank you!

[garifo]

Is there a way I can flash my asus to the previous version of oleg 1.9.2.7-9?
I'm currently on 1.9.2.7-10 but my router crashes every day almost.
Or how can I get the logs to see what is going on there?
I have wl-500gp v2
thank you.

[al37919]

Is there a way I can flash my asus to the previous version of oleg 1.9.2.7-9?
I'm currently on 1.9.2.7-10 but my router crashes every day almost.
Or how can I get the logs to see what is going on there?
I have wl-500gp v2
thank you.

what the problem is? Download and flash.

The best way to way to debug the situation is to get out system console output from the built in serial port. It requires some soldering skills.

More simple way could be to redirect syslog to the external storage, so that you can see if something was posted before the crash. I thing wengi's tutorial has something about that

[Etor]

ssh will be disabled, as dropbear is started from flashfs

you can either start it from web-command-line by typing:

dropbear 

or access router through telnet (it should be enabled in the web interface, but then it starts automatically)

Thanks, I havent time to test it yet but I have another question on my mind
Is it way how to access to LAN computer which have windows sharing? For example best way for me will be through mc But probably must be mounted to some directory? Anyone have experience with this?

[wengi]

Thanks, I havent time to test it yet but I have another question on my mind
Is it way how to access to LAN computer which have windows sharing? For example best way for me will be through mc But probably must be mounted to some directory? Anyone have experience with this?

Use TELNET instead of ssh (as posted before).
I do not get the question. You want to do what? With mc?

wengi

[cMcd01]

First - thanks for the great tutorial, wengi

My smb.conf is resetting on reboot so that I lose a couple key manual settings - specifically "encrypt = yes" which is required for access via a Mac. I'm using the onboard samba via the web interface. I added smb.conf to /usr/local/.files
so that it should be saved when I execute "flashfs save && flashfs commit && flashfs enable && reboot" which I've run after making the desired changes to smb.conf. Executing "flashfs load" at the command line after reboot effectively loads my customized smb.conf and I'm fine - but why isn't it loading automatically on reboot? Do I need to add the load to one of the startup scripts? I thought it should automatically run...

THANKS

[al37919]

if you enable samba in the web-interface then /etc/smb.conf is automatically generated based on the settings in it every time you start router. So if you wish to customize smb.conf --- disable samba in web-interface and run from post-boot something like:

/usr/sbin/smbd -D
/usr/sbin/nmbd -D 

[cMcd01]

I didn't realize that about smb.conf - makes sense based on what I'm seeing. I'll give your recommendation a try. THANKS

[adrianio]

I have asus wl500gpv2 and installed the latest Oleg WL500gpv2-1.9.2.7-10.7.trx.

Sometimes when I give command "iptables -t nat -L" or "iptables -L" the listing freezes at half. I have to stop it.
I followed Wengi tutorial and I enabled syslogd to log on fixed hdd, but the log does not show anything. I stopped dropbear in post-mount and start sshd (openssh) from /opt, but the behavior is the same.
It seems that ssh console take commands and react slowly. I work with all services stopped: samba, ftp, upnp, and most of the time I have 50% free RAM!!!
By the way, upnp service don't work. Does anybody knows whatever to make it work?
Or should be better to my router model to revert to previously OLEG firmware?(WL500gpv2-1.9.2.7-10.5.trx or so)

[kaizen]

I have asus wl500gpv2 and installed the latest Oleg WL500gpv2-1.9.2.7-10.7.trx.

Where have you found this firmware?
Last "original" oleg is WL500gp-1.9.2.7-10.trx

Try this.

[al37919]

adrianio
try -n switch of iptables

kaizen
WL500gpv2-1.9.2.7-10.7.trx is a bugfix pre-release. It has pretty minor changes against 10, but incorporates later wifi driver which performs better for wl500gPv2

[TheCrow]

what meens this error and how can i fix`it ??

Mar 12 20:37:48 kernel: ip_conntrack: table full, dropping packet.
Mar 12 20:37:49 kernel: ip_conntrack: table full, dropping packet.
Mar 12 20:37:49 kernel: ip_conntrack: table full, dropping packet.
Mar 12 20:37:49 kernel: ip_conntrack: table full, dropping packet.
Mar 12 20:37:49 kernel: ip_conntrack: table full, dropping packet.
Mar 12 20:37:49 kernel: ip_conntrack: table full, dropping packet.
Mar 12 20:37:49 kernel: ip_conntrack: table full, dropping packet.
Mar 12 20:37:49 kernel: ip_conntrack: table full, dropping packet.
Mar 12 20:37:49 kernel: ip_conntrack: table full, dropping packet.
Mar 12 20:37:49 kernel: ip_conntrack: table full, dropping packet.
Mar 12 20:37:53 kernel: NET: 85 messages suppressed.
Mar 12 20:37:53 kernel: ip_conntrack: table full, dropping packet.
Mar 12 20:37:58 kernel: NET: 91 messages suppressed.
Mar 12 20:37:58 kernel: ip_conntrack: table full, dropping packet.
Mar 12 20:38:03 kernel: NET: 141 messages suppressed.
Mar 12 20:38:03 kernel: ip_conntrack: table full, dropping packet.
Mar 12 20:38:08 kernel: NET: 134 messages suppressed.
Mar 12 20:38:08 kernel: ip_conntrack: table full, dropping packet.
Mar 12 20:38:13 kernel: NET: 170 messages suppressed.
Mar 12 20:38:13 kernel: ip_conntrack: table full, dropping packet.
Mar 12 20:38:18 kernel: NET: 174 messages suppressed.
Mar 12 20:38:18 kernel: ip_conntrack: table full, dropping packet.
Mar 12 20:38:23 kernel: NET: 157 messages suppressed.
Mar 12 20:38:23 kernel: ip_conntrack: table full, dropping packet.
Mar 12 20:38:28 kernel: NET: 189 messages suppressed.
Mar 12 20:38:28 kernel: ip_conntrack: table full, dropping packet.
Mar 12 20:38:33 kernel: NET: 180 messages suppressed.
Mar 12 20:38:33 kernel: ip_conntrack: table full, dropping packet.
Mar 12 20:38:38 kernel: NET: 173 messages suppressed.
Mar 12 20:38:38 kernel: ip_conntrack: table full, dropping packet.
Mar 12 20:38:43 kernel: NET: 226 messages suppressed.
Mar 12 20:38:43 kernel: ip_conntrack: table full, dropping packet.
Mar 12 20:38:48 kernel: NET: 158 messages suppressed.
Mar 12 20:38:48 kernel: ip_conntrack: table full, dropping packet.
Mar 12 20:38:53 kernel: NET: 190 messages suppressed.
Mar 12 20:38:53 kernel: ip_conntrack: table full, dropping packet.
Mar 12 20:38:58 kernel: NET: 185 messages suppressed.
Mar 12 20:38:58 kernel: ip_conntrack: table full, dropping packet.
Mar 12 20:39:03 kernel: NET: 178 messages suppressed.
Mar 12 20:39:03 kernel: ip_conntrack: table full, dropping packet.
Mar 12 20:39:08 kernel: NET: 212 messages suppressed.
Mar 12 20:39:08 kernel: ip_conntrack: table full, dropping packet.
Mar 12 20:55:43 ntp client: Synchronizing time with time.nist.gov ...
Mar 12 21:46:29 kernel: NET: 48 messages suppressed.
Mar 12 21:46:29 kernel: ip_conntrack: table full, dropping packet.
Mar 12 21:46:29 kernel: ip_conntrack: table full, dropping packet.
Mar 12 21:46:29 kernel: ip_conntrack: table full, dropping packet.
Mar 12 21:46:29 kernel: ip_conntrack: table full, dropping packet.
Mar 12 21:46:29 kernel: ip_conntrack: table full, dropping packet.
Mar 12 21:46:29 kernel: ip_conntrack: table full, dropping packet.
Mar 12 21:46:29 kernel: ip_conntrack: table full, dropping packet.
Mar 12 21:46:29 kernel: ip_conntrack: table full, dropping packet.
Mar 12 21:46:29 kernel: ip_conntrack: table full, dropping packet.
Mar 12 21:46:29 kernel: ip_conntrack: table full, dropping packet.
Mar 12 21:46:34 kernel: NET: 81 messages suppressed.
Mar 12 21:46:34 kernel: ip_conntrack: table full, dropping packet.
Mar 12 21:46:39 kernel: NET: 133 messages suppressed.
Mar 12 21:46:39 kernel: ip_conntrack: table full, dropping packet.
Mar 12 21:46:44 kernel: NET: 162 messages suppressed.
Mar 12 21:46:44 kernel: ip_conntrack: table full, dropping packet.
Mar 12 21:46:49 kernel: NET: 174 messages suppressed.
Mar 12 21:46:49 kernel: ip_conntrack: table full, dropping packet.
Mar 12 21:46:54 kernel: NET: 200 messages suppressed.
Mar 12 21:46:54 kernel: ip_conntrack: table full, dropping packet.
Mar 12 21:46:59 kernel: NET: 233 messages suppressed.
Mar 12 21:46:59 kernel: ip_conntrack: table full, dropping packet.
Mar 12 21:47:04 kernel: NET: 233 messages suppressed.
Mar 12 21:47:04 kernel: ip_conntrack: table full, dropping packet.