From: <dam...@ne...> - 2005-10-03 15:34:10
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-15" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#ffffff" text="#000000"> Hello all, <br> Thanks for the reply, but I still have an other problem.<br> My goal is to use a CoLinux server without windows network. So I want to access my CoLinux with standard port (22/80).<br> When my windows is launched with the network there is no problem, I can access all forwarded ports, even if I deactivate the network. But when I launch my windows without network I couldn't access forwarded port, even if I activate the network after... The port is responding but not the service : <br> example : <br> <u>Booting without network, and with network deactivate : </u><br> <tt>dboussie@daffy ~<br> $ telnet localhost 80<br> Trying 127.0.0.1...<br> Connected to daffy.<br> Escape character is '^]'.<br> Connection closed by foreign host.<br> <br> dboussie@daffy ~</tt><u><br> Booting without network, and with network activate after boot but without relaunching CoLinux</u><br> <tt>dboussie@daffy ~<br> $ telnet localhost 80<br> Trying 127.0.0.1...<br> Connected to daffy.<br> Escape character is '^]'.<br> Connection closed by foreign host.<br> <br> dboussie@daffy ~</tt><br> <br> <u>After relaunching CoLinux with network enable, it's ok.</u><br> <u>When I boot with network and deactivate the network I can access forwarded port ... </u><br> <br> I'm running coLinux-0.6.3-rc2, with Debian image and SLIRP network.<br> <br> Have someone the same problem as me ? <br> Have someone access its forwarded port, even if there is no network at boot ?<br> Have someone an idea for my problem ?<br> Thanks in advance, <br> bye, <br> <div class="moz-signature">-- <br> Damien...<a href="http://www.neolane.com"></a><br> </div> </body> </html> |
From: Henry N. <Henry.Ne@Arcor.de> - 2005-10-04 18:20:22
|
Damien Boussi=E9 wrote: > Hello all, > Thanks for the reply, but I still have an other problem. > My goal is to use a CoLinux server without windows network. So I=20 > want to access my CoLinux with standard port (22/80). > When my windows is launched with the network there is no problem, I= =20 > can access all forwarded ports, even if I deactivate the network. But=20 > when I launch my windows without network I couldn't access forwarded=20 > port, even if I activate the network after... The port is responding bu= t=20 > not the service : > example : > _Booting without network, and with network deactivate : _ > dboussie@daffy ~ > $ telnet localhost 80 > Trying 127.0.0.1... > Connected to daffy. > Escape character is '^]'. > Connection closed by foreign host. >=20 > dboussie@daffy ~_ > Booting without network, and with network activate after boot but=20 > without relaunching CoLinux_ > dboussie@daffy ~ > $ telnet localhost 80 > Trying 127.0.0.1... > Connected to daffy. > Escape character is '^]'. > Connection closed by foreign host. >=20 > dboussie@daffy ~ >=20 > _After relaunching CoLinux with network enable, it's ok._ > _When I boot with network and deactivate the network I can access=20 > forwarded port ... _ >=20 > I'm running coLinux-0.6.3-rc2, with Debian image and SLIRP network. >=20 > Have someone the same problem as me ? > Have someone access its forwarded port, even if there is no network= =20 > at boot ? > Have someone an idea for my problem ? > Thanks in advance, > bye, If you start colinux without networks, the SLiRP hangs on localhost=20 127.0.0.1, but it's not implement the forwarding for this address. Why you not install tun-tap for local network between windows and colinux= ? Good combination is using of SLiRP and TAP on different networks. This=20 allow you to use TAP all times from windows to linux, and SLiRP for=20 outgoing (or incomming, if forwards). Sample: <network index=3D"0" type=3D"slirp" redir=3D"tcp:22:22/tcp:23:23" /> <network index=3D"1" type=3D"tap" /> Inside colinux: eth0: 192.168.200.x (Or other network, that is not use in your LAN) eth1: 10.0.2.15/255.255.255.0 Gateway: 10.0.2.2 DNS: 10.0.2.3 --=20 Henry Nestler |
From: <dam...@ne...> - 2005-10-05 12:03:46
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-15" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#ffffff" text="#000000"> Henry Nestler a écrit : <blockquote cite="mid4342C7DA.8040407@Arcor.de" type="cite">Damien Boussié wrote: <br> <blockquote type="cite">Hello all, <br> Thanks for the reply, but I still have an other problem. <br> My goal is to use a CoLinux server without windows network. So I want to access my CoLinux with standard port (22/80). <br> When my windows is launched with the network there is no problem, I can access all forwarded ports, even if I deactivate the network. But when I launch my windows without network I couldn't access forwarded port, even if I activate the network after... The port is responding but not the service : <br> example : <br> _Booting without network, and with network deactivate : _ <br> dboussie@daffy ~ <br> $ telnet localhost 80 <br> Trying 127.0.0.1... <br> Connected to daffy. <br> Escape character is '^]'. <br> Connection closed by foreign host. <br> <br> dboussie@daffy ~_ <br> Booting without network, and with network activate after boot but without relaunching CoLinux_ <br> dboussie@daffy ~ <br> $ telnet localhost 80 <br> Trying 127.0.0.1... <br> Connected to daffy. <br> Escape character is '^]'. <br> Connection closed by foreign host. <br> <br> dboussie@daffy ~ <br> <br> _After relaunching CoLinux with network enable, it's ok._ <br> _When I boot with network and deactivate the network I can access forwarded port ... _ <br> <br> I'm running coLinux-0.6.3-rc2, with Debian image and SLIRP network. <br> <br> Have someone the same problem as me ? <br> Have someone access its forwarded port, even if there is no network at boot ? <br> Have someone an idea for my problem ? <br> Thanks in advance, <br> bye, <br> </blockquote> <br> If you start colinux without networks, the SLiRP hangs on localhost 127.0.0.1, but it's not implement the forwarding for this address. <br> <br> Why you not install tun-tap for local network between windows and colinux? <br> <br> Good combination is using of SLiRP and TAP on different networks. This allow you to use TAP all times from windows to linux, and SLiRP for outgoing (or incomming, if forwards). <br> <br> Sample: <br> <network index="0" type="slirp" redir="tcp:22:22/tcp:23:23" /> <br> <network index="1" type="tap" /> <br> <br> Inside colinux: <br> eth0: 192.168.200.x (Or other network, that is not use in your LAN) <br> eth1: 10.0.2.15/255.255.255.0 <br> Gateway: 10.0.2.2 <br> DNS: 10.0.2.3 <br> </blockquote> Yes, the combination of both is good. I can access the coLinux from outside when using the network, and I can access CoLinux from the window box in every case, thanks for this idea...<br> <br> For all people here is <u>my working configuration : </u><br> coLinux-0.6.3-rc2<br> Debian Im<font color="#330033">age : <a href="http://prdownloads.sourceforge.net/colinux/Debian-3.0r2.ext3-mit-backports.1gb.bz2?download">Debian-3.0r2.ext3-mit-backports.1gb.bz2</a></font><font color="#330033"> upg</font>raded to Debian 3.1 with apache/postgresql compiled<br> here is <u>my config.xml</u> : <br> <tt><?xml version="1.0" encoding="UTF-8"?><br> <colinux><br> </tt><tt><block_device index="0" path="\DosDevices\C:\Program Files\coLinux\*ImageName*.1gb" enabled="true" /><br> <bootparams>root=/dev/cobd0</bootparams><br> <initrd path="initrd.gz" /><br> <image path="vmlinux" /><br> <memory size="384" /><br> <network index="0" type="slirp" redir="tcp:22:22/tcp:23:22/tcp:80:80/tcp:81:80/tcp:110:110/tcp:443:443/tcp:5432:5432/tcp:5433:5432/tcp:8080:8080/tcp:8081:8080" /> <br> <network index="1" type="tap" /> <br> </colinux><br> <br> <u>Debian network </u>: <br> vi /etc/network/interfaces<br> auto lo<br> iface lo inet loopback<br> auto eth0<br> iface eth0 inet dhcp<br> iface eth1 inet dhcp<br> <br> <u>Windows TAP configuration </u>: <br> IP address : 192.168.13.13<br> mask : 255.255.255.0<br> all other : blank<br> <u><br> auto launch script : </u><br> start "*Name* - CoLinux" /D"C:\Program Files\coLinux" /min colinux-daemon.exe -c colinux.xml -d<br> </tt><br> I'm using the 192.168.13.13 to access the CoLinux box from the window host<br> and the window host (IP) to access the CoLinux from outside (by ports forwarded).<br> <br> Many thanks for all informations, on the web and on the mailing list ... and for this software.<br> GoodBye, <br> --<br> Damien ...<br> <br> </body> </html> |
From: Henry N. <Henry.Ne@Arcor.de> - 2005-10-06 08:21:16
|
Hello Damien, Damien Boussi=E9 wrote: > Henry Nestler a =E9crit : >=20 >> Damien Boussi=E9 wrote: >> >>> Hello all, >>> Thanks for the reply, but I still have an other problem. >>> My goal is to use a CoLinux server without windows network. So I=20 >>> want to access my CoLinux with standard port (22/80). >>> When my windows is launched with the network there is no problem,= =20 >>> I can access all forwarded ports, even if I deactivate the network.=20 >>> But when I launch my windows without network I couldn't access=20 >>> forwarded port, even if I activate the network after... The port is=20 >>> responding but not the service : >>> example : >>> _Booting without network, and with network deactivate : _ >>> dboussie@daffy ~ >>> $ telnet localhost 80 >>> Trying 127.0.0.1... >>> Connected to daffy. >>> Escape character is '^]'. >>> Connection closed by foreign host. >>> >>> dboussie@daffy ~_ >>> Booting without network, and with network activate after boot but=20 >>> without relaunching CoLinux_ >>> dboussie@daffy ~ >>> $ telnet localhost 80 >>> Trying 127.0.0.1... >>> Connected to daffy. >>> Escape character is '^]'. >>> Connection closed by foreign host. >>> >>> dboussie@daffy ~ >>> >>> _After relaunching CoLinux with network enable, it's ok._ >>> _When I boot with network and deactivate the network I can access=20 >>> forwarded port ... _ >>> >>> I'm running coLinux-0.6.3-rc2, with Debian image and SLIRP networ= k. >>> >>> Have someone the same problem as me ? >>> Have someone access its forwarded port, even if there is no=20 >>> network at boot ? >>> Have someone an idea for my problem ? >>> Thanks in advance, >>> bye, >> >> >> If you start colinux without networks, the SLiRP hangs on localhost=20 >> 127.0.0.1, but it's not implement the forwarding for this address. >> >> Why you not install tun-tap for local network between windows and=20 >> colinux? >> >> Good combination is using of SLiRP and TAP on different networks. =20 >> This allow you to use TAP all times from windows to linux, and SLiRP=20 >> for outgoing (or incomming, if forwards). >> >> Sample: >> <network index=3D"0" type=3D"slirp" redir=3D"tcp:22:22/tcp:23:23" = /> >> <network index=3D"1" type=3D"tap" /> >> >> Inside colinux: >> eth0: 192.168.200.x (Or other network, that is not use in your LAN) >> eth1: 10.0.2.15/255.255.255.0 >> Gateway: 10.0.2.2 >> DNS: 10.0.2.3 >=20 > Yes, the combination of both is good. I can access the coLinux from=20 > outside when using the network, and I can access CoLinux from the windo= w=20 > box in every case, thanks for this idea... >=20 > For all people here is _my working configuration : _ > coLinux-0.6.3-rc2 > Debian Image : Debian-3.0r2.ext3-mit-backports.1gb.bz2=20 > <http://prdownloads.sourceforge.net/colinux/Debian-3.0r2.ext3-mit-backp= orts.1gb.bz2?download>=20 > upgraded to Debian 3.1 with apache/postgresql compiled > here is _my config.xml_ : > <?xml version=3D"1.0" encoding=3D"UTF-8"?> > <colinux> > <block_device index=3D"0" path=3D"\DosDevices\C:\Program=20 > Files\coLinux\*ImageName*.1gb" enabled=3D"true" /> > <bootparams>root=3D/dev/cobd0</bootparams> > <initrd path=3D"initrd.gz" /> > <image path=3D"vmlinux" /> > <memory size=3D"384" /> > <network index=3D"0" type=3D"slirp"=20 > redir=3D"tcp:22:22/tcp:23:22/tcp:80:80/tcp:81:80/tcp:110:110/tcp:443:44= 3/tcp:5432:5432/tcp:5433:5432/tcp:8080:8080/tcp:8081:8080"=20 > /> > <network index=3D"1" type=3D"tap" /> > </colinux> >=20 > _Debian network _: > vi /etc/network/interfaces > auto lo > iface lo inet loopback > auto eth0 > iface eth0 inet dhcp > iface eth1 inet dhcp >=20 > _Windows TAP configuration _: > IP address : 192.168.13.13 > mask : 255.255.255.0 > all other : blank > _ > auto launch script : _ > start "*Name* - CoLinux" /D"C:\Program Files\coLinux" /min=20 > colinux-daemon.exe -c colinux.xml -d >=20 > I'm using the 192.168.13.13 to access the CoLinux box from the window h= ost > and the window host (IP) to access the CoLinux from outside (by ports=20 > forwarded). eth1 (TAP) should set as "static" for sample 192.168.13.111 DHCP would timeout and use some older configs. In your experiments, I think it was set one time before, and DHCP use=20 configs from older boots now. But it would not work on fresh image. Some times the dhcp-client on SLiRP have problems, missing one of the=20 entries, mostly the DNS. If works all times for you, please say us your=20 name and version of dhcp-client (pump or so?). If dhcp-client don't work correct, set the static addresses for eth0=20 (SLiRP). eth0 =3D 10.0.2.15/255.255.255.0, default route 10.0.2.2, and=20 the DNS in /etc/resolve the nameserver 10.0.2.3. Search 'Network' in=20 the wiki. Use 192.168.13.111 for access from windows the linux. This is faster,=20 as SLiRP and works without port forwardings. For access from linux to windows use 192.168.13.13 (windows side of TAP). "tcp:23:22" --> 23 (ssh) on windows forward as 22 (telnet) to linux? You should not forward a ssh-port as telnet. Except that you wand=20 confuse your users, our you are building a honypot ;-) --=20 Henry Nestler |
From: <dam...@ne...> - 2005-10-10 09:00:45
|
Henry Nestler a écrit : > Hello Damien, > > Damien Boussié wrote: > >> Henry Nestler a écrit : >> >>> Damien Boussié wrote: >>> >>>> Hello all, >>>> Thanks for the reply, but I still have an other problem. >>>> My goal is to use a CoLinux server without windows network. So >>>> I want to access my CoLinux with standard port (22/80). >>>> When my windows is launched with the network there is no >>>> problem, I can access all forwarded ports, even if I deactivate the >>>> network. But when I launch my windows without network I couldn't >>>> access forwarded port, even if I activate the network after... The >>>> port is responding but not the service : >>>> example : >>>> _Booting without network, and with network deactivate : _ >>>> dboussie@daffy ~ >>>> $ telnet localhost 80 >>>> Trying 127.0.0.1... >>>> Connected to daffy. >>>> Escape character is '^]'. >>>> Connection closed by foreign host. >>>> >>>> dboussie@daffy ~_ >>>> Booting without network, and with network activate after boot but >>>> without relaunching CoLinux_ >>>> dboussie@daffy ~ >>>> $ telnet localhost 80 >>>> Trying 127.0.0.1... >>>> Connected to daffy. >>>> Escape character is '^]'. >>>> Connection closed by foreign host. >>>> >>>> dboussie@daffy ~ >>>> >>>> _After relaunching CoLinux with network enable, it's ok._ >>>> _When I boot with network and deactivate the network I can access >>>> forwarded port ... _ >>>> >>>> I'm running coLinux-0.6.3-rc2, with Debian image and SLIRP >>>> network. >>>> >>>> Have someone the same problem as me ? >>>> Have someone access its forwarded port, even if there is no >>>> network at boot ? >>>> Have someone an idea for my problem ? >>>> Thanks in advance, >>>> bye, >>> >>> >>> >>> If you start colinux without networks, the SLiRP hangs on localhost >>> 127.0.0.1, but it's not implement the forwarding for this address. >>> >>> Why you not install tun-tap for local network between windows and >>> colinux? >>> >>> Good combination is using of SLiRP and TAP on different networks. >>> This allow you to use TAP all times from windows to linux, and SLiRP >>> for outgoing (or incomming, if forwards). >>> >>> Sample: >>> <network index="0" type="slirp" redir="tcp:22:22/tcp:23:23" /> >>> <network index="1" type="tap" /> >>> >>> Inside colinux: >>> eth0: 192.168.200.x (Or other network, that is not use in your LAN) >>> eth1: 10.0.2.15/255.255.255.0 >>> Gateway: 10.0.2.2 >>> DNS: 10.0.2.3 >> >> >> Yes, the combination of both is good. I can access the coLinux from >> outside when using the network, and I can access CoLinux from the >> window box in every case, thanks for this idea... >> >> For all people here is _my working configuration : _ >> coLinux-0.6.3-rc2 >> Debian Image : Debian-3.0r2.ext3-mit-backports.1gb.bz2 >> <http://prdownloads.sourceforge.net/colinux/Debian-3.0r2.ext3-mit-backports.1gb.bz2?download> >> upgraded to Debian 3.1 with apache/postgresql compiled >> here is _my config.xml_ : >> <?xml version="1.0" encoding="UTF-8"?> >> <colinux> >> <block_device index="0" path="\DosDevices\C:\Program >> Files\coLinux\*ImageName*.1gb" enabled="true" /> >> <bootparams>root=/dev/cobd0</bootparams> >> <initrd path="initrd.gz" /> >> <image path="vmlinux" /> >> <memory size="384" /> >> <network index="0" type="slirp" >> redir="tcp:22:22/tcp:23:22/tcp:80:80/tcp:81:80/tcp:110:110/tcp:443:443/tcp:5432:5432/tcp:5433:5432/tcp:8080:8080/tcp:8081:8080" >> /> >> <network index="1" type="tap" /> >> </colinux> >> >> _Debian network _: >> vi /etc/network/interfaces >> auto lo >> iface lo inet loopback >> auto eth0 >> iface eth0 inet dhcp >> iface eth1 inet dhcp >> >> _Windows TAP configuration _: >> IP address : 192.168.13.13 >> mask : 255.255.255.0 >> all other : blank >> _ >> auto launch script : _ >> start "*Name* - CoLinux" /D"C:\Program Files\coLinux" /min >> colinux-daemon.exe -c colinux.xml -d >> >> I'm using the 192.168.13.13 to access the CoLinux box from the window >> host >> and the window host (IP) to access the CoLinux from outside (by ports >> forwarded). > > > eth1 (TAP) should set as "static" for sample 192.168.13.111 > DHCP would timeout and use some older configs. > In your experiments, I think it was set one time before, and DHCP use > configs from older boots now. But it would not work on fresh image. > > Some times the dhcp-client on SLiRP have problems, missing one of the > entries, mostly the DNS. If works all times for you, please say us > your name and version of dhcp-client (pump or so?). > > If dhcp-client don't work correct, set the static addresses for eth0 > (SLiRP). eth0 = 10.0.2.15/255.255.255.0, default route 10.0.2.2, and > the DNS in /etc/resolve the nameserver 10.0.2.3. Search 'Network' in > the wiki. > > Use 192.168.13.111 for access from windows the linux. This is faster, > as SLiRP and works without port forwardings. > > For access from linux to windows use 192.168.13.13 (windows side of TAP). > > "tcp:23:22" --> 23 (ssh) on windows forward as 22 (telnet) to linux? > You should not forward a ssh-port as telnet. Except that you wand > confuse your users, our you are building a honypot ;-) Thanks for your help. I configure the network as you said, and it works perfect. I forward 23 to 22 because if a sshd server is running on the windows, it would not forward the port. So I use that to be sure that I can access the CoLinux box from outside. And the user I will confuse are just me :) (and, of course, we didn't use telnet ...) Many thanks for all your responses. bye -- Damien ... |