|
||||||||
One thing that I'm also seeing in the logs that I should also mention is this.. /kernel: wi0: watchdog timeout here is the full log from the Diagnostic Log.. Jan 27 06:27:44 /kernel: pci_cfgintr: 1:0 INTA routed to irq 3 Jan 27 06:27:44 /kernel: pcic0: <Ricoh RL5C475 PCI-CardBus Bridge> irq 3 at device 0.0 on pci1 Jan 27 06:27:44 /kernel: pcic0: PCI Memory allocated: 0x88000000 Jan 27 06:27:44 /kernel: pccard0: <PC Card 16-bit bus (classic)> on pcic0 Jan 27 06:27:44 /kernel: fxp0: <Intel 82801DB (ICH4) Pro/100 VE Ethernet> port 0xdc00-0xdc3f mem 0xff8ff000-0xff8fffff irq 7 at device 8.0 on pci1 Jan 27 06:27:44 /kernel: fxp0: Ethernet address 00:07:e9:93:10:71 Jan 27 06:27:44 /kernel: inphy0: <i82562ET 10/100 media interface> on miibus0 Jan 27 06:27:44 /kernel: inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Jan 27 06:27:44 /kernel: isab0: <PCI to ISA bridge (vendor=8086 device=24c0)> at device 31.0 on pci0 Jan 27 06:27:44 /kernel: isa0: <ISA bus> on isab0 Jan 27 06:27:44 /kernel: atapci0: <Intel ICH4 ATA100 controller> port 0xffa0-0xffaf,0-0x3,0-0x7,0-0x3,0-0x7 at device 31.1 on pci0 Jan 27 06:27:44 /kernel: ata0: at 0x1f0 irq 14 on atapci0 Jan 27 06:27:44 /kernel: ata1: at 0x170 irq 15 on atapci0 Jan 27 06:27:44 /kernel: pci0: <unknown card> (vendor=0x8086, dev=0x24c3) at 31.3 irq 5 Jan 27 06:27:44 /kernel: pmtimer0 on isa0 Jan 27 06:27:44 /kernel: fdc0: ready for input in output Jan 27 06:27:44 /kernel: fdc0: cmd 3 failed at out byte 1 of 3 Jan 27 06:27:44 /kernel: atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0 Jan 27 06:27:44 /kernel: atkbd0: <AT Keyboard> flags 0x1 irq 1 on atkbdc0 Jan 27 06:27:44 /kernel: kbd0 at atkbd0 Jan 27 06:27:44 /kernel: vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Jan 27 06:27:44 /kernel: sc0: <System console> at flags 0x100 on isa0 Jan 27 06:27:44 /kernel: sc0: VGA <16 virtual consoles, flags=0x300> Jan 27 06:27:44 /kernel: sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 Jan 27 06:27:44 /kernel: sio0: type 16550A Jan 27 06:27:44 /kernel: sio1 at port 0x2f8-0x2ff irq 3 on isa0 Jan 27 06:27:44 /kernel: sio1: type 16550A Jan 27 06:27:44 /kernel: BRIDGE 020214 loaded Jan 27 06:27:44 /kernel: IPsec: Initialized Security Association Processing. Jan 27 06:27:44 /kernel: IP Filter: v3.4.35 initialized. Default = block all, Logging = enabled Jan 27 06:27:44 /kernel: ad0: 7162MB <QUANTUM FIREBALLlct15 07> [15522/15/63] at ata0-master PIO4 Jan 27 06:27:44 /kernel: acd0: CD-RW <CR-48X9TE> at ata1-master PIO4 Jan 27 06:27:44 /kernel: Mounting root from ufs:/dev/md0c Jan 27 06:27:44 /kernel: pccard: card inserted, slot 0 Jan 27 06:27:44 /kernel: wi0 at port 0x240-0x27f irq 3 slot 0 on pccard0 Jan 27 06:27:44 /kernel: wi0: 802.11 address: 00:02:6f:3a:5d:d9 Jan 27 06:27:44 /kernel: wi0: using RF:PRISM2.5 MAC:ISL3873 Jan 27 06:27:44 /kernel: wi0: Intersil Firmware: Primary 1.01.00, Station 1.04.09 Jan 27 06:27:45 dropbear[127]: Running in background Jan 27 06:27:46 dhclient: DHCPDISCOVER on wi0 to 255.255.255.255 port 67 interval 8 Jan 27 06:27:50 /kernel: wi0: watchdog timeout Jan 27 06:27:54 dhclient: DHCPDISCOVER on wi0 to 255.255.255.255 port 67 interval 8 Jan 27 06:28:02 dhclient: DHCPDISCOVER on wi0 to 255.255.255.255 port 67 interval 7 Jan 27 06:28:09 dhclient: DHCPDISCOVER on wi0 to 255.255.255.255 port 67 interval 10 Jan 27 06:28:19 dhclient: DHCPDISCOVER on wi0 to 255.255.255.255 port 67 interval 14 Jan 27 06:28:23 last message repeated 4 times Jan 27 06:28:33 dhclient: DHCPDISCOVER on wi0 to 255.255.255.255 port 67 interval 12 Jan 27 06:28:45 dhclient: DHCPDISCOVER on wi0 to 255.255.255.255 port 67 interval 2 Jan 27 06:28:47 dhclient: No DHCPOFFERS received. Jan 27 06:28:47 dhclient: No working leases in persistent database - sleeping. On 1/27/06, Anthony Mattke <tony at mattke dot net> wrote: > I really appreciate all the quick responses. > > AND Yeah, I had ibss and bss mixed up, It was late and I was really > tired... sorry :) > > So, my mono box is in bss mode, which DHCP turned on, block private > networks is turned off. But I'm not getting an IP from the AP. (This > is just a routed bridge to my friend/neighbor.) > > Anyway, I just set it up on my AP here in the house so I can easily > check out the status. My AP shows that it is associated with it, but > it dosent seem like it is trying to get an IP address. > > So, I checked the logs, and it shows dhclient trying to get an ip > address, I even ssh'd in (i installed the ssh-shellpack version) and > ran /sbin/dhclient wi0 myself, still no IP. > > The 2 laptops in the house have no problems getting IPs from my AP, > so, why would this box be any different, I added the MAC address to > the allowed table. I've rebooted the AP and the monowall box for heck > of it, still no IP. > > Anyone have a clue where to start looking? > > Thanks so much for the help, > > Tony > > > On 1/27/06, Jim Thompson <jim at netgate dot com> wrote: > > Kenman Wong wrote: > > > > > Hi, > > > > > > I've tried this before. I have two m0n0wall boxes. One has the WiFi as > > > WAN interface and the other has WiFi on the LAN. > > > For the mode I set them both to BSS (infrastructure). (btw you got > > > IBSS, BSS/adhoc, infrastructure mixed up in your email) > > > Set up both side with the same SSID, WEP key, and Mode. I leave the > > > station name field blank. > > > > > > For the box with WiFi on the WAN interface, choose type to be DHCP and > > > disable the "Block private networks" option > > > at the bottom. I am assuming you are picking up an IP from the DHCP > > > server in the private network segment. > > > > > > For the box with WiFi on the LAN interface, enable your DHCP server on > > > the LAN side. > > > > > > Hope that helps. > > > > > > cheers, > > > Kenman > > > > > > Anthony Mattke wrote: > > > > > >> Is there a way to setup my wifi card to be a wireless client / for the > > >> WAN interface? > > >> > > >> How can I get it to associate with the AP? Which mode do I use (in the > > >> mono config)? > > >> > > >> I'm using 1.21 and under Interfaces -> WAN I set DHCP, the ssid, and > > >> the mode to IBSS since I know the other two are not what I want. (just > > >> in case, it shows hostap (which i assume is an AP mode), BSS (which is > > >> says is ad-hoc), and IBSS (which is says in infrastructure mode, and I > > >> have no clue what that is, but I know its not the other two) ) > > >> > > >> Anyway, thats what I changed so far, I currently just want it to pass > > >> traffic.. but I cant get it to pull an IP from the AP. (at least, > > >> according to System-> Interfaces) > > > > > I think you've both confused things some. Here is a key: > > > > Mode: hostap > > Meaning: Act as an AP for other stations. A wireless card in 'hostap' > > mode will *ONLY* communicate > > with a station (or set of stations) which have associated to it. A > > wireless card in "hostap" mode *MUST" have an ESSID set, and *MUST* have > > a channel (frequency) set, or it won't function. > > > > Mode: bss > > Meaning: Act as a client to an AP (the AP can be monowall powered or > > otherwise) > > A 'bss' client will *ONLY* 'communicate' with the AP to which it is > > associated. No BSS <--> BSS communication > > will take place. Unlikes hostap mode you don't have to set the > > channel (frequency) or ESSID. If you don't, then the driver and/or > > firmware on the card will work to select the "best" AP with which to > > associate. > > > > Mode: ibss > > Meaning: this is also known as "ad-hoc". Two ibss (or adhoc) stations > > *can* communicate IF (and only if) they have the same ESSID. The > > behavior of adhoc mode is not as well-defined as the other two modes. > > Its possible, of course, that you can just take two random cards in > > adhoc mode with random settings, and they'll eventually 'find' each > > other and create a network, but you are better off if you actually go > > ahead and set the essid and channel here on both cards. > > > > You can bridge an interface in 'hostap' mode to an Ethernet (or other > > 'hostap' mode wireless interface). > > > > You can *NOT* bridge a bss mode or ibss mode interface to anything > > else. For these, you would need to route the packets. (Technically, > > if the freebsd driver had WDS support, you could, but it doesn't, so..) > > > > So, assuming you want to associate with a distant AP, and provide > > service to a number of clients on an Ethernet segment: > > > > assign wi0 to WAN > > assign sis0 (or whatever) to LAN > > > > WAN > > set ESSID > > set channel > > set mode to BSS > > enable DHCP client (or set an IP address) > > If assigned address is in rfc1918 space, uncheck the "block private > > address space" option > > > > LAN > > set IP address (probably in 1918 space) and netmask > > enable DHCP, check the enabled "range" of IP addresses > > > > reboot > > > > Jim > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch > > For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch > > > > > |