Bug 2750 - Samba equivalent unicast packet to broadcast and broadcast packet
Summary: Samba equivalent unicast packet to broadcast and broadcast packet
Status: RESOLVED WORKSFORME
Alias: None
Product: Samba 3.0
Classification: Unclassified
Component: nmbd (show other bugs)
Version: 3.0.13
Hardware: All Windows XP
: P3 normal
Target Milestone: none
Assignee: Samba Bugzilla Account
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-05-29 09:53 UTC by Chagin Grigory (dead mail address)
Modified: 2020-12-11 13:29 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Chagin Grigory (dead mail address) 2005-05-29 09:53:42 UTC 
For all samba 2.x and 3.x
  
  I thing, that is small bug.
  If I send not broadcast (Unicast?) packet to broadcast IP of my
  subnet, nmbd answer to this packet and I see two samba-server in my
  subnet (on real IP and on broadcast IP)

  Example:
  Subnet: 192.168.222.0/24
  Samba server on 192.168.222.2

  Scanning by Lnetscan (for Windows):
  //Start of scan
  
  Lserver 192.168.222.2 MAC:xx:xx:xx:xx:xx:xx
  ...
  Lserver 192.168.222.255 MAC:

  //End of scan

  I think, that Samba equivalent unicast packet to 192.168.222.255
  and Broadcast packet.

  Windows is not answer for this packet in difference Samba.

  P.S. Sorry for my bad English.
Comment 1 Björn Jacke 2020-12-11 13:29:26 UTC 
I don't think this is a bug in recent samba versions. If you still see any wrong answers with a recent samba version, can you please reopen this bug and attach a network captture showing the broadcast request and samba's reply that is suspected to be wrong?