Dir-601 Installation Software Mac Download
In that location are (at to the lowest degree) three revisions of this router: A1, B1 and B2. Rev.A1 has been rebranded as FR-54RTR. The FR-54RTR is a close plenty friction match that it tin can be flashed with the A1's firmware from D-Link: ftp://ftp.dlink.com/Gateway/dir600/Firmware/dir600_firmware_101NA.nix
There are DIR-600N and DIR-600NW, both have reduced hardware feature (although non reduced price). DIR-600NW for example have reduced to 8MB memory and 2MB flash. DIR-600NB is suspected to have reduced features likewise. Any third party firmware are unlikely able to run on these reduced hardwares. They seem only sold in People's republic of china.
The DIR-601 is basically a slightly newer DIR-600 with Atheros AR7240 SoC version 2, and a non-detachable antenna.
Flash via D-Link Web Interface
These D-Link routers have a special (and very nice) web interface specifically for flashing firmware. This is the simplest way to upgrade this router to OpenWrt. Information technology too provides a fail-safe method of reflashing the firmware in case you "brick" your router and can no longer access it using other methods.
-
Manually set your PC'southward IP address to any accost between 192.168.0.2 and 192.168.0.253.
Don't apply 192.168.0.1 (The router IP address will default to 192.168.0.1 when reset as instructed below.) -
Concur the reset button while powering up the router and continue to concur until the power lite begins blinking. Repeat if necessary.
-
Open Net Explorer half-dozen, and get to
http://192.168.0.one.
Most other web browser such as Firefox and even after versions of Internet Explorer, will appear to piece of work but may not successfully upload the firmware to the router. -
Upload the .bin file you downloaded higher up.
The progress will become to a random pct and so cease while the router reboots. This is OK. The bodily percentage does not actually mean annihilation useful. -
Wait for the router to boot support.
The router signifies restarting by rapidly flashing all lights. You'll know when the router has fully booted when the 'Condition' light turns from orangish to greenish. The LAN and WAN link lights will not light up, but the router is performance. -
Set your computer's network interface back to automatic or manually to any IP address betwixt 192.168.one.2 and 192.168.1.253.
Don't use 192.168.one.1 equally this is the new IP address of the router at present that the OpenWrt firmware has been successfully installed. -
Telnet to 192.168.1.one and you lot should be presented with a beat out prompt.
If you set the password via Telnet, you will need to apply a SSH connection using a programme similar "Putty" to log in afterwards. Alternatively, you tin set your password via the web interface. -
Access the web interface using a web browser and become to
http://192.168.one.ane -
You lot will be presented with a login page.
If you cannot admission the router via Telnet or the web interface , check to ensure that you lot have properly reconfigured your estimator'south network interface and that information technology has a right IP address. If all else fails, echo these instructions as the router's firmware has not been successfually flashed with OpenWrt.
Flash via Normal Web Interface
The normal web interface accepts the ddwrt prototype linked in their wiki, simply not the openwrt images. Attempting to flash openwrt from ddwrt tin can damage the u-kick and wireless partitions, resulting in no wireless or a brick. Support EVERYTHING!
Wink via U-Boot panel
Loading an image via tftp may not piece of work, arp replies do non seem to brand it though the switch, these commands utilise y-modem instead.
ar7240> loady 0x81000000 ## Set up for binary (ymodem) download to 0x81000000 at 115200 bps... CCCCC *** file: /tftp_root/openwrt.bin sb -vv /tftp_root/openwrt.bin Sending: openwrt.bin Bytes Sent:3735680 BPS:9438 Sending: Ymodem sectors/kbytes sent: 0/ 0k Transfer complete *** exit status: 0 ## Total Size = 0x00390018 = 3735576 Bytes ar7240> protect off 0xbf040000 +0x00390017 ar7240> erase 0xbf040000 +0x00390017 ar7240> cp.b 0x81000000 0xbf040000 0x00390018 ar7240> bootm 0xbf040000 ## Booting image at bf040000 ... Epitome Name: MIPS OpenWrt Linux-2.6.32.27 Created: 2011-12-21 1:03:18 UTC Image Type: MIPS Linux Kernel Image (lzma compressed) Data Size: 894180 Bytes = 873.2 kB Load Accost: 80060000 Entry Point: 80060000 Verifying Checksum ... OK LZMA Umcompressing Kernel Image ... Image loaded from 80060000-803039c0 OK No initrd ## Transferring command to Linux (at address 80060000) ... ## Giving linux memsize in bytes, 33554432 Starting kernel ... ..... .....
| Compages | MIPS |
|---|---|
| Vendor | Atheros |
| Bootloader | U-Kick |
| System-On-Chip | AR7240 |
| CPU Speed | 350MHz |
| Flash-Chip | Winbond W25X32VF1G SPI wink |
| Wink size | 4MiB |
| RAM | 32MiB |
| Wireless | Atheros AR9285 |
| Ethernet | eth0, eth1 (confirmed on 601 merely) |
| Switch | AR7240 built-in half-dozen port switch (cpu @ port 0), 16 vlans (confirmed on 601 but) |
| USB | modern (601) |
| Serial | Yep |
| JTAG | No |
The swconfig command provides the post-obit info near the Dir-601 ethernet switch.
root@OpenWrt:/# swconfig dev eth0 prove Global attributes: enable_vlan: 1 Port 0: pvid: 1 Port one: pvid: 1 Port 2: pvid: 1 Port 3: pvid: 1 Port 4: pvid: i Port 5: pvid: 0 VLAN 0: vid: 0 ports: 5 VLAN 1: vid: 1 ports: 0 one 2 3 4
The information written on the main Atheros scrap is as follows:
AR7240-AH1A F48053, 1C 1005 TAIWAN
Link to datasheet
The information written on the WiFi Atheros chip is as follows:
AR9285-AL1A D02868B 1005 TAIWAN
Link to datasheet
The information written on the PSC DDR-Ram chip ar as equally follows:
A3S56D40ETP A10ANL25 TAIWAN -G5
Link to PSC datasheet Link to non-manufacturer datasheet (should be similar): here
The information on the W25X32VF1G Winbond Wink chip are equally follows:
25X32VF1G 1007
Datasheet: http://www.alldatasheet.com/view.jsp?Searchword=W25X32
Alternate Flash: MX25L3206E in SOP8 package (hidden under SOP16 in pics) http://www.zlgmcu.com/mxic/pdf/NOR_Flash_c/MX25L3206E_DS_EN.pdf
Series header pinout:
_______ | | Due south JP3 pinout: ___ | h 1: VCC (3.3V) (square) | o 1 | i 2: Rx S | o 2 | e 3: Tx h | o 3 | fifty 4: GND i | o four | d eastward | JP3 | l | |_______ d | ___| DS4 LED2 DS5 ___|*|__|*|____________
This setup:
http://images.kaneva.com/filestore9/4609772/6089590/UARTUJumperUWires_ad.JPG
works great for me. Just remember that you can't hook upwards a PC serial port straight. Yous need a TTL to RS232 level converter. Note that the linked image above has the ports facing you, and LEDs facing abroad. This is opposed to the in a higher place images of the DIR-601 with ports facing away. Take note of the position of the square solder pad in relation to the others when soldering.
Yous tin can also accept a wait at the picture in the USB modernistic section where these pins are labeled on the left-hand side.
The DIR-601 does not appear to have a JTAG interface. (I am non certain about the DIR-600).
Information on how to add USB hardware and support to the AR72xx processor.
Hardware
Hardware portion of the mod involving soldering and calculation a few passive components.
Caution
USB is possible on the DIR-601 (and probable DIR-600) and I (amishx64) take it working. I even so need to sort out some kinks before posting more details and pictures, just they will be posted shortly.
Note: This department is still existence written.
This USB port modernistic is very hard to exercise even with very expert tools due to the tiny pin spacing on the Atheros AR72xx processor.
| | Warning: You will run the risk of ruining the device if you attempt this mod. You accept been warned. |
Resources
This modern was completed with two main resource: the USB Host section of the TP-Link TL-WR741ND folio at tl-wr741nd and part 1 of the D-Link DIR-615 rev E1-E4 USB port modernistic ex-usb.
Connections
Solder two wires onto pins 73 and 74 on the Atheros SOC. The pins tin can be counted starting from the upper left corner of the chip with the dot (pin i) and counterclockwise along the sides. Since the SOC has 128 pins, there are 32 pins per side. Pins 73 and 74 should be on the right side of the chip if you are facing the bit right side up. Alternatively, the ii pins are nine and x when counting from the lesser of the right side of the fleck. The two pins should non have whatever PCB traces leading to them. Pin 73/9 is D- and pivot 74/x is D+ . I recommend using wire wrap to solder to the pins since information technology is very thin. Tin the wire wrap with a minimal amount of solder, hold information technology on top of a pivot with tweezers and utilise oestrus to a office of the wire not touching the pin itself with a solder-gratuitous tip. Do not touch the tip of the soldering iron direct to the pins like I did. You lot volition likely bridge some pins, rendering the device useless unless cleaned (very hard to do, but possible and very time consuming). Use aplenty flux. One time both wires have been soldered, apply hot glue to the lath and wires (not the bit!) to ensure they don't break off. If y'all don't glue them down, they will intermission off and will likely short out other pins.
Once y'all take soldered the two wires on and checked your work, employ a 15K Ohm resistor to pull the lines low. (In my film, I use 10K Ohm and 5.1K Ohm resistors = 15.1K Ohm since that is what I had on-hand.) To clarify, pulling the D+ and D- lines depression means that you need to hook 1 terminate of the resistor to GND and the other finish to one of the lines. Practise this for each line. A 330 ohm resisror is not needed as specified in the USB host standard, so I doubtable that the 330 ohm resistors are internal.
Next connect the two lines to a female person type A USB plug. +5V (red) can be sourced from the router's 5V connector and GND (black) can be continued at any unoccupied GND pad on the board. D- is likely to be white and D+ green on the USB female plug. Alternatively, from the front end of a female person type A USB connector, pin 1 is VCC (+5V), pin two is D- (white, 73/9), pin 3 is D+ (green, 74/10), and pin 4 is GND (black). Source: http://pinouts.ru/Slots/USB_pinout.shtml
| | Thermal Circumspection: Some of these new packages can be rather processor-intensive. Without additional cooling the CPU stops operation! I observe active cooling with heatsink and a small fan are required. |
Software
Check → usb-installing and → usb-drives or but build your own firmware with everything already integrated:
Kernel Modifications
The only file that needs to be modified is target/linux/ar71xx/files/curvation/mips/ar71xx/mach-dir-600-a1.c as part 1 of ex-usb.
I have tried this on Backfire 10.03.1-rc4 and confirmed it working. This should also apply to whatsoever other Backlash builds as well equally trunk only has not been tested by me withal.
-
Download SVN source code
-
Backup by copying
target/linux/ar71xx/files/arch/mips/ar71xx/mach-dir-600-a1.cto a completely different location (in case something goes wrong) -
Edit file
target/linux/ar71xx/files/arch/mips/ar71xx/mach-dir-600-a1.c -
Run 'make menuconfig' and select platform/profile (atheros ar71xx/Dir-600-a1) and other packages discussed in the next section
-
Compile the image and flash it to the router
Packages
Packages that I have enabled are listed below. They support Ext4 formated USB drives. I am currently having problems with FAT and large (2GB+ drives). Not all packages listed are necessary (few are). Just utilize this for a guide to get things up an running.
Base of operations system
block-extroot block-hotplugfdisk fat_filesystem Ext_filesystem linux_swap_filesystem (prob not needed) mountain umount block-mount
Base of operations System -> busybox -> Configuration -> Linux System Utilities
fdisk fat_filesystem Ext_filesystem linux_swap_filesystem (prob not needed) mount umount
Libraries
libusb
Kernel Modules -> Block Devices
kmod-scsi-core
Kernel Modules -> Filesystems
kmod-fs-autofs4 kmod-fs-ext4 kmod-fs-msdos kmod-fs-vfat
USB Support
kmod-usb-cadre kmod-usb-ohci kmod-usb-storage kmod-usb-usb2
Utilities
mount-utils
Alert: enabling mountd may crusade high CPU load without a patch
→ Basic configuration Afterward flashing, proceed with this.
Fix up your Internet connection, configure wireless, configure USB port, etc.
The default (OpenWrt) network configuration is:
| Interface Proper noun | Clarification | Default configuration |
|---|---|---|
| br-lan | LAN & WiFi | 192.168.1.i/24 |
| eth0 | LAN | None |
| eth1 | WAN | None |
| lan1 | LAN | None |
| lan2 | LAN | None |
| lan3 | LAN | None |
| lan4 | LAN | None |
You could prettify this wink.layout. — orca 2011/05/16 13:03
MTD retentiveness partitions for DIR-601:
| Address Kickoff | Address Stop | Proper noun |
|---|---|---|
| 0x000000000000 | 0x000000030000 | u-boot |
| 0x000000030000 | 0x000000040000 | nvram |
| 0x000000040000 | 0x000000120000 | kernel |
| 0x000000120000 | 0x0000003e0000 | rootfs |
| 0x00000025a000 | 0x0000003e0000 | rootfs_data |
| 0x0000003e0000 | 0x0000003f0000 | mac |
| 0x0000003f0000 | 0x000000040000 | fine art |
| 0x000000040000 | 0x0000003e0000 | firmware |
Decision-making LEDs
The ability to control LEDs has been confirmed to work on the DIR-601. I have not tested the DIR-600. There are iii predefined LEDs that can be controlled.
To plough on the green power led:
echo "one" >/sys/class/leds/dir-600-a1\:greenish\:power/brightness
To turn on the amber power led:
echo "ane" >/sys/class/leds/dir-600-a1\:amber\:power/brightness
To turn on the bluish wireless protected setup led (on the side of the router):
echo "i" >/sys/class/leds/dir-600-a1\:blue\:wps/brightness
To turn off the LEDs, you replace the "one" with a "0" in the above commands. I all the same don't know how to control the individual LAN/WAN LEDs. I besides don't know what the trigger (does aught), max_brightness (returns permission denied), and uevent functions exercise nor have I had time to look into them. Also, the brightness office used above doesn't seem to be able to vary the LED brightness (PWM), equally different values than "0" or "1" accept no noticeable effect. Software PWM is possible with the use of a timer but I don't see whatever developed software to implement it. Maybe someone could make a package that does this?
I (amishx64) will exist working on mapping and expanding the functionality of the LEDs/GPIOs next afterward I stop upward the USB modernistic section. Later on the GPIOs all work, I tin wait at adding SD can other bit-bang protocol support…
In order to add GPIOs/LEDs, the target/linux/ar71xx/files/arch/mips/ar71xx/mach-dir600-a1.c file needs to be modified. Backup by copying target/linux/ar71xx/files/arch/mips/ar71xx/mach-dir600-a1.c to a completely dissimilar location (in case something goes wrong).
The unmodified mach-dir600-a1.c file has ii main sections that need to be added to in social club to add LED 'devices' as GPIOs to the system.
Definitions
The first section that needs to be added to is the #define department, after the #include section. Since there are LEDs that need to be added, any additions should look similar to the provided code in the original file: #define DIR_600_A1_GPIO_LED_WPS 0 #ascertain DIR_600_A1_GPIO_LED_POWER_AMBER 1 #define DIR_600_A1_GPIO_LED_POWER_GREEN 6
Here is a table of the LEDs on the DIR-601 and corresponding GPIOs:
| Power | Globe | WiFi | LAN one | LAN two | LAN 3 | LAN 4 | WPS | |
|---|---|---|---|---|---|---|---|---|
| Amber | GPIO ane | GPIO 7 | ——- | ——- | ——- | ——- | ——- | —— |
| Light-green | GPIO 6 | GPIO 17 | GPIO ?? | GPIO 13 | GPIO 14 | GPIO xv | GPIO sixteen | —— |
| Blue | —— | ——- | ——- | ——- | ——- | ——- | ——- | GPIO 0 |
Of those, the WPS LED all LAN LEDs GPIOs are active low. If you don't define them as active depression in the side by side section they will behave equally if the signal is inverted.
The new definitions that need to exist added are as follows:
#ascertain DIR_600_A1_GPIO_LED_GLOBE_AMBER 7 #define DIR_600_A1_GPIO_LED_LAN1_GREEN 13 #define DIR_600_A1_GPIO_LED_LAN2_GREEN 14 #define DIR_600_A1_GPIO_LED_LAN3_GREEN 15 #define DIR_600_A1_GPIO_LED_LAN4_GREEN 16 #define DIR_600_A1_GPIO_LED_GLOBE_GREEN 17
Array Structure
The defined LED GPIOs then need to be implemented in in a structure to exist included in the kernel every bit devices.
Add the following lines to the static struct gpio_led dir_600_a1_leds_gpio[] __initdata assortment department of code:
Yous must not miss commas or any other syntax (missing a infinite is fine) otherwise you lot will break the build.
, { .name = "dir-600-a1:bister:earth", .gpio = DIR_600_A1_GPIO_LED_GLOBE_AMBER, }, { .name = "dir-600-a1:green:LAN1", .gpio = DIR_600_A1_GPIO_LED_LAN1_GREEN, .active_low = 1, }, { .name = "dir-600-a1:green:LAN2", .gpio = DIR_600_A1_GPIO_LED_LAN2_GREEN, .active_low = 1, }, { .name = "dir-600-a1:green:LAN3", .gpio = DIR_600_A1_GPIO_LED_LAN3_GREEN, .active_low = i, }, { .name = "dir-600-a1:light-green:LAN4", .gpio = DIR_600_A1_GPIO_LED_LAN4_GREEN, .active_low = ane, }, { .proper name = "dir-600-a1:green:earth", .gpio = DIR_600_A1_GPIO_LED_GLOBE_GREEN, .active_low = ane, }
Compile OpenWrt
And that should be it. Do a make clean and and then make. If you get any error on compiling the edited file or on linux/install, when building, yous messed something upward above.
Just a note for anyone with a different router reading this: if you get a leds-gpio/: probe of leds-gpio failed with error -22" fault that means that you tried to add a GPIO that either doesn't exist or can't exist made a GPIO. Change the GPIO pin definition.
Further Work and Other Thoughts
Once I become the WiFi LED working I volition submit a patch to the developers for future OpenWrt images. It seems equally though the WiFi LED is non a standard GPIO pin. I am making this assumption for two reasons:
i) I can't get the LED to turn on fifty-fifty when I ascertain every unmarried GPIO possibility.
2) The LED does not plow on at router boot upward similar all the LEDs do.
I don't call up it is worth my time to become 1 LED to work, specially since there are now and so many others working. My best approximate is that the LED is actually tied to the wireless chipset and blinks whenever there is traffic.
Likewise in that location is a empty spot on the PCB (DS2) where a LED could be present. Information technology is likely this would be controlled via GPIO also, but the surrounding area is missing some passive components that may need to exist put in. There is also a exam bespeak (TP29) near the CPU and a bit to the right of the serial header. This is likely a GPIO also. [EDIT: TP29 = GPIO xi]
I volition also host the modified mach-dir600-a1.c file for anyone that wants it (eventually).
@jkiddo: - I recently ported the DIR-632-A1, and for this lath the WLAN is non a normal GPIO, to become the WLAN LED to work you actually have to call
ap9x_pci_setup_wmac_led_pin(0, DIR_632_A1_WLAN_GPIO_LED);
where DIR_632_A1_WLAN_GPIO_LED is 0 in this case, I take seen it every bit 1 in other boards. I suspect you need to do something similar here…
If you forgot your countersign, bankrupt one of the startup scripts, firewalled yourself out, or corrupted the JFFS2 sectionalization, you lot can become dorsum in by using OpenWrt's failsafe fashion or only reflashing the firmware as instructed to a higher place.
NOTE: The root file system in failsafe mode is the SquashFS partition mounted in readonly mode. To switch to the normal writable root file organization run mount_root and make any changes. Run mount_root now.
-
Forgot/lost your password and you like to set a new one
passwd -
Forgot the routers IP address
uci get network.lan.ipaddr -
You accidentally run 'ipkg upgrade' or filled upwards the wink by installing large packages (clean the JFFS2 partition and beginning over)
mtd -r erase rootfs_data
If yous are washed with failsafe mode power cycle the router and kicking in normal mode.
U-Boot 1.1.4 (April 23 2009 - eleven:58:47) AP91 (ar7240) U-boot DRAM: sri #### TAP VALUE ane = viii, 2 = ix 32 MB Elevation of RAM usable for U-Boot at: 82000000 Reserving 243k for U-Boot at: 81fc0000 Reserving 192k for malloc() at: 81f90000 Reserving 44 Bytes for Board Info at: 81f8ffd4 Reserving 36 Bytes for Global Data at: 81f8ffb0 Reserving 128k for boot params() at: 81f6ffb0 Stack Arrow at: 81f6ff98 Now running in RAM - U-Boot at: 81fc0000 id read 0x100000ff wink size 4194304, sector count = 64 Flash: 4 MB *** Warning - bad CRC, using default environment In: serial Out: series Err: serial Internet: ag7240_enet_initialize... Fetching MAC Accost from 0x81fe6e50 : cfg1 0xf cfg2 0x7014 eth0: 00:03:7f:e0:04:33 eth0 upward No valid address in Flash. Using fixed address : cfg1 0xf cfg2 0x7214 eth1: 00:03:7f:09:0b:ad ATHRS26: resetting s26 ATHRS26: s26 reset done eth1 up eth0, eth1 Hit whatsoever key to stop autoboot: 0 ## Booting epitome at bf040000 ... Image Name: Linux Kernel Epitome Created: 2010-01-29 6:12:45 UTC Paradigm Type: MIPS Linux Kernel Image (lzma compressed) Information Size: 980953 Bytes = 958 kB Load Address: 80002000 Entry Betoken: 802b0000 Verifying Checksum ... OK LZMA Umcompressing Kernel Epitome ... Image loaded from 80002000-802d8086 OK No initrd ## Transferring control to Linux (at address 802b0000) ... ## Giving linux memsize in bytes, 33554432 Starting kernel ... Booting AR7240(Python)... Linux version 2.6.15--LSDK-seven.3.0.260 (root@debian) (gcc version three.4.4) #1 Friday Jan 29 01:08:23 EST 2010 flash_size passed from bootloader = four arg one: console=ttyS0,115200 arg 2: root=31:03 arg 3: rootfstype=squashfs,jffs2 arg 4: init=/sbin/init arg v: mtdparts=ar7240-nor0:192k(u-boot),64k(nvram),960k(linux),2752k(rootfs),64k(MAC),64k(Fine art) arg half dozen: mem=32M CPU revision is: 00019374 Determined concrete RAM map: retentivity: 02000000 @ 00000000 (usable) User-divers concrete RAM map: memory: 02000000 @ 00000000 (usable) Built 1 zonelists Kernel command line: console=ttyS0,115200 root=31:03 rootfstype=squashfs,jffs2 init=/sbin/init mtdparts=ar7240-nor0:192k(u-kicking),64k(nvram),960k(linux),2752k(rootfs),64k(MAC),64k(Art) mem=32M Principal instruction cache 64kB, physically tagged, 4-style, linesize 32 bytes. Chief information enshroud 32kB, four-fashion, linesize 32 bytes. Synthesized TLB refill handler (xx instructions). Synthesized TLB load handler fastpath (32 instructions). Synthesized TLB store handler fastpath (32 instructions). Synthesized TLB modify handler fastpath (31 instructions). Cache parity protection disabled PID hash table entries: 256 (social club: 8, 4096 bytes) Using 175.000 MHz loftier precision timer. Panel: colour dummy device 80x25 Dentry cache hash tabular array entries: 8192 (order: three, 32768 bytes) Inode-cache hash table entries: 4096 (order: 2, 16384 bytes) Memory: 29104k/32768k bachelor (2285k kernel code, 3648k reserved, 454k data, 164k init, 0k highmem) Mountain-enshroud hash table entries: 512 Checking for 'wait' instruction... available. NET: Registered protocol family 16 SCSI subsystem initialized Returning IRQ 48 TC classifier action (bugs to netdev@vger.kernel.org cc hadi@cyberus.ca) AR7240 GPIOC major 0 squashfs: version 3.ane (2006/08/19) Phillip Lougher Initializing Cryptographic API io scheduler noop registered io scheduler deadline registered HDLC line subject: version $Revision: 1.1.1.i $, maxframe=4096 N_HDLC line discipline registered. Software Watchdog Timer: 0.07 initialized. soft_noboot=0 soft_margin=60 sec (nowayout= 0) Series: 8250/16550 driver $Revision: 1.i.ane.i $ one ports, IRQ sharing disabled serial8250.0: ttyS0 at MMIO 0x0 (irq = nineteen) is a 16550A RAMDISK driver initialized: 1 RAM disks of 8192K size 1024 blocksize loop: loaded (max viii devices) PPP generic driver version 2.4.2 PPP Deflate Pinch module registered PPP BSD Compression module registered PPP MPPE Compression module registered NET: Registered protocol family 24 PPTP driver version 0.7.12 6 cmdlinepart partitions institute on MTD device ar7240-nor0 Creating vi MTD partitions on "ar7240-nor0": 0x00000000-0x00030000 : "u-boot" 0x00030000-0x00040000 : "nvram" 0x00040000-0x00130000 : "linux" 0x00130000-0x003e0000 : "rootfs" 0x003e0000-0x003f0000 : "MAC" 0x003f0000-0x00400000 : "Fine art" GACT probability on Mirror/redirect action on Elementary TC activity Loaded netem: version ane.1 u32 classifier Perfomance counters on input device check on Actions configured Netfilter messages via NETLINK v0.xxx. Internet: Registered protocol family 2 IP road enshroud hash table entries: 512 (guild: -one, 2048 bytes) TCP established hash tabular array entries: 2048 (society: i, 8192 bytes) TCP bind hash table entries: 2048 (social club: 1, 8192 bytes) TCP: Hash tables configured (established 2048 bind 2048) TCP reno registered ip_conntrack version ii.iv (256 buckets, 2048 max) - 232 bytes per conntrack ip_ct_h323: init success ip_conntrack_rtsp v0.6.21 loading ip_nat_rtsp v0.6.21 loading ip_conntrack_pptp version 3.1 loaded ip_nat_pptp version 3.0 loaded ip_tables: (C) 2000-2002 Netfilter core squad ipt_time loading ipt_recent v0.3.i: Stephen Frost <sfrost@snowman.net>. http://snowman.cyberspace/projects/ipt_recent/ ClusterIP Version 0.viii loaded successfully TCP bic registered NET: Registered protocol family 1 Cyberspace: Registered protocol family 10 lo: Disabled Privacy Extensions IPv6 over IPv4 tunneling driver Cyberspace: Registered protocol family 17 arch/mips/ar7240/gpio.c (ar7240_simple_config_init) JUMPSTART_GPIO: 12 ar7240: calling simple_config callback.. ar7240wdt_init: Registering WDT VFS: Mounted root (squashfs filesystem) readonly. Freeing unused kernel memory: 164k freed init started: BusyBox v1.01 (2010.01.29-06:12+0000) multi-telephone call binary Algorithmics/MIPS FPU Emulator v1.5 Please press Enter to activate this panel. ag7240_mod: module license 'unspecified' taints kernel. AG7240: Length per segment 1536 AG7240: Max segments per package 1 AG7240: Max tx descriptor count 80 AG7240: Max rx descriptor count 252 AG7240: fifo cfg 3 01f00140 AG7240CHH: Mac address for unit 0 AG7240CHH: 00:03:7f:e0:04:33 AG7240CHH: Mac address for unit one AG7240CHH: ff:ff:ff:ff:ff:ff in get_default_mac!!! ag7240_ring_alloc Allocated 1280 at 0x803c8000 ag7240_ring_alloc Allocated 4032 at 0x813b8000 Setting PHY... ADDRCONF(NETDEV_UP): eth0: link is non ready eth0: Cannot assign requested address ag7240_ring_alloc Allocated 1280 at 0x813d4800 ag7240_ring_alloc Allocated 4032 at 0x813df000 Phone call athrs26_reg_init_lan ATHRS26: resetting s26 ATHRS26: s26 reset done Setting PHY... ADDRCONF(NETDEV_UP): eth1: link is not ready eth1: Cannot assign requested address device eth1 entered promiscuous mode AG7240: enet unit:1 phy:0 is up...Mii 100Mbps total duplex AG7240: done cfg2 0x7205 ifctl 0x0 miictrl AG7240: enet unit i phy 0 manner 0x4c04 ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready br0: port 1(eth1) entering learning state br0: topology modify detected, propagating br0: port 1(eth1) entering forwarding state Friday Jan 29 01:11:00 UTC 2010 Entry gpio_ioctl init_module !! sh: cannot create /proc/sys/cyberspace/ipv6/conf/eth0/accept_ra: Directory nonexistent lan mac = 00:01:23:11:11:11rc is BUSY now! eth0: Cannot assign requested accost sh: cannot create /proc/sys/cyberspace/ipv6/conf/eth0/accept_ra: Directory nonexistent eth1: Cannot assign requested address dhcpd_enabled:::::: domain empty Failure parsing line 19 of /var/etc/udhcpd.conf Failure parsing line xx of /var/etc/udhcpd.conf Failure parsing line 21 of /var/etc/udhcpd.conf DHCP server start. device_lan_ip=192.168.0.1 , device_lan_subnet_mask=255.255.255.0 ======================= === insmod_wlan_mod === ======================= DHCP client beginning. max_leases value (254) not sane, setting to 100 instead Unable to open /var/misc/udhcpd.leases for reading ath_hal: 0.nine.17.1 (AR5416, DEBUG, REGOPS_FUNC, WRITE_EEPROM, 11D) eth0 Link encap:Ethernet HWaddr 1C:AF:F7:CC:9F:BC Upward BROADCAST MULTICAST MTU:1500 Metric:i RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:thousand RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) wlan: 0.8.4.2 (Atheros/multi-bss) ath_rate_atheros: Copyright (c) 2001-2005 Atheros Communications, Inc, All Rights Reserved ath_dev: Copyright (c) 2001-2007 Atheros Communications, Inc, All Rights Reserved ath_pci: 0.9.4.5 (Atheros/multi-bss) wifi0: Atheros 9285: mem=0x10000000, irq=48 hw_base=0xb0000000 wlan: mac acl policy registered wlan_me: Version 0.1 Copyright (c) 2008 Atheros Communications, Inc. All Rights Reserved Sending discover... ath0 device br0 already exists; can't create bridge with the same name device eth1 left promiscuous mode br0: port 1(eth1) inbound disabled state device ath0 entered promiscuous mode device eth1 entered promiscuous mode br0: port 2(eth1) entering learning land br0: topology change detected, propagating br0: port 2(eth1) entering forwarding state Country ie is USI /************** debug wlan setting ****************/ /* WlanMode: Set up to default mode (AP) /* 80211Mode: 11NGHT20 /* ChannelWidth: 20 /* Essid: dlink /* Channel: 6 /* WEP: close /* WPA: close (non security) /* WPS: Non-Sec-Enable /* WPS AP-DEFAULT-Pivot: 34102350 /* WPS AP-PIN: 34102350 /**************************************************/ ######################## ### plow wps-led off ### ######################## Sending discover... Reading topology file /tmp/tmp/topology.conf ... Reading bss configuration file /tmp/tmp/secath0.conf ... br0: port one(ath0) entering disabled land Defaulted uuid based on mac addr 1c:af:f7:cc:9f:bb Could not connect to kernel driver. Using interface ath0 with hwaddr 1c:af:f7:cc:9f:bb and ssid 'dlink' State ie is USI br0: port one(ath0) entering learning state br0: topology modify detected, propagating br0: port 1(ath0) entering forwarding state upnp_wps_device_init chosen l2_packet_receive - recvfrom: Network is down br0: File exists TFTP main standard_tftp_server launched on port 69. Friday Jan 29 01:xi:00 UTC 2010 DHCPC Received SIGUSR2=>DHCPC Release Performing a DHCPC release Performing a DHCPC release Inbound released state wantimer: dhcpc_release (VCT_DISCONNECT) wan_ipaddr == NULL, enable mac_filter/ upnp only Start Firewall: Clear iptables killall: crowdcontrol: no process killed killall: wakeOnLanProxy: no procedure killed rc is IDLE now! write_radvd_conf_cmd get-go write radvd_conf_cmd finished
Dir-601 Installation Software Mac Download
Posted by: taverasthivalt1947.blogspot.com

0 Komentar
Post a Comment