5.1r Bridge with one ip - no access from non-ip side

From: Bjorn Eikeland (bjorn_at_eikeland.info)
Date: 01/06/04

  • Next message: paul van den bergen: "Re: wireless monitoring of APs???"
    Date: Tue, 06 Jan 2004 01:38:03 +0100
    To: freebsd-net@freebsd.org
    
    

    Hi

    I've set up a bridge between the lan in my flat an my isp's adsl modem/nat
    router to shape traffic and also provide some services to both the lan and
    'wan' side.

    current setup:

      router --- (xl0) bridge (fxp0) --- switch w/ clients
    10.0.0.1 no-ip dhcp dhcp (10.0.0.2, 10.0.0.20-10.0.0.30)

    The bridge works for the clients and from the router to the clients.

    The fxp0 interface is configured by dhcp via the bridge, and later given a
    alias of 10.0.0.10 (just to have a fixed ip when switching between xl0 and
    fxp0 getting a ip assigned to it) so the fxp0 side is listening to the
    router when being configured, but not later.

    If I clear the arp entries (arp -da) and flush the routes (route flush)
    and ping the 10.0.0.1 router the arp entry is restored and a route is also
    put back.

    beerserver# arp 10.0.0.1
    ? (10.0.0.1) at 00:00:c5:98:21:0c on fxp0 [ethernet]
    beerserver# netstat -rn
    Destination Gateway Flags Refs Use Netif Expire
    10/24 link#2 UC 2 0 fxp0
    10.0.0.1 00:00:c5:98:21:0c UHLW 0 2 fxp0 1186
    10.0.0.2 00:a0:c9:f1:4e:6d UHLW 1 56 fxp0 1181
    127.0.0.1 127.0.0.1 UH 0 0 lo0

    Router pinging "bridge" (10.0.0.10):
    Tcpdump shows the packet arriving on xl0:
    00:10:18.628986 10.0.0.1 > 10.0.0.10: icmp: echo request
    But it shows this on fxp0:
    00:12:45.645646 arp who-has 10.0.0.10 tell 10.0.0.1

    "Bridge" pinging router (10.0.0.1)
    Tcpdump shows packet leaving fxp0:
    00:19:49.621531 10.0.0.10 > 10.0.0.1: icmp: echo request
    Tcpdump show reply comming back on xl0:
    00:21:30.836404 10.0.0.10 > 10.0.0.1: icmp: echo request
    00:21:30.836817 10.0.0.1 > 10.0.0.10: icmp: echo reply

    Just in case its a problem with the alias, I've tried only assigning
    10.0.0.10 to fxp0, same result.

    The bridge is compiled into the kernel as I read the module had problems
    with this, but compiling it into the kernel did not solve my problem.
    (I've checked the module isnt loaded)

    Any suggestions?
    (Please ask if you need more info/configs)

    - Bjorn
    _______________________________________________
    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: paul van den bergen: "Re: wireless monitoring of APs???"

    Relevant Pages

    • Re: Workgroup Client Bridge Configuration
      ... original SOHO-10 routers in service and on my router pile. ... do more than about 1Mbit/sec WAN to LAN. ... but the gateway is 216.216.216.1, some operating systems just will not ... The machine at the end of the wireless bridge should be configured the ...
      (alt.internet.wireless)
    • Re: Neighborhood WiFi?
      ... supplies their own firwall for NAT. ... methinks a transparent bridge or "wireless ... bridge" will be better in case the topology changes. ... end has a router as does the tower end. ...
      (alt.internet.wireless)
    • Re: Feasible to implement a router on a system on a chip?
      ... passes traffic between the ports (which may be of different types - ... A bridge will typically ... A "switch" is a type of bridge that is specialised for low-latency ... A "router" has two or more network ports and passes packets between them ...
      (comp.arch.embedded)
    • Re: Bridging firewall and NAT router setup
      ... >> - Put the OpenBSD bridge before the NAT router. ...
      (comp.security.firewalls)
    • Re: Feasible to implement a router on a system on a chip?
      ... passes traffic between the ports (which may be of different types - ... A bridge will typically ... A "switch" is a type of bridge that is specialised for low-latency ... A "router" has two or more network ports and passes packets between them ...
      (comp.arch.embedded)