From: Josep Ma [JAZ] <jo...@gm...> - 2008-01-23 18:47:25
|
As you say, you have to use a syntax like "eth0=slirp,,tcp:22:22/tcp:80:80" to open ports from colinux in slirp mode. Let's verify a few steps: How have you configured the eth in linux? you know you have to use the IP 10.0.2.15/24 , the gateway 10.0.2.2, and the DNS server 10.0.2.3, do you? (Configuring it with DHCP should also work). Do you get to internet from colinux? Ping doesn't work with slirp, but you can try telnet, ssh, wget.... Now, if that works, how do you try to connect to colinux from windows? Slirp connection makes colinux act as if it was the windows machine. This means that you have to connect to localhost. Example: http://localhost/ should connect to an http server in colinux, if using the above eth0 configuration. (That is, of course, if there port isn't already used in windows). If that still doesn't work, you would need to be more specific as to which configuration are you using and how do you try to use it. |
From: Henry N. <Henry.Ne@Arcor.de> - 2008-01-23 19:02:06
|
Josep Ma [JAZ] wrote: > As you say, you have to use a syntax like > "eth0=slirp,,tcp:22:22/tcp:80:80" to open ports from colinux in slirp mode. > > Let's verify a few steps: > > How have you configured the eth in linux? > you know you have to use the IP 10.0.2.15/24 , the gateway 10.0.2.2, and > the DNS server 10.0.2.3, do you? (Configuring it with DHCP should also > work). Be shure to have netmask 255.255.255.0 All other, or default generated netmask for ip 10.0.2.15 dos't work. > Do you get to internet from colinux? > Ping doesn't work with slirp, but you can try telnet, ssh, wget.... > > Now, if that works, how do you try to connect to colinux from windows? > Slirp connection makes colinux act as if it was the windows machine. > This means that you have to connect to localhost. Example: > http://localhost/ should connect to an http server in colinux, if using > the above eth0 configuration. (That is, of course, if there port isn't > already used in windows). > > If that still doesn't work, you would need to be more specific as to > which configuration are you using and how do you try to use it. Yes. Plesase check the steps from one to other network step by step. First inside coLinux check the running webserver, for example $ cd /tmp $ wget http://localhost/ Would get your index.htm without errors. $ wget http://10.0.2.15/ Should do the same without error. Go to windows side and open your browser with url http://localhost/ Should get your index.htm on windows. If not, check your firewall. Disable firewall temporaly, shutdown and start colinux again. If that not helps, check the running processes inside taskman. colinux-slirp-net-daemon.exe must run and should have the parameters "tcp:22:22/tcp:80:80". If taskman dos't give you the parameters, use the ProcessExplorer from http://www.sysinternals.com (redirection to MS). After the process parameter are ok, than check the listen port on tcp. You can do it also with ProcessExplorer or with tcpView.exe (from http://www.sysinternals.com). YOu should see an listen 0.0.0.0 on port 22 and 80. -- Henry N. |
From: <2...@pe...> - 2008-01-23 20:30:18
|
On Wed, 23 Jan 2008, Henry Nestler wrote: > Josep Ma [JAZ] wrote: >> As you say, you have to use a syntax like >> "eth0=slirp,,tcp:22:22/tcp:80:80" to open ports from colinux in slirp mode. >> >> Let's verify a few steps: >> >> How have you configured the eth in linux? >> you know you have to use the IP 10.0.2.15/24 , the gateway 10.0.2.2, and >> the DNS server 10.0.2.3, do you? (Configuring it with DHCP should also >> work). > > Be shure to have netmask 255.255.255.0 > All other, or default generated netmask for ip 10.0.2.15 dos't work. > >> Do you get to internet from colinux? >> Ping doesn't work with slirp, but you can try telnet, ssh, wget.... >> >> Now, if that works, how do you try to connect to colinux from windows? >> Slirp connection makes colinux act as if it was the windows machine. >> This means that you have to connect to localhost. Example: >> http://localhost/ should connect to an http server in colinux, if using >> the above eth0 configuration. (That is, of course, if there port isn't >> already used in windows). >> >> If that still doesn't work, you would need to be more specific as to >> which configuration are you using and how do you try to use it. > > Yes. Plesase check the steps from one to other network step by step. > First inside coLinux check the running webserver, for example > $ cd /tmp > $ wget http://localhost/ > Would get your index.htm without errors. > $ wget http://10.0.2.15/ > Should do the same without error. > > Go to windows side and open your browser with url > http://localhost/ > Should get your index.htm on windows. > If not, check your firewall. Disable firewall temporaly, shutdown and > start colinux again. > > If that not helps, check the running processes inside taskman. > colinux-slirp-net-daemon.exe must run and should have the parameters > "tcp:22:22/tcp:80:80". If taskman dos't give you the parameters, use the > ProcessExplorer from http://www.sysinternals.com (redirection to MS). > > After the process parameter are ok, than check the listen port on tcp. > You can do it also with ProcessExplorer or with tcpView.exe (from > http://www.sysinternals.com). YOu should see an listen 0.0.0.0 on port > 22 and 80. Everything you both listed is right, but http://localhost/ doesn't work from Windows. It does only if I run a native Windows server. In TCPView, I see: colinux-slirp-net-daemon.exe TCP PERVALIDUS:80 PERVALIDUS:0 LISTENING and firefox.exe TCP PERVALIDUS:3819 localhost:80 FIN_WAIT2 firefox.exe TCP PERVALIDUS:3819 localhost:80 ESTABLISHED ... when I try to connect from Firefox, but it stays at "Loading...". I don't have any firewall running on Windows, but added colinux-slirp-net-daemon.exe to the list of exceptions in Windows Firewall. On Linux there's iptables, but the same rules work on Linux. netstat on coLinux shows: tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN |
From: Henry N. <Henry.Ne@Arcor.de> - 2008-01-23 20:52:02
|
Frédéric L. W. Meunier wrote: > On Wed, 23 Jan 2008, Henry Nestler wrote: > >> Josep Ma [JAZ] wrote: >>> As you say, you have to use a syntax like >>> "eth0=slirp,,tcp:22:22/tcp:80:80" to open ports from colinux in slirp mode. >>> >>> Let's verify a few steps: >>> >>> How have you configured the eth in linux? >>> you know you have to use the IP 10.0.2.15/24 , the gateway 10.0.2.2, and >>> the DNS server 10.0.2.3, do you? (Configuring it with DHCP should also >>> work). >> Be shure to have netmask 255.255.255.0 >> All other, or default generated netmask for ip 10.0.2.15 dos't work. >> >>> Do you get to internet from colinux? >>> Ping doesn't work with slirp, but you can try telnet, ssh, wget.... >>> >>> Now, if that works, how do you try to connect to colinux from windows? >>> Slirp connection makes colinux act as if it was the windows machine. >>> This means that you have to connect to localhost. Example: >>> http://localhost/ should connect to an http server in colinux, if using >>> the above eth0 configuration. (That is, of course, if there port isn't >>> already used in windows). >>> >>> If that still doesn't work, you would need to be more specific as to >>> which configuration are you using and how do you try to use it. >> Yes. Plesase check the steps from one to other network step by step. >> First inside coLinux check the running webserver, for example >> $ cd /tmp >> $ wget http://localhost/ >> Would get your index.htm without errors. >> $ wget http://10.0.2.15/ >> Should do the same without error. >> >> Go to windows side and open your browser with url >> http://localhost/ >> Should get your index.htm on windows. >> If not, check your firewall. Disable firewall temporaly, shutdown and >> start colinux again. >> >> If that not helps, check the running processes inside taskman. >> colinux-slirp-net-daemon.exe must run and should have the parameters >> "tcp:22:22/tcp:80:80". If taskman dos't give you the parameters, use the >> ProcessExplorer from http://www.sysinternals.com (redirection to MS). >> >> After the process parameter are ok, than check the listen port on tcp. >> You can do it also with ProcessExplorer or with tcpView.exe (from >> http://www.sysinternals.com). YOu should see an listen 0.0.0.0 on port >> 22 and 80. > > Everything you both listed is right, but http://localhost/ > doesn't work from Windows. It does only if I run a native > Windows server. I don't know your difference you means. Windows != Windows Server ? If not native Windows? What else is it? > In TCPView, I see: > > colinux-slirp-net-daemon.exe TCP PERVALIDUS:80 PERVALIDUS:0 > LISTENING Please disable DNS Name Resolution on TCPview. It should be listen on 0.0.0.0 (every networks) Check: The first lines from Windows command NETSTAT.EXE /a /n (I don't know the paremters right). The IP 0.0.0.0 on port 80 and 22 should be "listen". Think it is, TCPview shows the same. Check: Stop coLinux. The port 80 and 22 should no longer listen. Try other port for remapping, for example tcp:2222:22/tcp:4000:80 Than on the windows side the port 4000 is your webserver and port 80 inside coLinux. Type the URL http://localhost:4000/ in your Windows browser. > I don't have any firewall running on Windows, but added > colinux-slirp-net-daemon.exe to the list of exceptions in > Windows Firewall. If you have no firewall on windows, why you can add exceptions to firewall? Try complete disable the windoes internal firewall. If you not would risk some, you can disconnect your networkcable for this testing time. Slirp is usable from windows to coLinux and via versa without any external network. Check: We talk about coLinux 0.7.1, 0.7.2 or 0.8.x? Not older, please. > On Linux there's iptables, but the same rules > work on Linux. > > netstat on coLinux shows: > > tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN Ok, let coLinux config it untouched. -- Henry N. |
From: <lis...@pe...> - 2008-01-23 21:40:31
|
On Jan 23, 2008 6:53 PM, Henry Nestler <Hen...@ar...> wrote: > > Fr=E9d=E9ric L. W. Meunier wrote: > > On Wed, 23 Jan 2008, Henry Nestler wrote: > > > > Everything you both listed is right, but http://localhost/ > > doesn't work from Windows. It does only if I run a native > > Windows server. > > I don't know your difference you means. > Windows !=3D Windows Server ? > If not native Windows? What else is it? > I meant Windows =3D XP Professional and Windows server =3D a Windows HTTP s= erver. > > In TCPView, I see: > > > > colinux-slirp-net-daemon.exe TCP PERVALIDUS:80 PERVALIDUS:0 > > LISTENING > > Please disable DNS Name Resolution on TCPview. It should be listen on > 0.0.0.0 (every networks) > It returns 0.0.0.0. > Try other port for remapping, for example > tcp:2222:22/tcp:4000:80 > Than on the windows side the port 4000 is your webserver and port 80 > inside coLinux. Type the URL http://localhost:4000/ in your Windows brows= er. Remapping, both work.Now I really don't have any idea why using the same ports doesn't. > > I don't have any firewall running on Windows, but added > > colinux-slirp-net-daemon.exe to the list of exceptions in > > Windows Firewall. > > If you have no firewall on windows, why you can add exceptions to > firewall? Try complete disable the windoes internal firewall. If you not > would risk some, you can disconnect your networkcable for this testing > time. Slirp is usable from windows to coLinux and via versa without any > external network. Windows Firewall is "off", but even with it disabled, the "Exceptions" tab is enabled. Just for safety, I had added colinux-slirp-net-daemon.exe to the list. > Check: We talk about coLinux 0.7.1, 0.7.2 or 0.8.x? Not older, please. 0.8.0-20071105. |
From: Henry N. <Henry.Ne@Arcor.de> - 2008-01-23 22:06:45
|
Frédéric L. W. Meunier schrieb: > On Jan 23, 2008 6:53 PM, Henry Nestler <Hen...@ar...> wrote: >> Frédéric L. W. Meunier wrote: >>> On Wed, 23 Jan 2008, Henry Nestler wrote: >>> >>> Everything you both listed is right, but http://localhost/ >>> doesn't work from Windows. It does only if I run a native >>> Windows server. >> I don't know your difference you means. >> Windows != Windows Server ? >> If not native Windows? What else is it? >> > > I meant Windows = XP Professional and Windows server = a Windows HTTP server. > >>> In TCPView, I see: >>> >>> colinux-slirp-net-daemon.exe TCP PERVALIDUS:80 PERVALIDUS:0 >>> LISTENING >> Please disable DNS Name Resolution on TCPview. It should be listen on >> 0.0.0.0 (every networks) >> > > It returns 0.0.0.0. > >> Try other port for remapping, for example >> tcp:2222:22/tcp:4000:80 >> Than on the windows side the port 4000 is your webserver and port 80 >> inside coLinux. Type the URL http://localhost:4000/ in your Windows browser. > > Remapping, both work.Now I really don't have any idea why using the > same ports doesn't. Only one program can agent as server on one tcp port. If you have a running program that is listen on port 80 (windows web Server ?), than an other program can not open the same port for listen. Or ir can open, but windows is faster and catch all the incommings. I don't know. Has your windows some more protections to not open ports lower than 1024 from a user program as server? Some firewalls or secure tools forbidden and and blocks it (Zone Alarm, Norton, ...). For example on Linux an user land program can only listen on ports >1023. On ports 22 and 80 only a user "root" can listen. -- Henry N. |
From: <2...@pe...> - 2008-01-23 22:26:56
|
On Wed, 23 Jan 2008, Henry Nestler wrote: >>> Try other port for remapping, for example >>> tcp:2222:22/tcp:4000:80 >>> Than on the windows side the port 4000 is your webserver and port 80 >>> inside coLinux. Type the URL http://localhost:4000/ in your Windows browser. >> >> Remapping, both work.Now I really don't have any idea why using the >> same ports doesn't. > > Only one program can agent as server on one tcp port. > If you have a running program that is listen on port 80 (windows web > Server ?), than an other program can not open the same port for listen. > Or ir can open, but windows is faster and catch all the incommings. I > don't know. > > Has your windows some more protections to not open ports lower than 1024 > from a user program as server? Some firewalls or secure tools forbidden > and and blocks it (Zone Alarm, Norton, ...). > > For example on Linux an user land program can only listen on ports >> 1023. On ports 22 and 80 only a user "root" can listen. I don't know what caused it, but now everything works. I changed it to eth0=slirp,,tcp:2222:22/tcp:80:80/tcp:8080:8080 and it works if I use in 80 or 8080. But if I recall correctly, when it didn't work, dhcpcd had set my IP to 10.0.2.16. Now it's 10.0.2.15. Does it change anything it the IP isn't 10.0.2.15 ? Sometimes dhcpcd doesn't offer 10.0.2.15. When it didn't work, I could connect from coLinux to localhost and 10.0.2.16. Anyway, thanks for your help. |
From: Henry N. <Henry.Ne@Arcor.de> - 2008-01-23 22:45:25
|
Frédéric L. W. Meunier wrote: > I don't know what caused it, but now everything works. I > changed it to > > eth0=slirp,,tcp:2222:22/tcp:80:80/tcp:8080:8080 > > and it works if I use in 80 or 8080. This confiused me! ;-( If you not have a server on port 8080 on coLinux (Linux) side, you should no have a positive response from port 8080 on Windows side. Or, you found a bug. Plesase send me your used colinux config file or batch script and say, what distri you use. > But if I recall correctly, when it didn't work, dhcpcd had set > my IP to 10.0.2.16. Now it's 10.0.2.15. Does it change anything > it the IP isn't 10.0.2.15 ? Sometimes dhcpcd doesn't offer > 10.0.2.15. IP 10.0.2.16 is not ok for DHCP. Have you more about the DHCP protocoll from /var/log/message with typicaly OFFER/ACK/NAK messages? Sems me, we have the bug with badly DHCP offers not fixed. Only 10.0.2.15 is the right address. The DHCP-Server inside slirp should give only this one address all times. You can set the working config as static to have no problems in future. -- Henry N. |
From: <2...@pe...> - 2008-01-23 23:00:19
|
On Wed, 23 Jan 2008, Henry Nestler wrote: > Frédéric L. W. Meunier wrote: >> I don't know what caused it, but now everything works. I >> changed it to >> >> eth0=slirp,,tcp:2222:22/tcp:80:80/tcp:8080:8080 >> >> and it works if I use in 80 or 8080. > > This confiused me! ;-( > If you not have a server on port 8080 on coLinux (Linux) side, you > should no have a positive response from port 8080 on Windows side. Or, > you found a bug. Plesase send me your used colinux config file or batch > script and say, what distri you use. > >> But if I recall correctly, when it didn't work, dhcpcd had set >> my IP to 10.0.2.16. Now it's 10.0.2.15. Does it change anything >> it the IP isn't 10.0.2.15 ? Sometimes dhcpcd doesn't offer >> 10.0.2.15. > > IP 10.0.2.16 is not ok for DHCP. Have you more about the DHCP protocoll > from /var/log/message with typicaly OFFER/ACK/NAK messages? Sems me, we > have the bug with badly DHCP offers not fixed. > Only 10.0.2.15 is the right address. The DHCP-Server inside slirp should > give only this one address all times. > You can set the working config as static to have no problems in future. I'll set manually. In /var/log/messages there are lines "offered 10.0.2.17 from 10.0.2.2" "leased 10.0.2.16" and "offered 10.0.2.18 from 10.0.2.2" "leased 10.0.2.16". |
From: Henry N. <Henry.Ne@Arcor.de> - 2008-01-23 23:04:56
|
Frédéric L. W. Meunier wrote: > I'll set manually. In /var/log/messages there are lines "offered > 10.0.2.17 from 10.0.2.2" "leased 10.0.2.16" and "offered 10.0.2.18 from > 10.0.2.2" "leased 10.0.2.16". That's very badly. What distry and what version of dhcp-client? -- Henry N. |
From: <2...@pe...> - 2008-01-23 23:09:16
|
On Thu, 24 Jan 2008, Henry Nestler wrote: > Frédéric L. W. Meunier wrote: >> I'll set manually. In /var/log/messages there are lines "offered >> 10.0.2.17 from 10.0.2.2" "leased 10.0.2.16" and "offered 10.0.2.18 from >> 10.0.2.2" "leased 10.0.2.16". > > That's very badly. What distry and what version of dhcp-client? It's Slackware but with dhcpcd 3.1.19. |
From: <2...@pe...> - 2008-01-24 01:13:14
|
On Wed, 23 Jan 2008, Frédéric L. W. Meunier wrote: > On Wed, 23 Jan 2008, Henry Nestler wrote: > >> Frédéric L. W. Meunier wrote: >>> I don't know what caused it, but now everything works. I changed it to >>> >>> eth0=slirp,,tcp:2222:22/tcp:80:80/tcp:8080:8080 >>> >>> and it works if I use in 80 or 8080. >> >> This confiused me! ;-( >> If you not have a server on port 8080 on coLinux (Linux) side, you >> should no have a positive response from port 8080 on Windows side. Or, >> you found a bug. Plesase send me your used colinux config file or batch >> script and say, what distri you use. I forgot to answer this. I tested the server in both ports, so no problem. |
From: Henry N. <Henry.Ne@Arcor.de> - 2008-01-23 23:24:37
|
Frédéric L. W. Meunier wrote: > On Thu, 24 Jan 2008, Henry Nestler wrote: > >> Frédéric L. W. Meunier wrote: >>> I'll set manually. In /var/log/messages there are lines "offered >>> 10.0.2.17 from 10.0.2.2" "leased 10.0.2.16" and "offered 10.0.2.18 from >>> 10.0.2.2" "leased 10.0.2.16". >> >> That's very badly. What distry and what version of dhcp-client? > > It's Slackware but with dhcpcd 3.1.19. Is that a special hacked version? Where can I get the source of your version? I only found up 3.1.9 on http://roy.marples.name/dhcpcd My working is 1.3.22 (SuSE 10.3) http://www.phystech.com/download/dhcpcd.html -- Henry N. |
From: <2...@pe...> - 2008-01-23 23:35:27
|
On Thu, 24 Jan 2008, Henry Nestler wrote: > Frédéric L. W. Meunier wrote: >> On Thu, 24 Jan 2008, Henry Nestler wrote: >> >>> Frédéric L. W. Meunier wrote: >>>> I'll set manually. In /var/log/messages there are lines "offered >>>> 10.0.2.17 from 10.0.2.2" "leased 10.0.2.16" and "offered 10.0.2.18 from >>>> 10.0.2.2" "leased 10.0.2.16". >>> >>> That's very badly. What distry and what version of dhcp-client? >> >> It's Slackware but with dhcpcd 3.1.19. > > Is that a special hacked version? > Where can I get the source of your version? > > I only found up 3.1.9 on > http://roy.marples.name/dhcpcd > > My working is 1.3.22 (SuSE 10.3) > http://www.phystech.com/download/dhcpcd.html No, sorry. It's 3.1.9. Slackware has 2.0.4. I'll see if I get another IP also with that version. |