Doc. # 1-00000559 | |||
---|---|---|---|
Date Updated | 10-26-2018 | Date Created | 09-12-2017 |
Document Type | Knowledge Base | Related OS | |
Related Product | ABDG-BR-DP501/ ABDG-BR-IN5010 |
Do you have an example of how to run a adhoc setup with a ABDG-BR-DP501 to a laptop wireless? | |||
---|---|---|---|
Solution:
I have a laptop with the BR connected to its Ethernet port and built in wireless turned off. My Ethernet LAN connection card is set to static 10.6.0.13 with a subnet of 255.255.255.0 no gateway entered.My ABDG-BR-DP501 unit from the web interface express setup page: Radio On Adhoc SSID=hello Security type=WEP 64 WEP Key 1=goode Ethernet role=bridge WLAN DHCP=disabled Ethernet DHCP=disabled WLAN Static=10.6.0.13 (matches laptop Im connected to) WLAN Subnet MASK=255.255.255.0 (matches laptop Im connected to) WLAN Gateway=0.0.0.0 (matches laptop Im connected to) Ethernet Static IP=10.6.0.2 Ethernet Subnet mask- 255.255.255.0 Port Settings Web Server=8080 Telnet=23 FTP=21 SSH=22 I did not change any other setting On the laptop that I am connecting to via it’s wireless interface card – turned on. I have changed the wireless adapter IP address to static 10.6.0.11 subnet mask 255.255.255.0. On both PC’s I have turned all firewall’s off. They will block the pings. On the PC with the wireless card I created a Adhoc network called hello using WEP64 key = goode I am able to ping the BR units eth IP and Wireless IP from the laptop with the wireless turned on and connected to adhoc. From the pc connected to the BR unit I am able to ping the laptop with the wireless network card turned on. Adhoc is not suggested for the most part because if for some reason power is lost or you go out of range. If one of the device is the network does not see the other device that started the ADHOC network it will try to start it’s own network and will cause the initiator to not be able to connect. It is very unpredicatable.
|