Quick Routing Question
iaccounts at ibctech.ca
Tue Nov 1 07:25:34 PST 2005
> Destination Gateway Flags Refs Use Netif
> default 220.127.116.11 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
> 18.104.22.168/26 link#2 UC 0 0 xl0
> 22.214.171.124 00:13:5f:00:f0:ee UHLW 1 0
> xl0 1188
> 126.96.36.199 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.
- Give the wireless laptop a static IP inside the wireless IP subnet
- 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
- effectively, if you have wireless connectivity from the laptop to the
AP, you should be able to ping the FW, and vice-versa
If it doesn't work, cable up the laptop to the LAN side of the AP,
ensuring it has a proper IP in the wifi range, and then ping.
If all else fails, set up a round of say 100 pings from the laptop to
the FBSD box, and on the FBSD box, do this:
# tcpdump -n -i fxp0
where fxp0 is the interface the AP is plugged into. This will show you
first, if the pings are getting from the wifi subnet to the FBSD box,
and also if they are being returned. Inbound pings but no outbound pings
could indicate a deeper routing issue or FW issue. No inbound pings
could indicate a problem with IP allocation or subnet issues.
tcpdump (1) is a great tool, and may even help further troubleshoot the
If you can ping from wifi to FBSD wifi interface, then push the scope of
the test further, trying to ping the cabled side of the FBSD box.
let us know what you find, as the more detail we have after certain
tests, will enable us to provide further recommendations. Also, an
ifconfig output could help too, so long everything is all connected.
> 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.
> > Steve
> > >
> > > Fabian
> > > --
> > > http://www.fabiankeil.de/
> > >
> Thanks alot for the replies. I appreciate it.
> freebsd-questions at freebsd.org mailing list
> To unsubscribe, send any mail to
> "freebsd-questions-unsubscribe at freebsd.org"
More information about the freebsd-questions