Author Topic: Switch to Wifi broke network?  (Read 1748 times)

Offline newbi462

  • Hero Member
  • *****
  • Posts: 629
Switch to Wifi broke network?
« on: August 09, 2012, 12:10:05 AM »
Ok I have a Win box..... it was on the network....

I switch my PCLin from cat 5 to Wifi connection and now the network drives are not there... it is the same network only dif is connection means...

but my "Samba Shares" are empty...

If I open "Access Windows (SMB) shared drives and dir" in "PClin Control Center>Netwrok Sharing" it can find the Win Vista system, but can not find any of the folders just sits there when I click on it. And all my links to my shared folders time out....

any one have any ideas how to get this working once more? Sould not make a dif if the Linux box is on Wired or Wifi....
« Last Edit: August 10, 2012, 01:49:22 PM by newbi462 »

Offline pags

  • Hero Member
  • *****
  • Posts: 2606
  • Keep it clean.
Re: Switch to Wifi broke network?
« Reply #1 on: August 09, 2012, 06:42:43 AM »
Actually, it is more common for wired and wireless on the same internal LAN to be different segments, so depending on the routing employed, it is quite likely that such a switch could cause this kind of break.

Some information you could provide:
1) The IP address of the Linux box when on wired connection.
Code: [Select]
ifconfig
route -n
2) the IP address of the Linux box when on wireless (same commands as above)
3) The IP address of the Windows box
Code: [Select]
ipconfig
route print


Other tests for connectivity would be to use ping.

With the Linux box on the wired connection, ping the Windows box from the Linux box and ping the Linux box from the Windows box.  Do you get replies in both directions?
With the Linux box on the wireless connection, ping the Windows box from the Linux box and ping the Linux box from the Windows box.  Do you get replies in both directions?

Offline newbi462

  • Hero Member
  • *****
  • Posts: 629
Re: Switch to Wifi broke network?
« Reply #2 on: August 09, 2012, 09:42:22 AM »
Actually, it is more common for wired and wireless on the same internal LAN to be different segments, so depending on the routing employed, it is quite likely that such a switch could cause this kind of break.


If you mean the topology.... the computer s connect to a Linksys router... that connect to the internet modem....

Some information you could provide:
1) The IP address of the Linux box when on wired connection.
Code: [Select]
ifconfig
route -n


on this one unfortunately I cannot do this now as the reason the change took place is I had to move the computer, it is not by the router anymore, at least not close enough that I  can plug in a cable :(. However the network is dynamic. Though 90% of the time it was 192.168.1.100, or 192.168.101.... but some times was ....104 or what not... like I said dynamic network ips


2) the IP address of the Linux box when on wireless (same commands as above)


here is the output for the Wireless:

wlan0     Link encap:Ethernet  HWaddr 00:18:39:07:76:AE
          inet addr:192.168.1.101  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::218:39ff:fe07:76ae/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:255791 errors:0 dropped:0 overruns:0 frame:0
          TX packets:193073 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:269413129 (256.9 MiB)  TX bytes:32476964 (30.9 MiB)
          Interrupt:16 Memory:febfe000-fec00000


3) The IP address of the Windows box
Code: [Select]
ipconfig
route print

The win box  is currently 192.168.1.103

Other tests for connectivity would be to use ping.

With the Linux box on the wired connection, ping the Windows box from the Linux box and ping the Linux box from the Windows box.  Do you get replies in both directions?

like I said can not do the cable anymore :(


With the Linux box on the wireless connection, ping the Windows box from the Linux box and ping the Linux box from the Windows box.  Do you get replies in both directions?


on wireless from Linux

[omega@localhost ~]$ ping -c 4 192.168.1.103
PING 192.168.1.103 (192.168.1.103) 56(84) bytes of data.
64 bytes from 192.168.1.103: icmp_req=1 ttl=128 time=57.1 ms
64 bytes from 192.168.1.103: icmp_req=2 ttl=128 time=0.876 ms
64 bytes from 192.168.1.103: icmp_req=3 ttl=128 time=0.855 ms
64 bytes from 192.168.1.103: icmp_req=4 ttl=128 time=0.864 ms

--- 192.168.1.103 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3001ms
rtt min/avg/max/mdev = 0.855/14.941/57.171/24.381 ms
[omega@localhost ~]$


on Windows to linux

Ping statistics for 192.168.1.101
Packets: Sent = 4, Received = 4, Lost = 0<0%. loss>,
Approximate round trip times in milli-seconds:
Minimum = oms, Maximum = 27ms, Average = 10ms


Did not type out the 4 pings, and for get how to copy from Win terminal :)

It is wired because they can clearly see each other, and both are clearly on the network, but cannot see the Windows shard folders, nor manually browse to them using SAMBA


Offline pags

  • Hero Member
  • *****
  • Posts: 2606
  • Keep it clean.
Re: Switch to Wifi broke network?
« Reply #3 on: August 09, 2012, 12:00:04 PM »
OK.  Looks like the wireless and the wired are both on the same segment (192.168.1.x).  Is the Linksys the router for both wired and wireless, or do you have a separate wireless route (acting as a bridge, based on IP assignments).  If it the same device, could there be a setting in it (could one or the other of your networks be considered a DMZ, for security)?

You never gave any routing information.  Could we see that, also.

Linux
Code: [Select]
route -n

Windows
Code: [Select]
route print

Thanks.

Offline newbi462

  • Hero Member
  • *****
  • Posts: 629
Re: Switch to Wifi broke network?
« Reply #4 on: August 09, 2012, 12:14:18 PM »
OK.  Looks like the wireless and the wired are both on the same segment (192.168.1.x).  Is the Linksys the router for both wired and wireless, or do you have a separate wireless route (acting as a bridge, based on IP assignments).  If it the same device, could there be a setting in it (could one or the other of your networks be considered a DMZ, for security)?

no all the same router for both wired and wifi... no DMZ or other sub networks at this level all the systems connect directly to the router...



You never gave any routing information.  Could we see that, also.


Linux
Code: [Select]
route -n


[omega@localhost ~]$ route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.1.0     0.0.0.0         255.255.255.0   U     35     0        0 wlan0
169.254.0.0     0.0.0.0         255.255.0.0     U     35     0        0 wlan0
127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo
0.0.0.0         192.168.1.1     0.0.0.0         UG    35     0        0 wlan0
[omega@localhost ~]$



Windows
Code: [Select]
route print

Thanks.

C:\Users\Big>route print
===========================================================================
Interface List
 11 ...00 1e e5 22 f1 a5 ...... Linksys Wireless-G PCI Network Adapter with Spee
dBooster
 10 ...00 21 85 1e 58 29 ...... Realtek PCIe GBE Family Controller
  1 ........................... Software Loopback Interface 1
 13 ...00 00 00 00 00 00 00 e0  isatap.cfl.rr.com
 12 ...02 00 54 55 4e 01 ...... Teredo Tunneling Pseudo-Interface
 15 ...00 00 00 00 00 00 00 e0  isatap.{80C33C51-2302-451E-ABA0-AE68FD9D4466}
 16 ...00 00 00 00 00 00 00 e0  isatap.{80C33C51-2302-451E-ABA0-AE68FD9D4466}
===========================================================================

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0      192.168.1.1    192.168.1.103     30
        127.0.0.0        255.0.0.0         On-link         127.0.0.1    306
        127.0.0.1  255.255.255.255         On-link         127.0.0.1    306
  127.255.255.255  255.255.255.255         On-link         127.0.0.1    306
      192.168.1.0    255.255.255.0         On-link     192.168.1.103    286
    192.168.1.103  255.255.255.255         On-link     192.168.1.103    286
    192.168.1.255  255.255.255.255         On-link     192.168.1.103    286
        224.0.0.0        240.0.0.0         On-link         127.0.0.1    306
        224.0.0.0        240.0.0.0         On-link     192.168.1.103    286
  255.255.255.255  255.255.255.255         On-link         127.0.0.1    306
  255.255.255.255  255.255.255.255         On-link     192.168.1.103    286
===========================================================================
Persistent Routes:
  None

IPv6 Route Table
===========================================================================
Active Routes:
 If Metric Network Destination      Gateway
  1    306 ::1/128                  On-link
 11    286 fe80::/64                On-link
 11    286 fe80::fc9f:ace9:9cf0:c92e/128
                                    On-link
  1    306 ff00::/8                 On-link
 11    286 ff00::/8                 On-link
===========================================================================
Persistent Routes:
  None

« Last Edit: August 09, 2012, 12:16:07 PM by newbi462 »

Online muungwana

  • Hero Member
  • *****
  • Posts: 6268
Re: Switch to Wifi broke network?
« Reply #5 on: August 09, 2012, 10:53:19 PM »
Ok I have a Win box..... it was on the network....

I switch my PCLin from cat 5 to Wifi connection and now the network drives are not there... it is the same network only dif is connection means...

but my "Samba Shares" are empty...

If I open "Access Windows (SMB) shared drives and dir" in "PClin Control Center>Netwrok Sharing" it can find the Win Vista system, but can not find any of the folders just sits there when I click on it. And all my links to my shared folders time out....

any one have any ideas how to get this working once more? Sould not make a dif if the Linux box is on Wired or Wifi....

what does the output of this command give you?

smbtree -N -d2

The problem is most likely caused by a firewalled samba local master server on one or both of your computers.

Do you have a firewall set up?

Go to your windows computer and turn off its firewall, restart both computers and check to see if the problem is still there.
.. 3 things are certain in life : death, taxes and software bloat ..
.. tell me something i don't know, something i can use as i struggle to reason with the world around me ..

Offline newbi462

  • Hero Member
  • *****
  • Posts: 629
Re: Switch to Wifi broke network?
« Reply #6 on: August 09, 2012, 11:05:38 PM »

what does the output of this command give you?

smbtree -N -d2


[omega@localhost ~]$ smbtree -N -d2
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
added interface wlan0 ip=fe80::218:39ff:fe07:76ae%wlan0 bcast=fe80::ffff:ffff:ffff:ffff%wlan0 netmask=ffff:ffff:ffff:ffff::
added interface wlan0 ip=192.168.1.101 bcast=192.168.1.255 netmask=255.255.255.0
tdb(/var/cache/samba/gencache.tdb): tdb_open_ex: could not open file /var/cache/samba/gencache.tdb: Permission denied
Got a positive name query response from 192.168.1.103 ( 192.168.1.103 )
Got a positive name query response from 192.168.1.103 ( 192.168.1.103 )
WORKGROUP
Got a positive name query response from 192.168.1.103 ( 192.168.1.103 )
        \\BIGGINS
Error connecting to 66.152.109.110 (Success)
Error connecting to 69.16.143.110 (Success)
cli_start_connection: failed to connect to BIGGINS<20> (0.0.0.0). Error NT_STATUS_UNSUCCESSFUL




The problem is most likely caused by a firewalled samba local master server on one or both of your computers.

Do you have a firewall set up?

Go to your windows computer and turn off its firewall, restart both computers and check to see if the problem is still there.

On the Win box I killed Windows Fire Wall.... it says it is off, but you know how Vista is... but when I go in " Windows Fire Wall" it says "Windows Fire Wall is off" even tripples cheacked and rebooted every thing... still no go.

Online muungwana

  • Hero Member
  • *****
  • Posts: 6268
Re: Switch to Wifi broke network?
« Reply #7 on: August 09, 2012, 11:17:05 PM »

what operating system is running on a computer with IP of 192.168.1.103?

open "/etc/samba/smb.conf" make below changes.
Make sure all those below lines are NOT commented out and they have the values below.

Make sure samba server is set to start at boot time.

Turn off all of your computers and start pclinuxos first and then turn on the rest of them after a minute or two

Then run "smbtree -N -d2" and post its output

os level = 254
preferred master = yes
local master = yes

Error connecting to 66.152.109.110 (Success) ????
How do you explain an attempt to connect to a publicly addressable IP address?
.. 3 things are certain in life : death, taxes and software bloat ..
.. tell me something i don't know, something i can use as i struggle to reason with the world around me ..

Offline newbi462

  • Hero Member
  • *****
  • Posts: 629
Re: Switch to Wifi broke network?
« Reply #8 on: August 09, 2012, 11:44:46 PM »

what operating system is running on a computer with IP of 192.168.1.103?

It is Win Vista.



open "/etc/samba/smb.conf" make below changes.
Make sure all those below lines are NOT commented out and they have the values below.


I am assuming you mean the lines you put out of order at the end?

os level = 254
preferred master = yes
local master = yes

i do not have one in that file that is = 254 but have

# OS Level determines the precedence of this server in master browser
# elections. The default value should be reasonable
#   os level = 33

Should I change the "= 33" to "= 254"?

for "preferred master = yes" I have:

# Preferred Master causes Samba to force a local browser election on startup
# and gives it a slightly higher chance of winning the election
#   preferred master = yes

for "local master = yes" I have:

# set local master to no if you don't want Samba to become a master
# browser on your network. Otherwise the normal election rules apply
#   local master = no

So I need to change "= no"to "= yes"?

I am assuming by "NOT commented" you mean remove the "#" from those 3 lines correct?


Make sure samba server is set to start at boot time.

I am 99% sure it is but how would I check?

Turn off all of your computers and start pclinuxos first and then turn on the rest of them after a minute or two

Then run "smbtree -N -d2" and post its output

os level = 254
preferred master = yes
local master = yes


On this bit I want to make sure I am follow your directions correctly but will do. I always boot the Linux box first. I had to do that even when it was wired or got wired results, no clue why...


Error connecting to 66.152.109.110 (Success) ????
How do you explain an attempt to connect to a publicly addressable IP address?

Honestly I have no clue there. I noticed that, not sure what to make of that as it is not even my IP I connect to the inter by,nor is it one I had before?
« Last Edit: August 09, 2012, 11:47:28 PM by newbi462 »

Online muungwana

  • Hero Member
  • *****
  • Posts: 6268
Re: Switch to Wifi broke network?
« Reply #9 on: August 10, 2012, 12:00:05 AM »

Quote
Should I change the "= 33" to "= 254"?

yes, and remove the "#" character that precede the line.

same for the remaining two lines, remove the preceding "#" character and change the option to "yes".

you can check if samba is running and is set to start at boot time by going to pcc services section and look at samba entry. It should say "running" and "start at boot" option should also be set.

you are to modify those lines in place, its easier to edit them in place because comments above them are useful if you get lost or what to know what the options are doing.
.. 3 things are certain in life : death, taxes and software bloat ..
.. tell me something i don't know, something i can use as i struggle to reason with the world around me ..

Offline newbi462

  • Hero Member
  • *****
  • Posts: 629
Re: Switch to Wifi broke network?
« Reply #10 on: August 10, 2012, 12:44:16 AM »
Bingo... while not serve called "samba" there is one called SMB. And no clue how but it was stopped and not set to run at boot.

But the sec I turned it back on everything works once more.

Did not even need to reboot or make the changes to the config..

Thanks a trillion :)

TEMP FIX REBOOTING BROKE EVERY THING
« Last Edit: August 10, 2012, 02:05:35 PM by newbi462 »

Offline newbi462

  • Hero Member
  • *****
  • Posts: 629
Re: Switch to Wifi broke network?
« Reply #11 on: August 10, 2012, 01:55:01 PM »
Ok after rebooting Windows box it stopped working again :(

I made the changes you suggested, since it rebroke,

# set local master to no if you don't want Samba to become a master
# browser on your network. Otherwise the normal election rules apply
   local master = yes

# OS Level determines the precedence of this server in master browser
# elections. The default value should be reasonable
   os level = 254

# Domain Master specifies Samba to be the Domain Master Browser. This
# allows Samba to collate browse lists between subnets. Don't use this
# if you already have a Windows NT domain controller doing this job
#   domain master = yes

# Preferred Master causes Samba to force a local browser election on startup
# and gives it a slightly higher chance of winning the election
   preferred master = yes


and rebooted every thing...

Turn off all of your computers and start pclinuxos first and then turn on the rest of them after a minute or two

Then run "smbtree -N -d2" and post its output



[omega@localhost ~]$ smbtree -N -d2
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
added interface wlan0 ip=fe80::218:39ff:fe07:76ae%wlan0 bcast=fe80::ffff:ffff:ffff:ffff%wlan0 netmask=ffff:ffff:ffff:ffff::
added interface wlan0 ip=192.168.1.101 bcast=192.168.1.255 netmask=255.255.255.0
tdb(/var/cache/samba/gencache.tdb): tdb_open_ex: could not open file /var/cache/samba/gencache.tdb: Permission denied
Got a positive name query response from 192.168.1.103 ( 192.168.1.103 )
Got a positive name query response from 192.168.1.103 ( 192.168.1.103 )
WORKGROUP
Got a positive name query response from 192.168.1.103 ( 192.168.1.103 )
        \\BIGGINS
Error connecting to 66.152.109.110 (Success)
Error connecting to 69.16.143.110 (Success)
cli_start_connection: failed to connect to BIGGINS<20> (0.0.0.0). Error NT_STATUS_UNSUCCESSFUL


so it re broke no clue why? but it is broke once more
« Last Edit: August 10, 2012, 02:02:33 PM by newbi462 »

Offline pags

  • Hero Member
  • *****
  • Posts: 2606
  • Keep it clean.
Re: Switch to Wifi broke network?
« Reply #12 on: August 10, 2012, 02:25:34 PM »
OK.  Looks like the wireless and the wired are both on the same segment (192.168.1.x).  Is the Linksys the router for both wired and wireless, or do you have a separate wireless route (acting as a bridge, based on IP assignments).  If it the same device, could there be a setting in it (could one or the other of your networks be considered a DMZ, for security)?

no all the same router for both wired and wifi... no DMZ or other sub networks at this level all the systems connect directly to the router...



You never gave any routing information.  Could we see that, also.


Linux
Code: [Select]
route -n


[omega@localhost ~]$ route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.1.0     0.0.0.0         255.255.255.0   U     35     0        0 wlan0
169.254.0.0     0.0.0.0         255.255.0.0     U     35     0        0 wlan0
127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo
0.0.0.0         192.168.1.1     0.0.0.0         UG    35     0        0 wlan0
[omega@localhost ~]$



Windows
Code: [Select]
route print

Thanks.

C:\Users\Big>route print
===========================================================================
Interface List
 11 ...00 1e e5 22 f1 a5 ...... Linksys Wireless-G PCI Network Adapter with Spee
dBooster
 10 ...00 21 85 1e 58 29 ...... Realtek PCIe GBE Family Controller
  1 ........................... Software Loopback Interface 1
 13 ...00 00 00 00 00 00 00 e0  isatap.cfl.rr.com
 12 ...02 00 54 55 4e 01 ...... Teredo Tunneling Pseudo-Interface
 15 ...00 00 00 00 00 00 00 e0  isatap.{80C33C51-2302-451E-ABA0-AE68FD9D4466}
 16 ...00 00 00 00 00 00 00 e0  isatap.{80C33C51-2302-451E-ABA0-AE68FD9D4466}
===========================================================================

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0      192.168.1.1    192.168.1.103     30
        127.0.0.0        255.0.0.0         On-link         127.0.0.1    306
        127.0.0.1  255.255.255.255         On-link         127.0.0.1    306
  127.255.255.255  255.255.255.255         On-link         127.0.0.1    306
      192.168.1.0    255.255.255.0         On-link     192.168.1.103    286
    192.168.1.103  255.255.255.255         On-link     192.168.1.103    286
    192.168.1.255  255.255.255.255         On-link     192.168.1.103    286
        224.0.0.0        240.0.0.0         On-link         127.0.0.1    306
        224.0.0.0        240.0.0.0         On-link     192.168.1.103    286
  255.255.255.255  255.255.255.255         On-link         127.0.0.1    306
  255.255.255.255  255.255.255.255         On-link     192.168.1.103    286
===========================================================================
Persistent Routes:
  None

IPv6 Route Table
===========================================================================
Active Routes:
 If Metric Network Destination      Gateway
  1    306 ::1/128                  On-link
 11    286 fe80::/64                On-link
 11    286 fe80::fc9f:ace9:9cf0:c92e/128
                                    On-link
  1    306 ff00::/8                 On-link
 11    286 ff00::/8                 On-link
===========================================================================
Persistent Routes:
  None



Is 192.168.1.1 the same device (from the point of view of the two networks)?  Can you connect to it (with a web browser) from each OS, and let us know if they are the same page(s)?

I'm wondering if it just so happens that your wired and wireless networks are configured with the same (default?) sub-nets, and it is causing some kind of routing conflict...

...can you access the Internet without issue from both devices?

What is the IP of the Wireless Router?

Offline newbi462

  • Hero Member
  • *****
  • Posts: 629
Re: Switch to Wifi broke network?
« Reply #13 on: August 10, 2012, 02:51:36 PM »


Is 192.168.1.1 the same device (from the point of view of the two networks)?  Can you connect to it (with a web browser) from each OS, and let us know if they are the same page(s)?

I'm wondering if it just so happens that your wired and wireless networks are configured with the same (default?) sub-nets, and it is causing some kind of routing conflict...

...can you access the Internet without issue from both devices?

What is the IP of the Wireless Router?

192.168.1.1 is the Wifi Router, so yes I can access it from both devices.... but for security reasons the device is set to only allow access to the ADMIN by wired. but I get the same prompts from both systems. they are both conected to the same router, so no, not 2 networks with the same IP scheme.

And yes both systems can see the internet. I can google and what not from both. Just do not seem to be able to reliably access the shared folders on the Windows system from the PCLinux box

Online muungwana

  • Hero Member
  • *****
  • Posts: 6268
Re: Switch to Wifi broke network?
« Reply #14 on: August 10, 2012, 07:36:35 PM »
Ok after rebooting Windows box it stopped working again :(

I made the changes you suggested, since it rebroke,

# set local master to no if you don't want Samba to become a master
# browser on your network. Otherwise the normal election rules apply
   local master = yes

# OS Level determines the precedence of this server in master browser
# elections. The default value should be reasonable
   os level = 254

# Domain Master specifies Samba to be the Domain Master Browser. This
# allows Samba to collate browse lists between subnets. Don't use this
# if you already have a Windows NT domain controller doing this job
#   domain master = yes

# Preferred Master causes Samba to force a local browser election on startup
# and gives it a slightly higher chance of winning the election
   preferred master = yes


and rebooted every thing...

Turn off all of your computers and start pclinuxos first and then turn on the rest of them after a minute or two

Then run "smbtree -N -d2" and post its output



[omega@localhost ~]$ smbtree -N -d2
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
added interface wlan0 ip=fe80::218:39ff:fe07:76ae%wlan0 bcast=fe80::ffff:ffff:ffff:ffff%wlan0 netmask=ffff:ffff:ffff:ffff::
added interface wlan0 ip=192.168.1.101 bcast=192.168.1.255 netmask=255.255.255.0
tdb(/var/cache/samba/gencache.tdb): tdb_open_ex: could not open file /var/cache/samba/gencache.tdb: Permission denied
Got a positive name query response from 192.168.1.103 ( 192.168.1.103 )
Got a positive name query response from 192.168.1.103 ( 192.168.1.103 )
WORKGROUP
Got a positive name query response from 192.168.1.103 ( 192.168.1.103 )
        \\BIGGINS
Error connecting to 66.152.109.110 (Success)
Error connecting to 69.16.143.110 (Success)
cli_start_connection: failed to connect to BIGGINS<20> (0.0.0.0). Error NT_STATUS_UNSUCCESSFUL


so it re broke no clue why? but it is broke once more
did you check to make sure samba service is also set to start at boot time?

log in to root on the terminal and then run the following commands

service smb restart

smbtree -N -d2

wait for 10 seconds before issuing the second command and post the output of both
.. 3 things are certain in life : death, taxes and software bloat ..
.. tell me something i don't know, something i can use as i struggle to reason with the world around me ..