Quick Routing Question

Glenn Dawson glenn at antimatter.net
Tue Nov 1 07:00:31 PST 2005


At 06:34 AM 11/1/2005, Jason Morgan wrote:
>On Tue, Nov 01, 2005 at 09:03:11AM -0500, Steve Bertrand wrote:
> >
> >
> > > -----Original Message-----
> > > From: owner-freebsd-questions at freebsd.org
> > > [mailto:owner-freebsd-questions at freebsd.org] On Behalf Of Fabian Keil
> > > Sent: Tuesday, November 01, 2005 5:58 AM
> > > To: Jason Morgan
> > > Cc: FreeBSD Questions
> > > Subject: Re: Quick Routing Question
> > >
> > > Jason Morgan <jwm-freebsd at sentinelchicken.net> wrote:
> > >
> > > > I am setting up a wireless subnet and, while the gateway (FreeBSD
> > > > system) is communicating fine with the wireless router, my other
> > > > subnet is not able to connect to the wireless router. Here is a
> > > > diagram of my network, I think it's fairly typical.
> > > >
> > > >
> > > >                          Wired Subnet (10.0.0.x)
> > > >                             /
> > > >                            /
> > > > Internet <-- FreeBSD Machine
> > > >                            \
> > > >                             \
> > > >                          Wireless Subnet (192.168.1.x)
> > > >
> > > >
> > > > The 'wired' interface on the FreeBSD machine has an IP of 10.0.0.1,
> > > > with the 'wireless' IP being 192.168.1.1.  Now, the FreeBSD machine
> > > > and the wireless router (192.168.1.2) communicate fine as does the
> > > > wired subnet; however, I am not able to connect from a
> > > 10.0.0.x client
> > > > to the wireless router. After running traceroute, etc, it
> > > seems that
> > > > the FreeBSD machine is simply not routing the data from one
> > > subnet to
> > > > the other. I've verified that it's not the firewall
> > > blocking packets.
> > > > How do I get these subnets to communicate?
> > >
> > > Did you put gateway_enable=YES in rc.conf?
> > > Did you read
> > > 
> <<http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/net>http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/net>  
>  > work-routing.html>?
>
>Yes, the FreeBSD machine has been acting as a router/gateway/firewall
>for the wired network for quite some time. I did look at the handbook,
>that's usually my first stop.
>
> >
> > Also, what does:
> >
> > # netstat -rn
> >
> > ...output?
>
># netstat -rn
>
>Routing tables
>
>Internet:
>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
>
>Internet6:
>Destination                       Gateway              Flags Netif Expire
>::1                               ::1                  UH     lo0
>fe80::%dc0/64                     link#1               UC     dc0
>fe80::204:5aff:fe42:5084%dc0      00:04:5a:42:50:84    UHL    lo0
>fe80::%xl0/64                     link#2               UC     xl0
>fe80::250:4ff:fecf:528a%xl0       00:50:04:cf:52:8a    UHL    lo0
>fe80::%fxp0/64                    link#3               UC     fxp0
>fe80::2d0:b7ff:fe44:f9c6%fxp0     00:d0:b7:44:f9:c6    UHL    lo0
>fe80::%lo0/64                     fe80::1%lo0          U      lo0
>fe80::1%lo0                       link#4               UHL    lo0
>ff01::/32                         ::1                  U      lo0
>ff02::%dc0/32                     link#1               UC     dc0
>ff02::%xl0/32                     link#2               UC     xl0
>ff02::%fxp0/32                    link#3               UC     fxp0
>ff02::%lo0/32                     ::1                  UC     lo0
>
>
>Also, made one small error in my initial post.  The wireless router has
>IP 192.168.1.1 and the server's 'wireless' interface is 192.168.1.2
>(going to switch these as soon as I get access to the wireless router
>settings).
>
>I've tried setting static routes between various interfaces on the
>FreeBSD machine, it hasn't worked, but I may be doing it wrong. I
>thought routed should take care of this dynamically, but I'm a bit
>unsure about that.

This sounds a lot like the freebsd machine does not know how to route 
packets to the other side of the wireless router.

Just to confirm how things are connected, ignoring the "wired net" 
for a moment, it sounds like you have something like this:


internet -- A -- freebsd machine -- B -- wireless router/AP -- C -- 
wireless device

You mention that the addresses in use for what I have marked as 'B' 
above, are 192.168.1.1 and 192.168.1.2.  What about the other side of 
the wireless router/AP?  What IP's are being used for the wireless 
devices?  If those IP's are not in the same net as 'B' you'll need a 
static route in the freebsd machine so it knows to send packets for 
the 'C' network to the wireless router/AP.

However, if the wireless router/AP is acting as a bridge, and the 
same address space exists on both sides of the device, then you have 
a different problem.

-Glenn


> >
> > Steve
> >
> > >
> > > Fabian
> > > --
> > > http://www.fabiankeil.de/
> > >
> >
>
>Thanks alot for the replies. I appreciate it.
>
>Jason
>
>_______________________________________________
>freebsd-questions at freebsd.org mailing list
>http://lists.freebsd.org/mailman/listinfo/freebsd-questions
>To unsubscribe, send any mail to "freebsd-questions-unsubscribe at freebsd.org"



More information about the freebsd-questions mailing list