[openbeosnetteam] Re: Eureka!!!

> Um, no.  How would one do that in the new stack?

Look at your new /etc/resolv.conf, you should find a line looking like 
this:
nameserver 192.168.0.1

Edit it to suit your case.
> Where exactly would one turn off the debugging in the stack?  I tried 
> kernel/net_stack_driver.c and changed DEBUG to 0, but this didn't 
seem to 
> have any effect. 

Yep, no surprise here, because the kernel/net_stack_driver.c is a proof
-of-concept sample driver, and is not 
used anymore. The real /dev/net/socket driver code is in driver/
socket.c (huh, too many files are called socket.c, I guess)
 
> Do I have to do this on a per file basis or is there one 
> global flag I can turn off?

Per file.
See driver/socket.c lines (at top): 
#define SHOW_INSANE_DEBUGGING   0
#define SERIAL_DEBUGGING                         1

Currently, only output to serial line is turn on.
Keep in mind that this /dev/net/socket driver is a thin layer acting as 
a kernel gate between libnet.so and your app on one 
(userland-) side and the real stack living in core module and others 
sub-modules (see them in $HOME/config/add-ons/kernel/network)
on the other (kernel-)side.
 
> I don't see anything from the new netstack in syslog.  Is that 
expected?  

Dunno for core & co modules, but from /dev/net/socket driver, yes.
Change the previous line to these ones;
#define SHOW_INSANE_DEBUGGING   1
#define SERIAL_DEBUGGING                         0

to see the driver message appears on your /var/log/syslog (after a 
reboot, of course).

-Philippe, who have a keep_loaded version of this /dev/net/socket on 
the work...

--
Fortune Cookie Says:

All extremists should be taken out and shot.

Other related posts: