E-Maculation

Hello,

the bytes not passing the filter look to me to be sign of a routing problem.
If you have access to w2003 server then you could use "routing and remote access" to configure windows routing. It works for me all the time.

First give the tap device a ip address in the normally not routed ranges like 10.10.10.1 or 192.168.0.1

Then use the routing and remote access wizard and select your normal nic to allow others to have internet access, and then choose the tap device as allowed device.

Last give OS X an ip-address like 10.10.10.2 or 192.168.0.2 depending on which address you gave the tap device.
Set default gateway to the tap ip-address and dns' to your normal dns' from the normal nick.

One other remark: networking with 10.2 and 3com is not as "mature" as in 10.3 with the realtek device

Best wishes

Cat_7

I guess the filter is the IP-forwarding filter. Your machine only forwards ip-packets its routing table allows.

You should definitely try the "routing and remote access" option under administrative tools in w2003 server. It configures things automatically, thus eradicating possible errors on the windows side.

Best wishes

Cat_7

@gram
i followed exactly like you said except i turned on ics on my main conection
and i now have a connection i'm using openvpn-2.0_beta2
router and dns in mac are set to the tap ip 192.168.2.1
btw i've been trying to get this to work for 3 days
oh yea i'm also using the rtl8139 nic

also you need to change the 1 to a 0 on the one your not using

pci_3c90x_installed = 0
pci_3c90x_mac = "de:ad:ca:fe:12:34"
#pci_rtl8139_installed = 1
#pci_rtl8139_mac = "de:ad:ca:fe:12:34"

I decided to try the 3com driver and i got the same garbage you got
does the 3com driver even work with the windows port of PearPC
i'm typing this in safari right now so it does work but not with 3com driver
the funny thing is my real nic is a 3com 3C940