Josep Maria Antolín Segura wrote:
> When you talk about a bridge, you talk about the windows XP feature that lets
> you connect two network interfaces, creating a third one that then has the IP,
> right? (I sort of got confused by you saying "both the host and the bridge have
> the same IP").
> Or do you mean the pcap-bridged type of connection of colinux?
> By the description of the windows machine losing connectivity to outside world,
> it indeed sounds as a problem on the bridge, or (less probable) on network
> card, cable, switch or otherwhise physical element.
> So for now, take a look at
> and see if that's what you have.
That sems me the XP-Bridge. Not the pcap-bridge mode.
One problem, I see, you have self made: "The bridge and the host have
the same IP"
You need to know, that the bridge and the host have different MAC. If
you shutting down the bridge, than the other PC would try to send
packets to the old MAC. After a while (some minutes) the MAC cache would
be cleared automaticly and the host network should work normal. You can
watch the MAC-cache from XP command prompt with "arp -a" or "arp print"
(I currently don't remember).
To fix this you have one of thise choices:
A) Configure a different IP address for the bridge (different from all
others you currently have)
B) Configure the TAP-Win32 as "always connected" to have all times the
bridge online, also if coLinux is not running
C) Run the "arp" with clear parameter after shutting down coLinux