Re: [Simh] EXT :Re: winpcap problem
Hi Mark, Le 11/04/2019 à 18:02, Mark Pizzolato a écrit : On Thursday, April 11, 2019 at 8:48 AM, gérard Calliet wrote: Le 11/04/2019 à 17:21, Mark Pizzolato a écrit : Everything Dave said is true, AND part of the issue may be a need to configure some details about the new NIC you've just installed. Specifically, you say it is a server NIC and may include specific awareness of (and need configurationdetails for) VLANs. Configuring this is likely also necessary to get an IP address on the interface. The NICs were ip-configured for the window host. And you confirmed that you could actually communicate through those NICs to other hosts on the VLAN they were connected to? Yes Once useful LAN packets can be transmitted and received by the host OS, that interface can be used by simh via WinPcap Or Npcap. So I can try Npcap? I'll do that. Simh should work with Npcap in either WinPcap compatible mode or otherwise. Ok Once you know the host can use the interface. Aside from this, on Windows, there is absolutely no need for simh simulators to have dedicated network interfaces. The host system's primary interface can readily be used by simh to communicate both with other external systems AND directly with the host system (via IP). Yes but the windows host system has to be in a vlan, and the emulated VAXen on another. And I cannot share between 2 VAXen the same NIC because I use Decnet and Decnet pushes a Decnet specific Mac address on the NIC. As I said, on Windows multiple VAXen running DECnet CAN share the same NIC as long as they are configured with different DECnet addresses. I thought configuring multiple MAC addresses (for DecNet use) was impossible. I'll try that. This may require that the host NIC be configured with the correct VLAN tag or possibly configured as untagged with the switch port that it is wired to setup with the appropriate VLAN as the untagged VLAN for that port. I have already NICs on the good vlan. A lot of thanks to all. - Mark ___ Simh mailing list Simh@trailing-edge.com http://mailman.trailing-edge.com/mailman/listinfo/simh
Re: [Simh] EXT :Re: winpcap problem
On Thursday, April 11, 2019 at 8:48 AM, gérard Calliet wrote: > Le 11/04/2019 à 17:21, Mark Pizzolato a écrit : > > Everything Dave said is true, AND part of the issue may be a need to > > configure some details about the new NIC you've just installed. > > Specifically, you say it is a server NIC and may include specific awareness > > of > > (and need configurationdetails for) VLANs. Configuring this is likely > > also > > necessary to get an IP address on the interface. > > The NICs were ip-configured for the window host. And you confirmed that you could actually communicate through those NICs to other hosts on the VLAN they were connected to? > > Once useful LAN packets can be transmitted and received by the host > > OS, that interface can be used by simh via WinPcap Or Npcap. > > So I can try Npcap? I'll do that. Simh should work with Npcap in either WinPcap compatible mode or otherwise. > > > > Once you know the host can use the interface. > > > > Aside from this, on Windows, there is absolutely no need for simh > > simulators to have dedicated network interfaces. The host system's > > primary interface can readily be used by simh to communicate both with > > other external systems AND directly with the host system (via IP). > > Yes but the windows host system has to be in a vlan, and the emulated VAXen > on another. And I cannot share between 2 VAXen the same NIC because I use > Decnet and Decnet pushes a Decnet specific Mac address on the NIC. As I said, on Windows multiple VAXen running DECnet CAN share the same NIC as long as they are configured with different DECnet addresses. This may require that the host NIC be configured with the correct VLAN tag or possibly configured as untagged with the switch port that it is wired to setup with the appropriate VLAN as the untagged VLAN for that port. - Mark ___ Simh mailing list Simh@trailing-edge.com http://mailman.trailing-edge.com/mailman/listinfo/simh
Re: [Simh] EXT :Re: winpcap problem
Hi Mark, Le 11/04/2019 à 17:21, Mark Pizzolato a écrit : Hi Gérard, Everything Dave said is true, AND part of the issue may be a need to configure some details about the new NIC you've just installed. Specifically, you say it is a server NIC and may include specific awareness of (and need configuration details for) VLANs. Configuring this is likely also necessary to get an IP address on the interface. The NICs were ip-configured for the window host. Once useful LAN packets can be transmitted and received by the host OS, that interface can be used by simh via WinPcap Or Npcap. So I can try Npcap? I'll do that. Once you know the host can use the interface. Aside from this, on Windows, there is absolutely no need for simh simulators to have dedicated network interfaces. The host system's primary interface can readily be used by simh to communicate both with other external systems AND directly with the host system (via IP). Yes but the windows host system has to be in a vlan, and the emulated VAXen on another. And I cannot share between 2 VAXen the same NIC because I use Decnet and Decnet pushes a Decnet specific Mac address on the NIC. You should start with this and only try to use a separate NIC if you observe specific problems. Good Luck, - Mark On Thursday, April 11, 2019 at 8:05 AM, David Hittner wrote: Due to subtle differences in Windows drivers, sometimes WinPcap can't see a NIC unless it has an IP address assigned to it (or some other protocol - that is, that the NIC should appear to be "active" to the host). Also, certain version of WinPcap had issues adding NICs, and the solution was to remove WinPcap and re-install it to allow the installation procedure to generate the correct registry entries for the new NIC during the installation. Note that depending upon the Windows driver, sometimes the NIC had to be "active" before the WinPcap installation procedure could see the NIC to generate the correct registry entries. WinPcap has very limited support for a long time, and suggests use of the NPcap product in this post from the WinPcap home page (https://www.winpcap.org/): 15 September 2018 WinPcap, though still available for download (v4.1.3), has not seen an upgrade in many years and there are no road map/future plans to update the technology. While community support may persist, technical oversight by Riverbed staff, responses to questions posed by Riverbed resources, and bug reporting are no longer available. Gordon Lyon, Nmap project founder, has created Npcap, a packet capture library for Windows, that includes WinPcap compatibility and may be a suitable replacement for WinPcap and WinPcap Pro. Information can be found at https://nmap.org/npcap/. -Original Message- From: Simh [mailto:simh-boun...@trailing-edge.com] On Behalf Of gérard Calliet Sent: Thursday, April 11, 2019 5:15 AM To: simh@trailing-edge.com Subject: EXT :Re: [Simh] winpcap problem Hello, I used the recommended tool windump -D and it doesn't see the new NICs. So it is a pure problem of compatibility between Winpcap and the new NICs. Did anyone see a similar problem? Are there somewhere WinPcap gurus? Gérard Calliet Le 11/04/2019 à 09:42, gérard Calliet a écrit : Hello, I tried a reboot of the host. Same problem. Is it possible there are NICs not compatible with WinPcap? or some bizarre configuration to do on the NIC? Gérard Calliet Le 05/04/2019 à 02:19, Mark Pizzolato a écrit : On Tuesday, April 2, 2019 at 1:42 PM, gérard Calliet wrote: I have some trouble using winpcap (on windows) with simh. I added a NIC (intel ethernet server adapter i350-t2), I can see it on the windows configuration panel, but I don't see it using simh "sho eth" command, which uses winpcap (version 4.1.3). The other NICs are seen by the same command. Any help? Winpcap has a problem with detecting newly installed network devices that weren't present when the system was booted. Try rebooting the system and see if you continue to see the same problem. - Mark ___ Simh mailing list Simh@trailing-edge.com http://mailman.trailing-edge.com/mailman/listinfo/simh ___ Simh mailing list Simh@trailing-edge.com http://mailman.trailing-edge.com/mailman/listinfo/simh ___ Simh mailing list Simh@trailing-edge.com http://mailman.trailing-edge.com/mailman/listinfo/simh ___ Simh mailing list Simh@trailing-edge.com http://mailman.trailing-edge.com/mailman/listinfo/simh
Re: [Simh] EXT :Re: winpcap problem
Hi Gérard, Everything Dave said is true, AND part of the issue may be a need to configure some details about the new NIC you've just installed. Specifically, you say it is a server NIC and may include specific awareness of (and need configuration details for) VLANs. Configuring this is likely also necessary to get an IP address on the interface. Once useful LAN packets can be transmitted and received by the host OS, that interface can be used by simh via WinPcap Or Npcap. Once you know the host can use the interface. Aside from this, on Windows, there is absolutely no need for simh simulators to have dedicated network interfaces. The host system's primary interface can readily be used by simh to communicate both with other external systems AND directly with the host system (via IP). You should start with this and only try to use a separate NIC if you observe specific problems. Good Luck, - Mark On Thursday, April 11, 2019 at 8:05 AM, David Hittner wrote: > Due to subtle differences in Windows drivers, sometimes WinPcap can't see a > NIC unless it has an IP address assigned to it (or some other protocol - that > is, > that the NIC should appear to be "active" to the host). Also, certain version > of > WinPcap had issues adding NICs, and the solution was to remove WinPcap and > re-install it to allow the installation procedure to generate the correct > registry > entries for the new NIC during the installation. Note that depending upon the > Windows driver, sometimes the NIC had to be "active" before the WinPcap > installation procedure could see the NIC to generate the correct registry > entries. > > WinPcap has very limited support for a long time, and suggests use of the > NPcap product in this post from the WinPcap home page > (https://www.winpcap.org/): > > > 15 September 2018 > > WinPcap, though still available for download (v4.1.3), has not seen an upgrade > in many years and there are no road map/future plans to update the > technology. While community support may persist, technical oversight by > Riverbed staff, responses to questions posed by Riverbed resources, and bug > reporting are no longer available. > Gordon Lyon, Nmap project founder, has created Npcap, a packet capture > library for Windows, that includes WinPcap compatibility and may be a > suitable replacement for WinPcap and WinPcap Pro. Information can be found > at https://nmap.org/npcap/. > > > -Original Message- > From: Simh [mailto:simh-boun...@trailing-edge.com] On Behalf Of gérard > Calliet > Sent: Thursday, April 11, 2019 5:15 AM > To: simh@trailing-edge.com > Subject: EXT :Re: [Simh] winpcap problem > > Hello, > > I used the recommended tool windump -D and it doesn't see the new NICs. > So it is a pure problem of compatibility between Winpcap and the new NICs. > > Did anyone see a similar problem? Are there somewhere WinPcap gurus? > > Gérard Calliet > > > Le 11/04/2019 à 09:42, gérard Calliet a écrit : > > Hello, > > > > I tried a reboot of the host. Same problem. Is it possible there are > > NICs not compatible with WinPcap? or some bizarre configuration to do > > on the NIC? > > > > Gérard Calliet > > > > Le 05/04/2019 à 02:19, Mark Pizzolato a écrit : > >> On Tuesday, April 2, 2019 at 1:42 PM, gérard Calliet wrote: > >>> I have some trouble using winpcap (on windows) with simh. > >>> > >>> I added a NIC (intel ethernet server adapter i350-t2), I can see it > >>> on the windows configuration panel, but I don't see it using simh > >>> "sho eth" > >>> command, which uses winpcap (version 4.1.3). The other NICs are seen > >>> by the same command. > >>> > >>> Any help? > >> Winpcap has a problem with detecting newly installed network devices > >> that weren't present when the system was booted. Try rebooting the > >> system and see if you continue to see the same problem. > >> > >> - Mark > > ___ > > Simh mailing list > > Simh@trailing-edge.com > > http://mailman.trailing-edge.com/mailman/listinfo/simh > ___ > Simh mailing list > Simh@trailing-edge.com > http://mailman.trailing-edge.com/mailman/listinfo/simh > ___ > Simh mailing list > Simh@trailing-edge.com > http://mailman.trailing-edge.com/mailman/listinfo/simh ___ Simh mailing list Simh@trailing-edge.com http://mailman.trailing-edge.com/mailman/listinfo/simh
Re: [Simh] EXT :Re: winpcap problem
Hello, Thanks for all the information Le 11/04/2019 à 17:04, Hittner, David T [US] (MS) a écrit : Due to subtle differences in Windows drivers, sometimes WinPcap can't see a NIC unless it has an IP address assigned to it (or some other protocol - that is, that the NIC should appear to be "active" to the host). Also, certain version of WinPcap had issues adding NICs, and the solution was to remove WinPcap and re-install it to allow the installation procedure to generate the correct registry entries for the new NIC during the installation. I'll try that. ... Gordon Lyon, Nmap project founder, has created Npcap, a packet capture library for Windows, that includes WinPcap compatibility and may be a suitable replacement for WinPcap and WinPcap Pro. Information can be found at https://nmap.org/npcap/. Is Npcap compatible with simh? -Original Message- From: Simh [mailto:simh-boun...@trailing-edge.com] On Behalf Of gérard Calliet Sent: Thursday, April 11, 2019 5:15 AM To: simh@trailing-edge.com Subject: EXT :Re: [Simh] winpcap problem Hello, I used the recommended tool windump -D and it doesn't see the new NICs. So it is a pure problem of compatibility between Winpcap and the new NICs. Did anyone see a similar problem? Are there somewhere WinPcap gurus? Gérard Calliet Le 11/04/2019 à 09:42, gérard Calliet a écrit : Hello, I tried a reboot of the host. Same problem. Is it possible there are NICs not compatible with WinPcap? or some bizarre configuration to do on the NIC? Gérard Calliet Le 05/04/2019 à 02:19, Mark Pizzolato a écrit : On Tuesday, April 2, 2019 at 1:42 PM, gérard Calliet wrote: I have some trouble using winpcap (on windows) with simh. I added a NIC (intel ethernet server adapter i350-t2), I can see it on the windows configuration panel, but I don't see it using simh "sho eth" command, which uses winpcap (version 4.1.3). The other NICs are seen by the same command. Any help? Winpcap has a problem with detecting newly installed network devices that weren't present when the system was booted. Try rebooting the system and see if you continue to see the same problem. - Mark ___ Simh mailing list Simh@trailing-edge.com http://mailman.trailing-edge.com/mailman/listinfo/simh ___ Simh mailing list Simh@trailing-edge.com http://mailman.trailing-edge.com/mailman/listinfo/simh ___ Simh mailing list Simh@trailing-edge.com http://mailman.trailing-edge.com/mailman/listinfo/simh
Re: [Simh] EXT :Re: winpcap problem
Due to subtle differences in Windows drivers, sometimes WinPcap can't see a NIC unless it has an IP address assigned to it (or some other protocol - that is, that the NIC should appear to be "active" to the host). Also, certain version of WinPcap had issues adding NICs, and the solution was to remove WinPcap and re-install it to allow the installation procedure to generate the correct registry entries for the new NIC during the installation. Note that depending upon the Windows driver, sometimes the NIC had to be "active" before the WinPcap installation procedure could see the NIC to generate the correct registry entries. WinPcap has very limited support for a long time, and suggests use of the NPcap product in this post from the WinPcap home page (https://www.winpcap.org/): 15 September 2018 WinPcap, though still available for download (v4.1.3), has not seen an upgrade in many years and there are no road map/future plans to update the technology. While community support may persist, technical oversight by Riverbed staff, responses to questions posed by Riverbed resources, and bug reporting are no longer available. Gordon Lyon, Nmap project founder, has created Npcap, a packet capture library for Windows, that includes WinPcap compatibility and may be a suitable replacement for WinPcap and WinPcap Pro. Information can be found at https://nmap.org/npcap/. -Original Message- From: Simh [mailto:simh-boun...@trailing-edge.com] On Behalf Of gérard Calliet Sent: Thursday, April 11, 2019 5:15 AM To: simh@trailing-edge.com Subject: EXT :Re: [Simh] winpcap problem Hello, I used the recommended tool windump -D and it doesn't see the new NICs. So it is a pure problem of compatibility between Winpcap and the new NICs. Did anyone see a similar problem? Are there somewhere WinPcap gurus? Gérard Calliet Le 11/04/2019 à 09:42, gérard Calliet a écrit : > Hello, > > I tried a reboot of the host. Same problem. Is it possible there are > NICs not compatible with WinPcap? or some bizarre configuration to do > on the NIC? > > Gérard Calliet > > Le 05/04/2019 à 02:19, Mark Pizzolato a écrit : >> On Tuesday, April 2, 2019 at 1:42 PM, gérard Calliet wrote: >>> I have some trouble using winpcap (on windows) with simh. >>> >>> I added a NIC (intel ethernet server adapter i350-t2), I can see it >>> on the windows configuration panel, but I don't see it using simh >>> "sho eth" >>> command, which uses winpcap (version 4.1.3). The other NICs are seen >>> by the same command. >>> >>> Any help? >> Winpcap has a problem with detecting newly installed network devices >> that weren't present when the system was booted. Try rebooting the >> system and see if you continue to see the same problem. >> >> - Mark > ___ > Simh mailing list > Simh@trailing-edge.com > http://mailman.trailing-edge.com/mailman/listinfo/simh ___ Simh mailing list Simh@trailing-edge.com http://mailman.trailing-edge.com/mailman/listinfo/simh ___ Simh mailing list Simh@trailing-edge.com http://mailman.trailing-edge.com/mailman/listinfo/simh
