Re: NetBSD domU on routed Xen setup

[Dustin Marquess <dmarquess%gmail.com@localhost>]

I don't have a setup to test it on, but...

Linux ifconfig(8) says:

      [-]pointopoint [addr]
              This  keyword  enables  the point-to-point mode of an interface,
              meaning that it is a  direct  link  between  two  machines  with
              nobody else listening on it.
              If  the address argument is also given, set the protocol address
              of the other side of the link, just like  the  obsolete  dstaddr
              keyword  does.  Otherwise, set or clear the IFF_POINTOPOINT flag
              for the interface.

NetBSD ifconfig(8) has:

     ifconfig interface address_family [address [dest_address]] [parameters]
[SNIP]
     dest_address    Specify the address of the correspondent on the other end
                     of a point to point link.

So I guess the NetBSD version would just involve putting the remote IP
after the local IP on the ifconfig line.

-Dustin

On Tue, Feb 23, 2010 at 11:18 AM, Dirk H. Schulz
<dirk.schulz%kinzesberg.de@localhost> wrote:
> Hi all,
>
> I am running several Debian dom0s with NetBSD domUs using a bridged setup,
> that is working fine.
>
> I have one Debian dom0 with a routed xen setup, and that is where I have
> trouble getting NetBSD domUs to connect to the network. On the Debian domUs
> I have a network interface definition like this:
>
>> iface eth0 inet static
>>  address 1.2.3.4.5
>>  gateway 7.8.9.10
>>  netmask 255.255.255.192
>>  pointopoint 7.8.9.10
>
> The gateway address is the address of the dom0 external interface. In the
> Linux domUs the "pointopoint ..." entry makes the routed setup work.
>
> Now how do I configure a NetBSD domU similarly? There seems not to be a
> "pointopoint" configuration option for interfaces, and setting up a pppoe
> interface does not make sense to me since there is no pppoe counter part.
> I googled around a lot but came up empty.
>
> Any hint or help is appreciated.
>
> Dirk
>
>