Paul Beard paulbe...@gmail.com wrote:
After some more head scratching, it sounds like what I want is a
bridge. Reading if_bridge(4), the first example looks a lot like
what I am trying to do.
...
Did I misread this? Does sending packets between two physical
interfaces require a bridge?
It
On 08/27/2011 11:08 PM, Paul Beard wrote:
On Aug 27, 2011, at 8:48 PM, CyberLeo Kitsana wrote:
tcpdump(1) is your friend; it seems cryptic and obtuse at first glance,
but it will help immensely
I wasn't sure there was any reason to use that yet: I can't even ping it from
another host.
On Aug 28, 2011, at 7:04 AM, CyberLeo Kitsana wrote:
It is especially useful when you cannot ping, as it can tell you if the
packets are even arriving.
The no route to host result makes me think the packets aren't going far ;-)
The new device and the wired interface are at adjacent numeric
On Aug 28, 2011, at 12:38 PM, Bill Tillman wrote:
I did this to have the experience with it and to have a backup to my Netgear
wireless router. The trouble was the Netgear wireless AP device works so well
and is plenty fast, unlike what I was getting with my FreeBSD server. The
Netgear
On Sun, 28 Aug 2011, Paul Beard wrote:
One thing that has seemed opaque to me is that both ath0 and wlan0
display when I run ifconfig and look very similar: makes me think they
might be stepping on each other. Or it's just one more thing I don't
understand :-(
In 8.x, a virtual wlan0 device
On Aug 28, 2011, at 3:17 PM, Warren Block wrote:
In 8.x, a virtual wlan0 device is created to speak to the actual device, ath0
in this case. It's normal.
Maybe I'm just confused by normality. I guess what would help in the Handbook,
if nowhere else, is the *full* output of ifconfig(8)
From: Paul Beard paulbe...@gmail.com
To:
Cc: freebsd-questions@FreeBSD. ORG freebsd-questions@freebsd.org
Sent: Sunday, August 28, 2011 12:22 PM
Subject: Re: wireless access point in FreeBSD 8.2p2
On Aug 28, 2011, at 7:04 AM, CyberLeo Kitsana wrote:
It is especially useful when you cannot
On Sun, 28 Aug 2011, Paul Beard wrote:
On Aug 28, 2011, at 3:17 PM, Warren Block wrote:
In 8.x, a virtual wlan0 device is created to speak to the actual device, ath0
in this case. It's normal.
Maybe I'm just confused by normality. I guess what would help in the
Handbook, if nowhere
On Aug 28, 2011, at 5:28 PM, Warren Block wrote:
IMO, the wireless section is already so stuffed full of detail that it
obscures the basics. In fairness, it's a complicated topic. But I'd much
rather see a simple setup for the 80% use case followed by another section
with all the grimy
From owner-freebsd-questi...@freebsd.org Sun Aug 28 20:41:41 2011
From: Paul Beard paulbe...@gmail.com
Date: Sun, 28 Aug 2011 18:39:41 -0700
To: Warren Block wbl...@wonkity.com
Cc: freebsd-questions@FreeBSD. ORG freebsd-questions@freebsd.org
Subject: Re: wireless access point in FreeBSD
I seem to be missing something, possibly from reading too many HOWTOs. What I
am trying to do is get a system with a wireless card to stand in as a wireless
AP should my aging LinkSys base station develop a tragic smoke leak.
It's an ath0-based card and the following steps suggest it should
On 08/28/11 02:21, Paul Beard wrote:
I seem to be missing something, possibly from reading too many HOWTOs. What I
am trying to do is get a system with a wireless card to stand in as a
wireless AP should my aging LinkSys base station develop a tragic smoke leak.
It's an ath0-based card and
On 08/27/2011 11:21 AM, Paul Beard wrote:
I seem to be missing something, possibly from reading too many HOWTOs. What I
am trying to do is get a system with a wireless card to stand in as a
wireless AP should my aging LinkSys base station develop a tragic smoke leak.
It's an ath0-based
On Aug 27, 2011, at 8:48 PM, CyberLeo Kitsana wrote:
tcpdump(1) is your friend; it seems cryptic and obtuse at first glance,
but it will help immensely
I wasn't sure there was any reason to use that yet: I can't even ping it from
another host.
wlan0 itself will not assign v4 addresses to
14 matches
Mail list logo
