This is a discussion on Wireless Gateway/Router within the comp.unix.bsd.openbsd.misc forums, part of the OpenBSD category; --> Hi all. I am in the process of trying to set up a a wirless router so I can ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hi all. I am in the process of trying to set up a a wirless router so I can get rid of some cables and stuff running all over the place I having a real problem with getting it to work though (ive googled and man'd and faq'd) Here is the issue in a nut shell The server A has two nic, one ext and int on server A I can surf and do everything fine I can login from a laptop via int_nic (wireless) and everything works fine but once I try to acutally surf from the laptop, nothing happens i ahve a few questions Since int_nic is a dhcpd server, should I just be naming in form the 192.168.1.0/24 or should it be a separated subnet 192.168.2 say. Another way of stating this is, should the int_nic and the dhcpd assigned IPs be on the same net or on different subnets? |
| |||
| dude <garnaez@gmail.com> wrote: [...] It's a little difficult to diagnose such problems remote -- so I won't be trying that. But what I will say is -- there's more than 1 way to set these things up. Presumably you config the wifi router using a web interface. I expect that is working OK. You then attach one of the "internal" ports to your desktop box (say). I presume your desktop box has a fixed IP & MAC. It then should be a matter of getting your laptop to connect to the right SID (set on your web interface to th router) and simply try to "ping" (or whatever) the fixed IP of your desktop box. If you can get THAT far, you might try enabling dhcp on the router and allwoing it assign IPS to connecting laptops -- but I'd not be trying that first up. You should also setup a screen (semi permanently soming headed toward the desktop from the router. You can setup tcpdump to listen only for packets from specific subnets, if there is too much traffic on the relevamt wire. Oh yes, get some vallium. And welcome to wifi. |
| ||||
| 1. thanks for the reply 2. It turned out that I didnt understand routing as well as I thought I did 3 ie Routing only defines the next hop!!!!!! 4. so when my laptop got its default gateway, it was a nic complete different thatn the only one it knew about so I when ahead and defined it and voila it worked ie C(laptop) ---> B(Wifi CARD) ---> (ext-if) I was defining the laptop's gateway as ext-if, which it had no way of contacting russell kym horsell wrote: > dude <garnaez@gmail.com> wrote: > [...] > > It's a little difficult to diagnose such problems remote -- so I won't > be trying that. > > But what I will say is -- there's more than 1 way to set these things up. > > Presumably you config the wifi router using a web interface. I expect > that is working OK. You then attach one of the "internal" ports to > your desktop box (say). I presume your desktop box has a fixed IP & MAC. > > It then should be a matter of getting your laptop to connect to the right > SID (set on your web interface to th router) and simply try to "ping" > (or whatever) the fixed IP of your desktop box. > > If you can get THAT far, you might try enabling dhcp on the router and > allwoing it assign IPS to connecting laptops -- but I'd not be trying that > first up. > > You should also setup a screen (semi permanently > soming headed toward the desktop from the router. You can setup > tcpdump to listen only for packets from specific subnets, if there is too > much traffic on the relevamt wire. > > Oh yes, get some vallium. And welcome to wifi. |