View Single Post
  #9   (View Single Post)  
Old 15th September 2008
ocicat ocicat is offline
Administrator
 
Join Date: Apr 2008
Posts: 3,318
Default

Quote:
Originally Posted by kevinz View Post
Windows Box - Wireless nic - 192.168.0.5/255.255.255.0
- 2nd nic - 10.0.0.2/255.0.0.0

Connected to that 2nd nic via crossover cable to openbsd is
xl0 - 10.0.0.1/255.0.0.0
2nd nic - xl1 - dhcp(dsl connection)
This summary is a bit misleading. One interface on your OpenBSD system may be getting its IP address via a DHCP server from your DSL ISP, but xl0 exposed to your Windows box appears to be manually set as is the IP address of your second NIC on your Windows box itself.
Quote:
So from other hosts I need to reach 10.0.0.1/255.0.0.0
Correct. You have hosts on one subnet which need to communicate to a host in a different subnet. Routers classically redirect packets from one subnet into another.

The problem you are experiencing is when hosts on 192.168.0.0/24 want to send a message to 10.0.0.0/8, the sending NIC will see that the target address is on a different subnet, so they will send packets destined to 10.0.0.0/8 via the default router -- which is most likely configured to be your wireless router. When your wireless router receives packets for yet another private network, it will most likely be dropping the packets as it should.

What you really want to do is:
  • route all packets destined to 10.0.0.0/8 to your Windows box. It is up to you to determine whether your wireless router is flexible enough in its configuration to support this kind of action.
  • Your wireless router will also need to have a default route which points anything not targeting 10.0.0.0/8 on to your cable ISP.
  • Your Windows box will also need to be configured as a router (multihoming) as discussed earlier.
Could this be simpler? Yes, but you have already cited reasons for why you don't want to have your OpenBSD system connected to your wireless router.
Reply With Quote