Networking :: Setting with a routeur

Quote (rlara333 @ May 29 2004,03:11)

Hello, I too have a DLink 614 and have been able to use the net with DSL on every computer I have tried with the auto detection of DSL. If you have other computers available at home try DSL on these. It does seem to be a problem with your NIC; but I have never had DSL not recognize one of mine. Look in the config utility of your router and see if it sees your DSL box. If it is not there with an asigned IP, your problem is most likely with your DSL box. Try running DSL w/o restore to see if the auto-detect for the network gives you any probs.
God Bless
rlara333

I am trying to use a D-Link 614+ WAP/router as well. I am using a D-Link DWL-122 as client (USB) card. I know the pair work well running Windows 98SE on the client, so hardware is working fine.

I can use "ndiswrapper" to wrapper either of the Windows drivers which come with the client card, followed by use of "prism2" (both come with DSL 0.8.2) - and then the WAP/router sees the client card make contact (reports its MAC address.)
DSL's iwconfig can be used to see the MAC address and other things about the WAP/router.

The one trick I needed was to plug in the client USB card AFTER DSL boots. (This seems to be a problem with some cards based on the PRISM 2.5 chip.)

But then I fail. I cannot figure out how to get DHCP to work. The WAP/router never reports any DHCP requests, much less successes, from the DSL client card. It sure doesn't work using either "pump -i wlan0" or the netcardconfig tool (which calls wlcardconfig in turn.) One can use netcardconfig to assign a static (non-DHCP) IP address to wlan0 (as reported by ifconfig). But even when you FORCE a static DHCP association between the same IP address and the client card MAC address on the WAP/router, the WAP and client cannot connect via IP. (Ping fails from both ends.)

Odd behavior - if you manually set up the routing table so: (192.168.0.1 is the wireless address the WAP/router uses)
route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0 * 255.255.255.0 U 0 0 0 wlan0
default 192.168.0.1 0.0.0.0 UG 0 0 0 wlan0

the first table entry prints out at once, but the second entry only does so after a delay of many seconds - as if it is trying to do something, not just looking at a table. Also, if you use it, pump seems to be doing SOMETHING - it sures clears out the routing table reported upon by route, if you had previously set it up manually.

I'd appreciate any suggestions.
Thanks

I am stilll trying to use a D-Link 614+ WAP/router and a D-Link DWL-122 as client (USB) card.

I just noticed that DSL 0.8.2 may have native support for the D-Link DWL-122. Sure enough, when I do the following:

insmod wlan
insmod prism_usb

and then run the "prism2" utility, again the WAP/router sees the client card connect. However, AGAIN (as with alternate use of wrappered Windows drivers above) I find that "pump -i wlan0" fails in exactly the same way. (Minimal success AGAIN requires that one plug the USB card in AFTER DSL boots.)

Does this give you a hint about my problem? Are there any diagnostics I can run to watch what "pump" is trying to do? Apparently, the WAP sees NO DHCP request, for it logs such, even if they do not succeed!

RSVP, thanks!

P.S. For fun here is some of the kernel ring buffer (via dmesg)
[I plug in the DWL-122 and generate the next line]
hub.c: new USB device 00:07.2-1, assigned address 3
ds: no socket drivers loaded!
ident: nic h/w: id=0x8026 1.0.0
ident: pri f/w: id=0x15 1.1.3
ident: sta f/w: id=0x1f 1.7.1
MFI:SUP:role=0x00:id=0x01:var=0x01:b/t=1/1
CFI:SUP:role=0x00:id=0x02:var=0x02:b/t=1/1
PRI:SUP:role=0x00:id=0x03:var=0x01:b/t=1/4
STA:SUP:role=0x00:id=0x04:var=0x01:b/t=1/12
PRI-CFI:ACT:role=0x01:id=0x02:var=0x02:b/t=1/1
STA-CFI:ACT:role=0x01:id=0x02:var=0x02:b/t=1/1
STA-MFI:ACT:role=0x01:id=0x01:var=0x01:b/t=1/1
Prism2 card SN: 000000000000
p80211knetdev_hard_start_xmit: Tx attempt prior to association, frame dropped.
linkstatus=ASSOCFAIL (unhandled)
linkstatus=CONNECTED
skb_ether_to_p80211: Host en-WEP failed, dropping frame (-3).
NETDEV WATCHDOG: wlan0: transmit timed out
wlan0 rx pipe reset complete.
wlan0 tx pipe reset complete.
skb_ether_to_p80211: Host en-WEP failed, dropping frame (-1).
NETDEV WATCHDOG: wlan0: transmit timed out
wlan0 rx pipe reset complete.
wlan0 tx pipe reset complete.
NETDEV WATCHDOG: wlan0: transmit timed out
wlan0 rx pipe reset complete.
wlan0 tx pipe reset complete.
NETDEV WATCHDOG: wlan0: transmit timed out
wlan0 rx pipe reset complete.
wlan0 tx pipe reset complete.
NETDEV WATCHDOG: wlan0: transmit timed out
wlan0 rx pipe reset complete.
wlan0 tx pipe reset complete.

May I recommend a firewall release similar to DSL, the only thing is that it is a HD install only system

SmoothWall Express 2.0

Here is how I have my network setup behind the SmoothWall at my house

Brian
AwPhuch

docdtv - try using

modprobe prism2_usb prism2_doreset=1

before the wlanctl-ng/pump commands described elswhere in the forum

This works for me using a D-LinK DWL-122 Ver A1 with D-Link DL-614+ Revision A (2 antenna) combination

Ah...you are trying to get your wireless card to connect to your network...sorry

Is DSL not finding the correct drivers??

Brian
AwPhuch

Next Page...
original here.