It looks like, due to bridging, the arp table isn't populated correctly.
try tcpdump -i bridge0 (or whatever bridgeN corresponds this interfaces pair) and see what's going on when you try to access the web page and are getting a timeout.
watch for messages like "who has arp blablabla" and replies
Glad I came across this thread before I posted my problem!! ;)
I was having similar problems like "namviet": On my laptop (WinXP) I was able to surf using LAN, but no luck using WLAN!! >:( In addition, through WLAN I was not able to ping my gateway (192.168.1.1) and yet I was able to access the web interface and make any changes that I needed to make without any problems. ??? I even had my NIC "disabled" when I'd have the wireless NIC "enabled", and vice-versa (to avoid any possible conflict).
I know it's weird and doesn't make sense. And yes, I did have the firewall rule setup for the WLAN.
Thanks to "Perry" and the pic he included, I realized where my mistake was…..in the firewall rule for WLAN I had the source as "LAN Subnet" (fyi, I had also tried "any", which obviously didn't work) and not "WLAN Subnet". This was the difference maker for me. Such a mistake had me going in circles.
Thanks again and hope this helps whoever is running into the same problem.
yep, now I'm feeling silly, forgot about one interface, the on board one, so, yes, the wifi card isn't even recognized.
I guess I should pick up one of these atheros cards I've seen mentioned around here.
Thanks for the reply.
I hope it is done.
Interface bonding and n class interface cards make for exiting days ahead.
The wimax forum has caged us up from the speeds and distances they can run in the licenced bands by not ratifying N or releasing good candidates into the unlicensed markets.
Compared to b/g/a this is a slow train coming.
Pfsense is a excellent platform for this kind of development
An entire branch of revenue generation would be opened up for a WISP product that could smoke a LOK box.
Regards
Well… Possible reason for your problems is your router from Ebay.... Here what you can try to check it:
1.Try changing working frequency on router
2. Try to access router from different computer, and work through it for several hours, if it drops frequently, then most likely it is your router.
Found something (didn't explicitely search for it, but just stumbled over it by accident in another forum): rum
Unfortunately it has not (yet) been backported from FreeBSD 7-current.
i still can connect my ppc to the internet….nobody seem to understand why...plz help im very desperate right now and i dont wnat to hook up a cheap wifi router to my switch to get the internet on my ppc.
thx in advance
The problem doing it the way you describe, is that you will end up in a double/triple nat situation, I would recommend going the WDS route (wireless distribution system) as it is a transparent bridge and the only nat on your network would be your pfsense box, unless you switch off the firewall on your 2 linksys routers and probably some other settings, I've never played with stock linksys firmware as I usually flash ddwrt on them as soon as I get hold of them, I suggest firstly you find out what model you have and see if what you need is possible with stock firmware, if not then head over to the ddwrt forums and check if your model/revision if supported using their firmware.
http://www.dd-wrt.com/
Slam
Okay…I enabled polling and interrupt time does go down. However, this does not solve the system locking up (but not completely dead. Only wan dead). I tried the mnbcluster workaround but it still seems to lock up.
Out of ideas now...
I have put this in my /cf/conf/config.xml to set a fixed rate on my atheros wireless card. Hope it helps.
<wan><if>ath2</if>
<mtu><media>OFDM/54Mbps</media>
<mediaopt><bandwidth>100</bandwidth>
<bandwidthtype>Mb</bandwidthtype></mediaopt></mtu></wan>
The line with <media>is what i have added.</media>
