Atheros AR9485
-
I would expect that work without any additional components, though I've never tried that personally. If the card is recognised and you are seeing ath0 as an assignable interface it should only be a matter of configuring it correctly.
Steve
-
i got it to appear as "WAN(wan) -> ath0_wlan0 -> " however no IP is assigned to it and im not sure how to configure it cause I can't seem to log into the webgui cause nothing can detect it.
-
Ah OK you'll definitely have to configure it to allow it to connect. Do you not have a LAN interface, an Ethernet port on the laptop?
I would normally expect to connect to the webgui via the LAN and configure the WAN wifi connection that way.
Steve
-
i actually do have a ethernet cable running out of the laptop, do i just hook the ethernet up to my PC like I would do with a regular router or switch?
-
Yes, assuming it's a Gigabit NIC. If it's a 10/100 NIC it probably doesn't support auto MDX and you may need a cross over cable for direct connection. A switch in between would solve that though if it doesn't show a link.
That NIC is assigned as the LAN interface then? If not you will need to assign it from the console.
Steve
-
yes it is it currently is "LAN(lan) -> re0 -> v4: ip"
-
I was able to access the webgui with a direct connection from the laptop (console) to another laptop (tester). i also manage to figure out that through shell (option 8) i can see my galaxy hotspot however I am utterly lost at this point on how to configure WAN to detect this device. I'm assuming it have to do with the MAC address but I'm afraid I might break something without guidance.
I'm also getting spammed by "ar9300_Stub_GetAntennaSwitch [GetCTSTimeout]: called" a lot when in the dash -
I assume you are seeing "ar9300_Stub_GetAntennaSwitch [GetCTSTimeout]: called" on the console rather than in the webgui dashboard? That would be unusual to see any sort of message like that there.
It may be purely cosmetic, just a warning rather than something that will prevent this working.
All the configuration of the WAN should be done through the webgui. If you make changes using the command shell at the console they will be lost at the next boot.
First go to Interfaces > (assign) and make sure the WAN is assigned as the ath0 interface. There should be only one variant of that available to assign.
Then go to Interfaces > WAN and configure the wireless part.
It needs to be in Infrastructure mode to connect to an access point (your hot spot in this case). You will need to configure the other settings to match whatever you set on the phone.
An alternative here might be to use a USB connection to your phone if it supports that.
Steve
-
Yes the spam is just flooding my console now that I setup the WAN I'm being spammed with
ath_reset_grablock: didn't finish after 10 iterations \n warning recursive reset path \n concurrent reset! Danger! -
Hard to say what causes those errors. They certainly can be caused by misconfiguration though. Can we see screenshots of your WAN config? Redact the WPA key obviously. ;)
Steve
-
Hey stephen, sorry for the uber later reply. I haven't been at home to work on this project but here are my settings untouched from since the last post.
http://prnt.sc/drmedu
http://prnt.sc/drmei0
http://prnt.sc/drmeky
http://prnt.sc/drmeo3
http://prnt.sc/drmesi -
What IP does the phone hotspot hand out ?
If it's a RC1918 address range your blocking it on the WAN interface, check the last screenshot.
-
This doesn't seem to be the problem my IP from the hotspot starts with 208 so from what I read wikipedia it seems to be out the range of RC1918
-
No need to apologise about replying late. Unfortunately I'm the master or late replies. ;)
Still better late than never…..
You may need to force WME iod the access point is using it.
You may need to set the channel specifically.
If you go to Status > Wireless and scan does it detect the hotspot? Or any wifi?
Steve
-
Strangely it no longer detect the s6, even if I do "ifconfig ath0_wlan0 scan" before it showed the s6 as an accessible device
edit: nvm im stupid it was set to 5.0 ghz when I changed it back to 2.4 ghz it is able to detect the hotspot -
You were able to connect OK and use it as a WAN then?
Steve
-
No i was not the same error is still showing up
-
Hmm, possibly just some combination of hardware that isn't supported then. :-\
Steve
