And as Boochi99 says, the WAN is disabled by default not sure why. I took out the PcieX one and rebooted. Hence the Second NIC card is not showing up when running 'ifconfig'. Just like any system you build yourself, you have to verify the drivers are available and will work for the additional NIC.
Just lucky. Posted: Wed Aug 01, Post subject:. Have you thought about running dd-wrt under a hypervisor? Knowing the chipset on the NIC will help if it is not recognized as there are community work arounds to get them going. Posted: Thu Aug 02, Post subject:. Posted: Mon Sep 17, Post subject: At it again. Hi I have been away from this project for awhile. I purchased a new Intel Lan Card and installed it into my unit.
I am trying to get back up to where I was previously. I am not sure just what this means. I seem unable to copy anything to the OS as it is mounted 'read only'. There are a very limited bunch of functions available in this OS to do any poking around, it seems. Any help would be appreciated Posted: Thu Oct 11, Post subject:. Use this one. And boot from it. Now remember this you can't boot this with a high performance video card it will green screen and reboot.
It likes the onboard video system or low end video card in mb or less. There is no need to install drivers if the cards and hardware is supported it will work. Then once you see the DD-wrt Screen boot up with a prompt. Connect a working computer by a 5 port or 8 port switch or a router with its DHCP turned off so it functions like a switch.
Then try one of the lan adapters and access its Webgui page at It will let you access its setup page if you want to use it like a router enable WAN on the setup page and then go to save and apply and reboot your modem while rebooting the DD-wrt system. Once everything is completed booting up you should have working internet. Posted: Fri Jan 18, Post subject:. You do not put a router between your modem and DD-wrt system. I have attached a picture on how its supposed to be setup.
If you need more help just leave a reply. Hi flood I just received notice of your post. There are multiple targets for x86 OpenWrt, some are targeted at old or specific hardware and their build defaults may not be suit modern x86 hardware:. Now you will see different files offered, the following two are disk images you can download and use:. All images support basic video output screen text terminal , so you can connect a screen to the device's video ports and see it boot up.
The installation consists of writing a raw disk image on the drive which will boot OpenWrt system. Installation procedure differs depending from what OS you are using to write the raw disk image from, mostly because of different tools you have to use.
Then you will need to open the raw image file with a program that can write it on the drive you want to install OpenWrt on. A good free and opensource archiver program you can use is 7zip , or Keka. A good free and opensource raw disk image writer program you can use is Win32 Disk Imager , or Etcher.
Extract the image file from the archive. Then write the image file you extracted to the drive you want to install OpenWrt in. Identify the disk you want to write the image on, e. Note you have to gain administrative privileges with sudo and write to the drive sda, sdb , not to a partition sda1, sdb3. But if you cannot remove the storage from the device or do not have an adapter to connect them to the PC , you can write OpenWrt on a USB drive or another removable storage device , then you can then insert it in a USB port or slot.
When booting select the drive where you installed OpenWrt. Be aware that you will also see the USB drive or the storage device you have temporarily installed OpenWrt on.
After you have identified the onboard storage you want to install OpenWrt in, you can follow the Linux install instructions above. Then power off the system, unplug the removable storage device you used to install OpenWrt, and power on again. Now it should boot from the internal storage. Be sure to resize the image before resizing partitions when installing in a VM. Be sure to resize partitions before resizing filesystem.
When OpenWrt is installed on a x86 machine using generic-ext4-combined. Any remaining space will be unallocated and the drive will have a normal MBR partition table. Any partition management tool that supports MBR and ext4 can be used to create extra partitions on the drive, in example fdisk, GParted. But attention must be taken for future upgrades. If extra partitions are added, you cannot use -combined.
On most embedded devices, upgrading OpenWrt is much simpler than the first installation and consists of simply executing sysupgrade. On x86 machines, on the other hand, upgrading is more complex than the first installation. One of the advantages of x86 is the easiness to backup and restore drives, using any normal backup tool that supports MBR and ext4. Always make a proper backup of the whole drive and test its restore before any upgrade procedure.
It's also recommended to restore the backup on a virtual machine and execute the upgrade on it prior to upgrading the real router, to learn and experiment the procedures without risking the real thing. If you had used a ext4-combined.
The 2 last options require more steps to execute, but have the advantage of leaving MBR partition intact, therefore keeping boot and rootfs partitions sizes in case of having resized them and any extra partitions. At this time they are the most recommended methods of upgrading. At the moment, it's not built a separated image file with boot partition, as it's available for rootfs.
To be able to upgrade boot partition without overriding the whole drive, we must extract it from ext4-combined. We will end up with the partition image openwrt Note we're here writing on the partition sdd1, not on the drive sdd. As said above, there are 2 options for upgrading rootfs partition, when we are using the ext4 file system and not squashfs: writing ext4-rootfs.
Writing ext4-rootfs. When using dd , it will preserve partition's actual size, it won't revert its size to image's. For uncompressing rootfs. It may be tempting to not delete config files, but the risk isn't worth it, because some file may conflict and not be properly upgraded. It's safer to backup config files as we should also backup whole drive before upgrading and copy them back after upgrading. I suggest going further and having a Subversion repository on another computer where all config files are saved and their changes are tracked, and use rsync to sync between the repository working copy and production files on the router.
Anyone can compile OpenWrt from source, but it's a complex procedure with many options which require some experience, specially for using it on a production router. Different from compiling, we can build our own custom image using the Image Builder.
0コメント