Re: tcpdump - laptop

["Hans Steegers" <hsx,AT,dds,DOT,nl>]

James,

>[2003/09/11 21:59:45, 0] nmbd/nmbd_subnetdb.c:create_subnets(240)
>   create_subnets: No local interfaces ! <<=======================<!!!>
>[2003/09/11 21:59:45, 0] nmbd/nmbd.c:main(861)
>   ERROR: Failed when creating subnet lists. Exiting.

There must be something wrong with the interfaces or route table, as nmbd is
stumbling on the local interface and subnets.
I suspect the problem in your routing and/or sub-netting, or the lo
interface is missing...

Please, provide the following information:

1. 'ifconfig' output of ALL your interfaces on the notebook and the
router/gatway.

2. your route tables 'route -n' of both the notebook and router/gateway.

3. the relevant ip-up script of the involved cipe interfaces (only if you
changed something, omit if standard)

4. the settings in your samba configuration file (notebook only) of:
hosts allow =, interfaces =, bind interfaces only = , socket options =

5. Check again with 'netstat -lnpt' for a list of tcp ports listening (139?)

6. Verify that your traffic is going through the tunnel, if connected via
WiFi or LAN, and not by-passing it:
Use tcpdump [-n -i <cipcbX> icmp and host <serveraddress> ] on the cipcb
interface on the router, ping from the notebook to the server.
You should see something like:
10:24:58.289472 192.168.a.x > 192.168.b.y: icmp: echo request (DF)
10:24:58.290441 192.168.b.y > 192.168.a.x: icmp: echo reply (DF)
..
Note: an encrypted CIPE tunnel over Wi-Fi is 128-bit CIPE encryption over an
effectively 104 bit encrypted connection: is your traffic that secret? Or
didn't you set the 128-bit WEB-key?

7. Verify the setting of ip_forward: cat /proc/sys/net/ipv4/ip_forward (just
to be sure, it should say '1').

=

Why no 137/138 ports are listening when nmb is running is a mystery to me.
Anyone any idea?

** For reference:
When I only run NMBD, after stopping SMBD:
# ps ax | grep mbd
  157 ?        S      0:05 /usr/local/samba/bin/nmbd -D
I get the following:
# netstat -lnpu
...
udp        0      0 192.168.x.y:137         0.0.0.0:*             157/nmbd
udp        0      0 0.0.0.0:137             0.0.0.0:*             157/nmbd
udp        0      0 192.168.x.y:138         0.0.0.0:*             157/nmbd
udp        0      0 0.0.0.0:138             0.0.0.0:*             157/nmbd
..
udp        0      0 192.168.x.y:9900        0.0.0.0:* ESTABLISHED
19815/ciped-db
..
If I start SMBD again, I also get 139/tcp listening.
# ps ax | grep mbd
  157 ?        S      0:05 /usr/local/samba/bin/nmbd -D
20875 ?        S      0:00 /usr/local/samba/bin/smbd -D
# netstat -lnpt
...
tcp        0      0 0.0.0.0:139             0.0.0.0:* LISTEN      20875/smbd
...

*** The SMB/CIFS protocol must have been developed in a mental asylum, like
most M$$hit, so I am not going to waste time on it.
I want to restrict my involvement to the CIPE-related issues.
Start nmbd with increasing -d <debug_level> , to get more verbose error
messages, if necessary. Search the Samba mailing lists or 'google' the error
message(s).

And, DO USE A FIREWALL when connected to the internet! Not doing so is
stupid. But wait until this problem is solved, to not complicate matters
further..

Hans Steegers