To: | |
---|---|
Subject: | [ts-7000] Re: TS-7200 not getting IP from router - please help |
From: | "arquattr" <> |
Date: | Fri, 30 Apr 2010 15:07:25 -0000 |
Thank you Jason and Jim for your responses. --- In Jim Jackson <> wrote: > > > > The router type is Linksys WRT160Nv2, f/w rev v2.0.03. DHCP is enabled > > with start address 192.168.0.100. > > How many IP addresses in the pool? > Only about four, all dynamically assigned. > > NAT is enabled, DMZ is disabled, > > essentially all the settings are default. > > > > There is a straight Ethernet cable tied between the router and the > > TS-7200. Below is the terminal output on boot up: > > > > > >>> TS-BOOTROM, Rev 1.08 - built 10:44:37, May 26 2006 > >>> Copyright (C) 2006, Technologic Systems > >>> TS-7200: Rev >E1 CPU, Rev C PLD, 32MB SDRAM, options ( RS485 ) > > > > +Ethernet eth0: MAC address 00:d0:69:40:66:ce > > IP: 192.168.0.110/255.255.255.0, Gateway: 192.168.0.1 > > Default server: 192.168.0.1 > > > > RedBoot(tm) bootstrap and debug environment [ROMRAM] > > Non-certified release, version current-TS_5 - built 11:24:54, Jun 7 2006 > > > > Platform: TS-7200 Board (ARM920T) Rev A > > Copyright (C) 2000, 2001, 2002, 2003, 2004 Red Hat, Inc. > > > > RAM: 0x00000000-0x02000000, [0x00044f88-0x01fdd000] available > > FLASH: 0x60000000 - 0x60800000, 64 blocks of 0x00020000 bytes each. > > == Executing boot script in 0.100 seconds - enter ^C to abort > > RedBoot> fis load vmlinux > > RedBoot> exec -c "console=ttyAM0,115200 ip=dhcp root=/dev/hda1" > > You don't need ip=dhcp above. Take it out and retry. The kernel only needs > ip details if it is going to use e.g. NFS root partition. > I had suspected that ip=dhcp in the boot script wasn't needed but I tried it without and it didn't seem to work either. This is what I'm seeing: ts7200:~# cat /etc/network/interfaces Is there some problem with the dhclient configuration? > It maybe that the kernel is doing a dhcp and then useland dhcp is doing it > again, and there might be some interaction. > > > Using base address 0x00218000 and length 0x000c0000 > > Linux version 2.4.26-ts11 (gcc version 3.3.4) #215 Thu Jun 8 14:30:17 MST 2006 > > CPU: Arm920Tid(wb) revision 0 > > Machine: ep9301 > > On node 0 totalpages: 2048 > > zone(0): 2048 pages. > > zone(1): 0 pages. > > zone(2): 0 pages. > > On node 1 totalpages: 2048 > > zone(0): 2048 pages. > > zone(1): 0 pages. > > zone(2): 0 pages. > > On node 4 totalpages: 2048 > > zone(0): 2048 pages. > > zone(1): 0 pages. > > zone(2): 0 pages. > > On node 5 totalpages: 2048 > > zone(0): 2048 pages. > > zone(1): 0 pages. > > zone(2): 0 pages. > > Kernel command line: console=ttyAM0,115200 ip=dhcp root=/dev/hda1 > > Console: colour dummy device 80x30 > > Calibrating delay loop... 99.94 BogoMIPS > > Memory: 8MB 8MB 8MB 8MB = 32MB total > > Memory: 28500KB available (1320K code, 350K data, 72K init) > > 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) > > CPU: Testing write buffer: pass > > POSIX conformance testing by UNIFIX > > Linux NET4.0 for Linux 2.4 > > Based upon Swansea University Computer Society NET3.039 > > Initializing RT netlink socket > > Starting kswapd > > devfs: v1.12c (20020818) Richard Gooch > > devfs: boot_options: 0x1 > > JFFS2 version 2.2. (C) 2001-2003 Red Hat, Inc. > > ttyAM0 at MMIO 0x808c0000 (irq = 52) is a AMBA > > ttyAM1 at MMIO 0x808d0000 (irq = 54) is a AMBA > > ttyAM2 at MMIO 0x808e0000 (irq = 55) is a AMBA > > pty: 1024 Unix98 ptys configured > > Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ enabled > > rtc: no TS-5620 RTC detected. > > ep93xx_eth() version: ep93xx_eth.c: V1.0 09/04/2003 Cirrus Logic > > Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4 > > ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx > > Technologic Systems TS-7XXX IDE initialization - driver version 1.3, 6/21/04. > > hda: SanDisk SDCFB-1024, CFA DISK drive > > ide0 at 0x8d000000-0x8d000007,0x88400006 on irq 32 > > hda: attached ide-disk driver. > > hda: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error } > > hda: task_no_data_intr: error=0x04 { DriveStatusError } > > hda: 2001888 sectors (1025 MB) w/1KiB Cache, CHS=1986/16/63 > > Partition check: > > /dev/ide/host0/bus0/target0/lun0: [PTBL] [993/32/63] p1 > > TS-7200 flash: Found 1 x16 devices at 0x0 in 16-bit bank > > Intel/Sharp Extended Query Table at 0x0031 > > Using buffer write method > > cfi_cmdset_0001: Erase suspend on write enabled > > Creating 3 MTD partitions on "TS-7200 flash": > > 0x00000000-0x00020000 : "TS-BOOTROM" > > 0x00020000-0x00620000 : "Linux" > > 0x00620000-0x00800000 : "RedBoot" > > NET4: Linux TCP/IP 1.0 for NET4.0 > > IP Protocols: ICMP, UDP, TCP, IGMP > > IP: routing cache hash table of 512 buckets, 4Kbytes > > TCP: Hash tables configured (established 2048 bind 4096) > > Sending DHCP requests ...... timed out! > > IP-Config: Reopening network devices... > > Sending DHCP requests .... > > > > > > (and it continues forever...) > > > > Since my last post I was able to get the TS-7200 to successfully get an > > address by reserving an IP address on the router for the MAC of the > > TS-7200. DHCP is still enabled on the router, but it immediately > > recognizes the MAC and assigns the reserved IP. Hopefully that will help > > figure out why 'standard' DHCP isn't working. > > 'standard' DHCP ? Where I last did network management (I'm retired) > 'standard' DHCP was a huge table of fixed IP allocations matched to MACs. > There was a "pool" of IP for unknown machines but they didn't get > a default router allocated, and the syslog watcher soon told us when > unknown machines appeared. > > Do you really need the ability to pick up some random IP address? > Or is just as a convenience when moving it from network to network? > I always prefer my devices to have a known IP address - at least on the > "home" network. > I would like if possible to move the device to different networks as needed and not have to adjust the routers from their default settings. > > I'm not sure if there is any other information I can provide to figure > > this out - if so, please let me know, and thanks for any help you can > > offer. > > > > Angelo > > > > > > > > > > > > > __._,_.___
Your email settings: Individual Email|Traditional
Change settings via the Web (Yahoo! ID required) Change settings via email: =Email Delivery: Digest | m("yahoogroups.com?subject","ts-7000-fullfeatured");=Change Delivery Format: Fully Featured">Switch to Fully Featured Visit Your Group | Yahoo! Groups Terms of Use | =Unsubscribe __,_._,___ |
<Prev in Thread] | Current Thread | [Next in Thread> |
---|---|---|
|
Previous by Date: | [ts-7000] Re: Ehternet data transfer problem, talhaperacha4 |
---|---|
Next by Date: | [ts-7000] Can't telnet or ssh into Lenny on a 7350, Blair |
Previous by Thread: | [ts-7000] Re: Ehternet data transfer problem, talhaperacha4 |
Next by Thread: | Re: [ts-7000] Re: TS-7200 not getting IP from router - please help, Jim Jackson |
Indexes: | [Date] [Thread] [Top] [All Lists] |
Disclaimer: Neither Andrew Taylor nor the University of NSW School of Computer and Engineering take any responsibility for the contents of this archive. It is purely a compilation of material sent by many people to the birding-aus mailing list. It has not been checked for accuracy nor its content verified in any way. If you wish to get material removed from the archive or have other queries about the archive e-mail Andrew Taylor at this address: andrewt@cse.unsw.EDU.AU