Bridging problems.. (WaveLan related?)
I have been trying for over a week now to get bridging working, but without success. I have tried both 4.0 and current, but with no luck. Anyways, my setup is as follows.. On one end is a Lucent WavePoint attached to the outside world. (Some sort of switch I believe. I really don't understand the setup--they are using some sort of vlan stuff) I'm tempted to replace the WavePoint with a PC, but I don't have the hardware for that now. On my end, I have a box with a wi0 and fxp0--I was hoping to set it up to do transparent bridging. So far however, I can't get anything on this side of the bridge box to talk to the outside world. I can see all the network traffic from my box, however I can't talk through the bridge. Basically, any arp request that goes out, seems to disappear. If I run tcpdump on the wavelan interface, it shows the arp requests, but never any replies. I can see incoming arp requests for my box, and it seems to send the reply, only to be lost somewhere as well. Another interesting thing occurs from the bridge box itself. If I ping the network broadcast, only things on the wavelan side reply. This may be some irrelevant quirk, I'm not sure. Has anyone ever set up a box like this? Will it work with a WavePoint attached to a switch on the other side? I can't see why it shouldn't, but maybe I am missing something. Does the wavelan network need to be "ad-hoc" instead of BSS mode? All I know is this is becoming really irritating. (Not FreeBSD, but the fact that we don't have direct access to the network on the other side.) We have been trying to get this set up since May, and it has been a nightmare to deal with the politics and to debug it from one side. Ugh. Any theories/etc would be very welcome.. Thanks, Chris Csanady To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Bridging problems.. (WaveLan related?)
It never fails.. I always post stuff just minutes too soon. Anyways, it seems that the problem is with the WaveLan network. In ad-hoc, or infrastructure mode, the card can only send frames with its own mac address as the source. Apparrently, the card needs to be set up as an access point (or something) to do bridging. Is there a way to do this in the current driver? If not, are there plans? Chris To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Bridging problems.. (WaveLan related?)
On Sat, Jul 01, 2000 at 01:56:51AM -0500, Chris Csanady wrote: It never fails.. I always post stuff just minutes too soon. Anyways, it seems that the problem is with the WaveLan network. In ad-hoc, or infrastructure mode, the card can only send frames with its own mac address as the source. Apparrently, the card needs to be set up as an access point (or something) to do bridging. You can make it run as an access point... if and only if you're prepared to produce an 802.11 protocol suite to run in the FreeBSD kernel, because you won't be able to use the one in the card's firmware. Of course, if you want to do something as insane as that, I'm sure your efforts will be welcommed with open legs^H^H^H^Harms. Being able to replace an access point with a FreeBSD box which costs a third as much would be tres cool. This is particularly true in the case of the Aironet 802.11 gear, which has even worse restrictions wrt bridging and even more expensive access points. (FWIW: With the Aironet kit, when you place the card into "monitor mode" you can't transmit frames at all). - mark -- Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
