RE: Quick Routing Question

From: Steve Bertrand (iaccounts_at_ibctech.ca)
Date: 11/01/05

  • Next message: Andrew P.: "Re: MAC_by_default" 
    To: "'Jason Morgan'" <jwm-freebsd@sentinelchicken.net>
Date: Tue, 1 Nov 2005 11:24:59 -0500

     

    > -----Original Message-----
    > From: owner-freebsd-questions@freebsd.org
    > [mailto:owner-freebsd-questions@freebsd.org] On Behalf Of Jason Morgan
    > Sent: Tuesday, November 01, 2005 11:03 AM
    > To: FreeBSD Questions
    > Subject: Re: Quick Routing Question
    >
    > On Tue, Nov 01, 2005 at 10:25:25AM -0500, Steve Bertrand wrote:
    > >
    > > > Destination Gateway Flags Refs
    > Use Netif
    > > > Expire
    > > > default 70.183.13.193 UGS 0
    > 24701 xl0
    > > > 10/24 link#3 UC 0
    > 0 fxp0
    > > > 10.0.0.1 00:d0:b7:44:f9:c6 UHLW 0
    > 903 lo0
    > > > 10.0.0.2 00:50:8d:e5:a5:41 UHLW 0 322468
    > > > fxp0 572
    > > > 10.0.0.4 00:e0:98:04:01:f6 UHLW 0 1131
    > > > fxp0 1140
    > > > 70.183.13.192/26 link#2 UC 0
    > 0 xl0
    > > > 70.183.13.193 00:13:5f:00:f0:ee UHLW 1 0
    > > > xl0 1188
    > > > 70.183.13.213 00:50:04:cf:52:8a UHLW 0
    > 18 lo0
    > > > 127.0.0.1 127.0.0.1 UH 0
    > 0 lo0
    > > > 192.168.1 link#1 UC 0
    > 0 dc0
    > >
    > > Ok, this looks ok. The 10/24 network *should* be able to see/route
    > > anything back and forth to the 192.168.1/24 network without
    > difficulty.
    > >
    > > Now, I can't remember if you said how this was cabled, but
    > this is how
    > > I set up my wifi networks:
    > >
    > > - plug the wireless network interface in the FBSD router
    > into one of
    > > the LAN switch ports on the wireless AP/router (if indeed
    > it is a router).
    > > The IP address on the LAN side of the AP is irrelevant, so
    > long as you
    > > don't conflict with another IP.
    >
    > Yes, that's what I've done.
    >
    > > - Give the wireless laptop a static IP inside the wireless IP subnet
    >
    > As soon as I can get the Linksys set up, I will.
    >
    > > - Have nothing plugged into the WAN side of the wireless AP, as you
    > > don't want routing with that unit, you just want a layer-2
    > > (bridged/switched) AP.
    >
    > Correct.
    >
    > > - effectively, if you have wireless connectivity from the laptop to
    > > the AP, you should be able to ping the FW, and vice-versa
    >
    > Checking to make sure the wireless router is routing now, but
    > I can ping from the FreeBSD gateway to the router (as well as
    > hit the web setup with lynx).

    Ok, slick...you are more than half way there. Carry on with bringing
    over a client to the wireless side of things (even if it's just cabled
    into the Linksys for now), to see if you can get through the AP, to the
    router. Then proceed to try to ping the cabled iface of the FBSD box
    from said client. If you can do that, then try a wireless client, to
    ensure the problem doesn't stem from wifi connectivity.

    And again, tcpdump is a very good tool. The -i switch tells it what
    interface to listen on, so if the wireless side of the router works but
    you can't ping across to the cabled side, then apply the cabled
    interface to the -i switch and you'll be able to see if traffic is
    making that far, and if it is, if it's even attempting to go back.

    Cheers, and good luck!

    Steve

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

  • Next message: Andrew P.: "Re: MAC_by_default"

    Relevant Pages

    • Re: Wireless Network in Public Places Options
      ... two client radios, none of the packets will go through the router. ... but that's not the way commodity wireless access points work. ...
      (microsoft.public.win2000.networking)
    • Re: Gaming adapter as access point
      ... remember is that *ALL* 802.11 wireless is bridging. ... Linksys WRT54G/GS with DD-WRT firmware in client mode. ... have to study VPN ... then act as a router on the LAN side. ...
      (alt.internet.wireless)
    • Re: DI 624 revC- severe wireless latency after consistent throughput
      ... >The latency measurements were from pinging the router from the wireless ... >between the router and the wireless client. ...
      (alt.internet.wireless)
    • Re: home network problem: access a computer under another router
      ... The problem seems to be that you are using the router as a bridge so I would ... I have turned routers into Wireless Clients to other routers ... DHCP Server: Enabled ... Mode: Infrastructure Client ...
      (microsoft.public.windowsxp.general)
    • Re: Bridges, not yet houseboat redux
      ... Well it looks like you got your connection to the Client ... or ping the router or anywhere beyond the APclient's configuration page. ... down the following values for your existing wireless router or AP: ... Wireless Security Settings ...
      (alt.internet.wireless)