On Thu, 22 Oct 2015 03:14:56 +0200
"Wyzbox" <[email protected]> wrote:

> On Wed, 21 Oct 2015 22:50:43 +0200
> "Genghis Khan" wrote:
> >So far I use my newly born router as a wireless adapter.  
> >It seems to work well, except not being able to access to OpenWrt
> >from the IP address I set up for it (IP is 192.168.0.1, different
> >than 192.168.1.1), even though I was able to, earlier this session.  
> 
> This is something very strange, maybe you could try to reboot the
> router and refresh network settings/reboot your PC. Anyway your PC
> should stay in the same subnet in use by the router (192.168.0.x or
> 192.168.1.x)
> 

I think it would not help.

I have unplugged the power supplier, and  it did not work.

I have connected the OpenWrt router to another computer machine; the
other computer machine has an IP of 192.168.1.x allocated and is
connected to the internet, and I am still failing to access to
192.168.0.1.

I think I will turn off the main router or will go to a place where it
is out of range, and then I will try again.

Would it be safe to press on the physical reset button on the OpenWrt
router?

> >In general, OpenWrt 8.09 seems to be working as expected.
> >The thing I would like to do is to use that router as a wireless
> >repeater (bridge).  
> 
> That's surely working, at least try to avoid double DHCP and/or DNS
> between the wireless repeater/router and the main router/appliance
> where you get connected to. Some OpenWrt releases will automatically
> disable DHCP if another DHCP server is met in the network (but
> obviously your PC may loose the OpenWrt subnet and move to the main
> router/gateway network settings).
> 

Most pages I read, guide users with DD-WRT; do you know of a document
that guides how to set a wireless repeater with OpenWrt?

Are there others names that mean "wireless repeater"?

> 
> >> Any following update, when OpenWrt is already installed, will have
> >> to be executed with slightly different procedure.  
> > 
> >I did not expect that.  I thought that once OpenWrt is successfully
> >installed, user will be able to upgrade OpenWrt by web interface,
> >too.  
> 
> Yes, you can upgrade OpenWrt from the web interface, but you cannot
> use pre-built images which are made for matching the mandatory
> requirements of the original firmware. You need a more generic
> firmware image, which is generally available in the same download
> folder, for example: From original firmware to OpenWrt
> http://downloads.openwrt.org/chaos_calmer/15.05/brcm47xx/legacy/openwrt-15.05-brcm47xx-legacy-linksys-wrt54g-squashfs.bin
> From OpenWrt to OpenWrt
> http://downloads.openwrt.org/chaos_calmer/15.05/brcm47xx/legacy/openwrt-15.05-brcm47xx-legacy-squashfs.trx
> 

This is good to know.

Looking at these links, I wonder why the firmware image I downloaded
from /kamikaze/8.09/brcm-2.4/ (not /kamikaze/8.09/brcm47xx/) fits to my
router.

What command procedure should I execute in order to see as much
detailed specifications of my router?

> 
> >> Please consider this as a preliminary habit: put your device in a 
> >> factory default status, in order to avoid any unpredictable issue
> >> and reboot it before any flash update or upgrade.  
> > 
> >Does factory default status mean to downgrade to stock firmware?  
> 
> No, just removing all configured settings to avoid any unpredictable
> issue. This is something generally preferred when moving from stock
> firmware to OpenWrt, due to some NVRAM saved data. Sometimes a NVRAM
> clear procedure is available.
> 

Good.

> 
> >> As per Benjamin H. and Aaron Z comments, the latest firmware
> >> images could slow down the device because of the "lua web
> >> interface". I would appreciate if anybody with experience on
> >> WRT54G and WRT54GL could possibly offer some mode details on the
> >> noted slow down of the router with any of the latest releases.
> >> From my personal experience, I'm currently testing a couple of
> >> WRT54GL with CC 15.05 (with LUCI enabled) and I am not able to see
> >> any evidence in normal operations when compared to TL-WDR3600 with
> >> the same release.  
> > 
> >I guess it occurs at the moments you use LUCI.  
> 
> Still checking my router to see some slow issues.
> 
> >> Please consider that I speeded up my WRT54GL from 200MHz to 250MHz
> >> via software config, modded RAM memory has been increased from
> >> 16MB to 64MB and FLASH memory increased from 4MB to 8MB.  
> > 
> >How did you do it?  
> 
> You can find in the OpenWrt forum some very good advices and gurus,
> in short I just applied their hits. Please consider to read carefully
> some of those posts.
> 
> SPEED/CLK MOD: 
> nvram set clkfreq=250
> nvram commit
> 
> RAM MOD: removed 16MB ram chip and replaced with a 64MB ram chip
> (from an old notebook ram module). nvram set sdram_init=0x0113 
> nvram set sdram_ncdl=0x000000
> nvram commit
> 
> FLASH MOD: saved CFE (backup bootloader data), removed 4MB (32Mbit)
> flash chip and replaced with a 8MB (64Mbit) flash chip (from an old
> broken Cisco 82x router), reflashed the CFE (restore bootloader data)
> 
> In the end, all experimental mods are just for testing purposes, good
> soldering skills are required.
> 

Thank you for the explanation!
_______________________________________________
openwrt-users mailing list
[email protected]
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-users

Reply via email to