Hi! Some general question + Wifi USB Realtek RTL8191S

[matzi]

I noticed another difference comparing our ifconfig outputs. Mine shows ip4 and ip6 data on eth0. Yours doesn't

root@fvdwsl-base:/ # ifconfig
eth0 Link encap:Ethernet HWaddr 00:D0:4B:91:XX:XX
inet addr:192.168.178.200 Bcast:192.168.178.255 Mask:255.255.255.0
inet6 addr: fe80::2d0:4bff:fe91:71ff/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:770 errors:0 dropped:0 overruns:0 frame:0
TX packets:190 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:75183 (73.4 KiB) TX bytes:13614 (13.2 KiB)
Interrupt:11

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:407 errors:0 dropped:0 overruns:0 frame:0
TX packets:407 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:37343 (36.4 KiB) TX bytes:37343 (36.4 KiB)

wlan0 Link encap:Ethernet HWaddr 7C:DD:90:16:XX:XX
inet addr:192.168.178.28 Bcast:192.168.178.255 Mask:255.255.255.0
inet6 addr: fe80::7edd:90ff:fe16:eee9/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1212 errors:0 dropped:0 overruns:0 frame:0
TX packets:34 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:221656 (216.4 KiB) TX bytes:3223 (3.1 KiB)

[fvdw]

wlan not operational

I don't understand in scan without lan cable it mentions the mac of your dongle (so to see) and it has an ip, so what do you mena with not functional

my ifconfig with lan cable connected

Code: Select all

root@fvdwsl-5big2:/ # ifconfig
eth0      Link encap:Ethernet  HWaddr 00:D0:xxxxxxxxxx
          inet addr:192.168.1.188  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::2d0:4bff:fe93:772/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1748 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1698 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:143207 (139.8 KiB)  TX bytes:143970 (140.5 KiB)
          Interrupt:11

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:443 errors:0 dropped:0 overruns:0 frame:0
          TX packets:443 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:37607 (36.7 KiB)  TX bytes:37607 (36.7 KiB)

wlan0     Link encap:Ethernet  HWaddr 64:D1:xxxxxxxx
          inet addr:192.168.1.173  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::66d1:a3ff:fe18:e5cd/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:4177 errors:0 dropped:3 overruns:0 frame:0
          TX packets:233 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

root@fvdwsl-5big2:/ #

if without lan cable connected see previous post

I noticed another difference comparing our ifconfig outputs. Min show ip4 and ip6 data on eth0. Mine doesn't

it is not clear what you want to say ?? your has ipv6 output (my eth0 also has it when connected)
When no cable is connected of course eth0 cannot have ip4 nor ipv6 address

ps this evening I will take a nwsp2 out of cupboard

ps which kernel do you run ?

[matzi]

Seems you were too fast for me in reading and answering. I try to order things:
1. Sorry I did not regard that your ifconfig output was taken with no eth0 connection, so of course there is no ip4 or ip6 data. Question solved.
2. Non functional for me means that I cannot open the webinterface under this IP
3. Kernel version is 188 It is the last one you gave me. I am pretty sure it is running but how can I ask that from the system?
4. Please review my last post on page 16. I edited (amanded) that question about ports.

[fvdw]

Edit:

All 100 scanned ports on 192.168.178.28 are filtered


Does that mean the IP is fine but just no Port open?

as you can see on my nmap scan it should list all "normal" ports like 22 and 80

The kernel version you can see in the web interface in system information window

ps I am setting up the nwsp2

[matzi]

The kernel is 188 indeed.

So the main difference between our systems is how the ports appear. I have no idea how i could change that, at least I did not play on that.
Waiting for your findings on your nwsp2.

[fvdw]

the nwsp is giving the same result as the 5big2

output form run without lan cable connected
ps I connected using the wlan ip address just fine

Code: Select all

   /share/1000/fvdw/cron-boot/wlan.sh
udhcpc (v1.21.0) started
Setting IP address 0.0.0.0 on wlan0
Sending discover...
Sending discover...
Sending select for 192.168.1.173...
Lease of 192.168.1.173 obtained, lease time 86400
Setting IP address 192.168.1.173 on wlan0
Deleting routers
Adding router 192.168.1.1
Recreating /etc/resolv.conf
 Adding DNS server 192.168.1.1


Code: Select all

root@nwsp2-lite:/ # ifconfig
eth0      Link encap:Ethernet  HWaddr 00:D0:xxxxxxxx
          UP 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)
          Interrupt:11

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:22 errors:0 dropped:0 overruns:0 frame:0
          TX packets:22 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:396 (396.0 B)  TX bytes:396 (396.0 B)

wlan0     Link encap:Ethernet  HWaddr 64:D1:xxxxxx
          inet addr:192.168.1.173  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::66d1:a3ff:fe18:e5cd/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:4715 errors:0 dropped:10 overruns:0 frame:0
          TX packets:384 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

root@nwsp2-lite:/ #

nmap quickscan

Code: Select all

Starting Nmap 6.25 ( http://nmap.org ) at 2014-01-04 22:16 West-Europa (standaardtijd)

Nmap scan report for 192.168.1.173
Host is up (0.013s latency).
Not shown: 95 closed ports
PORT    STATE SERVICE
22/tcp  open  ssh
80/tcp  open  http
111/tcp open  rpcbind
139/tcp open  netbios-ssn
445/tcp open  microsoft-ds

MAC Address: 64:D1:xxxxxxx (Sitecom Europe BV)

Nmap done: 1 IP address (1 host up) scanned in 17.08 seconds

kernel used

Code: Select all

root@nwsp2-lite:/ # uname -a
Linux nwsp2-lite.local 3.9.5 #188 PREEMPT Sat Nov 2 19:14:41 GMT+1 2013 armv5tel unknown unknown GNU/Linux

so everything seems to works fine

[matzi]

Could you post an nmap scan of your wireless ip with active eth0 connection? Let us look for the MAC and interface manufacturer in this case.

[fvdw]

here you go, I just plugged in the LAN cable

Code: Select all

root@nwsp2-lite:/ # ifconfig
eth0      Link encap:Ethernet  HWaddr 00:D0:xxxxxxxx
          inet addr:192.168.1.136  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::2d0:4bff:fe91:1c7/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:797 errors:0 dropped:0 overruns:0 frame:0
          TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:54038 (52.7 KiB)  TX bytes:1282 (1.2 KiB)
          Interrupt:11

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:49 errors:0 dropped:0 overruns:0 frame:0
          TX packets:49 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:882 (882.0 B)  TX bytes:882 (882.0 B)

wlan0     Link encap:Ethernet  HWaddr 64:D1:xxxxxxxx
          inet addr:192.168.1.173  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::66d1:a3ff:fe18:e5cd/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:11476 errors:0 dropped:23 overruns:0 frame:0
          TX packets:1175 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

root@nwsp2-lite:/ #

nmap scan wlan0

Code: Select all

Starting Nmap 6.25 ( http://nmap.org ) at 2014-01-04 22:41 West-Europa (standaardtijd)

Nmap scan report for 192.168.1.173

Host is up (0.0020s latency).
Not shown: 95 closed ports
PORT    STATE SERVICE
22/tcp  open  ssh
80/tcp  open  http
111/tcp open  rpcbind
139/tcp open  netbios-ssn
445/tcp open  microsoft-ds
MAC Address: 00:D0:4B:91:01:C7 (LA CIE Group S.A.)

Nmap done: 1 IP address (1 host up) scanned in 17.04 seconds

yep now it is showing the eth0 mac

I had a putty window open via wlan0 (connected before the putting in the LAN cable) it remains working after plugging in.

Now disconnection LAN cable again (of course eth0 info will remain visible in ifconfig)
Putty connection via wlan keeps working (so wireless is up
nmap scan

Code: Select all

Starting Nmap 6.25 ( http://nmap.org ) at 2014-01-04 22:46 West-Europa (standaardtijd)

Nmap scan report for 192.168.1.173

Host is up (0.0082s latency).
Not shown: 95 closed ports
PORT    STATE SERVICE
22/tcp  open  ssh
80/tcp  open  http
111/tcp open  rpcbind
39/tcp open  netbios-ssn
445/tcp open  microsoft-ds

MAC Address: 64:D1:xxxxxxx (Sitecom Europe BV)

Nmap done: 1 IP address (1 host up) scanned in 17.06 seconds

[fvdw]

this is status info of wlan0
maybe helpful

Code: Select all

root@nwsp2-lite:/ # wpa_cli status
Selected interface 'wlan0'
bssid=removed-this-info-is-mac router
ssid=removed also is wlan name transmitted by router
id=0
mode=station
pairwise_cipher=CCMP
group_cipher=TKIP
key_mgmt=WPA2-PSK
wpa_state=COMPLETED
ip_address=192.168.1.173
address=64:d1:xx:xx:xx
root@nwsp2-lite:/ #

[matzi]

So we have pretty much the same setup and findings beside of the closed ports. I assume when all ports are closed there is no traffic possible and that might cause the router to drop the connection. I noticed we are using different routers (D-Link - Fritzbox). What about firewalls? Is there something in your software that can alert firewalls? Fritzbox has no configurable firewalls. What I could do is trying an ols Siemens Router (But not tonight..)