9/20/2019 Install Openwrt On X86 Pc
This guide should be considered as a simple walk-through for using APU3 platform in some generic use-cases. I’m trying to explain how to work with the device and use it in a generic manner.
There is a part about the coreboot firmware, which could be used as a reference of how to start customizing it for own purposes. Configuring the hardware At first, let’s figure out some basic requirements for our new device:. It will be wireless router with some advenced functionality provided by OpenWRT. In order for it to be wireless, we need to add WiFi network adapters.
I want it to be dual-band simultaneous connection, so we will need 2 separate WiFi adapters. Operating system will be placed on?SD card. There will be an additional storage in the form of mSata disk. APU3 has 3 mPcie slots. Unfortunately it supports PCI express only on slot mPCIe 1, so WiFi card has to use it. For the second WiFi card, we could use mPCIe 2 slot, but we would need USB only type, which are rare. Instead I’m using some cheap Ralink RT5370 based USB dongle WiFi adapter.
MPCIe 3 slot will be used for mSata drive. For the OS drive, I’ll use some generic?SD card with adapter. MPCIe 2 slot could be used in future for GSM modem or some other kind of USB device in the form of mPcie card.
Getting the sources We will use latest stable version which is Chaos Calmer, in order to be compatible with upstream packages. Thanks to that we can just use the opkg to download new version of packages from the main OpenWRT’s repositories. The sources we need are located on. Let’s clone the needed version. Our target is APU system, which has AMD x8664 CPU.
So let’s use generic settings:. Target System x86. Subtarget x8664 and then Exit and make. After compilation our image is in bin/x86 dir. We need a SD card to burn the image and boot the system on the target platform.
![]()
On my host system, card is present under the device file /dev/sde. Carefully check the device the card is present on your system. This is potentially dangerous operation and can lead to lost data, when used wrong device! In the config we need to select those drivers:. Device Drivers MMC/SD/SDIO card support:.
MMC block device driver. Secure Digital Host Controller Interface support. SDHCI support on PCI bus Now the system should boot without problems.
Network problems After booting the systems it appears we don’t have any connectivity (ethernet nor wifi). When trying ifconfig -a we can see only the lo interface. Let’s install some additional packages, which should help us investigate. Base system busybox Customize busybox options Linux System Utilities:.
lspci. lsusb. Base system wireless-tools When the image is built and system is booted on target we can use lspci -k to check which devices have kernel modules assigned to them and which don’t. This lspci flavour is pretty poor, compared to usual one, supplied with main Linux distributions, but should be enough for our uses. Among others, we can find these devices (VID:DID), which look interesting.
First let’s mark the driver for our wireless card:. Kernel modules Wireless Drivers:. kmod-ath10k And also some packages we’ll need to set up the access-point:.
Network:. hostapd. wpasupplicant Unfortunately, during my build I got and error. After rerunning make V=s it appears that kernel hasn’t got the full configuration it wants.
I managed get by this problem checking this option in make kernelmenuconfig:. Power management and ACPI options:. ACPI (Advanced Configuration and Power Interface) Support After successful build and boot. So I’ve got the network.
Basic configuration It’s good idea to set the default password using passwd utility. Thanks to this we can login using the SSH connection. If you want to add your public key to authorizedkeys file, which is usually placed under.ssh dir in user’s home dir, it has to be placed in /etc/dropbear/ dir or it will be ignored.
Make sure that permissions to the file are also set right ( 600). We can also set some other IP address for the ethernet connection, if our host computer occupies the one or is using other mask. In my case, my host computer has static address, which happens to be the same as the default one in OpenWRT. Here’s short example how to change it.
Unfortunately OpenWRT/LEDE doesn't have a traditional installer. They provide a disk image that you put on to your x86 machine's bootdisk (SATA drive, etc) using dd. After that you have to install drivers for your NICs/USB (this is the hard part). So getting a working system isn't exactly easy and there isn't a one size fits all tutorial (it really depends on how much of your hardware works out of the box). This has the rough guide of what you are trying to accomplish. I would start there and ask questions when you get stumped. I gave up on OpenWRT- I just started doing my own thing based on Debian and hostAPD - which for all intents and purposes was going pretty well.
Currently evaluating the best way to bridge the wifi AP clients to the LAN clients. While the idea of a super barebones OS on a dragracer machine is the ideal, I traded simplicity for some unnecessary overhead. Maybe simplicity is the wrong word, but it was easier once I gave up trying to use OpenWRT/LEDE.I say that as a fan of OpenWRT and DD-WRT and third-party router firmware. It is all good stuff. Just was difficult to make the pre-bundled system happen on beefy hardware.
( used 'dd' to copy the image to a boot drive 'sdb' (which became the only disk in the router machine.). And gparted to resize the partition. Then it booted. Had to load the ath9k and ath10k opkg drivers if I remember right. Also the 4x Gigabit ethernet Intel opkg driver. From there the GUI wasn't really meant for what I was doing with multiple AP MIMO devices (USB 802.11g, PCIE.
The little network routers you can purchase in the store are ok, but they are not upgradeable. With things changing so fast, that seems like a boon only for the router manufacturers. Also firmware upgrades quickly cease. Having a router on a pc makes more sense not only for the ability to upgrade the hardware, but you can add so many more features software wise. You are not limited by the memory or space of the boxed routers. Nothing wrong with the boxed routers for a turnkey setup.
If you are like me, you want more. That is why I also use Openwrt. This is a great project to put an old pc back to work. Openwrt is a cousin so to speak of DD-WRT that is installed on many brand name routers to increase their capabilities. Openwrt will also allow a pc to act as an expensive router without the big price tag.
Of course, you could easy use some of the router distros such as ipcop and many others (see ). Openwrt is so much more upgradeable and expandable. Did this with the original image on a pentium2 and it worked well.
If you want the gui, you may need to install the web add-on. Installing OpenWrt x86 on a PC. ( Try this at your own risk!!!) Requirements: An X86 compatible pc (i386) or greater with at least 16MB of RAM, 2 network cards, and a hard drive. With newer versions of openwrt require higher hardware requirements. Check openwrt.org for more details.
OpenWrt binary file, for x86. Old: Newer: (need to gunzip first) to openwrt-x86-generic-combined-ext4.img ($ gunzip openwrt-x86-generic-combined-ext4.img.gz) Installation: For M$ Windows, please also get physdiskwrite. For Linux just use dd. Grab the latest binary code from OpenWrt download site.
Dd if=openwrt-x86-2.6-ext2.image of=/dev/hda (where hda and image name must be changed) or dd if=openwrt-x86-2.6-ext2.image of=/dev/sda (where hda and image name must be changed). Edit the network configuration '/etc/config/network' (this assumes a static IPv4 address): config interface loopback option ifname lo option proto static option ipaddr 127.0.0.1 option netmask 255.0.0.0 config interface lan option ifname eth0 option type bridge option proto static option ipaddr 192.168.0.126 option netmask 255.255.255.0 option gateway 192.168.0.254 option dns 192.168.0.16 192.168.0.2 Load the updated lan network configuration # ifup lan Edit /etc/ipkg.conf. Add the last line (bold) (use the version for your openwrt.
Latest version is 8.x) src release src packages dest root / dest ram /tmp src X-WRT (use the version for your openwrt. Latest version is 8.x) Update and install webif root@OpenWrt:# ipkg update root@OpenWrt:# ipkg install webif Update. # ipkg update Downloading Updated list of available packages in /usr/lib/ipkg/lists/release Downloading Updated list of available packages in /usr/lib/ipkg/lists/packages Downloading Updated list of available packages in /usr/lib/ipkg/lists/X-WRT Done. Install webif # ipkg install webif Installing webif (0.3-12) to root.
Downloading Installing haserl (0.8.0-2) to root. Downloading Configuring haserl Configuring webif Linux OpenWrt 2.6.22 #2 Sun Sep 30 21:02:32 CEST 2007 i586 unknown Committing new firmware id. Device: PC Engines WRAP Committing new device id. Webif^2 installation appears OK.
Welcome to X-Wrt! You may need to do a hard REFRESH to clear old CSS style from your browser. Reinitializing httpd. From: After creating my OpenWRT live USB , I wanted to use it on an older PC but ran into a problem: its BIOS does not support booting from USB.
Openwrt Downloads
I had two choices. One was to boot up Linux from CD then switching to USB drive. The other was to get a CD bootloader that can read USB drives. Not wanting to do more work, I went searching and found. It is very impress. Compact but full of features. It handles multiboot.
It works with many bootloaders. It can boot OS on USB or CD without BIOS support. It even has a great GUI reminiscent of video arcade games. And it’s free. Do take a look.
But if you just want to get down to business, I have a ready-to-use CD image (plpbthiddenusb.iso on my ). Just insert the CD and plug in your USB drive.
Plop Boot Manager will do the rest. Pulled out of the closet the pc I was using as a router and found that a few things have changed. I just went ahead and installed the latest openwrt kamikaze image on the system. What does the system have? Intel PII 266 mhz with 192 meg ram.
The openwrt hard drive is only 2 gig. Thinking about using another case. The system actually has two drives. One with a minimal Debian linux to be able to get the latest image or dd (or install) to the openwrt drive. The Debian linux drive is usally left unconnected. There have been a few changes and a few quirks.
Oct 7, 2017 - Nonton film Korea Love 911 (2012) subtitle Indonesia. Download video kualitas SD 360p 480p dan HD 720p kualitas gambar jernih dan tajam. Nonton Film Love 911 (2012) Subtitle Indonesia - Streaming Movie, Nonton Bioskop Online Gratis Full Movie, Download Film Terbaru Sub Indo. Nonton Film Love () BluRay p & p mp4 English Hindi Sub Watch Online Indo Free Streaming Full HD Korean Movie Download LkTv21 Indoxxi. Download drama. Browser Tidak. Nonton Love 911 (2012) Film Subtitle Indonesia Streaming Movie Download Gratis Online. Love 911 (2012). Country, South Korea. Download film korea love 911 sub indo.
When I cranked up the system it did not seem to see the wan (internet). So I had to do a couple of things. # Copyright (C) 2006 OpenWrt.org config interface loopback option ifname lo option proto static option ipaddr 127.0.0.1 option netmask 255.0.0.0 config interface lan option ifname eth0 option type bridge option proto static option ipaddr 192.168.6.1 option netmask 255.255.255.0 config interface wan option ifname eth1 option proto dhcp First I had to add the wan interface to the /etc/config/network file. Those are the last three lines.
Then I had to bring up the interface with: (ifup wan) # ifup eth1 I also changed the default ipaddress of the lan from 192.168.1.1 to 192.168.6.1 so as to not interfere with my local network. Local network 192.168.1.x) router private network (192.168.6.x) Then there were changes to some of the commands. You used to use ipkg, so now to update the system you would use (opkg replaced ipkg): # opkg update You can ssh root@openwrtbox and do everything remotey from the command line. So far so good. Then I tried to access a web interface remotely. Diablo 2 lod lvl 99 character download. Did not work, So I had to install a web interface to the system. There are actually three to choose from.
I chose Luci or the first on the list suggested in the install notes. To do that you have to add the repository (where to get the files from). So you add that repository to the /etc/opkg.conf file. In this case it was just one line or the last line in the file: src/gz snapshots dest root / dest ram /tmp listsdir ext /var/opkg-lists option overlayroot /jffs src luci Now you let the system know the file has changed, so again you do: # opkg update The you need to install the web interface. There are quite a few modules you can install, but I just did the basic interface. You can add more later.
# opkg install luci-web At this point it would not hurt to do a reboot. You should then be able to see the router's web page.
The little network routers you can purchase in the store are ok, but they are not upgradeable. With things changing so fast, that seems like a boon only for the router manufacturers. Also firmware upgrades quickly cease. Having a router on a pc makes more sense not only for the ability to upgrade the hardware, but you can add so many more features software wise. You are not limited by the memory or space of the boxed routers. Nothing wrong with the boxed routers for a turnkey setup.
If you are like me, you want more. That is why I also use Openwrt. This is a great project to put an old pc back to work. Openwrt is a cousin so to speak of DD-WRT that is installed on many brand name routers to increase their capabilities. Openwrt will also allow a pc to act as an expensive router without the big price tag. Of course, you could easy use some of the router distros such as ipcop and many others (see ).
Openwrt is so much more upgradeable and expandable. Did this with the original image on a pentium2 and it worked well. If you want the gui, you may need to install the web add-on.
Installing OpenWrt x86 on a PC. ( Try this at your own risk!!!) Requirements: An X86 compatible pc (i386) or greater with at least 16MB of RAM, 2 network cards, and a hard drive. With newer versions of openwrt require higher hardware requirements. Check openwrt.org for more details.
OpenWrt binary file, for x86. Old: Newer: (need to gunzip first) to openwrt-x86-generic-combined-ext4.img ($ gunzip openwrt-x86-generic-combined-ext4.img.gz) Installation: For M$ Windows, please also get physdiskwrite.
For Linux just use dd. Grab the latest binary code from OpenWrt download site. Dd if=openwrt-x86-2.6-ext2.image of=/dev/hda (where hda and image name must be changed) or dd if=openwrt-x86-2.6-ext2.image of=/dev/sda (where hda and image name must be changed). Edit the network configuration '/etc/config/network' (this assumes a static IPv4 address): config interface loopback option ifname lo option proto static option ipaddr 127.0.0.1 option netmask 255.0.0.0 config interface lan option ifname eth0 option type bridge option proto static option ipaddr 192.168.0.126 option netmask 255.255.255.0 option gateway 192.168.0.254 option dns 192.168.0.16 192.168.0.2 Load the updated lan network configuration # ifup lan Edit /etc/ipkg.conf. Add the last line (bold) (use the version for your openwrt. Latest version is 8.x) src release src packages dest root / dest ram /tmp src X-WRT (use the version for your openwrt.
Latest version is 8.x) Update and install webif root@OpenWrt:# ipkg update root@OpenWrt:# ipkg install webif Update. # ipkg update Downloading Updated list of available packages in /usr/lib/ipkg/lists/release Downloading Updated list of available packages in /usr/lib/ipkg/lists/packages Downloading Updated list of available packages in /usr/lib/ipkg/lists/X-WRT Done. Install webif # ipkg install webif Installing webif (0.3-12) to root. Downloading Installing haserl (0.8.0-2) to root. Downloading Configuring haserl Configuring webif Linux OpenWrt 2.6.22 #2 Sun Sep 30 21:02:32 CEST 2007 i586 unknown Committing new firmware id. Download crosshair overlay rust.
![]()
Device: PC Engines WRAP Committing new device id. Webif^2 installation appears OK.
Welcome to X-Wrt! You may need to do a hard REFRESH to clear old CSS style from your browser. Reinitializing httpd. From: After creating my OpenWRT live USB , I wanted to use it on an older PC but ran into a problem: its BIOS does not support booting from USB. I had two choices. One was to boot up Linux from CD then switching to USB drive.
The other was to get a CD bootloader that can read USB drives. Not wanting to do more work, I went searching and found. It is very impress. Compact but full of features. It handles multiboot. It works with many bootloaders.
It can boot OS on USB or CD without BIOS support. It even has a great GUI reminiscent of video arcade games. And it’s free. Do take a look.
![]() Openwrt On Pc
But if you just want to get down to business, I have a ready-to-use CD image (plpbthiddenusb.iso on my ). Just insert the CD and plug in your USB drive. Plop Boot Manager will do the rest. Pulled out of the closet the pc I was using as a router and found that a few things have changed. I just went ahead and installed the latest openwrt kamikaze image on the system. What does the system have?
Intel PII 266 mhz with 192 meg ram. The openwrt hard drive is only 2 gig. Thinking about using another case.
The system actually has two drives. One with a minimal Debian linux to be able to get the latest image or dd (or install) to the openwrt drive. The Debian linux drive is usally left unconnected. There have been a few changes and a few quirks. When I cranked up the system it did not seem to see the wan (internet). So I had to do a couple of things.
# Copyright (C) 2006 OpenWrt.org config interface loopback option ifname lo option proto static option ipaddr 127.0.0.1 option netmask 255.0.0.0 config interface lan option ifname eth0 option type bridge option proto static option ipaddr 192.168.6.1 option netmask 255.255.255.0 config interface wan option ifname eth1 option proto dhcp First I had to add the wan interface to the /etc/config/network file. Those are the last three lines. Then I had to bring up the interface with: (ifup wan) # ifup eth1 I also changed the default ipaddress of the lan from 192.168.1.1 to 192.168.6.1 so as to not interfere with my local network. Local network 192.168.1.x) router private network (192.168.6.x) Then there were changes to some of the commands. You used to use ipkg, so now to update the system you would use (opkg replaced ipkg): # opkg update You can ssh root@openwrtbox and do everything remotey from the command line.
Openwrt X86 Iso
So far so good. Then I tried to access a web interface remotely. Did not work, So I had to install a web interface to the system. There are actually three to choose from. I chose Luci or the first on the list suggested in the install notes. To do that you have to add the repository (where to get the files from).
So you add that repository to the /etc/opkg.conf file. In this case it was just one line or the last line in the file: src/gz snapshots dest root / dest ram /tmp listsdir ext /var/opkg-lists option overlayroot /jffs src luci Now you let the system know the file has changed, so again you do: # opkg update The you need to install the web interface. There are quite a few modules you can install, but I just did the basic interface. You can add more later. # opkg install luci-web At this point it would not hurt to do a reboot.
You should then be able to see the router's web page.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |