Date: Tue, 10 Mar 1998 02:26:35 -0800 (PST) From: nasruddin@iiu.edu.my To: freebsd-gnats-submit@FreeBSD.ORG Subject: kern/5965: FreeBSD TCP/IP connectivity get buried by Xylan OmniSwitch VLAN Message-ID: <199803101026.CAA02013@hub.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 5965 >Category: kern >Synopsis: FreeBSD TCP/IP connectivity get buried by Xylan OmniSwitch VLAN >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Tue Mar 10 02:30:06 PST 1998 >Last-Modified: >Originator: Nasruddin Abu Sari >Organization: Islamic International University >Release: 2.2.5 >Environment: >Description: Connectivity to FreeBSD machine is unavailable via Xylan Omniswitch VLAN after a certain period of time of inactivity. ( However I had cases with active pinging from freebsd box or while in active telnet session when connection get terminated). In all these cases I am connecting from outside (LAN subnet) the VLAN. The freebsd machine is up and running fine. >How-To-Repeat: Wait for a few hours and freebsd box will not reachable from outside the Xylan VLAN. >Fix: 1. Reboot the machine manually ( I got to go to the room what the machine is located and either type reboot (as root) or turn it off/on) OR 2. Keep another Win95/NT box running (in the same VLAN). Apperently Win95/NT box activities keep the Xylan OmniSwith to sustain the VLAN. >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199803101026.CAA02013>