Jordan Breeding wrote:
> #ifconfig xl0 netmask
> #ifconfig xl1 netmask

This is bogus.  You are telling the machine that the 192.168.1
net exists on both xl0 and xl1.  It exists on only one or the
other of them.  To which interface do you expect it to send a
packet destined for

> #route delete -net
> #route add -net default
> #route add -net -interface
> #netstat -r

This is still pretty bogus.  The route is before
the other one, or it doesn't know how to frind the gateway, since it doesn't know which interface to write

> This shows no problems at all and works whether I use the routing daemon
> or use static routes at boot up, however -current will not allow me to
> do the same thing that I have done above, instead I get the following:

[ ... ]

> bash-2.05a# ifconfig xl1 netmask
> ifconfig: ioctl (SIOCAIFADDR): File exists
> The only thing which I can think of is that either a) it is a userland
> change in -current, or b) I was only ever running the GENERIC kernel for
> 4.5-RELEASE and never recompiled my kernel until I was compiling with
> -current source so maybe it is some option in the GENERIC config file
> for the -current source.  If it is b) could someone please tell me which
> option is causing this so that I may turn it back off.  I would really
> like to try and get this working exactly as I have in Linux, Solaris,
> FreeBSD 4.5-RELEASE.  Thanks for any help.

Change the netmask to to tell it that it is a
point-to-point link.

If you want to build a bridge, then you need to turn on ip
forwarding (net.inet.ip.forwarding=1).

Really, you need to think through your network setup a bit
more; each interface needs to be on its own network, so if
you mask off the top parts using the netmask, no two interfaces
are equal.

-- Terry

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to