I also don't want any clients on the bridge radio. Is there a way to stop it from accepting any.
this is called Point to Point. Choose this from disable, LAN and Point to Point in WDS flick _________________ wrt54gs v1.0 BS build 14289 mini
wrt600n v11 eko build 14853 mega...
Fonera FON2200
Motorola WR850G v2 BS build 14289 mini
Posted: Wed Oct 07, 2009 12:10 Post subject: Problem with macs on Linksys WRT600N v1.1 BS svn12966 built,
NOT WORKING............. BS svn12966 built
The router don't get ISPs IP nr. because IPs are related to a WAN mac addr. (they use max public IPs for connection and they register wan MAC). Probably ISP use physical layer to see if WAN mac is in the register. I fixit this by changeing wan mac
in gui MAC Address Clone to xx:xx:xx:A7:17:26
NEW!!!!!
I have tested the software and I find worse problem...
I have tested with IX67, wrt54gs v1 and wrt600n v1.1 connected to a switch(netgear) with WAN port (I have 5 IPs from my ISP). And I discover that then I connect to switch wrt600n (after I get ip on IX67 and wrt54gs) al devices start messing around. I tested to renew ip on IX67 and wrt54gs and it gives 0.0.0.0/(DHCP not respond on IX67). I tested vice versa were I first connected wrt600n (went ok after mod of wan mac), after I connected IX67 and wrt54gs and it gives 0.0.0.0/(DHCP not respond on IX67) a wrt54gs and IX67.
I never encounter such a problem, so I tested cables, switch, and routers. I used before svn10431 and there wasn't such a problem except wrong macs on wrt600n.
I think this is a problem on network layer getting ARP request. (first I was thinking that It was bug on DD-WRT networking system, but I tested and this is only wrt600n specific problem).
Except from this there is no other bugs I can find on svn12966 built... _________________ wrt54gs v1.0 BS build 14289 mini
wrt600n v11 eko build 14853 mega...
Fonera FON2200
Motorola WR850G v2 BS build 14289 mini
There is an annoying problem i have on my WRT600N v1.1, when i download large files, my download will hang. In order to finish the download, I have to pause then resume and it will continue to download. Also the same for streaming music, I can only hear a limited amount of minutes or so of a music stream and it will stop. Only refreshing will cause the stream to continue. I used v. 12533(std) and 13064(mega,)both have the same problem, but works fine the stock Linksys firmware.
Joined: 25 Apr 2008 Posts: 13 Location: Indianapolis, IN, USA
Posted: Thu Nov 19, 2009 17:58 Post subject:
I've searched the Wiki and the forums and can't find the answer. I'm sure I've seen it before, but it's been months and my memory has faded.
#1: How should I setup dual-band simultaneous N? Do I set the same SSID and Encryption on both 2.4 & 5GHz frequencies?
#2: I have 2 WRT600Ns. The second one is in a different part of the house, DHCP disabled, LAN port connected to LAN port of main router via wired Ethernet. For seamless roaming, should I set the same SSID and Encryption as the main router (but different channels) on this second router?
Question: I've linked the Wireless Access Point to the main router via wired Ethernet. So both radios (2.4 & 5GHz) are free to connect to clients. Should they both use the same SSID and security settings? Will this allow clients to connect to both radios at the same time? I want max bandwidth to the clients (dual-band wireless N access).
Joined: 19 May 2007 Posts: 283 Location: Los Angeles, CA USA
Posted: Mon Dec 14, 2009 4:14 Post subject:
i have acquired a wrt600n v1.1 and i telneted into it today and saw something peculiar is the dmesg output where it tells me it is a 4785 rev2 chip running at 300 mhz. i have overclocked it at 330 mhz. should 330 mhz show instead of 300 mhz?
BusyBox v1.13.4 (2009-12-07 13:45:37 CET) built-in shell (ash)
Enter 'help' for a list of built-in commands.
root@WRT-600N:~# dmesg
CPU ProcId is: 0x0002901a, options: 0x0000004d
Linux version 2.4.37 (eko@dd-wrt) (gcc version 3.4.6 (OpenWrt-2.0)) #4279 Mon De
c 7 13:53:04 CET 2009
Setting the PFC to its default value
Determined physical RAM map:
memory: 02000000 @ 00000000 (usable)
On node 0 totalpages: 8192
zone(0): 8192 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Kernel command line: root=/dev/mtdblock2 rootfstype=squashfs,jffs2 noinitrd cons
ole=ttyS0,115200
CPU: BCM4785 rev 2 at 300 MHz
Using 150.000 MHz high precision timer.
Calibrating delay loop... 299.82 BogoMIPS
Dentry cache hash table entries: 4096 (order: 3, 32768 bytes)
Inode cache hash table entries: 2048 (order: 2, 16384 bytes)
Mount cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer cache hash table entries: 1024 (order: 0, 4096 bytes)
Page-cache hash table entries: 8192 (order: 3, 32768 bytes)
Checking for 'wait' instruction... unavailable.
POSIX conformance testing by UNIFIX
PCI: Initializing host
PCI: Ignoring BAR0-1 of IDE controller 00:06.0
PCI: Fixing up bus 0
PCI: Fixing up bridge
PCI: Setting latency timer of device 01:00.0 to 64
PCI: Fixing up bus 1
Initializing RT netlink socket
Starting kswapd
devfs: v1.12c (20020818) Richard Gooch (rgooch@atnf.csiro.au)
devfs: boot_options: 0x1
squashfs: version 3.0 (2006/03/15) Phillip Lougher
pty: 256 Unix98 ptys configured
Serial driver version 5.05c (2001-07-0 with MANY_PORTS SHARE_IRQ SERIAL_PCI en
abled
ttyS00 at 0xb8000300 (irq = 2) is a 16550A
ttyS01 at 0xb8000400 (irq = 2) is a 16550A
PCI: Enabling device 01:01.0 (0000 -> 0002)
PCI: Setting latency timer of device 01:01.0 to 64
PCI: Enabling device 01:02.0 (0000 -> 0002)
PCI: Setting latency timer of device 01:02.0 to 64
PPPoL2TP kernel driver, V0.13
Universal TUN/TAP device driver 1.5 (C)1999-2002 Maxim Krasnyansky
Physically mapped flash: Found an alias at 0x800000 for the chip at 0x0
Physically mapped flash: Found an alias at 0x1000000 for the chip at 0x0
Physically mapped flash: Found an alias at 0x1800000 for the chip at 0x0
Amd/Fujitsu Extended Query Table v0.0 at 0x0040
Physically mapped flash: JEDEC Device ID is 0xE2. Assuming broken CFI table.
Physically mapped flash: Swapping erase regions for broken CFI table.
number of CFI chips: 1
cfi_cmdset_0002: Disabling fast programming due to code brokenness.
Flash device: 0x800000 at 0x1c000000
bootloader size: 262144
Physically mapped flash: Filesystem type: squashfs, size=0x4ecae3
partition size = 5222400
Creating 5 MTD partitions on "Physically mapped flash":
0x00000000-0x00040000 : "cfe"
0x00040000-0x007f0000 : "linux"
0x00145000-0x00640000 : "rootfs"
mtd: partition "rootfs" doesn't start on an erase block boundary -- force read-o
nly
0x007f0000-0x00800000 : "nvram"
0x00640000-0x007f0000 : "ddwrt"
sflash not supported on this router
Initializing Cryptographic API
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 2048 bind 4096)
ip_conntrack version 2.1 (512 buckets, 4096 max) - 336 bytes per conntrack
ip_tables: (C) 2000-2002 Netfilter core team
ipt_random match loaded
netfilter PSD loaded - (c) astaro AG
ipt_osf: Startng OS fingerprint matching module.
ipt_IPV4OPTSSTRIP loaded
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
All bugs added by David S. Miller <davem@redhat.com>
VFS: Mounted root (squashfs filesystem) readonly.
Mounted devfs on /dev
Broadcom Gigabit Ethernet Driver bcm5700 ver. 8.3.14 (11/2/05)
PCI: Setting latency timer of device 00:01.0 to 64
PHY ID unknown, assume it is a copper PHY.
bcm_robo_attach: devid read succesfully via mii: 0x95
bcm_robo_attach: mii access to switch works
bcm_robo_attach: Resetting 539x robo switch
VID 0 is set in nvram, Ignoring
dd-wrt already booted, use internal fixup
configure vlan1 (1 2 3 4 8*) instead of vlan0 for BCM5395
eth2: Broadcom BCM4785 10/100/1000 Integrated Controller found at mem 18010000,
IRQ 5, node addr 0021296c49f0
eth2: tranceiver BC050CF0
eth2: tbiflags 0
eth2: Unknown transceiver found
eth2: Scatter-gather ON, 64-bit DMA ON, Tx Checksum ON, Rx Checksum ON, 802.1Q V
LAN ON, NAPI ON
usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
PCI: Setting latency timer of device 00:02.1 to 64
ehci_hcd 00:02.1: PCI device 14e4:471a
ehci_hcd 00:02.1: irq 3, pci mem b8002800
usb.c: new USB bus registered, assigned bus number 1
ehci_hcd 00:02.1: illegal capability!
ehci_hcd 00:02.1: USB 0.0 enabled, EHCI 1.00, driver 2003-Dec-29/2.4
hub.c: USB hub found
hub.c: 2 ports detected
SCSI subsystem driver Revision: 1.00
Initializing USB Mass Storage driver...
usb.c: registered new driver usb-storage
USB Mass Storage support registered.
hub.c: new USB device 00:02.1-1, assigned address 2
hub.c: USB hub found
hub.c: 4 ports detected
hub.c: new USB device 00:02.1-1.1, assigned address 3
scsi0 : SCSI emulation for USB Mass Storage devices
Vendor: SanDisk Model: U3 Cruzer Micro Rev: 3.27
Type: Direct-Access ANSI SCSI revision: 02
Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0
SCSI device sda: 8027790 512-byte hdwr sectors (4110 MB)
sda: Write Protect is off
Partition check:
/dev/scsi/host0/bus0/target0/lun0: p1
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 3
hub.c: new USB device 00:02.1-1.4, assigned address 4
scsi1 : SCSI emulation for USB Mass Storage devices
Vendor: Memorex Model: TD Classic 003C Rev: 1.04
Type: Direct-Access ANSI SCSI revision: 02
Attached scsi removable disk sdb at scsi1, channel 0, id 0, lun 0
eth2: Using PCI INTX interrupt
SCSI device sdb: 2007040 512-byte hdwr sectors (1028 MB)
sdb: Write Protect is off
/dev/scsi/host1/bus0/target0/lun0: p1
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 4
vlan1: add 01:00:5e:00:00:01 mcast address to master interface
vlan1: del 01:00:5e:00:00:01 mcast address from vlan interface
vlan1: del 01:00:5e:00:00:01 mcast address from master interface
vlan1: add 01:00:5e:00:00:01 mcast address to master interface
vlan1: del 01:00:5e:00:00:01 mcast address from vlan interface
vlan1: del 01:00:5e:00:00:01 mcast address from master interface
vlan1: add 01:00:5e:00:00:01 mcast address to master interface
vlan1: dev_set_promiscuity(master, 1)
device eth2 entered promiscuous mode
device vlan1 entered promiscuous mode
device eth0 entered promiscuous mode
device eth1 entered promiscuous mode
device vlan2 entered promiscuous mode
vlan2: Setting MAC address to 00 21 29 6c 49 f1.
vlan2: dev_set_promiscuity(master, 1)
vlan2: dev_set_allmulti(master, 1)
vlan2: dev_set_promiscuity(master, -1)
device vlan2 left promiscuous mode
vlan2: dev_set_allmulti(master, -1)
vlan2: add 01:00:5e:00:00:01 mcast address to master interface
etherip: Ethernet over IPv4 tunneling driver
ip_conntrack_pptp version 1.9 loaded
ip_conntrack_pptp version 1.9 unloaded
ip_conntrack_pptp version 1.9 loaded
ip_nat_pptp version 1.5 loaded
vlan2: add 01:00:5e:7f:ff:fa mcast address to master interface
ip_nat_pptp version 1.5 unloaded
ip_conntrack_pptp version 1.9 unloaded
ip_conntrack_pptp version 1.9 loaded
ip_nat_pptp version 1.5 loaded
vlan2: del 01:00:5e:7f:ff:fa mcast address from master interface
vlan2: add 01:00:5e:7f:ff:fa mcast address to master interface
ip_nat_pptp version 1.5 unloaded
ip_conntrack_pptp version 1.9 unloaded
ip_conntrack_pptp version 1.9 loaded
ip_nat_pptp version 1.5 loaded
vlan2: del 01:00:5e:7f:ff:fa mcast address from master interface
vlan2: add 01:00:5e:7f:ff:fa mcast address to master interface
vlan2: del 01:00:5e:7f:ff:fa mcast address from master interface
ip_nat_pptp version 1.5 unloaded
ip_conntrack_pptp version 1.9 unloaded
ip_conntrack_pptp version 1.9 loaded
ip_nat_pptp version 1.5 loaded
vlan2: del 01:00:5e:00:00:01 mcast address from vlan interface
vlan2: del 01:00:5e:00:00:01 mcast address from master interface
vlan1: dev_set_promiscuity(master, -1)
device eth2 left promiscuous mode
device vlan1 left promiscuous mode
device eth0 left promiscuous mode
device eth1 left promiscuous mode
vlan1: del 01:00:5e:00:00:01 mcast address from vlan interface
vlan1: del 01:00:5e:00:00:01 mcast address from master interface
vlan1: add 01:00:5e:00:00:01 mcast address to master interface
vlan1: del 01:00:5e:00:00:01 mcast address from vlan interface
vlan1: del 01:00:5e:00:00:01 mcast address from master interface
vlan1: add 01:00:5e:00:00:01 mcast address to master interface
vlan1: dev_set_promiscuity(master, 1)
device eth2 entered promiscuous mode
device vlan1 entered promiscuous mode
device eth0 entered promiscuous mode
device eth1 entered promiscuous mode
device vlan2 entered promiscuous mode
vlan2: Setting MAC address to 00 21 29 6c 49 f1.
vlan2: dev_set_promiscuity(master, 1)
vlan2: dev_set_allmulti(master, 1)
vlan2: add 01:00:5e:00:00:01 mcast address to master interface
vlan2: dev_set_promiscuity(master, -1)
device vlan2 left promiscuous mode
vlan2: dev_set_allmulti(master, -1)
ip_nat_pptp version 1.5 unloaded
ip_conntrack_pptp version 1.9 unloaded
ip_conntrack_pptp version 1.9 loaded
ip_nat_pptp version 1.5 loaded
ip_nat_pptp version 1.5 unloaded
ip_conntrack_pptp version 1.9 unloaded
ip_conntrack_pptp version 1.9 loaded
ip_nat_pptp version 1.5 loaded
ip_nat_pptp version 1.5 unloaded
ip_conntrack_pptp version 1.9 unloaded
ip_conntrack_pptp version 1.9 loaded
ip_nat_pptp version 1.5 loaded
vlan2: add 01:00:5e:7f:ff:fa mcast address to master interface
ip_nat_pptp version 1.5 unloaded
ip_conntrack_pptp version 1.9 unloaded
ip_conntrack_pptp version 1.9 loaded
ip_nat_pptp version 1.5 loaded
root@WRT-600N:~#
i have telnetted into a wrt300n v1.1 and indeed it shows 330 mhz when overclocked... is overclocking not working on a wrt600n v1.1? any input will be appreciated... _________________ e3200 stock <- waiting for support
wrt400n v26 std with modded antennas
in the router database, it recommends 13064. should we trust it?
i have been lazy and running an old version, 12124M NEWD Eko mini, for a while now. i notice that DNS lookups sometimes take quite a while (i have tried different DNS servers) and also all network activity will halt for several seconds and then return to normal... rather often. i know i'm using an old version and maybe a newer version is better, but thought i would add my 2 cents so far. i have been wanting to upgrade because of this problem for a while now.. but i've been lazy like i said and just dealing with this :)
should i go for the "official recommended" 13064 or try the latest SVN release, or something else?
thanks
edit: i went with the latest SVN release, mini - build 13491M NEWD-2 Eko, since the recommended stable is still at v24-sp1... which is obviously not stable otherwise this whole thread wouldn't exist. still having slow DNS issues. will post about it in the 13491 thread.
does QoS work at all? i am still using the snow release, 13491M and QoS rules don't seem to be matching the connections. even something easy like NNTP which is running on port 119 isn't getting matched. i tried to define a new service on port 119 and now the connections are getting matched to 'whois' ???