Tag Info

Hot answers tagged

2

The section you should ignore is the Configure Network Address Translation section. In fact if you want to guarantee that wireless clients can't go onto the Ethernet connection do the following: Run sudo nano /etc/sysctl.conf. Scroll to the bottom and add net.ipv4.ip_forward=0 on a new line. Save the file. This will disable ip forwarding on boot up. Run: ...


1

I believe that some, but not all wifi chipsets will allow 2 subinterfaces, one of them in master mode and one of them in client mode. The difficulty is that there is only one radio. The client subinterface needs to search for the SSID it wants to join and set the radio to the same channel as the access point it associates to. Master subinterfaces, on the ...


1

You could take a look at the manpage, and the link in there - http://wireless.kernel.org/en/developers/Regulatory/ $ apropos CRDA crda (8) - send to the kernel a wireless regulatory domain for a given ISO / IEC 3166 alpha2 output of man crda: CRDA(8) Linux ...


1

With just the right help from the comments and a very simple Google search I was able to find a solution and it was even in the original site for Raspberry :) If anyone else ever wonders about the same thing, the solution that worked for me can be found here. It turned out pretty basic, fundamental stuff. TL;DR: disabling the hotplug for the ethernet ...


1

Turns out to be a false warning. To quote from the (now closed) kernel bug report: Alfred Krohmer: If I unterstand your patch correctly it just removes the warning, but it won't actually fix the driver crash this bug report was submitted for. So why mark it as resolved? Emmanuel Grumbach: There is no real bug. The commit message explains this. ...



Only top voted, non community-wiki answers of a minimum length are eligible