[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Wireless AP setup: RTL8188CUS



Scott Ferguson <scott.ferguson.debian.user@gmail.com> writes:
> On 31/01/14 04:53, Csanyi Pal wrote:
> I just bought an USB dongle nano Netis WF-2120 adapter.
> WI1 chip1: Realtek RTL8188CUS
> I want to set it up on my headless Debian Wheezy server as a Wireless
> Access Point. 

I builded the custom kernel version 2.6.39.4-13 with module
rtl8192cu and reboot with this kernel. So the kernel part of the setup
is OK now.

I also have installed the firmware-realtek debian package which contains
the following among others:
Realtek RTL8192CU/RTL8188CU firmware (rtlwifi/rtl8192cufw.bin)

I edited the file
/etc/udev/rules.d/70-persistent-net.rules
and have the following line that determine the wlan0 interface:
# USB device 0x:0x (rtl8192cu)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", \
ATTR{address}=="00:e0:4c:81:92:*", ATTR{dev_id} \
=="0x0", ATTR{type}=="1", KERNEL=="wlan*", NAME="wlan0"

The ATTR{address}=="00:e0:4c:81:92:*" option determine that that
whenever I plug in again this usb wifi adapter to the usb port, I get
always the wlan0 name for this interface. Here is the "*" character is
the relevant, because that part of the mac address changes always, when
one plug in the adapter again and again.

>> Scott Ferguson <scott.ferguson.debian.user@gmail.com> writes:
>> FCC ID: T58WF2120R
>> https://apps.fcc.gov/oetcf/eas/reports/GenericSearchResult \
>> .cfm?RequestTimeout=500

>>>> When I run the command bellow: 
>>>> sudo hostapd -dd /etc/hostapd/hostapd.conf
>>>> I get the messages: random: Trying to read entropy from
>>>> /dev/random Configuration file: /etc/hostapd/hostapd.conf Line 6:
>>>> invalid/unknown driver 'rtl8192sfw' 1 errors found in
>>>> configuration file '/etc/hostapd/hostapd.conf'
>>>> I tried with driver names: rtl8192cu
> FWIW that's the one I'd try (only if the stock module failed would I
> compile one from non-Debian source).
>>>>, rtlwifi to, but without
>>>> any success. Which drivername is walid? How can I find the proper
>>>> drivername for my usb wireless network adapter?

No, I think no.
Regardnig to the web page:
http://wireless.kernel.org/en/users/Documentation/hostapd

<quote>
All new mac80211 based drivers that implement AP functionality are
supported with hostapd's nl80211 driver. 
</quote>

so, I think I must to use the 'nl80211' nema for the driver in the
hostapd.conf file.

However, I'm still trying to set this to work. I'm trying to test
hostapd by using the file hostapd-minimal.conf:
interface=wlan0
driver=nl80211
ssid=test
channel=1
bridge=br0
<end of file>

and when I run the following command:

csanyipal@b2:~$ sudo hostapd /etc/hostapd/hostapd-minimal.conf 
Configuration file: /etc/hostapd/hostapd-minimal.conf
rfkill: Cannot open RFKILL control device
Could not set interface mon.wlan0 flags: No such device
nl80211: Failed to set interface wlan0 into AP mode
nl80211 driver initialization failed.

but does'n lose the ssh connection anymore with Bubba Two. :)

Now I have the followings in my interfaces file:
auto lo br0
iface lo inet loopback

# Internet on eth0
allow-hotplug eth0
iface eth0 inet manual

# wifi on wlan0
allow-hotplug wlan0
iface wlan0 inet manual

# Bridge setup
# for dhcp address
iface br0 inet dhcp
bridge_ports eth0 wlan0

# dns-* options are implemented by the resolvconf package, if installed
# I want to remain my wired LAN
# LAN on eth1
allow-hotplug eth1
iface eth1 inet static
    address 192.168.10.1
    netmask 255.255.255.0
    network 192.168.10.0
    broadcast 192.168.10.255
    gateway 192.168.10.1
    dns-nameservers 192.168.10.1
    dns-search localdomain
<end of file>

With this setup I can't only reach the Internet, but can to ssh into
Bubba Two.

The command sudo ifconfig gives to me the followings:
br0       Link encap:Ethernet  HWaddr 00:22:02:00:07:3c  
          inet addr:95.85.167.81  Bcast:95.85.167.255
          Mask:255.255.252.0
          inet6 addr: fe80::222:2ff:fe00:73c/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:7577 errors:0 dropped:0 overruns:0 frame:0
          TX packets:58 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:360740 (352.2 KiB)  TX bytes:8581 (8.3 KiB)

eth0      Link encap:Ethernet  HWaddr 00:22:02:00:07:3c  
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:7577 errors:0 dropped:0 overruns:0 frame:0
          TX packets:57 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:588072 (574.2 KiB)  TX bytes:8047 (7.8 KiB)
          Base address:0x8000 

eth1      Link encap:Ethernet  HWaddr 00:22:02:00:07:3d  
          inet addr:192.168.10.1  Bcast:192.168.10.255
          Mask:255.255.255.0
          inet6 addr: fe80::222:2ff:fe00:73d/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:3116 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4157 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:318666 (311.1 KiB)  TX bytes:343364 (335.3 KiB)
          Base address:0xc000 

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:2524 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2524 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:215081 (210.0 KiB)  TX bytes:215081 (210.0 KiB)

wlan0     Link encap:Ethernet  HWaddr 00:e0:4c:81:92:0e  
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)


How can I setup my home network so I can use wifi AP and the eth1 LAN at
same time?

What can I do further to get this works?
Any advices will be appreciated!

-- 
Regards from Pal


Reply to: