Hi Igor,

 

nice idea to open this board

 

i have a problem with my wireless connection using your jessie image with kernel 4.0.4 (newest release right now).

 

at the first start i use a wired connection to connect via SSH - this works without any problems.

Next step: configure wireless connection

 

My /etc/network/interfaces looks like this:

auto eth0
iface eth0 inet static
address 192.168.178.150
netmask 255.255.255.0
# hwaddress ether # if you want to set MAC manually
# pre-up /sbin/ifconfig eth0 mtu 3838 # setting MTU for DHCP, static just: mtu 3838
#
# Wired adapter #2
#auto eth1
# iface eth1 inet dhcp
# hwaddress ether # if you want to set MAC manually
# pre-up /sbin/ifconfig eth0 mtu 3838 # setting MTU for DHCP, static just: mtu 3838
#
# Wireless adapter #1
auto wlan0
allow-hotplug wlan0
iface wlan0 inet static
address 192.168.178.151
netmask 255.255.255.0
gateway 192.168.178.1
wireless-power off
wpa-ssid ###############
wpa-psk ############
dns-nameservers 192.168.178.1 8.8.8.8 8.8.4.4
# to generate proper encrypted key: wpa_passphrase yourSSID yourpassword
#
# Local loopback
auto lo
iface lo inet loopback

So i use the static 192.168.178.150 IP for wired connection and 151 for wireless connection.

Then i do a reboot. Result: i can connect via 150 and 151 ip adress. thats ok, because both are connected.

BUT: as soon as i disconnect the ethernet cable, im not able to connect via wireless connection to 192.168.178.151

when i connect the ethernet cable again -> both are working again O_o

 

ifconfig output:

eth0 Link encap:Ethernet HWaddr 02:4b:02:c1:63:11
inet addr:192.168.178.150 Bcast:192.168.178.255 Mask:255.255.255.0
inet6 addr: fe80::4b:2ff:fec1:6311/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:251 errors:0 dropped:0 overruns:0 frame:0
TX packets:386 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:18962 (18.5 KiB) TX bytes:36416 (35.5 KiB)
Interrupt:45

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:65536 Metric:1
RX packets:10 errors:0 dropped:0 overruns:0 frame:0
TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:740 (740.0  TX bytes:740 (740.0 

wlan0 Link encap:Ethernet HWaddr 98:3b:16:5a:8c:24
inet addr:192.168.178.151 Bcast:192.168.178.255 Mask:255.255.255.0
inet6 addr: fe80::9a3b:16ff:fe5a:8c24/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:535 errors:0 dropped:36 overruns:0 frame:0
TX packets:149 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:52419 (51.1 KiB) TX bytes:13916 (13.5 KiB)

iwconfig output:

wlan0 IEEE 802.11bgn ESSID:"###########"
Mode:Managed Frequency:2.452 GHz Access Point: 34:31:C4:89:21:CA
Bit Rate=65 Mb/s Tx-Power=1496 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality=70/70 Signal level=-38 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

i just dont get it....everything looks fine, but it just doesnt work. even my router is able to recognize both IPs correcty...

 

do you have an idea? i need to use the wireless connection on this cubietruck..

Disable (commend out) eth0 and boot only with wlan0 and you should be fine.

 

If you want to have so called backup or notebook mode - to work with any connection in "plug and play" mode  - than you need to use bonding. There is one example configuration and I hope it works in kernel 4.x ... I was testing this only on 3.4.x

Thanks Igor, im gonna try this later.

 

This is a little bit strange...because right now the CT is running with the same configuration..just an older release of your image with kernel 3.4.x.

There are many confusions which I am trying to merge. A lot has been done in this matter but still.

 

If you are using Jessie and you want to establish AP you will need to create additional file in:

/etc/modprobe.d

nano local.conf 

options bcmdhd op_mode=2

And this is needed only on old 3.4 kernel

 

This is how you check if your CT adapter is in proper mode - 0 is default:

systool -m bcmdhd -v | grep op_mode

Your solution works...i disabled eth0 and everything is fine. thank you!

 

i dont need AP mode..i am just confused that exactly the same config with enabled eth0 works on kernel 3.4.x wheezy.

 

4.0.4 jessie doesnt allow me to run both adapters at the same time (without bonding).

Just for Information:

 

Debian Jessie with 4.0.4 Kernel crashes completely (freeze) when using the last nightly build of tvheadend and watching something via tvheadend with kodi

Not recommended

 

greetings