Yann Nottara wrote: > Dec 17 13:59:02 bull mpd: 192.168.0.10 -> 192.168.0.202 > Dec 17 13:59:02 bull mpd: [pptp2] IFACE: Up event > Dec 17 13:59:02 bull mpd: [pptp2] exec: /sbin/ifconfig ng0 192.168.0.10 > 192.168.0.202 netmask 0xffffffff -link0 > Dec 17 13:59:02 bull mpd: [pptp2] exec: /usr/sbin/arp -s 192.168.0.202 > 0:b0:d0:e1:48:74 pub > Dec 17 13:59:02 bull mpd: [pptp2] exec: /sbin/route add 192.168.0.0 > 192.168.0.202 -netmask 0xffffff00 > Dec 17 13:59:02 bull mpd: [pptp2] exec: command returned 256 > Dec 17 13:59:02 bull mpd: [pptp2] IFACE: Up event > Dec 17 13:59:02 bull mpd: [pptp2] rec'd unexpected protocol IP on link -1 > > As I wrote before, my problem is only this "verbosity", the server > itself is doing fine. > > So, my questions regarding the logs are : > > 1) What does "exec: command returned 256" means ?
The "route add" command failed for some reason. Does the route already exist? > 2) What "does rec'd unexpected protocol IP on link -1" means ? That's a transient error, it should really just be suppressed. The peer sent an IP packet before we were completely ready. No big deal. > BTW, my setup only allows 1 client now but I'd like to allow up to about > 10-15 machines more. > > Any idea of the burden this would put on a PIII 866 - 512 MB - U160 SCSI > server already providing some other basic net services ? Do you think > it's feasible ? Should be no problem. -Archie __________________________________________________________________________ Archie Cobbs * Packet Design * http://www.packetdesign.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-net" in the body of the message
