uhhhhh, what did you just say? I don't understand. What are you trying to do?
why would you need a second name server on your local LAN? The netgear can only port forward for one. Are you trying to route between the 2 nics on the OBSD machine? Gmail b0rked your ASCII diagram. --Bryan On 3/3/06, Harry Putnam <[EMAIL PROTECTED]> wrote: > I'm not sure which way to jump with this question which is a > reflection of unskilled, inexperienced networking background. > > This may not even be the right way to do it. > > First: This is all something of a training exercise and not > an important production setup. > > Summary: > I'm attempting to add a second nic and address on a machine running > current. I also run an authoratative nameserver on a separate machine > not running bsd but running bind-9.3.2. So this problem may slop over > into the named setup on a gentoo linux box. > > A simple diagram will convey more than a description: The prefix to all > displayed IPs is 192.168, but be aware it is simplified ... there are > more machines involved. > > INTERNET > | (Dynamic IP) > | > NETGEAR (consumer grade router FVS-318) > | 0.20 > -------------------------------------------------- > | 0.4 | 0.3 | 0.5 | 0.19 > | | | | > [ m1 ] [ m2 ] [ m3 ] [ m4 ] > | 1.2 | 1.1 > |________________ Unswitched hub ________________| > > So the far right (m4) is the obsd machine and is sent copies of all > connections that come to NETGEAR. All incoming on that intface is > blocked and logged (0.19). Out on that int_fc is passed keeping > state. > > In and out are passed with no restrictions on 1.1. This line > in /etc/sysctl.conf is not uncommented nor is it set manually. > # net.inet.ip.forwarding=1 # 1=Permit [...] > > I've tried to set this up all under one domain so my network would end > up 192.168/16 all under `local.lan'. I'm not sure that is the best > way to go but it seemed to be easier to setup bind on the other computer > this way. Or I should say I lacked examples for doing it. While going > net/16 is similar to the examples in `DNS and Bind 4th. ed'. > > /etc/hostname.* look like: > /etc/hostname.rl0 /etc/hostname.xl0 > 192.168.0.19 255.255.0.0 192.168.1.1 255.255.0.0 > > /etc/mygate > 192.168.0.20 > > So how do I keep stuff from happening like firing up > `lynx www.google.com' and not being able to connect because > 192.168.1.1 tries to handle it? > > I think I'm missing specific routing for 1.1.
