On Thu, 22 Oct 2015 19:18:34 +0200 "Wyzbox" <[email protected]> wrote:
> On Thu, 22 Oct 2015 08:34:12 +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. > > Do you connect your WRT54G to another computer using the WAN port or > using a LAN port (1...4)? > At the moment, my machine is connected to my OpenWrt router via ethernet interface, using a cable connected to a LAN port. The OpenWrt router is connected, as a client, to a main router. Me --> (wire) --> OpenWrt --> (wireless) --> router --> (wire) --> WWW Ever since I have obtained this WRT54G router, I have never used nor even touched the WAN port. Is it possible to connect with the router via its WAN port? > If any LAN port or WIFI link (default on 192.168.0.x) is established > between WRT54G and another router with DHCP enabled, OpenWrt would > surely disable DHCP server functions, allowing all connected devices > to change all IP settings coming from the other router you have > (192.168.1.x). If any computer is connected with an IP different from > 192.168.0.x, you'll not be able to connect to the WRT54G web > configuration service. If the main network is based on 192.168.1.x > subnet, you should modify your WRT54G to use a static IP belonging to > 192.168.1.x network. > I still can't. I must have done something wrong. It would be nice if I had a log or a configuration file of what has been done. > > 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. > > This could be a good chance. > Apparently, allegedly, OpenWrt does not even interested in me entering into it, not even when main router is out of range. I think I will rename a "smartphone" device ESSID, hope OpenWrt to connect to it, and try again; this is, probably, the last solution before resting settings. > > Would it be safe to press on the physical reset button on the > > OpenWrt router? > > Generally the reset button brings the router into a factory default > configuration with a static IP setting 192.168.0.x, DHCP on, wifi off. > Any reset would not help to connect it while using a different IP > subnet. > As long as anything is back to where I was starting, I will be glad. > > > 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"? > > What do you exactly mean with "wireless repeater"? > Wireless interface in Access Point/infrastructure mode? (=lan bridged > to wireless, wireless available for wireless clients) > This is how I use OpenWrt, at the moment. > Wireless interface in wireless client mode with bridged lan? > (=wireless connected to another network, lan bridged to wireless) > I did not understand. > Wireless interface in wireless client mode with routed lan? (=wireless > connected to another network, lan routed to wireless) I did not understand. > Wireless interface in repeater mode? (=wireless packets are repeated > from the main wireless network to a far away wireless client) > I think the last one described is what I was referring to. I have a router on 4th floor, and I want to extend the range to floor -1; so I intend to use the OpenWrt router and, position it on 1st or 2nd floor. I ask for other terms for "wireless repeater" so I will have more keywords to use when I search for a solution. > > > 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/openwr > > > t-15.05-brcm47xx-legacy-linksys-wrt54g-squashfs.bin From OpenWrt > > > to OpenWrt > > > http://downloads.openwrt.org/chaos_calmer/15.05/brcm47xx/legacy/openwr > > > t-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? > > Any OpenWrt edition/release may review and modify the classified > families or groups. > By the time, new products and new chipsets are released, so any older > group could be changed, grouped or split into more folders. > You probably found the right firmware for "Broadcom 2.4" on Kamikaze > 8.09, that in next OpenWrt releases was split into different several > Broadcom 47xx, 53xx, 63xx, etc etc, new families. > Thank you for this elaboration. _______________________________________________ openwrt-users mailing list [email protected] https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-users
