PearPC Quad-IDE build

[redscorp]

1536 MB DDR2
1.99 GHz AMD Mobile Sempron
ATi Radeon Xpress 200M
Windows Vista - Ultimate (build 6000, I think)

I have notebook with similar configuration but with XP on board.
I'll try this build of pearpc on it.
Post your config file here.

UPD: this was buggy release. I made small release summary in first message of this thread.
symbolic X: Use latest binaries to fix your problems.

[ElGuillermo]

Hey there !

I've asked the same two months ago... Any news ?

[redscorp]

You simply reading my mind...
Yesterday I had finish development of PCAP based network interface for PearPC.

redscorp-release-20080329.rar

PearPC with PCAP interface support.

(767.69 KiB) Downloaded 2304 times

PCAP interface allow PearPC connect over the real Ethernet card like vmWare Workstation's or Virtual PC's bridged network.

For running PearPC over PCAP driver you have to install WinPCAP 4.0.2 first.

WinPcap_4_0_2.rar

WinPCAP driver v.4.0.2.

(488.08 KiB) Downloaded 1986 times

And for listing of PC network interfaces you should you pcap-list utility.

pcap-list.rar

PCAP interface lister

(2.44 KiB) Downloaded 1633 times

This utility produce output like that:

Code: Select all

\Device\NPF_GenericDialupAdapter (Adapter for generic dialup and VPN capture)
\Device\NPF_{0007F387-533A-4475-A734-A370148B2781} (TAP-Win32 Adapter V8 (Microsoft's Packet Scheduler) )
\Device\NPF_{696E3F75-AB0A-4D05-A3EB-C7ECB3A9ECB9} (Marvell Yukon Ethernet Controller. (Microsoft's Packet Scheduler) )

In this example "\Device\NPF_{696E3F75-AB0A-4D05-A3EB-C7ECB3A9ECB9}" is a real Ethernet card name.

I have introduced new entries for configuration file:
pci_rtl8139_type and pci_3c90x_type - interface type "tap" or "pcap"
pci_rtl8139_interface and pci_3c90x_interface - interface name e.g. "\Device\NPF_{696E3F75-AB0A-4D05-A3EB-C7ECB3A9ECB9}"

I have tested PCAP connectivity so far with RTL8139 virtual ethernet card.

Example of configuration entry for RTL8139 to work with PCAP:

Code: Select all

pci_rtl8139_installed = 1
pci_rtl8139_mac = "de:ad:ca:fe:12:34"
pci_rtl8139_type = "pcap"
pci_rtl8139_interface = "\Device\NPF_{696E3F75-AB0A-4D05-A3EB-C7ECB3A9ECB9}"

And code below show how to configure virtual card to work "old way":

Code: Select all

pci_rtl8139_installed = 1
pci_rtl8139_mac = "de:ad:ca:fe:12:34"
pci_rtl8139_type = "tap"
pci_rtl8139_interface = ""

Entry "pci_rtl8139_interface" must be valid only for "pcap" connection.

Known issues:
- PCAP access may work not with Wi-Fi or BlueTooth connections. Use tap method in this case.
- When MacOS X produce packets bigger than MTU (1500 bytes), PCAP drive fail to send this packet. This cause error message while disconnecting of Windows share folder. This issue probably can be fixed later.

UPDATE:
- MTU > 1500 issue is fixed.
- In my home encrypted Wi-Fi network PCAP connection doesn't work! Please report if PCAP connection works in your Wi-Fi network!
- In my work network PCAP connection over Ethernet line also doesn't work well. This issue may be fixed later... because at my home network this connection works fine...

[ElGuillermo]

Woohoo ! talk about some news !

Great work ! I'll play with that today and post my impressions

[redscorp]

I did fix, earlier described, problem with big packets.

redscorp-release-20080329.1.rar

PearPC with PCAP interface support (update).

(767.28 KiB) Downloaded 6294 times

RTL8139 virtual HW code generated unnecessary CRC, that increase packet size and cause problem while sending this packet over PCAP.
Interesting that nobody detected and fixed this before. Enjoy!

[ElGuillermo]

I managed to get my wifi USB dongle (Netgear WG111v1) working with some tweaking :

Entering the interface real MAC adress as "pci_rtl8139_mac" parameter is the key to success. I had to force the IP adress/submask and router parameters in OSX too. The emulated Mac is now accessing fullspeed to my router

The only drawback for the moment : Windows connexion seems garbled while OSX accesses the network. I guess having two computers running the same IP on the same interface must be the reason. I'll try to figure out how to get them both connected without using the same IP, nor the same MAC...

More tests ahead...

[redscorp]

I was able today to run two instances of pearpc connected over pcap to one physical ethernet NIC. This two instances did communicate one with another and I was able to see the traffic in ethernet wire with sniffer program. So, it's proof that this method of connection behaves same way as bridged network in vmWare.
Note: both instances of pearpc must have different mac address set in config file and must have different IP addresses.

[ElGuillermo]

Cool

I still can't connect if the MAC and IP adress specified in config file and network config panel are not the same as the "real" ones... So it garbles the host's connexion. I'll try to fiddle some more today, as you say you can connect two times on the same interface, specifying two differents MACs and IPs.

this is a nice little toy you got us, Mr Redscorp. Thanks

[ElGuillermo]

OK... I've managed to get the OSX interface running on a different MAC adress with a different IP than the one used in Windows... File sharing is OK, internet is OK... Cool stuff. The only prob I get is some disconnections from time to time when transfering VERY large file (I had to try to copy a DVD iso from OSX desktop to the PC four times to get it entirely)... PearPC's log shows "event dropped" entries...

[redscorp]

I had no problems with that.
Big (about of 6,2Gb) iso image was copied from Windows share to /dev/null of OSX Panther over pcap interface, connected to Gigabit Ethernet, without any problem.