D-Link NIC Won't Talk To Bridge

From: Drew Tomlinson (drew_at_mykitchentable.net)
Date: 09/30/03

  • Next message: Brooks Davis: "finishing the if.h/if_var.h split"
    To: <freebsd-net@freebsd.org>
    Date: Mon, 29 Sep 2003 15:32:54 -0700
    
    

    I asked on -questions but was unable to resolve. I'm hoping there's an
    expert here that is willing and able to help. :)

    I'm trying to get a Linksys WET11 Wireless Ethernet Bridge
    (http://www.linksys.com/products/product.asp?prid=432&scid=36) working
    with a D-Link 530TX+ NIC that uses the rl driver. I have configured the
    bridge and gotten it to work with a Windows XP box. However I can not
    get it working on my 4.8 FBSD gateway box.

    I am trying to set things up so I can use my neighbor's Internet
    connection as a backup link. He has a Linksys Wireless Access
    Point/Router in his home. Instead of installing a
    wireless card in my FBSD box, I bought the WET11 so I could install it
    by a window to get a better signal. The Linksys bridge connects via
    ethernet cable to the NIC in my FBSD box. Here's a diagram of the
    setup:

             Internet
                 |
             Public IP
                 |
           ADSL Modem/Router
            192.168.10.1
                 |
                dc0
            192.168.10.2
                 |
             FBSD 4.8 --------- rl0
                 | 192.168.100.2
                dc1 |
            192.168.1.2 192.168.100.225
                 | Wireless Bridge
            Internal LAN |
                           192.168.100.1
                           Neighbor's AP

    I have added the following to the beginning of my ipfw2 rules to verify
    that traffic is going out the correct interface:

    ipfw add allow log ip from any to any via rl0

    When attempting a connection to anything on the 100 subnet, I see
    entries like this in the firewall log:

    Sep 29 14:58:05 blacksheep /kernel: ipfw: 50 Accept ICMP:8.0
    192.168.100.2 192.168.100.1 out via rl0

    Sep 29 14:43:47 blacksheep /kernel: ipfw: 50 Accept TCP
    192.168.100.2:2626 192.168.100.225:80 out via rl0

    However no response comes back. I'm sure ipfw2 is not blocking return
    packets because I log all denied packets. I have also tried with all
    ipfw2 rules flushed and have the same result.

    There may be a clue in the arp tables. After trying connections to the
    100 subnet, I have entries like these in the arp tables:

    ? (192.168.100.1) at (incomplete) on rl0 [ethernet]
    ? (192.168.100.2) at 00:05:5d:d0:ba:67 on rl0 permanent [ethernet]
    ? (192.168.100.225) at (incomplete) on rl0 [ethernet]

    So I thought maybe adding static entries to the arp table might help but
    it did not.

    Does anyone have any idea on what I need to do to get this working? I'm
    willing to read and learn but at this point I'm so stuck I don't know
    where to turn next.

    Thanks,

    Drew

    _______________________________________________
    freebsd-net@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-net
    To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"


  • Next message: Brooks Davis: "finishing the if.h/if_var.h split"

    Relevant Pages

    • message in my server
      ... arp: 172.18.14.40 is on rl1 but got reply from ... 00:30:84:40:f3:ea on rl0 ... how i dismis this message in my server because make ...
      (freebsd-questions)
    • Re: ARP Poisoning
      ... Static ARP entries are not a viable solution in a dynamic environment. ... workstations and servers on an internal network space. ... ARP has no authentication or security built into it. ...
      (Security-Basics)
    • Re: [fw-wiz] How to Secure Windows? was How to Save the World
      ... That's easy to work around- but it looks like ARP is in the driver and not ... > DOS arp command to set static arp entries for all the entries you ... Paul D. Robertson "My statements in this message are personal opinions ...
      (Firewall-Wizards)
    • Re: proxy-arp & mpd
      ... after some more tests here is what i came to (patch provided is for freebsd 6.3 but can be adapted for other versions): it is a dirty hack and might not be the right solution but it is working in the case i described earlier and i hope it will help discussing the issue. ... It seems that the process that block read all entries available in the PF_ROUTE socket, do not find the one it is looking for and ends blocked on the PF_ROUTE socket as no more entries are available after reading ... add a bunch of arp entries in your arp table. ... warn("writing to routing socket"); ...
      (freebsd-net)
    • clearing ARP cache
      ... ARP entries, and the "arp" command would not clear them up. ... due to letting magic smoke and magic sparks out of its power supply had ... the problems w/o a reboot. ...
      (comp.os.linux.development.system)