| To: | "CIPE-list" <cipe-l,AT,inka,DOT,de> |
| Subject: | Re: tcpdump - laptop -2- |
| From: | "Hans Steegers" <hsx,AT,dds,DOT,nl> |
| Date: | Fri, 12 Sep 2003 17:41:29 +0200 |
| Reply-to: | "Hans Steegers" <steegers,AT,steegers,DOT,nl> |
James, >It's "1" on the firewall and "0" on the notebook, as expected. Since there are two external network interfaces: # echo "1" > /proc/sys/net/ipv4/ip_forward could help. See what happens. ** Samba config: >> 4. the settings in your samba configuration file (notebook only) of: >> hosts allow =, interfaces =, bind interfaces only = , socket options = Try: * specify the interfaces: (you can specify by device or by network..) interfaces = cipcb0 lo bind interfaces only = yes * specify some sane socket options socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 ** Run the samba test program testparm to check your smb config: # testparm /path/to/smb.conf There is a text file DIAGNOSIS.TXT describing step-by-step how to diagnose problems with Samba. Consult it. An older version is available at: http://us3.samba.org/samba/ftp/docs/textdocs/DIAGNOSIS.txt (And start the nmbd daemon in debug mode, to get more verbose output). ** Samba may have problems with the 255.255.255.255 netmasks on your cipcb0 and/or ppp0 devices, but hopefully testparm will tell you. ** Was SMBD running? And how-the-hell could you access smb-shares on your notebook without smbd/nmbd running and without ports 137,138,139 somehow active?? __________________________________________ Hans Steegers