The SMC barricade is essentially the same product but in a different case. Though of course there are probably some firmware differences. I started to think about trying to jam the SMC firmware on there, but I've heard that although you can do that, D-link has fixed it so you then can't go back. Sigh. Anyway, its on the way back and as I said, I have decided to roll my own. Chris Feist wrote: > You might want to try the SMC barricade, I've bought about 5 of them for > various people and they work pretty good. > > Chris > > On Mon, Mar 25, 2002 at 11:05:26AM -0600, Steve Hanson wrote: > >>Well - >>Just as a follow up - >>Some time over the weekend this silly box started blowing its brains out >>completely. The wireless functions stopped working - even weirder - the >>wireless configuration options disappeared from the menus. I've read >>this complaint from other people. >> >>So I gave up - it had a LOT of functionality and was really cheap -but >>it appears that at least the one I had was a POS. I boxed it up, it's >>going back to Amazon today. >> >> >> >>Steve Hanson wrote: >> >>>Okay - anybody have any light to shed on this? >>> >>>I just bought a DI-713p D-link wireless gateway, thinking it'd make my >>>life easier :-). >>> >>>Some of it works fine. I can hook its built-in switch to my machines >>>and I can connect to it from my wireless cards just fine. >>> >>>But I can't get an IP address from my ISP. My DSL service is pretty >>>straightforward - you plug a machine into the DSL modem and set it up >>>for DHCP and in general it's worked just fine. Until I put in this box. >>>It never gets a DHCP address. It tries, but it seems to keep on asking >>>for an address that my ISP won't give it - the log looks like this: >>> >>>WAN Type: Dynamic IP Address (2.57 build 3a) >>>Display time: Sat 23 Mar 2002 03:39:41 PM CST >>> >>>Sat 23 Mar 2002 03:38:39 PM CST 192.168.0.2 login successful >>>Sat 23 Mar 2002 03:39:28 PM CST DHCP:discover() >>>Sat 23 Mar 2002 03:39:28 PM CST DHCP:offer(64.33.170.129) >>>Sat 23 Mar 2002 03:39:28 PM CST DHCP:request(64.33.194.246) >>>Sat 23 Mar 2002 03:39:28 PM CST DHCP:nak >>>Sat 23 Mar 2002 03:39:32 PM CST DHCP:discover() >>>Sat 23 Mar 2002 03:39:32 PM CST DHCP:offer(64.33.170.129) >>>Sat 23 Mar 2002 03:39:32 PM CST DHCP:request(64.33.194.246) >>>Sat 23 Mar 2002 03:39:32 PM CST DHCP:nak >>>Sat 23 Mar 2002 03:39:35 PM CST DHCP:discover() >>>Sat 23 Mar 2002 03:39:35 PM CST DHCP:offer(64.33.170.129) >>>Sat 23 Mar 2002 03:39:35 PM CST DHCP:request(64.33.194.246) >>>Sat 23 Mar 2002 03:39:35 PM CST DHCP:nak >>> >>>Eventually it seems to give up on logging, although the DHCP chatter >>>seems to go on forever. >>> >>>I've sent in a request to D-Link support, but past experience leads me >>>to believe that they will read me the couple of pages in the lousy >>>manual that apply, and then tell me there must be somethign wrong with >>>my computer. >>> >>>Anyway, I'm about ready to box it up and send it back to Amazon. >>> >>>And yes, it has the latest firmware revision. I even tried some older >>>ones. >>> >>> >>>_______________________________________________ >>>Twin Cities Linux Users Group Mailing List - Minneapolis/St. Paul, >>>Minnesota >>>http://www.mn-linux.org >>>tclug-list at mn-linux.org >>>https://mailman.mn-linux.org/mailman/listinfo/tclug-list >> >> >>_______________________________________________ >>Twin Cities Linux Users Group Mailing List - Minneapolis/St. Paul, Minnesota >>http://www.mn-linux.org >>tclug-list at mn-linux.org >>https://mailman.mn-linux.org/mailman/listinfo/tclug-list > > _______________________________________________ > Twin Cities Linux Users Group Mailing List - Minneapolis/St. Paul, Minnesota > http://www.mn-linux.org > tclug-list at mn-linux.org > https://mailman.mn-linux.org/mailman/listinfo/tclug-list