You can subscribe to this list here.
| 1999 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(15) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2000 |
Jan
(6) |
Feb
(1) |
Mar
(39) |
Apr
(13) |
May
(24) |
Jun
(11) |
Jul
(23) |
Aug
(85) |
Sep
(12) |
Oct
(103) |
Nov
(79) |
Dec
(112) |
| 2001 |
Jan
(52) |
Feb
(82) |
Mar
(84) |
Apr
(65) |
May
(105) |
Jun
(188) |
Jul
(174) |
Aug
(182) |
Sep
(103) |
Oct
(137) |
Nov
(143) |
Dec
(98) |
| 2002 |
Jan
(258) |
Feb
(236) |
Mar
(386) |
Apr
(307) |
May
(238) |
Jun
(170) |
Jul
(252) |
Aug
(230) |
Sep
(278) |
Oct
(394) |
Nov
(336) |
Dec
(194) |
| 2003 |
Jan
(290) |
Feb
(182) |
Mar
(175) |
Apr
(220) |
May
(209) |
Jun
(286) |
Jul
(279) |
Aug
(164) |
Sep
(208) |
Oct
(324) |
Nov
(204) |
Dec
(380) |
| 2004 |
Jan
(344) |
Feb
(332) |
Mar
(395) |
Apr
(357) |
May
(349) |
Jun
(352) |
Jul
(279) |
Aug
(269) |
Sep
(374) |
Oct
(442) |
Nov
(428) |
Dec
(253) |
| 2005 |
Jan
(225) |
Feb
(219) |
Mar
(245) |
Apr
(249) |
May
(203) |
Jun
(157) |
Jul
(171) |
Aug
(194) |
Sep
(200) |
Oct
(232) |
Nov
(190) |
Dec
(195) |
| 2006 |
Jan
(158) |
Feb
(190) |
Mar
(235) |
Apr
(161) |
May
(134) |
Jun
(169) |
Jul
(117) |
Aug
(161) |
Sep
(170) |
Oct
(297) |
Nov
(230) |
Dec
(205) |
| 2007 |
Jan
(197) |
Feb
(132) |
Mar
(151) |
Apr
(97) |
May
(109) |
Jun
(99) |
Jul
(57) |
Aug
(110) |
Sep
(56) |
Oct
(119) |
Nov
(39) |
Dec
(45) |
| 2008 |
Jan
(101) |
Feb
(116) |
Mar
(141) |
Apr
(98) |
May
(133) |
Jun
(61) |
Jul
(43) |
Aug
(76) |
Sep
(20) |
Oct
(32) |
Nov
(22) |
Dec
(41) |
| 2009 |
Jan
(35) |
Feb
(15) |
Mar
(18) |
Apr
(13) |
May
(13) |
Jun
(26) |
Jul
(12) |
Aug
(32) |
Sep
(21) |
Oct
(41) |
Nov
(35) |
Dec
(12) |
| 2010 |
Jan
(3) |
Feb
(35) |
Mar
(28) |
Apr
(20) |
May
(5) |
Jun
(14) |
Jul
(6) |
Aug
(8) |
Sep
(20) |
Oct
(20) |
Nov
(10) |
Dec
(12) |
| 2011 |
Jan
(14) |
Feb
(10) |
Mar
(14) |
Apr
(14) |
May
(13) |
Jun
(43) |
Jul
(13) |
Aug
(50) |
Sep
(30) |
Oct
(23) |
Nov
(15) |
Dec
(49) |
| 2012 |
Jan
(15) |
Feb
(28) |
Mar
(7) |
Apr
|
May
(12) |
Jun
(13) |
Jul
(28) |
Aug
(11) |
Sep
(19) |
Oct
(27) |
Nov
(5) |
Dec
(25) |
| 2013 |
Jan
(18) |
Feb
(19) |
Mar
(56) |
Apr
(26) |
May
(38) |
Jun
(24) |
Jul
(42) |
Aug
(24) |
Sep
(4) |
Oct
(3) |
Nov
(18) |
Dec
(4) |
| 2014 |
Jan
(10) |
Feb
(9) |
Mar
(3) |
Apr
|
May
(12) |
Jun
(34) |
Jul
(8) |
Aug
(18) |
Sep
(3) |
Oct
(27) |
Nov
(2) |
Dec
(1) |
| 2015 |
Jan
|
Feb
(10) |
Mar
(49) |
Apr
(2) |
May
(4) |
Jun
(7) |
Jul
(1) |
Aug
(17) |
Sep
(7) |
Oct
(35) |
Nov
(40) |
Dec
(4) |
| 2016 |
Jan
(9) |
Feb
|
Mar
(6) |
Apr
|
May
(10) |
Jun
(2) |
Jul
|
Aug
|
Sep
(5) |
Oct
|
Nov
|
Dec
(1) |
| 2017 |
Jan
(2) |
Feb
(4) |
Mar
(1) |
Apr
(4) |
May
(31) |
Jun
(9) |
Jul
(1) |
Aug
|
Sep
|
Oct
(1) |
Nov
(1) |
Dec
(2) |
| 2018 |
Jan
|
Feb
|
Mar
(1) |
Apr
(4) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2022 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Richard W. <ric...@gm...> - 2015-12-08 21:32:47
|
On Tue, Dec 1, 2015 at 9:18 PM, Geyslan G. Bem <ge...@gm...> wrote:
> When using va_list ensure that va_start will be followed by va_end.
>
> Signed-off-by: Geyslan G. Bem <ge...@gm...>
> ---
> arch/um/drivers/net_user.c | 10 ++++++----
> 1 file changed, 6 insertions(+), 4 deletions(-)
>
> diff --git a/arch/um/drivers/net_user.c b/arch/um/drivers/net_user.c
> index e697a41..e9f8445 100644
> --- a/arch/um/drivers/net_user.c
> +++ b/arch/um/drivers/net_user.c
> @@ -249,21 +249,23 @@ void close_addr(unsigned char *addr, unsigned char *netmask, void *arg)
>
> char *split_if_spec(char *str, ...)
> {
> - char **arg, *end;
> + char **arg, *end, *ret = NULL;
> va_list ap;
>
> va_start(ap, str);
> while ((arg = va_arg(ap, char **)) != NULL) {
> if (*str == '\0')
> - return NULL;
> + goto out;
> end = strchr(str, ',');
> if (end != str)
> *arg = str;
> if (end == NULL)
> - return NULL;
> + goto out;
> *end++ = '\0';
> str = end;
> }
> + ret = str;
> +out:
> va_end(ap);
> - return str;
> + return ret;
> }
Applied! :)
--
Thanks,
//richard
|
|
From: Balaco B. <bal...@im...> - 2015-11-29 13:04:08
|
On Mon, Nov 23, 2015, at 19:15, Balaco Baco wrote: > On Mon, Nov 23, 2015, at 18:32, Richard Weinberger wrote: > > Am 23.11.2015 um 22:31 schrieb Balaco Baco: > > > I skimmed though it. To use ping to test if Internet connections are > > > working or not is one the most basic things everybody does and learn. > > > If, in some exotic setup (like UML's) makes this different, it should > > > say so, clearly (and not "indirectly obvious"). There are more than 15 > > > years I have done and seen ping being used to test connections. > > > > > > ... now I must do this! I'm barely believing it... BRB... - if it does > > > not work only! :P hahaha > > > > > > > Again, this has 0 to do with UML, with qemu's user networking, which is > > based > > on SLIRP, it is the same... > > I don't understand these things much more than knowing their names and > what it does. > > (...) > > :( > > Believe it or not, It still does not work: > > ============== > $ apt-get download vim > Err Downloading vim 2:7.3.547-7 > Temporary failure resolving 'ftp.fr.debian.org' > ============== > > And /etc/resolv.conf has the same contents of the host's file. > > The command ifconfig gives: > ==================== > $ 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:125 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:256 > RX bytes:0 (0.0 B) TX bytes:10296 (10.0 KiB) > Interrupt:5 > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > UP LOOPBACK RUNNING MTU:65536 Metric:1 > RX packets:26 errors:0 dropped:0 overruns:0 frame:0 > TX packets:26 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:2004 (1.9 KiB) TX bytes:2004 (1.9 KiB) > ==================== > > Makeing a wget with IPs (I copied manually) also don't work: > > ======================= > $ wget ftp://208.118.235.20/gnu/bison/bison-1.25.tar.gz > --2015-11-23 22:10:02-- > ftp://208.118.235.20/gnu/bison/bison-1.25.tar.gz > => `bison-1.25.tar.gz' > Connecting to 208.118.235.20:21... failed: Connection timed out. > Retrying. > > --2015-11-23 22:12:11-- > ftp://208.118.235.20/gnu/bison/bison-1.25.tar.gz > (try: 2) => `bison-1.25.tar.gz' > Connecting to 208.118.235.20:21... > > # Minutes pass without any better output. The file is just 280KiB, it > could have > # been downloaded with a dial up connection (so the slowness of Slirp > surely is > # not the case here). > ======================= > > I don't know what else would be useful for you. I would try SSH but it's > not installed now in the my Debian. > > How can I make DNS work, then? > > I still cannot make it run with network fully working (for programs like apt-get, ssh, links, ...). What do I need to do now? -- Balaco -- http://www.fastmail.com - mmm... Fastmail... |
|
From: Richard W. <ri...@no...> - 2015-11-28 23:11:48
|
Am 29.11.2015 um 00:00 schrieb Mickaël Salaün: > > > On 28/11/2015 23:55, Richard Weinberger wrote: >> Am 28.11.2015 um 23:52 schrieb Mickaël Salaün: >>> >>> On 28/11/2015 22:40, Richard Weinberger wrote: >>>> Am 28.11.2015 um 22:32 schrieb Mickaël Salaün: >>>>> Replace the default insecure mode 0777 with 0700 for temporary file. >>>>> >>>>> Prohibit other users to change the executable mapped code. >>>> >>>> Hmm, isn't the tmp file already unlinked at this stage? >>>> >>> >>> Yes, but if someone could open it before the unlink e.g. because of the umask (which does not seems to be the case thanks to mkstemp, but remains unspecified [1]), this user should then be able to have write access to the file descriptor/description. >> >> Yes, someone can open it before the unlink. But you change the file mode after that. >> How does it improve the situation? The attacker has already the file handle. > > The attacker could have the file handle only in a read-only mode, which is a bit different than being able to write and execute arbitrary code thanks to a file descriptor mapped RWX :) Fair point. Please describe this in detail in the patch changelog. :-) Thanks, //richard |
|
From: Richard W. <ri...@no...> - 2015-11-28 22:59:11
|
Am 28.11.2015 um 23:56 schrieb Mickaël Salaün: > > On 28/11/2015 23:07, Richard Weinberger wrote: >> Am 28.11.2015 um 22:32 schrieb Mickaël Salaün: >>> Open the memory mapped file with the O_TMPFILE flag when available. >>> >>> Signed-off-by: Mickaël Salaün <mi...@di...> >>> --- >>> arch/um/os-Linux/mem.c | 12 ++++++++++++ >>> 1 file changed, 12 insertions(+) >>> >>> diff --git a/arch/um/os-Linux/mem.c b/arch/um/os-Linux/mem.c >>> index 798aeb4..fe52e2d 100644 >>> --- a/arch/um/os-Linux/mem.c >>> +++ b/arch/um/os-Linux/mem.c >>> @@ -106,6 +106,18 @@ static int __init make_tempfile(const char *template) >>> } >>> } >>> >>> +#ifdef O_TMPFILE >>> + fd = open(tempdir, O_CLOEXEC | O_RDWR | O_EXCL | O_TMPFILE, 0700); >>> + /* >>> + * If the running system does not support O_TMPFILE flag then retry >>> + * without it. >>> + */ >>> + if (fd != -1 || (errno != EINVAL && errno != EISDIR && >> >> Why are you handling EISDIR? > > I follow the man page for open [1], I think it was a workaround needed for some kernel versions just after the O_TMPFILE was added but before the support for EOPNOTSUPP. > We may need to add the EACCES too for some version of glibc [2, 3]? Makes sense! :) > 1. http://man7.org/linux/man-pages/man2/openat.2.html#BUGS > 2. Commit 69a91c237ab0ebe4e9fdeaf6d0090c85275594ec and https://sourceware.org/bugzilla/show_bug.cgi?id=17523 > 3. https://bugs.gentoo.org/529044 > >> >>> + errno != EOPNOTSUPP)) >>> + return fd; >>> + errno = 0; >> >> Why are you resetting errno? > > It's to ignore/reset the error code from open, but it may not be needed because of the next call to malloc? But then you'd have to reset errno after every syscall. :-) Thanks, //richard |
|
From: Richard W. <ri...@no...> - 2015-11-28 22:55:33
|
Am 28.11.2015 um 23:52 schrieb Mickaël Salaün: > > On 28/11/2015 22:40, Richard Weinberger wrote: >> Am 28.11.2015 um 22:32 schrieb Mickaël Salaün: >>> Replace the default insecure mode 0777 with 0700 for temporary file. >>> >>> Prohibit other users to change the executable mapped code. >> >> Hmm, isn't the tmp file already unlinked at this stage? >> > > Yes, but if someone could open it before the unlink e.g. because of the umask (which does not seems to be the case thanks to mkstemp, but remains unspecified [1]), this user should then be able to have write access to the file descriptor/description. Yes, someone can open it before the unlink. But you change the file mode after that. How does it improve the situation? The attacker has already the file handle. Thanks, //richard |
|
From: Richard W. <ri...@no...> - 2015-11-28 22:07:19
|
Am 28.11.2015 um 22:32 schrieb Mickaël Salaün: > Open the memory mapped file with the O_TMPFILE flag when available. > > Signed-off-by: Mickaël Salaün <mi...@di...> > --- > arch/um/os-Linux/mem.c | 12 ++++++++++++ > 1 file changed, 12 insertions(+) > > diff --git a/arch/um/os-Linux/mem.c b/arch/um/os-Linux/mem.c > index 798aeb4..fe52e2d 100644 > --- a/arch/um/os-Linux/mem.c > +++ b/arch/um/os-Linux/mem.c > @@ -106,6 +106,18 @@ static int __init make_tempfile(const char *template) > } > } > > +#ifdef O_TMPFILE > + fd = open(tempdir, O_CLOEXEC | O_RDWR | O_EXCL | O_TMPFILE, 0700); > + /* > + * If the running system does not support O_TMPFILE flag then retry > + * without it. > + */ > + if (fd != -1 || (errno != EINVAL && errno != EISDIR && Why are you handling EISDIR? > + errno != EOPNOTSUPP)) > + return fd; > + errno = 0; Why are you resetting errno? Thanks, //richard |
|
From: Richard W. <ri...@no...> - 2015-11-28 21:40:37
|
Am 28.11.2015 um 22:32 schrieb Mickaël Salaün: > Replace the default insecure mode 0777 with 0700 for temporary file. > > Prohibit other users to change the executable mapped code. Hmm, isn't the tmp file already unlinked at this stage? Thanks, //richard |
|
From: Ricardo N. <ric...@gm...> - 2015-11-24 16:30:53
|
I've already made that question a few weeks ago but I couldn't make it work. So, in order to support new IRQs I understand that we need to follow those steps: 1. Add the IRQ IDs to /kernel/arch/um/include/asm/irq.h, or at least change LAST_IRQ macro value to the bigger IRQ ID; 2. Create one file per IRQ: is that a host or UML file? I'm trying to follow random driver example but /dev/random exists in both; 3. When I need to throw an IRQ I just have to write something on the file and send a SIGIO signal. Which process needs to receive the SIGIO? In my system I'm using the original driver and using a userspace application to emulate the hardware (communication through netlink sockets). So, the emulator decides when IRQs needs to be launched and, at the moment, communicates that to the kernel driver. |
|
From: Balaco B. <bal...@im...> - 2015-11-23 22:15:25
|
On Mon, Nov 23, 2015, at 18:32, Richard Weinberger wrote: > Am 23.11.2015 um 22:31 schrieb Balaco Baco: > > I skimmed though it. To use ping to test if Internet connections are > > working or not is one the most basic things everybody does and learn. > > If, in some exotic setup (like UML's) makes this different, it should > > say so, clearly (and not "indirectly obvious"). There are more than 15 > > years I have done and seen ping being used to test connections. > > > > ... now I must do this! I'm barely believing it... BRB... - if it does > > not work only! :P hahaha > > > > Again, this has 0 to do with UML, with qemu's user networking, which is > based > on SLIRP, it is the same... I don't understand these things much more than knowing their names and what it does. (...) :( Believe it or not, It still does not work: ============== $ apt-get download vim Err Downloading vim 2:7.3.547-7 Temporary failure resolving 'ftp.fr.debian.org' ============== And /etc/resolv.conf has the same contents of the host's file. The command ifconfig gives: ==================== $ 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:125 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:256 RX bytes:0 (0.0 B) TX bytes:10296 (10.0 KiB) Interrupt:5 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:26 errors:0 dropped:0 overruns:0 frame:0 TX packets:26 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2004 (1.9 KiB) TX bytes:2004 (1.9 KiB) ==================== Makeing a wget with IPs (I copied manually) also don't work: ======================= $ wget ftp://208.118.235.20/gnu/bison/bison-1.25.tar.gz --2015-11-23 22:10:02-- ftp://208.118.235.20/gnu/bison/bison-1.25.tar.gz => `bison-1.25.tar.gz' Connecting to 208.118.235.20:21... failed: Connection timed out. Retrying. --2015-11-23 22:12:11-- ftp://208.118.235.20/gnu/bison/bison-1.25.tar.gz (try: 2) => `bison-1.25.tar.gz' Connecting to 208.118.235.20:21... # Minutes pass without any better output. The file is just 280KiB, it could have # been downloaded with a dial up connection (so the slowness of Slirp surely is # not the case here). ======================= I don't know what else would be useful for you. I would try SSH but it's not installed now in the my Debian. How can I make DNS work, then? -- http://www.fastmail.com - Same, same, but different... |
|
From: Richard W. <ri...@no...> - 2015-11-23 21:32:59
|
Am 23.11.2015 um 22:31 schrieb Balaco Baco: > I skimmed though it. To use ping to test if Internet connections are > working or not is one the most basic things everybody does and learn. > If, in some exotic setup (like UML's) makes this different, it should > say so, clearly (and not "indirectly obvious"). There are more than 15 > years I have done and seen ping being used to test connections. > > ... now I must do this! I'm barely believing it... BRB... - if it does > not work only! :P hahaha > Again, this has 0 to do with UML, with qemu's user networking, which is based on SLIRP, it is the same... Thanks, //richard |
|
From: Balaco B. <bal...@im...> - 2015-11-23 21:31:18
|
On Mon, Nov 23, 2015, at 17:57, Richard Weinberger wrote: > Am 23.11.2015 um 21:55 schrieb Balaco Baco: > > On Mon, Nov 23, 2015, at 17:50, Richard Weinberger wrote: > >> Am 23.11.2015 um 21:48 schrieb Balaco Baco: > >>> Please be clearer. > >>> > >>> You said "you can also use the Internet". But after that you repeat "As > >>> I wrote ICMP is not supported on SLIRP." So what do I have here? What > >>> are the practical ways to use the Internet within UML machine? The > >>> things want to do is to download packages, open websites, and other > >>> common Internet uses from most computers. > >> > >> Please read on ICMP. You don't need it to view porn. > >> TCP is what you need. :-) > >> > > > > :-/ > > > > I really don't understand why you insist on repeating what I already > > showed that does not help me. I need more details. > > > > https://en.wikipedia.org/wiki/Internet_Control_Message_Protocol > > > > So? What can I do with it? Can you make a drawing, please? > > Did you read the article? > > It will tell you that ping is using it. So, no ping for you. > But as TCP and UDP are fully supported the web will work. > I skimmed though it. To use ping to test if Internet connections are working or not is one the most basic things everybody does and learn. If, in some exotic setup (like UML's) makes this different, it should say so, clearly (and not "indirectly obvious"). There are more than 15 years I have done and seen ping being used to test connections. ... now I must do this! I'm barely believing it... BRB... - if it does not work only! :P hahaha -- http://www.fastmail.com - Faster than the air-speed velocity of an unladen european swallow |
|
From: Richard W. <ri...@no...> - 2015-11-23 20:57:49
|
Am 23.11.2015 um 21:55 schrieb Balaco Baco: > On Mon, Nov 23, 2015, at 17:50, Richard Weinberger wrote: >> Am 23.11.2015 um 21:48 schrieb Balaco Baco: >>> Please be clearer. >>> >>> You said "you can also use the Internet". But after that you repeat "As >>> I wrote ICMP is not supported on SLIRP." So what do I have here? What >>> are the practical ways to use the Internet within UML machine? The >>> things want to do is to download packages, open websites, and other >>> common Internet uses from most computers. >> >> Please read on ICMP. You don't need it to view porn. >> TCP is what you need. :-) >> > > :-/ > > I really don't understand why you insist on repeating what I already > showed that does not help me. I need more details. > > https://en.wikipedia.org/wiki/Internet_Control_Message_Protocol > > So? What can I do with it? Can you make a drawing, please? Did you read the article? It will tell you that ping is using it. So, no ping for you. But as TCP and UDP are fully supported the web will work. Thanks, //richard |
|
From: Balaco B. <bal...@im...> - 2015-11-23 20:55:27
|
On Mon, Nov 23, 2015, at 17:50, Richard Weinberger wrote: > Am 23.11.2015 um 21:48 schrieb Balaco Baco: > > Please be clearer. > > > > You said "you can also use the Internet". But after that you repeat "As > > I wrote ICMP is not supported on SLIRP." So what do I have here? What > > are the practical ways to use the Internet within UML machine? The > > things want to do is to download packages, open websites, and other > > common Internet uses from most computers. > > Please read on ICMP. You don't need it to view porn. > TCP is what you need. :-) > :-/ I really don't understand why you insist on repeating what I already showed that does not help me. I need more details. https://en.wikipedia.org/wiki/Internet_Control_Message_Protocol So? What can I do with it? Can you make a drawing, please? -- http://www.fastmail.com - mmm... Fastmail... |
|
From: Richard W. <ri...@no...> - 2015-11-23 20:51:05
|
Am 23.11.2015 um 21:48 schrieb Balaco Baco: > Please be clearer. > > You said "you can also use the Internet". But after that you repeat "As > I wrote ICMP is not supported on SLIRP." So what do I have here? What > are the practical ways to use the Internet within UML machine? The > things want to do is to download packages, open websites, and other > common Internet uses from most computers. Please read on ICMP. You don't need it to view porn. TCP is what you need. :-) Thanks, //richard |
|
From: Balaco B. <bal...@im...> - 2015-11-23 20:48:17
|
On Mon, Nov 23, 2015, at 17:32, Richard Weinberger wrote: > Am 23.11.2015 um 21:31 schrieb Balaco Baco: > > On Mon, Nov 23, 2015, at 17:07, Richard Weinberger wrote: > >> Am 23.11.2015 um 21:04 schrieb Balaco Baco: > >>> On Mon, Nov 23, 2015, at 16:38, Richard Weinberger wrote: > >>>> Am 23.11.2015 um 20:04 schrieb Balaco Baco: > >>>>> On Mon, Nov 23, 2015, at 13:35, Richard Weinberger wrote: > >>>>>> Am 22.11.2015 um 16:39 schrieb Balaco Baco: > >>>>>>>>>>>>> Since I have no root access in the host machine, I must use 'slirp'. > >>>>>>>>>>>>> Right? Now I'll install it (https://en.wikipedia.org/wiki/Slirp) from > >>>>>>>>>>>>> source and pass the full path to UML in the command line, e.g.: > >>>>>>>>>>>> > >>>>>>>>>>>> Yes. > >>>>>>>>>>>> > >>>>>>>>>>>>> eth0=slirp,,/home/me/bin/ > >>>>>>>>>>>> > >>>>>>>>>>>> Documentation says: ethn=slirp,ethernet address,slirp path > >>>>>>>>>>>> > >>>>>>>>>>>> That said, the slirp tool is old and AFIAK unmaintained. > >>>>>>>>>>>> qemu forked it a long time ago and has it integrated into its > >>>>>>>>>>>> source. > >>>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>> Documentation of UML also said that ethernet address is optional. I did > >>>>>>>>>>> both ways, none worked (and it took me a few minutes and tries to find > >>>>>>>>>>> out that not all MAC addresses are possible to use for a virtual machine > >>>>>>>>>>> like UML; is this at least mentioned in some UML doc? It shouls, IMHO). > >>>>>>>>>>> > >>>>>>>>>>> So, is it possible that I run an UML with full Internet access, and > >>>>>>>>>>> without having root access in the host machine? Or am I trying something > >>>>>>>>>>> that from the start was not possible? > >>>>>>>>>>> > >>>>>>>>>>> If it is not possible, is it easy to set up some form of file sharing > >>>>>>>>>>> between the host and UML machine? (again, this must *not* depend on host > >>>>>>>>>>> root access!) > >>>>>>>>>> > >>>>>>>>>> As I said, if you don't have root on the host, you have to use slirp. > >>>>>>>>>> > >>>>>>>>> > >>>>>>>>> And I am using slirp. But it do not work yet. I'm not sure what is > >>>>>>>>> wrong. May you help me? > >>>>>>>> > >>>>>>>> Just gave it a try. Works here. > >>>>>>>> > >>>>>>>> ./linux ubda=../Downloads/Debian-Squeeze-AMD64-root_fs mem=1G > >>>>>>>> eth0=slirp,FE:FD:01:02:03:04,/home/rw/work/slirp/slirp-1.0.17/src/slirp > >>>>>>>> > >>>>>>>> root@uml:~# ifconfig eth0 10.0.2.15 up > >>>>>>>> root@uml:~# route add default gw 10.0.2.15 > >>>>>>> > >>>>>>> Do not work for me. And to point directly to the slirp program instead > >>>>>>> of its folder (which is understood by many as the *path* for anything, > >>>>>>> not the things themselves, with full path) is news for me, and something > >>>>>>> that should be pointed in the docs. I think many others will understand > >>>>>>> it as I did before you said this. > >>>>>> > >>>>>> "Does not work" is not a valid error description. > >>>>>> Please find out what exactly does not work. > >>>>> > >>>>> There is no clear error. In this paragraph I just pointed to something > >>>>> in the instructions that mislead me to give the path to the folder > >>>>> *where* slirp was, instead of the slip program itself, its file. The > >>>>> most I could see that did not work I said right after, below in the > >>>>> previous message. Please assume and try to see that I'm trying my best > >>>>> to follow your directions, but I still could not do it although you just > >>>>> said you did. > >>>>> > >>>>> You may also ask me to directly do things or steps that you do (maybe > >>>>> it's something I don't know or do that make it don't work). > >>>>> > >>>>> > >>>>>>> Now there is a few lines about slirt and ETH0: > >>>>>>> > >>>>>>> ======================= > >>>>>>> [autodetect SLIP/CSLIP, MTU 1500, MRU 1500, 115200 baud] > >>>>>>> > >>>>>>> SLiRP Ready ... > >>>>>>> Unsupported device type 256 for "eth0" > >>>>>>> Failed to bring up eth0. > >>>>>>> done. > >>>>>>> > >>>>>>> ======================== > >>>>>> > >>>>>> DHCP cannot work on SLIRP. > >>>>>> That's why you have to configure the interface manually. > >>>>>> > >>>>>>> What can I do? > >>>>>>> > >>>>> > >>>>> If configure the interface manually is to type the commands (inside UML) > >>>>> below, that I did before: > >>>>> > >>>>> root@uml:~# ifconfig eth0 10.0.2.15 up > >>>>> root@uml:~# route add default gw 10.0.2.15 > >>>>> > >>>>> It did not work. > >>>>> > >>>>> What information is useful for you? I don't know. So, since you seem to > >>>>> have thought I did not try enough before, now I'm sending the whole boot > >>>>> log, and each step I did before and repeated right now, after I read > >>>>> your message. > >>>>> > >>>>> > >>>>>>>> Then you can use networking. Please not that slirp does not have a > >>>>>>>> performance. > >>>>>>>> Depending on your slirp package you can tweak it. > >>>>>>> > >>>>>>> I have compiled it from source. Do you know exactly where and how I can > >>>>>>> tweak it? If so, please say how, so I don't have to search and find what > >>>>>>> is already known. > >>>>>> > >>>>>> AFAIK Debian folks have some patches in their package. > >>>>> > >>>>> I choose the best distro I know for the intended uses (RedHat and sister > >>>>> is usually not that good, but I don't discard using them to start). I > >>>>> did not use Fedora or RedHat that even the blog shows because I don't > >>>>> want and don't need graphical interface. Just CLI is perfect, just fine. > >>>>> > >>>>> If you can point which patch or which feature Debian patched I can work > >>>>> around it. Right now I know that it may have some problem, but I can > >>>>> even look for help my self or anywhere else because I don't know what it > >>>>> is - not much clues I can tell. > >>>>> > >>>>>> Thanks, > >>>>>> //richard > >>>>> > >>>>> Ironically, doing the same steps I did before it seemed to work today. > >>>>> :-/ I hate when this happens... hopefully it won't stop tomorrow, with > >>>>> another ironic happening. > >>>>> > >>>>> Now, with a close to work situaton, I guessed that it just needed to > >>>>> find the DNS the host uses (easy, fine), and then I repeat the route add > >>>>> command. But this is not true. Before I update UML's /etc/resolv.conf > >>>>> the only IP I can ping from UML is 127.0.0.1. What else do I need to do > >>>>> to have network in UML? > >>>> > >>>> ICMP is not supported on SLIRP. Only UDP and TCP. > >>>> > >>> > >>> What does this mean? Please explain a bit more clearly to me. I don't > >>> have much knowledge as you with UML and Kernel related (low system) > >>> things. > >> > >> This has 0 do to with UML. SLIRP is a very old user space tool. :) > >> > >>> Is TPC/IP supported? In theory, TPC happens above IP communication > >>> layer. So, should it work? > >> > >> TPC? > >> > > > > That's just a typo, of course. > > As I wrote, TCP and UDP work on SLIRP. > > >>> The network you said you had is the same as I just saw/did? Although I > >>> can communicate with the host, I won't be able to use its Internet > >>> connection? > >> > >> You can also use Internet. > >> > > > > I cannot. I have showed this with the attached with details in the > > complete session attached file. I can ping 127.0.0.1 (the host) but > > cannot ping any other IP addresses. May you help me find out the reason? > > If you need more information that I have sent in the attached file, > > please ask me. > > As I wrote ICMP is not supported on SLIRP. > > Thanks, > //richard Please be clearer. You said "you can also use the Internet". But after that you repeat "As I wrote ICMP is not supported on SLIRP." So what do I have here? What are the practical ways to use the Internet within UML machine? The things want to do is to download packages, open websites, and other common Internet uses from most computers. -- http://www.fastmail.com - Access your email from home and the web |
|
From: Richard W. <ri...@no...> - 2015-11-23 20:32:49
|
Am 23.11.2015 um 21:31 schrieb Balaco Baco: > On Mon, Nov 23, 2015, at 17:07, Richard Weinberger wrote: >> Am 23.11.2015 um 21:04 schrieb Balaco Baco: >>> On Mon, Nov 23, 2015, at 16:38, Richard Weinberger wrote: >>>> Am 23.11.2015 um 20:04 schrieb Balaco Baco: >>>>> On Mon, Nov 23, 2015, at 13:35, Richard Weinberger wrote: >>>>>> Am 22.11.2015 um 16:39 schrieb Balaco Baco: >>>>>>>>>>>>> Since I have no root access in the host machine, I must use 'slirp'. >>>>>>>>>>>>> Right? Now I'll install it (https://en.wikipedia.org/wiki/Slirp) from >>>>>>>>>>>>> source and pass the full path to UML in the command line, e.g.: >>>>>>>>>>>> >>>>>>>>>>>> Yes. >>>>>>>>>>>> >>>>>>>>>>>>> eth0=slirp,,/home/me/bin/ >>>>>>>>>>>> >>>>>>>>>>>> Documentation says: ethn=slirp,ethernet address,slirp path >>>>>>>>>>>> >>>>>>>>>>>> That said, the slirp tool is old and AFIAK unmaintained. >>>>>>>>>>>> qemu forked it a long time ago and has it integrated into its >>>>>>>>>>>> source. >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Documentation of UML also said that ethernet address is optional. I did >>>>>>>>>>> both ways, none worked (and it took me a few minutes and tries to find >>>>>>>>>>> out that not all MAC addresses are possible to use for a virtual machine >>>>>>>>>>> like UML; is this at least mentioned in some UML doc? It shouls, IMHO). >>>>>>>>>>> >>>>>>>>>>> So, is it possible that I run an UML with full Internet access, and >>>>>>>>>>> without having root access in the host machine? Or am I trying something >>>>>>>>>>> that from the start was not possible? >>>>>>>>>>> >>>>>>>>>>> If it is not possible, is it easy to set up some form of file sharing >>>>>>>>>>> between the host and UML machine? (again, this must *not* depend on host >>>>>>>>>>> root access!) >>>>>>>>>> >>>>>>>>>> As I said, if you don't have root on the host, you have to use slirp. >>>>>>>>>> >>>>>>>>> >>>>>>>>> And I am using slirp. But it do not work yet. I'm not sure what is >>>>>>>>> wrong. May you help me? >>>>>>>> >>>>>>>> Just gave it a try. Works here. >>>>>>>> >>>>>>>> ./linux ubda=../Downloads/Debian-Squeeze-AMD64-root_fs mem=1G >>>>>>>> eth0=slirp,FE:FD:01:02:03:04,/home/rw/work/slirp/slirp-1.0.17/src/slirp >>>>>>>> >>>>>>>> root@uml:~# ifconfig eth0 10.0.2.15 up >>>>>>>> root@uml:~# route add default gw 10.0.2.15 >>>>>>> >>>>>>> Do not work for me. And to point directly to the slirp program instead >>>>>>> of its folder (which is understood by many as the *path* for anything, >>>>>>> not the things themselves, with full path) is news for me, and something >>>>>>> that should be pointed in the docs. I think many others will understand >>>>>>> it as I did before you said this. >>>>>> >>>>>> "Does not work" is not a valid error description. >>>>>> Please find out what exactly does not work. >>>>> >>>>> There is no clear error. In this paragraph I just pointed to something >>>>> in the instructions that mislead me to give the path to the folder >>>>> *where* slirp was, instead of the slip program itself, its file. The >>>>> most I could see that did not work I said right after, below in the >>>>> previous message. Please assume and try to see that I'm trying my best >>>>> to follow your directions, but I still could not do it although you just >>>>> said you did. >>>>> >>>>> You may also ask me to directly do things or steps that you do (maybe >>>>> it's something I don't know or do that make it don't work). >>>>> >>>>> >>>>>>> Now there is a few lines about slirt and ETH0: >>>>>>> >>>>>>> ======================= >>>>>>> [autodetect SLIP/CSLIP, MTU 1500, MRU 1500, 115200 baud] >>>>>>> >>>>>>> SLiRP Ready ... >>>>>>> Unsupported device type 256 for "eth0" >>>>>>> Failed to bring up eth0. >>>>>>> done. >>>>>>> >>>>>>> ======================== >>>>>> >>>>>> DHCP cannot work on SLIRP. >>>>>> That's why you have to configure the interface manually. >>>>>> >>>>>>> What can I do? >>>>>>> >>>>> >>>>> If configure the interface manually is to type the commands (inside UML) >>>>> below, that I did before: >>>>> >>>>> root@uml:~# ifconfig eth0 10.0.2.15 up >>>>> root@uml:~# route add default gw 10.0.2.15 >>>>> >>>>> It did not work. >>>>> >>>>> What information is useful for you? I don't know. So, since you seem to >>>>> have thought I did not try enough before, now I'm sending the whole boot >>>>> log, and each step I did before and repeated right now, after I read >>>>> your message. >>>>> >>>>> >>>>>>>> Then you can use networking. Please not that slirp does not have a >>>>>>>> performance. >>>>>>>> Depending on your slirp package you can tweak it. >>>>>>> >>>>>>> I have compiled it from source. Do you know exactly where and how I can >>>>>>> tweak it? If so, please say how, so I don't have to search and find what >>>>>>> is already known. >>>>>> >>>>>> AFAIK Debian folks have some patches in their package. >>>>> >>>>> I choose the best distro I know for the intended uses (RedHat and sister >>>>> is usually not that good, but I don't discard using them to start). I >>>>> did not use Fedora or RedHat that even the blog shows because I don't >>>>> want and don't need graphical interface. Just CLI is perfect, just fine. >>>>> >>>>> If you can point which patch or which feature Debian patched I can work >>>>> around it. Right now I know that it may have some problem, but I can >>>>> even look for help my self or anywhere else because I don't know what it >>>>> is - not much clues I can tell. >>>>> >>>>>> Thanks, >>>>>> //richard >>>>> >>>>> Ironically, doing the same steps I did before it seemed to work today. >>>>> :-/ I hate when this happens... hopefully it won't stop tomorrow, with >>>>> another ironic happening. >>>>> >>>>> Now, with a close to work situaton, I guessed that it just needed to >>>>> find the DNS the host uses (easy, fine), and then I repeat the route add >>>>> command. But this is not true. Before I update UML's /etc/resolv.conf >>>>> the only IP I can ping from UML is 127.0.0.1. What else do I need to do >>>>> to have network in UML? >>>> >>>> ICMP is not supported on SLIRP. Only UDP and TCP. >>>> >>> >>> What does this mean? Please explain a bit more clearly to me. I don't >>> have much knowledge as you with UML and Kernel related (low system) >>> things. >> >> This has 0 do to with UML. SLIRP is a very old user space tool. :) >> >>> Is TPC/IP supported? In theory, TPC happens above IP communication >>> layer. So, should it work? >> >> TPC? >> > > That's just a typo, of course. As I wrote, TCP and UDP work on SLIRP. >>> The network you said you had is the same as I just saw/did? Although I >>> can communicate with the host, I won't be able to use its Internet >>> connection? >> >> You can also use Internet. >> > > I cannot. I have showed this with the attached with details in the > complete session attached file. I can ping 127.0.0.1 (the host) but > cannot ping any other IP addresses. May you help me find out the reason? > If you need more information that I have sent in the attached file, > please ask me. As I wrote ICMP is not supported on SLIRP. Thanks, //richard |
|
From: Balaco B. <bal...@im...> - 2015-11-23 20:31:09
|
On Mon, Nov 23, 2015, at 17:07, Richard Weinberger wrote: > Am 23.11.2015 um 21:04 schrieb Balaco Baco: > > On Mon, Nov 23, 2015, at 16:38, Richard Weinberger wrote: > >> Am 23.11.2015 um 20:04 schrieb Balaco Baco: > >>> On Mon, Nov 23, 2015, at 13:35, Richard Weinberger wrote: > >>>> Am 22.11.2015 um 16:39 schrieb Balaco Baco: > >>>>>>>>>>> Since I have no root access in the host machine, I must use 'slirp'. > >>>>>>>>>>> Right? Now I'll install it (https://en.wikipedia.org/wiki/Slirp) from > >>>>>>>>>>> source and pass the full path to UML in the command line, e.g.: > >>>>>>>>>> > >>>>>>>>>> Yes. > >>>>>>>>>> > >>>>>>>>>>> eth0=slirp,,/home/me/bin/ > >>>>>>>>>> > >>>>>>>>>> Documentation says: ethn=slirp,ethernet address,slirp path > >>>>>>>>>> > >>>>>>>>>> That said, the slirp tool is old and AFIAK unmaintained. > >>>>>>>>>> qemu forked it a long time ago and has it integrated into its > >>>>>>>>>> source. > >>>>>>>>>> > >>>>>>>>> > >>>>>>>>> Documentation of UML also said that ethernet address is optional. I did > >>>>>>>>> both ways, none worked (and it took me a few minutes and tries to find > >>>>>>>>> out that not all MAC addresses are possible to use for a virtual machine > >>>>>>>>> like UML; is this at least mentioned in some UML doc? It shouls, IMHO). > >>>>>>>>> > >>>>>>>>> So, is it possible that I run an UML with full Internet access, and > >>>>>>>>> without having root access in the host machine? Or am I trying something > >>>>>>>>> that from the start was not possible? > >>>>>>>>> > >>>>>>>>> If it is not possible, is it easy to set up some form of file sharing > >>>>>>>>> between the host and UML machine? (again, this must *not* depend on host > >>>>>>>>> root access!) > >>>>>>>> > >>>>>>>> As I said, if you don't have root on the host, you have to use slirp. > >>>>>>>> > >>>>>>> > >>>>>>> And I am using slirp. But it do not work yet. I'm not sure what is > >>>>>>> wrong. May you help me? > >>>>>> > >>>>>> Just gave it a try. Works here. > >>>>>> > >>>>>> ./linux ubda=../Downloads/Debian-Squeeze-AMD64-root_fs mem=1G > >>>>>> eth0=slirp,FE:FD:01:02:03:04,/home/rw/work/slirp/slirp-1.0.17/src/slirp > >>>>>> > >>>>>> root@uml:~# ifconfig eth0 10.0.2.15 up > >>>>>> root@uml:~# route add default gw 10.0.2.15 > >>>>> > >>>>> Do not work for me. And to point directly to the slirp program instead > >>>>> of its folder (which is understood by many as the *path* for anything, > >>>>> not the things themselves, with full path) is news for me, and something > >>>>> that should be pointed in the docs. I think many others will understand > >>>>> it as I did before you said this. > >>>> > >>>> "Does not work" is not a valid error description. > >>>> Please find out what exactly does not work. > >>> > >>> There is no clear error. In this paragraph I just pointed to something > >>> in the instructions that mislead me to give the path to the folder > >>> *where* slirp was, instead of the slip program itself, its file. The > >>> most I could see that did not work I said right after, below in the > >>> previous message. Please assume and try to see that I'm trying my best > >>> to follow your directions, but I still could not do it although you just > >>> said you did. > >>> > >>> You may also ask me to directly do things or steps that you do (maybe > >>> it's something I don't know or do that make it don't work). > >>> > >>> > >>>>> Now there is a few lines about slirt and ETH0: > >>>>> > >>>>> ======================= > >>>>> [autodetect SLIP/CSLIP, MTU 1500, MRU 1500, 115200 baud] > >>>>> > >>>>> SLiRP Ready ... > >>>>> Unsupported device type 256 for "eth0" > >>>>> Failed to bring up eth0. > >>>>> done. > >>>>> > >>>>> ======================== > >>>> > >>>> DHCP cannot work on SLIRP. > >>>> That's why you have to configure the interface manually. > >>>> > >>>>> What can I do? > >>>>> > >>> > >>> If configure the interface manually is to type the commands (inside UML) > >>> below, that I did before: > >>> > >>> root@uml:~# ifconfig eth0 10.0.2.15 up > >>> root@uml:~# route add default gw 10.0.2.15 > >>> > >>> It did not work. > >>> > >>> What information is useful for you? I don't know. So, since you seem to > >>> have thought I did not try enough before, now I'm sending the whole boot > >>> log, and each step I did before and repeated right now, after I read > >>> your message. > >>> > >>> > >>>>>> Then you can use networking. Please not that slirp does not have a > >>>>>> performance. > >>>>>> Depending on your slirp package you can tweak it. > >>>>> > >>>>> I have compiled it from source. Do you know exactly where and how I can > >>>>> tweak it? If so, please say how, so I don't have to search and find what > >>>>> is already known. > >>>> > >>>> AFAIK Debian folks have some patches in their package. > >>> > >>> I choose the best distro I know for the intended uses (RedHat and sister > >>> is usually not that good, but I don't discard using them to start). I > >>> did not use Fedora or RedHat that even the blog shows because I don't > >>> want and don't need graphical interface. Just CLI is perfect, just fine. > >>> > >>> If you can point which patch or which feature Debian patched I can work > >>> around it. Right now I know that it may have some problem, but I can > >>> even look for help my self or anywhere else because I don't know what it > >>> is - not much clues I can tell. > >>> > >>>> Thanks, > >>>> //richard > >>> > >>> Ironically, doing the same steps I did before it seemed to work today. > >>> :-/ I hate when this happens... hopefully it won't stop tomorrow, with > >>> another ironic happening. > >>> > >>> Now, with a close to work situaton, I guessed that it just needed to > >>> find the DNS the host uses (easy, fine), and then I repeat the route add > >>> command. But this is not true. Before I update UML's /etc/resolv.conf > >>> the only IP I can ping from UML is 127.0.0.1. What else do I need to do > >>> to have network in UML? > >> > >> ICMP is not supported on SLIRP. Only UDP and TCP. > >> > > > > What does this mean? Please explain a bit more clearly to me. I don't > > have much knowledge as you with UML and Kernel related (low system) > > things. > > This has 0 do to with UML. SLIRP is a very old user space tool. :) > > > Is TPC/IP supported? In theory, TPC happens above IP communication > > layer. So, should it work? > > TPC? > That's just a typo, of course. > > The network you said you had is the same as I just saw/did? Although I > > can communicate with the host, I won't be able to use its Internet > > connection? > > You can also use Internet. > I cannot. I have showed this with the attached with details in the complete session attached file. I can ping 127.0.0.1 (the host) but cannot ping any other IP addresses. May you help me find out the reason? If you need more information that I have sent in the attached file, please ask me. -- http://www.fastmail.com - Accessible with your email software or over the web |
|
From: Richard W. <ri...@no...> - 2015-11-23 20:07:54
|
Am 23.11.2015 um 21:04 schrieb Balaco Baco: > On Mon, Nov 23, 2015, at 16:38, Richard Weinberger wrote: >> Am 23.11.2015 um 20:04 schrieb Balaco Baco: >>> On Mon, Nov 23, 2015, at 13:35, Richard Weinberger wrote: >>>> Am 22.11.2015 um 16:39 schrieb Balaco Baco: >>>>>>>>>>> Since I have no root access in the host machine, I must use 'slirp'. >>>>>>>>>>> Right? Now I'll install it (https://en.wikipedia.org/wiki/Slirp) from >>>>>>>>>>> source and pass the full path to UML in the command line, e.g.: >>>>>>>>>> >>>>>>>>>> Yes. >>>>>>>>>> >>>>>>>>>>> eth0=slirp,,/home/me/bin/ >>>>>>>>>> >>>>>>>>>> Documentation says: ethn=slirp,ethernet address,slirp path >>>>>>>>>> >>>>>>>>>> That said, the slirp tool is old and AFIAK unmaintained. >>>>>>>>>> qemu forked it a long time ago and has it integrated into its >>>>>>>>>> source. >>>>>>>>>> >>>>>>>>> >>>>>>>>> Documentation of UML also said that ethernet address is optional. I did >>>>>>>>> both ways, none worked (and it took me a few minutes and tries to find >>>>>>>>> out that not all MAC addresses are possible to use for a virtual machine >>>>>>>>> like UML; is this at least mentioned in some UML doc? It shouls, IMHO). >>>>>>>>> >>>>>>>>> So, is it possible that I run an UML with full Internet access, and >>>>>>>>> without having root access in the host machine? Or am I trying something >>>>>>>>> that from the start was not possible? >>>>>>>>> >>>>>>>>> If it is not possible, is it easy to set up some form of file sharing >>>>>>>>> between the host and UML machine? (again, this must *not* depend on host >>>>>>>>> root access!) >>>>>>>> >>>>>>>> As I said, if you don't have root on the host, you have to use slirp. >>>>>>>> >>>>>>> >>>>>>> And I am using slirp. But it do not work yet. I'm not sure what is >>>>>>> wrong. May you help me? >>>>>> >>>>>> Just gave it a try. Works here. >>>>>> >>>>>> ./linux ubda=../Downloads/Debian-Squeeze-AMD64-root_fs mem=1G >>>>>> eth0=slirp,FE:FD:01:02:03:04,/home/rw/work/slirp/slirp-1.0.17/src/slirp >>>>>> >>>>>> root@uml:~# ifconfig eth0 10.0.2.15 up >>>>>> root@uml:~# route add default gw 10.0.2.15 >>>>> >>>>> Do not work for me. And to point directly to the slirp program instead >>>>> of its folder (which is understood by many as the *path* for anything, >>>>> not the things themselves, with full path) is news for me, and something >>>>> that should be pointed in the docs. I think many others will understand >>>>> it as I did before you said this. >>>> >>>> "Does not work" is not a valid error description. >>>> Please find out what exactly does not work. >>> >>> There is no clear error. In this paragraph I just pointed to something >>> in the instructions that mislead me to give the path to the folder >>> *where* slirp was, instead of the slip program itself, its file. The >>> most I could see that did not work I said right after, below in the >>> previous message. Please assume and try to see that I'm trying my best >>> to follow your directions, but I still could not do it although you just >>> said you did. >>> >>> You may also ask me to directly do things or steps that you do (maybe >>> it's something I don't know or do that make it don't work). >>> >>> >>>>> Now there is a few lines about slirt and ETH0: >>>>> >>>>> ======================= >>>>> [autodetect SLIP/CSLIP, MTU 1500, MRU 1500, 115200 baud] >>>>> >>>>> SLiRP Ready ... >>>>> Unsupported device type 256 for "eth0" >>>>> Failed to bring up eth0. >>>>> done. >>>>> >>>>> ======================== >>>> >>>> DHCP cannot work on SLIRP. >>>> That's why you have to configure the interface manually. >>>> >>>>> What can I do? >>>>> >>> >>> If configure the interface manually is to type the commands (inside UML) >>> below, that I did before: >>> >>> root@uml:~# ifconfig eth0 10.0.2.15 up >>> root@uml:~# route add default gw 10.0.2.15 >>> >>> It did not work. >>> >>> What information is useful for you? I don't know. So, since you seem to >>> have thought I did not try enough before, now I'm sending the whole boot >>> log, and each step I did before and repeated right now, after I read >>> your message. >>> >>> >>>>>> Then you can use networking. Please not that slirp does not have a >>>>>> performance. >>>>>> Depending on your slirp package you can tweak it. >>>>> >>>>> I have compiled it from source. Do you know exactly where and how I can >>>>> tweak it? If so, please say how, so I don't have to search and find what >>>>> is already known. >>>> >>>> AFAIK Debian folks have some patches in their package. >>> >>> I choose the best distro I know for the intended uses (RedHat and sister >>> is usually not that good, but I don't discard using them to start). I >>> did not use Fedora or RedHat that even the blog shows because I don't >>> want and don't need graphical interface. Just CLI is perfect, just fine. >>> >>> If you can point which patch or which feature Debian patched I can work >>> around it. Right now I know that it may have some problem, but I can >>> even look for help my self or anywhere else because I don't know what it >>> is - not much clues I can tell. >>> >>>> Thanks, >>>> //richard >>> >>> Ironically, doing the same steps I did before it seemed to work today. >>> :-/ I hate when this happens... hopefully it won't stop tomorrow, with >>> another ironic happening. >>> >>> Now, with a close to work situaton, I guessed that it just needed to >>> find the DNS the host uses (easy, fine), and then I repeat the route add >>> command. But this is not true. Before I update UML's /etc/resolv.conf >>> the only IP I can ping from UML is 127.0.0.1. What else do I need to do >>> to have network in UML? >> >> ICMP is not supported on SLIRP. Only UDP and TCP. >> > > What does this mean? Please explain a bit more clearly to me. I don't > have much knowledge as you with UML and Kernel related (low system) > things. This has 0 do to with UML. SLIRP is a very old user space tool. :) > Is TPC/IP supported? In theory, TPC happens above IP communication > layer. So, should it work? TPC? > The network you said you had is the same as I just saw/did? Although I > can communicate with the host, I won't be able to use its Internet > connection? You can also use Internet. Thanks, //richard |
|
From: Balaco B. <bal...@im...> - 2015-11-23 20:04:20
|
On Mon, Nov 23, 2015, at 16:38, Richard Weinberger wrote: > Am 23.11.2015 um 20:04 schrieb Balaco Baco: > > On Mon, Nov 23, 2015, at 13:35, Richard Weinberger wrote: > >> Am 22.11.2015 um 16:39 schrieb Balaco Baco: > >>>>>>>>> Since I have no root access in the host machine, I must use 'slirp'. > >>>>>>>>> Right? Now I'll install it (https://en.wikipedia.org/wiki/Slirp) from > >>>>>>>>> source and pass the full path to UML in the command line, e.g.: > >>>>>>>> > >>>>>>>> Yes. > >>>>>>>> > >>>>>>>>> eth0=slirp,,/home/me/bin/ > >>>>>>>> > >>>>>>>> Documentation says: ethn=slirp,ethernet address,slirp path > >>>>>>>> > >>>>>>>> That said, the slirp tool is old and AFIAK unmaintained. > >>>>>>>> qemu forked it a long time ago and has it integrated into its > >>>>>>>> source. > >>>>>>>> > >>>>>>> > >>>>>>> Documentation of UML also said that ethernet address is optional. I did > >>>>>>> both ways, none worked (and it took me a few minutes and tries to find > >>>>>>> out that not all MAC addresses are possible to use for a virtual machine > >>>>>>> like UML; is this at least mentioned in some UML doc? It shouls, IMHO). > >>>>>>> > >>>>>>> So, is it possible that I run an UML with full Internet access, and > >>>>>>> without having root access in the host machine? Or am I trying something > >>>>>>> that from the start was not possible? > >>>>>>> > >>>>>>> If it is not possible, is it easy to set up some form of file sharing > >>>>>>> between the host and UML machine? (again, this must *not* depend on host > >>>>>>> root access!) > >>>>>> > >>>>>> As I said, if you don't have root on the host, you have to use slirp. > >>>>>> > >>>>> > >>>>> And I am using slirp. But it do not work yet. I'm not sure what is > >>>>> wrong. May you help me? > >>>> > >>>> Just gave it a try. Works here. > >>>> > >>>> ./linux ubda=../Downloads/Debian-Squeeze-AMD64-root_fs mem=1G > >>>> eth0=slirp,FE:FD:01:02:03:04,/home/rw/work/slirp/slirp-1.0.17/src/slirp > >>>> > >>>> root@uml:~# ifconfig eth0 10.0.2.15 up > >>>> root@uml:~# route add default gw 10.0.2.15 > >>> > >>> Do not work for me. And to point directly to the slirp program instead > >>> of its folder (which is understood by many as the *path* for anything, > >>> not the things themselves, with full path) is news for me, and something > >>> that should be pointed in the docs. I think many others will understand > >>> it as I did before you said this. > >> > >> "Does not work" is not a valid error description. > >> Please find out what exactly does not work. > > > > There is no clear error. In this paragraph I just pointed to something > > in the instructions that mislead me to give the path to the folder > > *where* slirp was, instead of the slip program itself, its file. The > > most I could see that did not work I said right after, below in the > > previous message. Please assume and try to see that I'm trying my best > > to follow your directions, but I still could not do it although you just > > said you did. > > > > You may also ask me to directly do things or steps that you do (maybe > > it's something I don't know or do that make it don't work). > > > > > >>> Now there is a few lines about slirt and ETH0: > >>> > >>> ======================= > >>> [autodetect SLIP/CSLIP, MTU 1500, MRU 1500, 115200 baud] > >>> > >>> SLiRP Ready ... > >>> Unsupported device type 256 for "eth0" > >>> Failed to bring up eth0. > >>> done. > >>> > >>> ======================== > >> > >> DHCP cannot work on SLIRP. > >> That's why you have to configure the interface manually. > >> > >>> What can I do? > >>> > > > > If configure the interface manually is to type the commands (inside UML) > > below, that I did before: > > > > root@uml:~# ifconfig eth0 10.0.2.15 up > > root@uml:~# route add default gw 10.0.2.15 > > > > It did not work. > > > > What information is useful for you? I don't know. So, since you seem to > > have thought I did not try enough before, now I'm sending the whole boot > > log, and each step I did before and repeated right now, after I read > > your message. > > > > > >>>> Then you can use networking. Please not that slirp does not have a > >>>> performance. > >>>> Depending on your slirp package you can tweak it. > >>> > >>> I have compiled it from source. Do you know exactly where and how I can > >>> tweak it? If so, please say how, so I don't have to search and find what > >>> is already known. > >> > >> AFAIK Debian folks have some patches in their package. > > > > I choose the best distro I know for the intended uses (RedHat and sister > > is usually not that good, but I don't discard using them to start). I > > did not use Fedora or RedHat that even the blog shows because I don't > > want and don't need graphical interface. Just CLI is perfect, just fine. > > > > If you can point which patch or which feature Debian patched I can work > > around it. Right now I know that it may have some problem, but I can > > even look for help my self or anywhere else because I don't know what it > > is - not much clues I can tell. > > > >> Thanks, > >> //richard > > > > Ironically, doing the same steps I did before it seemed to work today. > > :-/ I hate when this happens... hopefully it won't stop tomorrow, with > > another ironic happening. > > > > Now, with a close to work situaton, I guessed that it just needed to > > find the DNS the host uses (easy, fine), and then I repeat the route add > > command. But this is not true. Before I update UML's /etc/resolv.conf > > the only IP I can ping from UML is 127.0.0.1. What else do I need to do > > to have network in UML? > > ICMP is not supported on SLIRP. Only UDP and TCP. > What does this mean? Please explain a bit more clearly to me. I don't have much knowledge as you with UML and Kernel related (low system) things. Is TPC/IP supported? In theory, TPC happens above IP communication layer. So, should it work? The network you said you had is the same as I just saw/did? Although I can communicate with the host, I won't be able to use its Internet connection? -- http://www.fastmail.com - The way an email service should be |
|
From: Richard W. <ri...@no...> - 2015-11-23 19:38:35
|
Am 23.11.2015 um 20:04 schrieb Balaco Baco: > On Mon, Nov 23, 2015, at 13:35, Richard Weinberger wrote: >> Am 22.11.2015 um 16:39 schrieb Balaco Baco: >>>>>>>>> Since I have no root access in the host machine, I must use 'slirp'. >>>>>>>>> Right? Now I'll install it (https://en.wikipedia.org/wiki/Slirp) from >>>>>>>>> source and pass the full path to UML in the command line, e.g.: >>>>>>>> >>>>>>>> Yes. >>>>>>>> >>>>>>>>> eth0=slirp,,/home/me/bin/ >>>>>>>> >>>>>>>> Documentation says: ethn=slirp,ethernet address,slirp path >>>>>>>> >>>>>>>> That said, the slirp tool is old and AFIAK unmaintained. >>>>>>>> qemu forked it a long time ago and has it integrated into its >>>>>>>> source. >>>>>>>> >>>>>>> >>>>>>> Documentation of UML also said that ethernet address is optional. I did >>>>>>> both ways, none worked (and it took me a few minutes and tries to find >>>>>>> out that not all MAC addresses are possible to use for a virtual machine >>>>>>> like UML; is this at least mentioned in some UML doc? It shouls, IMHO). >>>>>>> >>>>>>> So, is it possible that I run an UML with full Internet access, and >>>>>>> without having root access in the host machine? Or am I trying something >>>>>>> that from the start was not possible? >>>>>>> >>>>>>> If it is not possible, is it easy to set up some form of file sharing >>>>>>> between the host and UML machine? (again, this must *not* depend on host >>>>>>> root access!) >>>>>> >>>>>> As I said, if you don't have root on the host, you have to use slirp. >>>>>> >>>>> >>>>> And I am using slirp. But it do not work yet. I'm not sure what is >>>>> wrong. May you help me? >>>> >>>> Just gave it a try. Works here. >>>> >>>> ./linux ubda=../Downloads/Debian-Squeeze-AMD64-root_fs mem=1G >>>> eth0=slirp,FE:FD:01:02:03:04,/home/rw/work/slirp/slirp-1.0.17/src/slirp >>>> >>>> root@uml:~# ifconfig eth0 10.0.2.15 up >>>> root@uml:~# route add default gw 10.0.2.15 >>> >>> Do not work for me. And to point directly to the slirp program instead >>> of its folder (which is understood by many as the *path* for anything, >>> not the things themselves, with full path) is news for me, and something >>> that should be pointed in the docs. I think many others will understand >>> it as I did before you said this. >> >> "Does not work" is not a valid error description. >> Please find out what exactly does not work. > > There is no clear error. In this paragraph I just pointed to something > in the instructions that mislead me to give the path to the folder > *where* slirp was, instead of the slip program itself, its file. The > most I could see that did not work I said right after, below in the > previous message. Please assume and try to see that I'm trying my best > to follow your directions, but I still could not do it although you just > said you did. > > You may also ask me to directly do things or steps that you do (maybe > it's something I don't know or do that make it don't work). > > >>> Now there is a few lines about slirt and ETH0: >>> >>> ======================= >>> [autodetect SLIP/CSLIP, MTU 1500, MRU 1500, 115200 baud] >>> >>> SLiRP Ready ... >>> Unsupported device type 256 for "eth0" >>> Failed to bring up eth0. >>> done. >>> >>> ======================== >> >> DHCP cannot work on SLIRP. >> That's why you have to configure the interface manually. >> >>> What can I do? >>> > > If configure the interface manually is to type the commands (inside UML) > below, that I did before: > > root@uml:~# ifconfig eth0 10.0.2.15 up > root@uml:~# route add default gw 10.0.2.15 > > It did not work. > > What information is useful for you? I don't know. So, since you seem to > have thought I did not try enough before, now I'm sending the whole boot > log, and each step I did before and repeated right now, after I read > your message. > > >>>> Then you can use networking. Please not that slirp does not have a >>>> performance. >>>> Depending on your slirp package you can tweak it. >>> >>> I have compiled it from source. Do you know exactly where and how I can >>> tweak it? If so, please say how, so I don't have to search and find what >>> is already known. >> >> AFAIK Debian folks have some patches in their package. > > I choose the best distro I know for the intended uses (RedHat and sister > is usually not that good, but I don't discard using them to start). I > did not use Fedora or RedHat that even the blog shows because I don't > want and don't need graphical interface. Just CLI is perfect, just fine. > > If you can point which patch or which feature Debian patched I can work > around it. Right now I know that it may have some problem, but I can > even look for help my self or anywhere else because I don't know what it > is - not much clues I can tell. > >> Thanks, >> //richard > > Ironically, doing the same steps I did before it seemed to work today. > :-/ I hate when this happens... hopefully it won't stop tomorrow, with > another ironic happening. > > Now, with a close to work situaton, I guessed that it just needed to > find the DNS the host uses (easy, fine), and then I repeat the route add > command. But this is not true. Before I update UML's /etc/resolv.conf > the only IP I can ping from UML is 127.0.0.1. What else do I need to do > to have network in UML? ICMP is not supported on SLIRP. Only UDP and TCP. Thanks, //richard |
|
From: Balaco B. <bal...@im...> - 2015-11-23 19:04:49
|
On Mon, Nov 23, 2015, at 13:35, Richard Weinberger wrote: > Am 22.11.2015 um 16:39 schrieb Balaco Baco: > >>>>>>> Since I have no root access in the host machine, I must use 'slirp'. > >>>>>>> Right? Now I'll install it (https://en.wikipedia.org/wiki/Slirp) from > >>>>>>> source and pass the full path to UML in the command line, e.g.: > >>>>>> > >>>>>> Yes. > >>>>>> > >>>>>>> eth0=slirp,,/home/me/bin/ > >>>>>> > >>>>>> Documentation says: ethn=slirp,ethernet address,slirp path > >>>>>> > >>>>>> That said, the slirp tool is old and AFIAK unmaintained. > >>>>>> qemu forked it a long time ago and has it integrated into its > >>>>>> source. > >>>>>> > >>>>> > >>>>> Documentation of UML also said that ethernet address is optional. I did > >>>>> both ways, none worked (and it took me a few minutes and tries to find > >>>>> out that not all MAC addresses are possible to use for a virtual machine > >>>>> like UML; is this at least mentioned in some UML doc? It shouls, IMHO). > >>>>> > >>>>> So, is it possible that I run an UML with full Internet access, and > >>>>> without having root access in the host machine? Or am I trying something > >>>>> that from the start was not possible? > >>>>> > >>>>> If it is not possible, is it easy to set up some form of file sharing > >>>>> between the host and UML machine? (again, this must *not* depend on host > >>>>> root access!) > >>>> > >>>> As I said, if you don't have root on the host, you have to use slirp. > >>>> > >>> > >>> And I am using slirp. But it do not work yet. I'm not sure what is > >>> wrong. May you help me? > >> > >> Just gave it a try. Works here. > >> > >> ./linux ubda=../Downloads/Debian-Squeeze-AMD64-root_fs mem=1G > >> eth0=slirp,FE:FD:01:02:03:04,/home/rw/work/slirp/slirp-1.0.17/src/slirp > >> > >> root@uml:~# ifconfig eth0 10.0.2.15 up > >> root@uml:~# route add default gw 10.0.2.15 > > > > Do not work for me. And to point directly to the slirp program instead > > of its folder (which is understood by many as the *path* for anything, > > not the things themselves, with full path) is news for me, and something > > that should be pointed in the docs. I think many others will understand > > it as I did before you said this. > > "Does not work" is not a valid error description. > Please find out what exactly does not work. There is no clear error. In this paragraph I just pointed to something in the instructions that mislead me to give the path to the folder *where* slirp was, instead of the slip program itself, its file. The most I could see that did not work I said right after, below in the previous message. Please assume and try to see that I'm trying my best to follow your directions, but I still could not do it although you just said you did. You may also ask me to directly do things or steps that you do (maybe it's something I don't know or do that make it don't work). > > Now there is a few lines about slirt and ETH0: > > > > ======================= > > [autodetect SLIP/CSLIP, MTU 1500, MRU 1500, 115200 baud] > > > > SLiRP Ready ... > > Unsupported device type 256 for "eth0" > > Failed to bring up eth0. > > done. > > > > ======================== > > DHCP cannot work on SLIRP. > That's why you have to configure the interface manually. > > > What can I do? > > If configure the interface manually is to type the commands (inside UML) below, that I did before: root@uml:~# ifconfig eth0 10.0.2.15 up root@uml:~# route add default gw 10.0.2.15 It did not work. What information is useful for you? I don't know. So, since you seem to have thought I did not try enough before, now I'm sending the whole boot log, and each step I did before and repeated right now, after I read your message. > >> Then you can use networking. Please not that slirp does not have a > >> performance. > >> Depending on your slirp package you can tweak it. > > > > I have compiled it from source. Do you know exactly where and how I can > > tweak it? If so, please say how, so I don't have to search and find what > > is already known. > > AFAIK Debian folks have some patches in their package. I choose the best distro I know for the intended uses (RedHat and sister is usually not that good, but I don't discard using them to start). I did not use Fedora or RedHat that even the blog shows because I don't want and don't need graphical interface. Just CLI is perfect, just fine. If you can point which patch or which feature Debian patched I can work around it. Right now I know that it may have some problem, but I can even look for help my self or anywhere else because I don't know what it is - not much clues I can tell. > Thanks, > //richard Ironically, doing the same steps I did before it seemed to work today. :-/ I hate when this happens... hopefully it won't stop tomorrow, with another ironic happening. Now, with a close to work situaton, I guessed that it just needed to find the DNS the host uses (easy, fine), and then I repeat the route add command. But this is not true. Before I update UML's /etc/resolv.conf the only IP I can ping from UML is 127.0.0.1. What else do I need to do to have network in UML? Thank you, -- Balaco -- http://www.fastmail.com - Choose from over 50 domains or use your own |
|
From: Richard W. <ri...@no...> - 2015-11-23 16:35:58
|
Am 22.11.2015 um 16:39 schrieb Balaco Baco: > > On Fri, Nov 13, 2015, at 18:15, Richard Weinberger wrote: >> Am 12.11.2015 um 14:22 schrieb Balaco Baco: >>> On Thu, Nov 12, 2015, at 10:00, Richard Weinberger wrote: >>>> Am 12.11.2015 um 02:57 schrieb Balaco Baco: >>>>> On Wed, Nov 11, 2015, at 17:34, Richard Weinberger wrote: >>>>>> Am 11.11.2015 um 18:57 schrieb Balaco Baco: >>>>>>> Since I have no root access in the host machine, I must use 'slirp'. >>>>>>> Right? Now I'll install it (https://en.wikipedia.org/wiki/Slirp) from >>>>>>> source and pass the full path to UML in the command line, e.g.: >>>>>> >>>>>> Yes. >>>>>> >>>>>>> eth0=slirp,,/home/me/bin/ >>>>>> >>>>>> Documentation says: ethn=slirp,ethernet address,slirp path >>>>>> >>>>>> That said, the slirp tool is old and AFIAK unmaintained. >>>>>> qemu forked it a long time ago and has it integrated into its >>>>>> source. >>>>>> >>>>> >>>>> Documentation of UML also said that ethernet address is optional. I did >>>>> both ways, none worked (and it took me a few minutes and tries to find >>>>> out that not all MAC addresses are possible to use for a virtual machine >>>>> like UML; is this at least mentioned in some UML doc? It shouls, IMHO). >>>>> >>>>> So, is it possible that I run an UML with full Internet access, and >>>>> without having root access in the host machine? Or am I trying something >>>>> that from the start was not possible? >>>>> >>>>> If it is not possible, is it easy to set up some form of file sharing >>>>> between the host and UML machine? (again, this must *not* depend on host >>>>> root access!) >>>> >>>> As I said, if you don't have root on the host, you have to use slirp. >>>> >>> >>> And I am using slirp. But it do not work yet. I'm not sure what is >>> wrong. May you help me? >> >> Just gave it a try. Works here. >> >> ./linux ubda=../Downloads/Debian-Squeeze-AMD64-root_fs mem=1G >> eth0=slirp,FE:FD:01:02:03:04,/home/rw/work/slirp/slirp-1.0.17/src/slirp >> >> root@uml:~# ifconfig eth0 10.0.2.15 up >> root@uml:~# route add default gw 10.0.2.15 > > Do not work for me. And to point directly to the slirp program instead > of its folder (which is understood by many as the *path* for anything, > not the things themselves, with full path) is news for me, and something > that should be pointed in the docs. I think many others will understand > it as I did before you said this. "Does not work" is not a valid error description. Please find out what exactly does not work. > Now there is a few lines about slirt and ETH0: > > ======================= > [autodetect SLIP/CSLIP, MTU 1500, MRU 1500, 115200 baud] > > SLiRP Ready ... > Unsupported device type 256 for "eth0" > Failed to bring up eth0. > done. > > ======================== DHCP cannot work on SLIRP. That's why you have to configure the interface manually. > What can I do? > >> Then you can use networking. Please not that slirp does not have a >> performance. >> Depending on your slirp package you can tweak it. > > I have compiled it from source. Do you know exactly where and how I can > tweak it? If so, please say how, so I don't have to search and find what > is already known. AFAIK Debian folks have some patches in their package. Thanks, //richard |
|
From: Balaco B. <bal...@im...> - 2015-11-22 15:39:16
|
On Fri, Nov 13, 2015, at 18:15, Richard Weinberger wrote: > Am 12.11.2015 um 14:22 schrieb Balaco Baco: > > On Thu, Nov 12, 2015, at 10:00, Richard Weinberger wrote: > >> Am 12.11.2015 um 02:57 schrieb Balaco Baco: > >>> On Wed, Nov 11, 2015, at 17:34, Richard Weinberger wrote: > >>>> Am 11.11.2015 um 18:57 schrieb Balaco Baco: > >>>>> Since I have no root access in the host machine, I must use 'slirp'. > >>>>> Right? Now I'll install it (https://en.wikipedia.org/wiki/Slirp) from > >>>>> source and pass the full path to UML in the command line, e.g.: > >>>> > >>>> Yes. > >>>> > >>>>> eth0=slirp,,/home/me/bin/ > >>>> > >>>> Documentation says: ethn=slirp,ethernet address,slirp path > >>>> > >>>> That said, the slirp tool is old and AFIAK unmaintained. > >>>> qemu forked it a long time ago and has it integrated into its > >>>> source. > >>>> > >>> > >>> Documentation of UML also said that ethernet address is optional. I did > >>> both ways, none worked (and it took me a few minutes and tries to find > >>> out that not all MAC addresses are possible to use for a virtual machine > >>> like UML; is this at least mentioned in some UML doc? It shouls, IMHO). > >>> > >>> So, is it possible that I run an UML with full Internet access, and > >>> without having root access in the host machine? Or am I trying something > >>> that from the start was not possible? > >>> > >>> If it is not possible, is it easy to set up some form of file sharing > >>> between the host and UML machine? (again, this must *not* depend on host > >>> root access!) > >> > >> As I said, if you don't have root on the host, you have to use slirp. > >> > > > > And I am using slirp. But it do not work yet. I'm not sure what is > > wrong. May you help me? > > Just gave it a try. Works here. > > ./linux ubda=../Downloads/Debian-Squeeze-AMD64-root_fs mem=1G > eth0=slirp,FE:FD:01:02:03:04,/home/rw/work/slirp/slirp-1.0.17/src/slirp > > root@uml:~# ifconfig eth0 10.0.2.15 up > root@uml:~# route add default gw 10.0.2.15 Do not work for me. And to point directly to the slirp program instead of its folder (which is understood by many as the *path* for anything, not the things themselves, with full path) is news for me, and something that should be pointed in the docs. I think many others will understand it as I did before you said this. Now there is a few lines about slirt and ETH0: ======================= [autodetect SLIP/CSLIP, MTU 1500, MRU 1500, 115200 baud] SLiRP Ready ... Unsupported device type 256 for "eth0" Failed to bring up eth0. done. ======================== What can I do? > Then you can use networking. Please not that slirp does not have a > performance. > Depending on your slirp package you can tweak it. I have compiled it from source. Do you know exactly where and how I can tweak it? If so, please say how, so I don't have to search and find what is already known. Thank you -- http://www.fastmail.com - Email service worth paying for. Try it for free |
|
From: Richard W. <ri...@no...> - 2015-11-13 21:15:51
|
Am 12.11.2015 um 14:22 schrieb Balaco Baco: > > On Thu, Nov 12, 2015, at 10:00, Richard Weinberger wrote: >> Am 12.11.2015 um 02:57 schrieb Balaco Baco: >>> On Wed, Nov 11, 2015, at 17:34, Richard Weinberger wrote: >>>> Am 11.11.2015 um 18:57 schrieb Balaco Baco: >>>>> Since I have no root access in the host machine, I must use 'slirp'. >>>>> Right? Now I'll install it (https://en.wikipedia.org/wiki/Slirp) from >>>>> source and pass the full path to UML in the command line, e.g.: >>>> >>>> Yes. >>>> >>>>> eth0=slirp,,/home/me/bin/ >>>> >>>> Documentation says: ethn=slirp,ethernet address,slirp path >>>> >>>> That said, the slirp tool is old and AFIAK unmaintained. >>>> qemu forked it a long time ago and has it integrated into its >>>> source. >>>> >>> >>> Documentation of UML also said that ethernet address is optional. I did >>> both ways, none worked (and it took me a few minutes and tries to find >>> out that not all MAC addresses are possible to use for a virtual machine >>> like UML; is this at least mentioned in some UML doc? It shouls, IMHO). >>> >>> So, is it possible that I run an UML with full Internet access, and >>> without having root access in the host machine? Or am I trying something >>> that from the start was not possible? >>> >>> If it is not possible, is it easy to set up some form of file sharing >>> between the host and UML machine? (again, this must *not* depend on host >>> root access!) >> >> As I said, if you don't have root on the host, you have to use slirp. >> > > And I am using slirp. But it do not work yet. I'm not sure what is > wrong. May you help me? Just gave it a try. Works here. ./linux ubda=../Downloads/Debian-Squeeze-AMD64-root_fs mem=1G eth0=slirp,FE:FD:01:02:03:04,/home/rw/work/slirp/slirp-1.0.17/src/slirp root@uml:~# ifconfig eth0 10.0.2.15 up root@uml:~# route add default gw 10.0.2.15 Then you can use networking. Please not that slirp does not have a performance. Depending on your slirp package you can tweak it. Thanks, //richard |
|
From: Balaco B. <bal...@im...> - 2015-11-12 13:22:13
|
On Thu, Nov 12, 2015, at 10:00, Richard Weinberger wrote: > Am 12.11.2015 um 02:57 schrieb Balaco Baco: > > On Wed, Nov 11, 2015, at 17:34, Richard Weinberger wrote: > >> Am 11.11.2015 um 18:57 schrieb Balaco Baco: > >>> Since I have no root access in the host machine, I must use 'slirp'. > >>> Right? Now I'll install it (https://en.wikipedia.org/wiki/Slirp) from > >>> source and pass the full path to UML in the command line, e.g.: > >> > >> Yes. > >> > >>> eth0=slirp,,/home/me/bin/ > >> > >> Documentation says: ethn=slirp,ethernet address,slirp path > >> > >> That said, the slirp tool is old and AFIAK unmaintained. > >> qemu forked it a long time ago and has it integrated into its > >> source. > >> > > > > Documentation of UML also said that ethernet address is optional. I did > > both ways, none worked (and it took me a few minutes and tries to find > > out that not all MAC addresses are possible to use for a virtual machine > > like UML; is this at least mentioned in some UML doc? It shouls, IMHO). > > > > So, is it possible that I run an UML with full Internet access, and > > without having root access in the host machine? Or am I trying something > > that from the start was not possible? > > > > If it is not possible, is it easy to set up some form of file sharing > > between the host and UML machine? (again, this must *not* depend on host > > root access!) > > As I said, if you don't have root on the host, you have to use slirp. > And I am using slirp. But it do not work yet. I'm not sure what is wrong. May you help me? I have said what I tried and do to use slirp. If needed, I can say it again with more details, just ask. -- http://www.fastmail.com - Same, same, but different... |