Re: can't get vmd to work on current
> True. If it was merely GENERIC[.MP] with vmm enabled, then fine. But a > kernel named "TIMMU" could deserve some explanation as to what's been > done to it. That's why I included the config in the first email, but I see where the confusion arises. Since VMM is not enabled by default and changing the GENERIC config doesn't seem right (and will mess with cvs updates). Best way I can come up with.. # cat /usr/src/sys/arch/amd64/conf/VMM include "arch/amd64/conf/GENERIC.MP" vmm0at mainbus0 Is that acceptable? --- Regards, Mart
Re: can't get vmd to work on current
>> OpenBSD 6.0-current (TIMMU) #4: Wed Sep 7 00:35:13 EEST 2016 > > Not going to help with custom kernels. Work on -current on real Only reason that I'm using a custom kernel is to enable vmm, so this is a catch 22. > hardware with a standard kernel if you want to play with vmm please. Hm, yes, bare metal makes sense --- Regards, Mart > -ml > >> r...@bsd1.lan:/usr/src/sys/arch/amd64/compile/TIMMU >> real mem = 1056899072 (1007MB) >> avail mem = 1020399616 (973MB) >> mpath0 at root >> scsibus0 at mpath0: 256 targets >> mainbus0 at root >> bios0 at mainbus0: SMBIOS rev. 2.5 @ 0xe1000 (10 entries) >> bios0: vendor innotek GmbH version "VirtualBox" date 12/01/2006 >> bios0: innotek GmbH VirtualBox >> acpi0 at bios0: rev 2 >> acpi0: sleep states S0 S5 >> acpi0: tables DSDT FACP APIC SSDT >> acpi0: wakeup devices >> acpitimer0 at acpi0: 3579545 Hz, 32 bits >> acpimadt0 at acpi0 addr 0xfee0: PC-AT compat >> cpu0 at mainbus0: apid 0 (boot processor) >> cpu0: Intel(R) Pentium(R) CPU G4400 @ 3.30GHz, 3312.50 MHz >> cpu0: >> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,SSSE3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,RDRAND,NXE,LONG,LAHF,ABM,3DNOWP,ITSC,RDSEED,CLFLUSHOPT >> cpu0: 256KB 64b/line 8-way L2 cache >> cpu0: smt 0, core 0, package 0 >> mtrr: CPU supports MTRRs but not enabled by BIOS >> cpu0: apic clock running at 1009MHz >> cpu1 at mainbus0: apid 1 (application processor) >> cpu1: Intel(R) Pentium(R) CPU G4400 @ 3.30GHz, 3345.27 MHz >> cpu1: >> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,SSSE3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,RDRAND,NXE,LONG,LAHF,ABM,3DNOWP,ITSC,RDSEED,CLFLUSHOPT >> cpu1: 256KB 64b/line 8-way L2 cache >> cpu1: smt 0, core 1, package 0 >> ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins >> acpiprt0 at acpi0: bus 0 (PCI0) >> acpicpu0 at acpi0: C1(@1 halt!) >> acpicpu1 at acpi0: C1(@1 halt!) >> "PNP0303" at acpi0 not configured >> "PNP0F03" at acpi0 not configured >> "PNP0501" at acpi0 not configured >> acpiac0 at acpi0: AC unit online >> acpivideo0 at acpi0: GFX0 >> pci0 at mainbus0 bus 0 >> pchb0 at pci0 dev 0 function 0 "Intel 82441FX" rev 0x02 >> pcib0 at pci0 dev 1 function 0 "Intel 82371SB ISA" rev 0x00 >> pciide0 at pci0 dev 1 function 1 "Intel 82371AB IDE" rev 0x01: DMA, channel >> 0 configured to compatibility, channel 1 configured to compatibility >> wd0 at pciide0 channel 0 drive 0: >> wd0: 128-sector PIO, LBA, 20480MB, 41943040 sectors >> wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2 >> atapiscsi0 at pciide0 channel 1 drive 0 >> scsibus1 at atapiscsi0: 2 targets >> cd0 at scsibus1 targ 0 lun 0:ATAPI 5/cdrom removable >> cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2 >> vga1 at pci0 dev 2 function 0 "InnoTek VirtualBox Graphics Adapter" rev 0x00 >> wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) >> wsdisplay0: screen 1-5 added (80x25, vt100 emulation) >> em0 at pci0 dev 3 function 0 "Intel 82540EM" rev 0x02: apic 2 int 19, >> address 08:00:27:4e:af:77 >> "InnoTek VirtualBox Guest Service" rev 0x00 at pci0 dev 4 function 0 not >> configured >> ohci0 at pci0 dev 6 function 0 "Apple Intrepid USB" rev 0x00: apic 2 int 22, >> version 1.0 >> piixpm0 at pci0 dev 7 function 0 "Intel 82371AB Power" rev 0x08: apic 2 int >> 23 >> iic0 at piixpm0 >> isa0 at pcib0 >> isadma0 at isa0 >> com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo >> pckbc0 at isa0 port 0x60/5 irq 1 irq 12 >> pckbd0 at pckbc0 (kbd slot) >> wskbd0 at pckbd0: console keyboard, using wsdisplay0 >> pms0 at pckbc0 (aux slot) >> wsmouse0 at pms0 mux 0 >> pcppi0 at isa0 port 0x61 >> spkr0 at pcppi0 >> usb0 at ohci0: USB revision 1.0 >> uhub0 at usb0 configuration 1 interface 0 "Apple OHCI root hub" rev >> 1.00/1.00 addr 1 >> vmm at mainbus0 not configured >> vscsi0 at root >> scsibus2 at vscsi0: 256 targets >> softraid0 at root >> scsibus3 at softraid0: 256 targets >> root on wd0a (0726640cbb73e288.a) swap on wd0b dump on wd0b >> o >> On Wed, Sep 07, 2016 at 08:50:02AM -0700, Mike Larkin wrote: >> > On Wed, Sep 07, 2016 at 09:43:47PM +0300, Mart T??nso wrote: >> > > Hello, >> > > >> > > I'm trying to get vmd working, but am failing so far. >> > > >> > > What I've done: >> > > >> > > Custom kernel config to enable vmm: >> > > >> > > include "arch/amd64/conf/GENERIC" >> > > >> > > option MULTIPROCESSOR >> > > #option MP_LOCKDEBUG >> > > >> > > cpu*at mainbus? >> > > >> > > # enable vmm >> > > vmm0 at mainbus0 >> > > # EOF >> > > >> > > >> > > /etc/vm.conf: >> > > # vm.conf >> > > sets="/var/www/htdocs/pub/OpenBSD/snapshots/amd64/" >> > > >> > > # OpenBSD snapshot install test >> > > vm "openbsd.vm" { >> > > memory 512M >> > > kernel $sets "bsd.rd" >> > > >> > > # First disk from 'vmctl create "/home/vm/OpenBSD.img" -s 4G' >> > > disk "/home/vm/OpenBSD.img"
Re: can't get vmd to work on current
Pardon me, dmesg follows. This is inside a Virtualbox VM for "testing purposes". OpenBSD 6.0-current (TIMMU) #4: Wed Sep 7 00:35:13 EEST 2016 r...@bsd1.lan:/usr/src/sys/arch/amd64/compile/TIMMU real mem = 1056899072 (1007MB) avail mem = 1020399616 (973MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.5 @ 0xe1000 (10 entries) bios0: vendor innotek GmbH version "VirtualBox" date 12/01/2006 bios0: innotek GmbH VirtualBox acpi0 at bios0: rev 2 acpi0: sleep states S0 S5 acpi0: tables DSDT FACP APIC SSDT acpi0: wakeup devices acpitimer0 at acpi0: 3579545 Hz, 32 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Pentium(R) CPU G4400 @ 3.30GHz, 3312.50 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,SSSE3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,RDRAND,NXE,LONG,LAHF,ABM,3DNOWP,ITSC,RDSEED,CLFLUSHOPT cpu0: 256KB 64b/line 8-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: CPU supports MTRRs but not enabled by BIOS cpu0: apic clock running at 1009MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Pentium(R) CPU G4400 @ 3.30GHz, 3345.27 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,SSSE3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,RDRAND,NXE,LONG,LAHF,ABM,3DNOWP,ITSC,RDSEED,CLFLUSHOPT cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins acpiprt0 at acpi0: bus 0 (PCI0) acpicpu0 at acpi0: C1(@1 halt!) acpicpu1 at acpi0: C1(@1 halt!) "PNP0303" at acpi0 not configured "PNP0F03" at acpi0 not configured "PNP0501" at acpi0 not configured acpiac0 at acpi0: AC unit online acpivideo0 at acpi0: GFX0 pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel 82441FX" rev 0x02 pcib0 at pci0 dev 1 function 0 "Intel 82371SB ISA" rev 0x00 pciide0 at pci0 dev 1 function 1 "Intel 82371AB IDE" rev 0x01: DMA, channel 0 configured to compatibility, channel 1 configured to compatibility wd0 at pciide0 channel 0 drive 0: wd0: 128-sector PIO, LBA, 20480MB, 41943040 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2 atapiscsi0 at pciide0 channel 1 drive 0 scsibus1 at atapiscsi0: 2 targets cd0 at scsibus1 targ 0 lun 0:ATAPI 5/cdrom removable cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2 vga1 at pci0 dev 2 function 0 "InnoTek VirtualBox Graphics Adapter" rev 0x00 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) em0 at pci0 dev 3 function 0 "Intel 82540EM" rev 0x02: apic 2 int 19, address 08:00:27:4e:af:77 "InnoTek VirtualBox Guest Service" rev 0x00 at pci0 dev 4 function 0 not configured ohci0 at pci0 dev 6 function 0 "Apple Intrepid USB" rev 0x00: apic 2 int 22, version 1.0 piixpm0 at pci0 dev 7 function 0 "Intel 82371AB Power" rev 0x08: apic 2 int 23 iic0 at piixpm0 isa0 at pcib0 isadma0 at isa0 com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo pckbc0 at isa0 port 0x60/5 irq 1 irq 12 pckbd0 at pckbc0 (kbd slot) wskbd0 at pckbd0: console keyboard, using wsdisplay0 pms0 at pckbc0 (aux slot) wsmouse0 at pms0 mux 0 pcppi0 at isa0 port 0x61 spkr0 at pcppi0 usb0 at ohci0: USB revision 1.0 uhub0 at usb0 configuration 1 interface 0 "Apple OHCI root hub" rev 1.00/1.00 addr 1 vmm at mainbus0 not configured vscsi0 at root scsibus2 at vscsi0: 256 targets softraid0 at root scsibus3 at softraid0: 256 targets root on wd0a (0726640cbb73e288.a) swap on wd0b dump on wd0b o On Wed, Sep 07, 2016 at 08:50:02AM -0700, Mike Larkin wrote: > On Wed, Sep 07, 2016 at 09:43:47PM +0300, Mart T??nso wrote: > > Hello, > > > > I'm trying to get vmd working, but am failing so far. > > > > What I've done: > > > > Custom kernel config to enable vmm: > > > > include "arch/amd64/conf/GENERIC" > > > > option MULTIPROCESSOR > > #option MP_LOCKDEBUG > > > > cpu*at mainbus? > > > > # enable vmm > > vmm0 at mainbus0 > > # EOF > > > > > > /etc/vm.conf: > > # vm.conf > > sets="/var/www/htdocs/pub/OpenBSD/snapshots/amd64/" > > > > # OpenBSD snapshot install test > > vm "openbsd.vm" { > > memory 512M > > kernel $sets "bsd.rd" > > > > # First disk from 'vmctl create "/home/vm/OpenBSD.img" -s 4G' > > disk "/home/vm/OpenBSD.img" > > > > # Second disk from OpenBSD contains the install sets > > disk $sets "install59.fs" > > > > # Interface will show up as tap(4) on the host and as vio(4) in the > > VM > > interfaces 1 > > } > > # EOF > > > > > > And this is where it all falls apart: > > > > # vmd -vd > > vmd: /dev/vmm: Operation not supported by device > > > > > > What am I missing here? > > > > --- > > Regards, > > > > Mart > > > > Probably unsupported cpu. But you didn't give us even a dmesg, so who knows.
can't get vmd to work on current
Hello, I'm trying to get vmd working, but am failing so far. What I've done: Custom kernel config to enable vmm: include "arch/amd64/conf/GENERIC" option MULTIPROCESSOR #option MP_LOCKDEBUG cpu*at mainbus? # enable vmm vmm0 at mainbus0 # EOF /etc/vm.conf: # vm.conf sets="/var/www/htdocs/pub/OpenBSD/snapshots/amd64/" # OpenBSD snapshot install test vm "openbsd.vm" { memory 512M kernel $sets "bsd.rd" # First disk from 'vmctl create "/home/vm/OpenBSD.img" -s 4G' disk "/home/vm/OpenBSD.img" # Second disk from OpenBSD contains the install sets disk $sets "install59.fs" # Interface will show up as tap(4) on the host and as vio(4) in the VM interfaces 1 } # EOF And this is where it all falls apart: # vmd -vd vmd: /dev/vmm: Operation not supported by device What am I missing here? --- Regards, Mart
Re: spreed server
Did you use "gmake"? Mart On Thu, Jul 21, 2016 at 10:29 PM, Stephen Grafwrote: > Has anyone tried to build the spreed server? > https://github.com/strukturag/spreed-webrtc > > I tried, but the configure would not run with openbsd automake, autoconf and > m4 packages. > When I loaded the GNU equivalents, the configure ran but the makefile > produced did not work, > probably because the openbsd packages were not used.
Re: Secure PKG_PATH for doas
Do feel free to select from the list of actual mirrors: http://www.openbsd.org/ftp.html Mart On Thu, May 19, 2016 at 10:02 PM, Mihai Popescuwrote: >> echo "installpath = http://your.favorite.mirror/; > /etc/pkg.conf > >> .. and enjoy! > > Error from http://your.favorite.mirror/ > ftp: your.favorite.mirror: no address associated with name > http://your.favorite.mirror/ is empty > > :-)
Re: Secure PKG_PATH for doas
There is an alternative to PKG_PATH env var: http://man.openbsd.org/OpenBSD-current/man5/pkg.conf.5 echo "installpath = http://your.favorite.mirror/; > /etc/pkg.conf .. and enjoy! Mart On Thu, May 19, 2016 at 4:32 AM, Ted Unangstwrote: > Igor Mironov wrote: >> The packages and ports' FAQ mentions that those using doas need to pass >> keepenv { PKG_PATH } in the config file. Is there a way to instruct doas to >> take PKG_PATH (or another variable) from the target account's environment >> (~/.profile)? > > No, but you can easily write a shell wrapper that sets things up and calls > pkg_add.
Re: routes get assigned to a wrong interface, openbsd 5.9
Hello, It took a while, but I got the patch tested with current source. I can confirm that even with the gaping /8 netmask on ppp0 interface, routes end up on tun0 interface as expected. Are there any specific tests you would like me to do or extra information I could provide? Regards, Mart On Wed, Apr 13, 2016 at 1:50 PM, Martin Pieuchot <m...@openbsd.org> wrote: > On 13/04/16(Wed) 13:27, Mart Tõnso wrote: >> Thank you! Assigning a proper ppp netmask solved this issue. I'll see >> if I can get arround to testing the patch. Is there a chance of >> including it in the "current"? > > I'm waiting for you report, if it is positive I'll ask for reviews. If > the review are ok, it will be included.
Re: routes get assigned to a wrong interface, openbsd 5.9
Thank you! Assigning a proper ppp netmask solved this issue. I'll see if I can get arround to testing the patch. Is there a chance of including it in the "current"? > By the way why do you use the same src and dst address? I've been wondering about that myself, but that's how the client interface ends up when server is running with "subnet" topology. It seems to work well with bsd/linux/macos/windows clients, so I haven't gone digging deeper. Regards, Mart On Wed, Apr 13, 2016 at 10:45 AM, Martin Pieuchot <m...@openbsd.org> wrote: > Hello Mart, > > On 13/04/16(Wed) 09:22, Mart Tõnso wrote: >> Ah, yes, sorry about that. Here's the full routing info with ifconfig output: >> >> # ifconfig >> [...] >> ppp0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1500 >> priority: 0 >> groups: ppp egress >> inet 10.128.195.179 --> 10.64.64.64 netmask 0xff00 > ^^ > Here is the problem. For historical reasons the code that finds > a matching interface to attach your route matches your gateway > with ppp0's address/netmask. > > A workaround would be to change your ppp0 setup to use a /32 mask. > > A correct fix is included below, I'll be interested to hear if it > works for you. > >> tun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1500 >> priority: 0 >> groups: tun >> status: active >> inet 10.88.0.124 --> 10.88.0.124 netmask 0xff00 > ^^ > By the way why do you use the same src and dst address? > > Index: net/route.c > === > RCS file: /cvs/src/sys/net/route.c,v > retrieving revision 1.298 > diff -u -p -r1.298 route.c > --- net/route.c 26 Mar 2016 21:56:04 - 1.298 > +++ net/route.c 13 Apr 2016 07:38:11 - > @@ -740,20 +740,16 @@ ifa_ifwithroute(int flags, struct sockad > ifa = ifaof_ifpforaddr(dst, ifp); > if_put(ifp); > } else { > - ifa = ifa_ifwithnet(gateway, rtableid); > - } > - } > - if (ifa == NULL) { > - struct rtentry *rt = rtalloc(gateway, 0, rtableid); > - /* The gateway must be local if the same address family. */ > - if (!rtisvalid(rt) || ((rt->rt_flags & RTF_GATEWAY) && > - rt_key(rt)->sa_family == dst->sa_family)) { > + struct rtentry *rt; > + > + rt = rtalloc(gateway, RT_RESOLVE, rtableid); > + if (rt != NULL) > + ifa = rt->rt_ifa; > rtfree(rt); > - return (NULL); > } > - ifa = rt->rt_ifa; > - rtfree(rt); > } > + if (ifa == NULL) > + return (NULL); > if (ifa->ifa_addr->sa_family != dst->sa_family) { > struct ifaddr *oifa = ifa; > ifa = ifaof_ifpforaddr(dst, ifa->ifa_ifp);
Re: routes get assigned to a wrong interface, openbsd 5.9
pr 13 09:12:29 ruuter_dev01 openvpn[26943]: /sbin/route add -net 10.88.0.0 10.88.0.124 -netmask 255.255.255.0 Apr 13 09:12:29 ruuter_dev01 openvpn[26943]: /sbin/route add -net 10.99.0.0 10.88.0.1 -netmask 255.255.255.0 Apr 13 09:12:29 ruuter_dev01 openvpn[26943]: /sbin/route add -net 10.90.0.0 10.88.0.1 -netmask 255.255.255.0 # route -n get 10.88.0.1 route to: 10.88.0.1 destination: 10.88.0.0 mask: 255.255.255.0 gateway: 10.88.0.124 interface: tun0 if address: 10.88.0.124 priority: 8 (static) flags: <UP,GATEWAY,DONE,STATIC> use mtuexpire 0 0 0 This seems ok, so why do the routes end up on ppp0? --- Regards, Mart On Tue, Apr 12, 2016 at 4:55 PM, Martin Pieuchot <m...@openbsd.org> wrote: > On 12/04/16(Tue) 16:20, Mart Tõnso wrote: >> Hello. >> >> I am hitting a strange behaviour with openbsd 5.9. >> >> # uname -a >> OpenBSD router_dev01.lan 5.9 GENERIC.MP#1888 amd64 >> >> There's pppd running on the box (for a 3g connection) and OpenVPN >> connection on top of that. >> >> The bug is that any routes pushed from openvpn server get assigned to >> ppp0 interface (instead of tun0, as I would naively expect). >> >> It's possible reproduce this behaviour by running "route add" command >> manually, for example: >> >> # route add 1.2.3.4/32 10.88.0.1 >> add host 1.2.3.4/32: gateway 10.88.0.1 >> >> # netstat -rn -f inet >> Routing tables >> >> Internet: >> DestinationGatewayFlags Refs Use Mtu Prio Iface >> default10.64.64.64UGS1 19 - 8 ppp0 >> 1.2.3.410.88.0.1 UGHS 00 - 8 ppp0 >> 10.64.64.6410.145.0.40UH 11 - 8 ppp0 >> 10.88.0/24 10.88.0.124UGS0 161 - 8 tun0 >> 10.88.0.12410.88.0.124UHl11 - 1 tun0 >> 10.88.0.12410.88.0.124UH 00 - 8 tun0 >> 10.90.0/24 10.88.0.1 UGS00 - 8 ppp0 >> 10.99.0/24 10.88.0.1 UGS00 - 8 ppp0 >> 10.145.0.4010.145.0.40UHl04 - 1 ppp0 >> ... >> >> Note that 10.88.0/24 network is associated with interface tun0. >> The new route (with gw in that network, 10.88.0.1) however get's >> assigned to interface ppp0. >> >> What's happening here? > > Hard to say since you did not include the complete routing table output. > > Don't you have 10.88.0.1 configured on ppp0? What is your ifconfig > output? What does "$ route -n get 10.88.0.1" returns you?
routes get assigned to a wrong interface, openbsd 5.9
Hello. I am hitting a strange behaviour with openbsd 5.9. # uname -a OpenBSD router_dev01.lan 5.9 GENERIC.MP#1888 amd64 There's pppd running on the box (for a 3g connection) and OpenVPN connection on top of that. The bug is that any routes pushed from openvpn server get assigned to ppp0 interface (instead of tun0, as I would naively expect). It's possible reproduce this behaviour by running "route add" command manually, for example: # route add 1.2.3.4/32 10.88.0.1 add host 1.2.3.4/32: gateway 10.88.0.1 # netstat -rn -f inet Routing tables Internet: DestinationGatewayFlags Refs Use Mtu Prio Iface default10.64.64.64UGS1 19 - 8 ppp0 1.2.3.410.88.0.1 UGHS 00 - 8 ppp0 10.64.64.6410.145.0.40UH 11 - 8 ppp0 10.88.0/24 10.88.0.124UGS0 161 - 8 tun0 10.88.0.12410.88.0.124UHl11 - 1 tun0 10.88.0.12410.88.0.124UH 00 - 8 tun0 10.90.0/24 10.88.0.1 UGS00 - 8 ppp0 10.99.0/24 10.88.0.1 UGS00 - 8 ppp0 10.145.0.4010.145.0.40UHl04 - 1 ppp0 ... Note that 10.88.0/24 network is associated with interface tun0. The new route (with gw in that network, 10.88.0.1) however get's assigned to interface ppp0. What's happening here? --- Regards, Mart