From: Brett F. <fo...@uo...> - 2006-11-01 23:46:08
|
Whoops, I forget to reply-all. In any event, the problem is with SLiRP. These lines in main.c need to be commented out because it causes a seg fault (that goes unnoticed): //if((slirp_tty == NULL && strcmp(ttyname(0), ttyname(2)) == 0) || // (slirp_tty != NULL && strcmp(ttyname(2), slirp_tty) == 0) ) blnKeepErr = FALSE; //else // blnKeepErr = TRUE; ttyname(0) == NULL, and slirp_tty == NULL Brett On 11/1/06, Brett Foster <fo...@uo...> wrote: > On 10/31/06, Blaisorblade <bla...@ya...> wrote: > > eth0 is not a point-to-point interface, so shouldn't you add instead a default > > gateway (which normally is the host, but look at docs)? That way UML cannot > > set the output mac address... I do not know this particular case. > ...this time I tried doing: > root@fosterb-uml:~# ifconfig eth0 broadcast 10.0.2.15 > root@fosterb-uml:~# ifconfig > eth0 Link encap:Serial Line IP > inet addr:10.0.2.15 Mask:255.0.0.0 > UP RUNNING NOARP MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:256 > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > Interrupt:5 > > > > > > > So the next question is: how did you see slirp does not work? If the route is > > wrong then you'll not be able to communicate with outside (or even with the > > host). > > No luck! I test by telnetting: > telnet 10.0.2.0 -> Management console > or > telnet 10.0.2.2 22 > > Also try external networks like port 80 on google (by ip addr). It's > hard to test SLIRP because, but the debug output doesn't seem to say > much of anything. > |