Reason for Ierrs in netstat

[Frank Wille]

Hi,

one of our servers has some network issues. Symptoms are: Bad ping (twice
as high as comparable machines on the same net), packet loss and increasing
number of Ierrs in "netstat -i".

Is there any chance I can find out the reason behind those Ierrs?


I rebooted the system a few hours ago, and there are some Ierrs again
already:

tethys# netstat -i
Name  Mtu   Network   Address  Ipkts IerrsOpkts Oerrs Colls
wm0   1500  00:30:48:xx:xx:xx  2385235   714  1996966 0 0
[...]


Some more information (system ist running NetBSD/amd64 6.1.5):

wm0 at pci7 dev 0 function 0: Intel i82573E IAMT (rev. 0x03)
wm0: interrupting at ioapic0 pin 16
wm0: PCI-Express bus
wm0: 256 word (8 address bits) SPI EEPROM
wm0: Ethernet address 00:30:48:xx:xx:xx
makphy0 at wm0 phy 1: Marvell 88E Gigabit PHY, rev. 2


wm0: flags=8843 mtu 1500

capabilities=7ff80

enabled=3f80
address: 00:30:48:xx:xx:xx
media: Ethernet autoselect (100baseTX 
full-duplex,flowcontrol,rxpause,txpause)
status: active
inet 212.62.xx.xx netmask 0xfff8 broadcast 212.62.xx.xx
inet6 fe80::230:48ff::%wm0 prefixlen 64 scopeid 0x1

-- 
Frank Wille

Re: SMB

[Patrick Welche]

On Thu, Feb 22, 2018 at 05:31:19AM -0500, Jason Mitchell wrote:
> 
> > On Feb 21, 2018, at 9:16 AM, Stephen Borrill  
> > wrote:
> > 
> >> On Wed, 21 Feb 2018, Patrick Welche wrote:
> >> I haven't tried SMB in years (it definitely worked against a different
> >> windows server). Quick attempt on -current/amd64 gets:
> >> 
> >> $ smbutil -v login -I wibble //prlw1@wibble
> >> Password:
> >> smbutil: can't get handle to requester (no /dev/nsmb* device available)
> >> smbutil: can't get handle to requester (no /dev/nsmb* device available)
> >> smbutil: could not login to server WIBBLE: syserr = Invalid argument
> > 
> > I guess it is possible the error messages are spurious and the real problem 
> > is that SMBv1 is disabled on the target (unless SMBFS supported SMBv2 or 
> > later).
> > 
> > -- 
> > Stephen
> > 
> If this is the case, then the following might help. It talks about how to 
> enable SMBv1 on Windows 7 and later:
> 
> https://support.microsoft.com/en-us/help/2696547/how-to-detect-enable-and-disable-smbv1-smbv2-and-smbv3-in-windows-and

Thank you for your suggestions!

- the test server is an ancient real pentium running windows server 2003, so
  I don't think it knows about SMBv2.
- as pointed out in private email, I should have been root given the
  permissions on /dev/nsmb*

Now when I try, I see

# smbutil -v login -I wibble //prlw1@wibble
Password:
smbutil: connection already exists
# smbutil lc
SMB connections:
None

error = smb_ctx_lookup(ctx, level, 0);
if (error == 0) {
smb_error("connection already exists", error);
exit(0);
}

smb_ctx_lookup does complete, and ctx looks sane, but lc doesn't list
anything.


Cheers,

Patrick

Re: SMB

[Jason Mitchell]

> On Feb 21, 2018, at 9:16 AM, Stephen Borrill  wrote:
> 
>> On Wed, 21 Feb 2018, Patrick Welche wrote:
>> I haven't tried SMB in years (it definitely worked against a different
>> windows server). Quick attempt on -current/amd64 gets:
>> 
>> $ smbutil -v login -I wibble //prlw1@wibble
>> Password:
>> smbutil: can't get handle to requester (no /dev/nsmb* device available)
>> smbutil: can't get handle to requester (no /dev/nsmb* device available)
>> smbutil: could not login to server WIBBLE: syserr = Invalid argument
> 
> I guess it is possible the error messages are spurious and the real problem 
> is that SMBv1 is disabled on the target (unless SMBFS supported SMBv2 or 
> later).
> 
> -- 
> Stephen
> 
If this is the case, then the following might help. It talks about how to 
enable SMBv1 on Windows 7 and later:

https://support.microsoft.com/en-us/help/2696547/how-to-detect-enable-and-disable-smbv1-smbv2-and-smbv3-in-windows-and

Jason M.