Need help connecting Linux box to DLink AP

Post #319,265 by drook 12/29/09 11:21:11 AM Reply	Need help connecting Linux box to DLink AP I've got a DLink DWL 810+. I connected it to an old Linux box that was last connected directly to the router. The DLink isn't appearing in the Active MAC table for the router. The docs for the DLink say that I need to configure it via the web interface, which is at 192.168.0.30. I can't ping that from the Linux box. Says "Network is unreachable". The Linux box is reporting its IP as 169.254.4.40. I try 'ifdown etho;ifup eth0' and it downs the interface, then tries a DHCPREQUEST which times out, and I no longer have an IP. I'm sure I'm missing an easy step, but I don't know what it is. Any pointers? -- Drew
Post #319,266 by pwhysall 12/29/09 11:23:29 AM Reply	Re: Need help connecting Linux box to DLink AP Manually put the Linux box on the same network as the AP (say, 192.168.0.50/24) and try again. 169.254.x.x is APIPA (automatic private IP addressing) range.
Post #319,268 by drook 12/29/09 11:24:53 AM 12/29/09 11:26:38 AM Reply	How? I thought I needed to, but don't know networking for fuck-all. Nevermind, just looked it up. -- Drew Edited by drook Dec. 29, 2009, 11:26:38 AM EST Expand All History
Post #319,271 by drook 12/29/09 11:46:14 AM Reply	"Destination Host Unreachable" I've got it set static to 192.168.0.50, still not seeing the DLink. And I just reset it to make sure it's got the factory IP. -- Drew
Post #319,272 by boxley 12/29/09 12:02:58 PM Reply	do a tcpdump -i eth0 you should see packets or your network to the PC is horked
Post #319,288 by folkert 12/29/09 8:10:20 PM Reply	Re: "Destination Host Unreachable" What Linux are you using? anything ubuntu/debian /etc/network/interfaces auto eth0 iface eth0 inet static address 192.168.0.50 netmask 255.255.255.0 network 192.168.0.0 broadcast 192.168.0.255 gateway 192.168.0.1 That is how the static setup should be. Once set, then: `ifdown eth0 ; ifup eth0` Then try and ping the device. Assuming you are plugging into it on a network/LAN port and not the WAN port. Once there... you should be good.
Post #319,292 by drook 12/29/09 9:30:46 PM Reply	No joy Still showing "Destination Host Unreachable". I'd really like to fix this before putting it back in their room so I don't have to do this again, but I think I'm reaching the yak shaving stage (http://sethgodin.typ...t_shave_that.html). I have a solution -- I don't like it, but it works -- and I have real work I need to do. -- Drew
Post #319,297 by folkert 12/29/09 11:12:00 PM Reply	Bleah. I have a good sharp almost done knife... sharp enough to deform the tips of my left index finger... Probably good enough for shaving!
Post #319,310 by drook 12/30/09 9:11:10 AM Reply	Have you learned anything? Specifically, have you figured out how to do them in a reasonable amount of time? I really want to tell people about "this guy I know who makes crazy-high-end knives." -- Drew
Post #319,317 by boxley 12/30/09 10:04:54 AM Reply	sniff? high end sniff? :-)
Post #319,323 by drook 12/30/09 11:47:30 AM Reply	Uhhh ... say what? That whooshing sound is whatever your point was clearing my head by a few feet. -- Drew
Post #319,326 by boxley 12/30/09 12:19:12 PM Reply	smelling an opportunity
Post #319,347 by drook 12/30/09 4:05:38 PM Reply	Nah, you wouldn't be interested I takes too much hardware ... stuff you couldn't secure when you move under the bridge. -- Drew
Post #319,348 by boxley 12/30/09 4:36:31 PM Reply	tongs anvil couple of hammers and files too heavy to carry away
Post #319,345 by folkert 12/30/09 3:18:39 PM Reply	Well yes and yes. Yes, its better to start with your bases covered rather than assuming its what you want. Yes, I've discovered that certain pieces of materials aren't exactly what they are supposedly cracked up to be. BUT... the process only will change at the suppliers side of things. He understand about clean up now. Will let me do the clean up rather than a quick splash with a belt sander. But... it seems family stuff is getting in the way. If you'd answer your phone once in a while, we could talk about what you have to look forward too... :P Well maybe not with your girls. Except the Wedding now being planned has sucked out $1K/month for the past two months and will continue to for the next 9 months (or longer) until its done. Bleah. Call me some time after 5PM eastern.. ok?
Post #319,346 by drook 12/30/09 4:04:48 PM Reply	Dude, I never answer the phone Whenever Jenn tells me I got a call from you, if I've chatted with you here that day I assume it's covered. Sorry, bad assumption. I'll give you a call. -- Drew
Post #319,363 by folkert 12/30/09 8:59:58 PM Reply	Naw, its fine. Life has been tough the past month and a bit. Its amazing at how much it throws at you, just when you think you'll have some time to get things together.
Post #319,270 by boxley 12/29/09 11:32:35 AM Reply	that 169.x is what you get when the pc cant find a network its a default put in by the nic so check basic connectivity
Post #319,277 by Another Scott 12/29/09 1:38:49 PM Reply	Sounds familiar... Is that a box I sent you long ago? IIRC, it was fairly easy to set up once you got the numbers set correctly. Note that it's not a router, but a range extender or an Ethernet to WiFi bridge. Your router or wifi access point needs to be able to see it first, I think. Maybe check the comments here (scroll down) - perhaps it'll help a little. http://www.expansys.de/ft.aspx?k=7579 Good luck! Cheers, Scott.
Post #319,278 by drook 12/29/09 3:17:25 PM Reply	Yup, that's it And step 6 is where it fails. With the computer using a static IP, and directly connected to the dwl-810, it doesn't respond to ping at 192.168.0.30. Any configuration steps after that are moot until I can connect to it. I've punted on this and am about to move the computer so I can plug it directly into the router. -- Drew
Post #319,282 by drook 12/29/09 5:32:34 PM Reply	Replugged it ... now how do I reach it (headless)? The keyboard and monitor are still in the other room. I assumed, since I set up a static IP, that I'd be able to SSH into it as soon as it booted. No such luck. So is there a way to reach it, or do I need to haul the monitor in, too? -- Drew
Post #319,283 by static 12/29/09 5:36:18 PM Reply	Did you check that sshd was installed? And remember sshd can take a few minutes for to start up from cold-boot. It's quite late in the boot process, IIRC. Wade. Q:Is it proper to eat cheeseburgers with your fingers? A:No, the fingers should be eaten separately.
Post #319,284 by drook 12/29/09 5:40:59 PM Reply	Had it set up before I ran this box headless for several weeks before moving it to the kids' room where it doesn't have a network connection. I suspect the problem is it's at 192.168.1.50, and the router I'm connected to is set to 192.168.2.1. So if I understand correctly, they're on different segments, and unable to talk to each other? -- Drew
Post #319,285 by pwhysall 12/29/09 6:02:10 PM Reply	Re: Had it set up before Assuming a /24 netmask, your understanding is correct.
Post #319,286 by drook 12/29/09 7:10:03 PM Reply	Did the stupid, simple thing I dragged the monitor and keyboard in from the other room and switched it to DHCP. I'm doing the backup, and will move everything back when it's done. It still bugs me that I couldn't connect to the DLink. Maybe I'll try again while I have a connection and can research things faster than running from room-to-room. -- Drew
Post #319,303 by static 12/30/09 12:06:55 AM Reply	Good plan. :-) Q:Is it proper to eat cheeseburgers with your fingers? A:No, the fingers should be eaten separately.

Welcome to IWETHEY!