From: Etay M. <cl...@ne...> - 2001-05-24 20:51:22
|
On Thu, May 24, 2001 at 04:50:27PM -0500, Jeff Dike wrote: > cl...@ne... said: > > sl0 Link encap:Serial Line IP > > inet addr:192.168.0.254 P-t-P:192.168.1.4 Mask:255.255.255.255 > > This is a bit confused. I think the ip address (192.168.0.254) should be on > your network, i.e. 192.168.0.x. > actually, my network is 192.168.1.x > Also the netmask should be 255.255.255.0. > right > It might work better after you fix those. > OK, so I booted the virtual kernel and gave it umn=192.168.1.4 on the command line. inside the virtual machine it looked like that: umn Link encap:Ethernet HWaddr 00:00:00:00:00:00 inet addr:192.168.1.4 Mask:255.255.255.0 which seems ok. however, on the host it looks like this sl0 Link encap:Serial Line IP inet addr:192.168.1.4 P-t-P:192.168.1.4 Mask:255.255.255.255 which doesn't look correct. the host can ping 192.168.1.4 but it is probably just pinging itself. the virtual machine cannot ping the host. So I set the netmask of sl0 to 255.255.255.0 manually but its still not working. any idea? > Also, I've got a set of new network drivers on the way, plus a helper which > sets up everything on the host for people who want that. Once I release that > stuff, networking should be a lot easier to get running. > sounds great, because I've been able to do most of the other stuff very quickly (compiling, watching with gdb, host file access) but got stuck with networking. > > -- ************************************************************************ "When in doubt, use brute force." Ken Thompson Etay Meiri cl...@ne... ************************************************************************ |