Bridged Networking: packet tx: pcap - FAILED

Help
Anonymous
2004-08-13
2013-05-09
  • Anonymous - 2004-08-13

    Hi,

    after fiddling aroung with the TAP driver I gave on this (I couldn't figure out how to configure it when my IP is in the NAT range 192.168.0.x. As soon as I enabled connection sharing my network went crazy).

    So I tried to setup bridged networking. I installed  WinPcap 3.1 beta 3 from http://winpcap.polito.it/install/default.htm

    Installed with no apparent error.

    Starting co-linux logs this:

    ----

    [...]
    colinux: launching net daemons
    daemon: launching daemon for conet0
    executing: colinux-bridged-net-daemon -c 0 -i 0 -n "NdisWan" -mac 00:43:4f:4e:45
    :30
    daemon: launching console
    executing: colinux-console-fltk -a 0
    [...]
    Freeing unused kernel memory: 52k freed
    bridged-net-daemon: Checking adapter: Generic NdisWan adapter
    bridged-net-daemon: Listening on: Generic NdisWan adapter...
    bridged-net-daemon: Listening for: (ether dst 00:43:4f:4e:45:30) or (ether broad
    cast or multicast) or (ip broadcast or multicast)
    pipe client 0/8: Connecting to daemon...
    pipe client 0/8: Connection established
    daemon: module connected: conet0
    co_message_switch: setting callback rule for 8
    EXT3 FS 2.4-0.9.19, 19 August 2002 on cobd(117,0), internal journal
    packet tx: pcap - FAILED
    packet tx: pcap - FAILED
    packet tx: pcap - FAILED
    packet tx: pcap - FAILED
    [...]
    ----

    I can log into colinux fine, but don't have networking available. I can't ping my gateway nor my windows ip.

    Here's the output from ipconfig /all of my Windows 2000 (only the relevant parts).

    ---
    Ethernetadapter "LAN-Verbindung 4":

            Verbindungsspezifisches DNS-Suffix:
            Beschreibung. . . . . . . . . . . : NVIDIA nForce MCP Networking Control
    ler
            Physikalische Adresse . . . . . . : 00-04-61-4B-1C-9B
            DHCP-aktiviert. . . . . . . . . . : Nein
            IP-Adresse. . . . . . . . . . . . : 192.168.0.184
            Subnetzmaske. . . . . . . . . . . : 255.255.255.0
            Standardgateway . . . . . . . . . : 192.168.0.1
            DNS-Server. . . . . . . . . . . . : 192.168.0.1

    ----

    my /etc/network/interfaces :

    auto lo eth0

    iface eth0 inet static

    address 192.168.0.84
    gateway 192.168.0.1
    netmask 255.255.255.0

    iface lo inet loopback

    ----

    So ist .84 under colinux and .184 under windows.

    My network interface is the integrated NIC of nforce2 chipset.

    my colinux-xml looks like this:

    ---
    [...]
        <!-- This allows you to modify networking parameters, see the README
             or website for more information -->
        <network index="0" name="NdisWan" type="bridged"></network>
        <!-- <network index="0" type="tap" /> -->
    [...]

    ---

    I'm stuck. Any clues?

    Ciao

    Ulrich.

     
    • Anonymous - 2004-08-18

      Noone? Google isn't any help as well.

       
    • Rony Shapiro

      Rony Shapiro - 2004-08-29

      Hi,

      I'm getting stuck in a very similar manner:

      Here's my host connection (laptop running win2k, connected to the Internet via a NAT-ing ADSL modem):
      $ ipconfig
      Windows 2000 IP Configuration
      Ethernet adapter coLinux:
              Media State . . . . . . . . . . . : Cable Disconnected

      Ethernet adapter Local Area Connection:
              Connection-specific DNS Suffix  . : WinProxy
              IP Address. . . . . . . . . . . . : 10.100.0.1
              Subnet Mask . . . . . . . . . . . : 255.0.0.0
              Default Gateway . . . . . . . . . : 10.0.0.138

      Here's the network entry in the configuration file:
          <network index="0" name="Intel(R) PRO/100+ MiniPCI" type="bridged" />

      Here's the relevant output from the coLinux startup:
      colinux: launching net daemons
      daemon: launching daemon for conet0
      executing: colinux-bridged-net-daemon -c 0 -i 0 -n "Intel(R) PRO/100+ MiniPCI" - mac 00:43:4f:4e:45:30
      [...]
      bridged-net-daemon: Checking adapter: TAP VPN Adapter.
      bridged-net-daemon: Checking adapter: Intel(R) PRO/100+ MiniPCI

      /etc/network/interfaces has:

      auto lo eth0
      iface lo inet loopback
      iface eth0 inet static
      address 192.168.0.40
      gateway 192.168.0.1
      netmask 255.255.255.0

      route table has 192.168.0.1 as the default gateway
      ifconfig looks good
      pinging both 127.0.0.1 and 192.168.0.40 works fine
      pinging anything outside coLinux (192.268.0.1 or an external address) fails totally - the packet is reported as transmitted according to ifconfig, but zero packets received.

      I also get the ocassional "packet tx: pcap - FAILED" message.

      It's not really clear to me how this is supposed to work. What is doing the bridge function? How does pcap fit in (I've installed 3.0, BTW)? Would changing the IP addresses to the same network as my host machine (e.g., 10.0.0.0/255.0.0.0) make any sense? Guess this is what I'll try soon, since I don't have any better idea....

       
      • Rony Shapiro

        Rony Shapiro - 2004-08-29

        Well, the idea I wrote at the end of my last post worked!
        That is, the IP address assigned to colinux must be on the same network as that of the host adaptor. Looking back, this is obvious. Still, the documentation could be a bit clearer in this respect...

         
    • Daniele Franceschi

      Same problem...
      W2K has IP 10.0.2.2
      CoLinux (bridged, WinPCAP 3.0) has 10.0.2.102
      gateway for both is 10.0.2.254 (does nat too)
      netmask for both is 255.255.255.0

      I can ping everything in my LAN and _everything_ in the world, but i can't open any tcp connection, the result is always "packet tx: pcap - FAILED".

      PS: my NIC has no options about IP checksums.

      --Danny

       

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks