Re: ssh naar Linux computer achter "router"
Op 01-03-17 om 20:24 schreef Richard Lucassen: > On Wed, 1 Mar 2017 15:53:38 +0100 > Paul van der Vliswrote: > >>> Aan een VPN had ik nog niet aangedacht. >> >> Ik had het ook genoemd, het is een goede optie! >> >>> Ik denk echter dat het een oplossing is voor een ander probleem. >> >> Nee, het is hier heel bruikbaar voor. Een VPN is tweerichting verkeer. > > Het leuke van de VPN oplossing is dat-ie, i.t.t. een ssh-only oplossing, > altijd de tunnel probeert op te bouwen, Dat ligt er maar aan. Je kunt de VPN ook handmatig doen, bijvoorbeeld via de openvpn-plugin van networkmanager. Maar een VPN die het altijd doet is qua functionaliteit vergelijkbaar met een port forwarding in de router. Erg handig. > je hoeft dus alleen maar te > ssh-en naar het endpoint van de tunnel. En de keepalive houdt de > connection state table van de router wakker. Zelf met dynamische > adressen blijft het werken. En als de server een dyn adres heeft kun je > OpenVPN client nog expliciet vertellen dat ie een nieuwe lookup moet > doen bij een herstart (maar zeker ben ik daar niet van, heb het dacht > ik ooit ergens gelezen) Dat weet ik ook niet. Groeten, Paul -- Paul van der Vlis Linux systeembeheer Groningen https://www.vandervlis.nl/
Re: ssh naar Linux computer achter "router"
On Wed, 1 Mar 2017 15:53:38 +0100 Paul van der Vliswrote: > > Aan een VPN had ik nog niet aangedacht. > > Ik had het ook genoemd, het is een goede optie! > > > Ik denk echter dat het een oplossing is voor een ander probleem. > > Nee, het is hier heel bruikbaar voor. Een VPN is tweerichting verkeer. Het leuke van de VPN oplossing is dat-ie, i.t.t. een ssh-only oplossing, altijd de tunnel probeert op te bouwen, je hoeft dus alleen maar te ssh-en naar het endpoint van de tunnel. En de keepalive houdt de connection state table van de router wakker. Zelf met dynamische adressen blijft het werken. En als de server een dyn adres heeft kun je OpenVPN client nog expliciet vertellen dat ie een nieuwe lookup moet doen bij een herstart (maar zeker ben ik daar niet van, heb het dacht ik ooit ergens gelezen) R. -- richard lucassen http://contact.xaq.nl/
Re: ssh naar Linux computer achter "router"
Op 28-02-17 om 22:00 schreef Geert Stappers: > On Mon, Feb 27, 2017 at 11:53:39PM +0100, Richard Lucassen wrote: >> On Sat, 25 Feb 2017 17:00:12 +0100 >> Geert Stapperswrote: >> } Het idee is om Alice een SSH verbinding naar Mike te laten maken. >> } Bob gaat zelf ook naar Mike om vervolgens via de SSH verbinding >> } van Alice naar haar computer te gaan. >>> >>> B --- M === A >>> >>> Wat bestaat er aan Debian packages voor zulke situaties? >> >> Zet bij jou een OpenVPN server neer en laat de client er naartoe >> connecten. Dan heb je een volledige verbinding, alsof die remote comp >> in jouw netwerk staat. En als je een dynamisch ip hebt kun je de server >> op "float" zetten, dan volgt-ie de client zonder problemen. > > Aan een VPN had ik nog niet aangedacht. Ik had het ook genoemd, het is een goede optie! > Ik denk echter dat het een oplossing is voor een ander probleem. Nee, het is hier heel bruikbaar voor. Een VPN is tweerichting verkeer. Groeten, Paul -- Paul van der Vlis Linux systeembeheer Groningen https://www.vandervlis.nl/
Re: ssh naar Linux computer achter "router"
On Mon, Feb 27, 2017 at 11:53:39PM +0100, Richard Lucassen wrote: > On Sat, 25 Feb 2017 17:00:12 +0100 > Geert Stapperswrote: > } Het idee is om Alice een SSH verbinding naar Mike te laten maken. > } Bob gaat zelf ook naar Mike om vervolgens via de SSH verbinding > } van Alice naar haar computer te gaan. > > > > B --- M === A > > > > Wat bestaat er aan Debian packages voor zulke situaties? > > Zet bij jou een OpenVPN server neer en laat de client er naartoe > connecten. Dan heb je een volledige verbinding, alsof die remote comp > in jouw netwerk staat. En als je een dynamisch ip hebt kun je de server > op "float" zetten, dan volgt-ie de client zonder problemen. Aan een VPN had ik nog niet aangedacht. Ik denk echter dat het een oplossing is voor een ander probleem. Groeten Geert Stappers -- Leven en laten leven
Re: ssh naar Linux computer achter "router"
On Sat, 25 Feb 2017 17:00:12 +0100 Geert Stapperswrote: > B --- M === A > > Wat bestaat er aan Debian packages voor zulke situaties? Zet bij jou een OpenVPN server neer en laat de client er naartoe connecten. Dan heb je een volledige verbinding, alsof die remote comp in jouw netwerk staat. En als je een dynamisch ip hebt kun je de server op "float" zetten, dan volgt-ie de client zonder problemen. -- richard lucassen http://contact.xaq.nl/
Re: ssh naar Linux computer achter "router"
Op 25-02-17 om 18:42 schreef Geert Stappers: > On Sat, Feb 25, 2017 at 05:50:54PM +0100, Paul van der Vlis wrote: >> Verder het bijbehorende simpele paswoord wat ik regelmatig wijzig, maar >> een key is wellicht beter. > > "user management" op Mike is inderdaad iets om in te plannen. > Als in "van te voren over nadenken" Ondanks dat je /usr/sbin/nologin kunt gebruiken als shell, schijnt het toch gevaarlijk te zijn dat mensen kunnen connecten naar je VPS. Via een SOCKS proxy schijnen onaardige mensen je computer te kunnen misbruiken, zo is mij verteld. Mochten er hier mensen zijn die weten hoe je dat diabled en veilig krijgt, dan zou ik dat prettig vinden. Dan hoef ik niet steeds het paswoord te wijzigen of zou ik een generieke key kunnen gebruiken... Groeten, Paul -- Paul van der Vlis Linux systeembeheer Groningen https://www.vandervlis.nl/
Re: ssh naar Linux computer achter "router"
Op 25-02-17 om 18:11 schreef Geert Stappers: > Misschien is mijn probleem ook wel: Welk package maakt het makkelijk om > aan de Alice kant de juiste zaken klaar te zetten voor reverse SSH? Naar zoiets ben ik al lang op zoek, het is er volgens mij nog niet. Maar, ik zou het best willen maken. Ik denk dan aan een bash-script, een item in het start-menu en een simpele gui via iets als Zenity. Het lijkt me dat ik dat wel kan. Mijn package-kennis is wel te mager, maar toevallig was ik er net mee bezig dat te verbeteren ;-) Groeten, Paul -- Paul van der Vlis Linux systeembeheer Groningen https://www.vandervlis.nl/
Re: ssh naar Linux computer achter "router"
On Sat, Feb 25, 2017 at 05:50:54PM +0100, Paul van der Vlis wrote: > Op 25-02-17 om 17:00 schreef Geert Stappers: > > > > Het idee is om Alice een SSH verbinding naar Mike te laten maken. > > Bob gaat zelf ook naar Mike om vervolgens via de SSH verbinding > > van Alice naar haar computer te gaan. > > > > > > B --- M === A > > > > > > Wat bestaat er aan Debian packages voor zulke situaties? > > Ik geef Alice een commando zoals dit: > ssh -NfR 12888:localhost:22 wel...@xen7.vandervlis.nl > Dat staat bij mij op een webpagina, zodat ze copy/paste kan doen. > Het kan als gewone user. Mmm, met een webpagina plus knip en plak, ook een goed idee. > Verder het bijbehorende simpele paswoord wat ik regelmatig wijzig, maar > een key is wellicht beter. "user management" op Mike is inderdaad iets om in te plannen. Als in "van te voren over nadenken" > Op mijn server doe ik dan iets als: > ssh localhost -o "StrictHostKeyChecking no" -p 12888 > > Daarna log ik in als gewone gebruiker en wordt daarna root. Inloggen als > root is immers default geblokkeerd. Ja, Bob moet ook een account aan de Alice kant hebben/weten. En makkelijk root kunnen worden is wel zo fijn. > Dat "StrictHostKeyChecking no" lijkt niet te werken, ik weet niet > waarom. Moet ik nog eens uitzoeken. Ik moet dus steeds iets weghalen uit > mijn known_hosts. Wie weet waarom het niet werkt mag het zeggen. Ik weet het niet. Misschien omdat "localhost" iets specials is? > De user "welkom" kan als shell "/usr/sbin/nologin" hebben. Zinvolle tip, dank je wel. > Bij een klant is dit een icoontje op het desktop van de gebruikers met > een bijbehorende key waarmee wordt ingelogd. Heel gebruiksvriendelijk. > > Er is daar ook een icoontje waarmee je de user grafisch kunt overnemen, > en dat alles werkt via een Mike-server, dus er is geen poortforwarding > nodig bij Alice. Ik heb dit niet zelf ingericht, het werkt met Vino: > https://packages.debian.org/vino Vino, VNC server for GNOME, komt pas na de reverse SSH verbinding, zo ver ben ik dus nog niet. Zo ver zijn Alice en Bob nog niet ;-) Groeten Geert Stappers -- Leven en laten leven
Re: ssh naar Linux computer achter "router"
Hoi, En hier dan het plaatje B --- M === A Wat bestaat er aan Debian packages voor zulke situaties? Dat zou je toch kunnen oplossen met reverse ssh? Lees bv: https://www.howtoforge.com/reverse-ssh-tunneling MJ
ssh naar Linux computer achter "router"
Hoi, Eerst een verhaal om een plaatje te kunnen schetsen. Vijftig kilometer verderop staat een "huis-tuin-en-keuken-computer". Ter plekke is een Internet aansluiting m.b.v. een consumentenrouter. Je weet wel, van die "routers" die modem zijn en NAT doen. Laten die plaats/computer "Alice" noemen. Elders heb ik een VPS waar gelukkig geen Network Adres Translation gebeurd. Die computer noemen we "Mike" met de M van 'Man in the Middle'. Zelf zit ik op een derde plek in het mooie grote Internet. En laat me voor het verder verhaal "Bob" noemen. Als Bob kom ik niet zonder bij de computer van Alice. Het idee is om Alice een SSH verbinding naar Mike te laten maken. Bob gaat zelf ook naar Mike om vervolgens via de SSH verbinding van Alice naar haar computer te gaan. En hier dan het plaatje B --- M === A Wat bestaat er aan Debian packages voor zulke situaties? Groeten Geert Stappers -- Leven en laten leven
Re: Linux on a Router
ArcticFox wrote: On Jul 10, 2007, at 11:32 PM, Douglas Allan Tutty wrote: On Tue, Jul 10, 2007 at 11:20:09PM -0500, ArcticFox wrote: The problem with DD-WRT is that as far as I can tell it only works on WRT-routers, I don't have one of those I can mess with. As far as I can tell, there isn't a Linux dest that will run on the router I do have. That's not quite right, it runs on quite a wide variety of kit, including i386, some atheros stuff and most of the broadcom chips. What about using an old computer? If you need wireless then it has to have the bus to take a wireless NIC but if its wired then almost any computer will do. What is it you need your router to do? Allow 3 computers access to the internet plus my Vonage device. One of them is a server and there should be a firewall to stop/deter hackers. Wireless would be a plus, but not strictly necessary. I do have an old PC that could be used, would I need two NIC to do this? Or could I just use one? That depends on your network terminating device, if it's a USB, PCI, IR, serial, parallel or magic modem then no, if it's some sort of ethernet modem then yes, [0] but 100Mbps ethernet cards are so cheap now just buy another one, as long as you're internet connection doesn't exceed this speed, if it does I'm moving in and I'll bring a spare Gigabit network card with me. [0] unless you start playing around with switches that support vlans -- Garrr, do your bit for global warming, become a pirate, you can borrow my copy of Windows 95 if you want. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Linux on a Router
On Wed, Jul 11, 2007 at 02:00:11PM +1000, Alex Samad wrote: On Tue, Jul 10, 2007 at 09:18:43PM -0600, Nate Duehr wrote: OpenWRT being the more open of the options, is a good place to start, but might be a bit more manual than you want to set things up. I have been using openWRT for over 2 years and I have had not problems, my setup includes 2 uplinks and load balancing between the 2. They have 2 version 2.4 stream which they have come to end on and 2.6 there new release. Check out their wiki, it will have a table of hardware that work. I have been using OpenWRT also, and I think it's great. The package management system is very flexible, and the software is *very* stable. I tried the other Linux-on-router distros and none seemed to be as polished, robust and flexible as OpenWRT. Please check the webif^2 web interface also (http://www.x-wrt.org/). J. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Linux on a Router
On Tue, Jul 10, 2007 at 11:41:45PM -0500, ArcticFox wrote: On Jul 10, 2007, at 11:32 PM, Douglas Allan Tutty wrote: What about using an old computer? If you need wireless then it has to have the bus to take a wireless NIC but if its wired then almost any computer will do. What is it you need your router to do? Allow 3 computers access to the internet plus my Vonage device. One of them is a server and there should be a firewall to stop/deter hackers. Wireless would be a plus, but not strictly necessary. I do have an old PC that could be used, would I need two NIC to do this? Or could I just use one? You then need one computer to be your router/firewall. Assuming that your internet is in the form of a high-speed modem that presents you with an ethernet connection, you would need one NIC for that. If, like me, you use dialup, then just a modem or serial port and external modem. This then takes care of the internet side. For your inside network, if you want wireless then you need a wireless NIC and for ethernet you need an ethernet NIC. There may be cards that have both on one card but to Linux they will look like two ethernet connections. It may look like this: eth0NIC to internet modem. assume modem is 192.168.1.1, this NIC 192.168.1.2 eth1internal wireless: 192.168.2.1 eth2internal ethernet, connected to a simple ethernet switch to connect other computers and vonage. 192.168.3.1 Remember that you have three separate networks. Your required computer speed will depend on the speed of the networks. My 486's ISA bus gets saturated by one NIC. The kernel has to handle all the packets going between the ports. Put a base install (no tasks selected during install). Add iptables and shorewall, lynx, mc, your text-mode editor of choice [or just use mcedit], ssh server, a MTA that will send all mail to an inside box unless this will be your mail gateway [separate project], rsync too. Come up with one /etc/hosts file that lists all your boxes and put it on all boxes (I use rsync or the shell-link in mc for this, both use ssh). Install shorewall-doc on any of your workstations so that you can read on how to setup shorewall to do your routing. If all is well, you should be able to ping any box by name from any box. You should be able to ssh into any box from your internal boxes, by name. The two things in this setup that I don't know anything about is using wireless and dhcp (for the high-speed modem). Other than those two points, this really is trivial to setup; the most time consuming is reading the shorewall documentation. You should also read the harden-doc. The most important is to ensure that the firewall isn't listening on the outside interface to anything that you don't need. Unless you want to ssh in from the internet, you shouldn't need any services listening on the outside interface. Anything that _can't_ be so set will be caught by shorewall. A nice touch to add would be ntp on all boxes with the firewall syncing with a timeserver and your internal boxes syncing with the firewall. Good luck, Doug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Linux on a Router
On 07/10/2007 11:06 PM, ArcticFox wrote: I've been having a heck of a time trying to keep my internet connection active. It likes to drop on me for no apparent reason. I've managed to narrow the problem down to the router, but Linksys wants to charge me ~$30 to troubleshoot the router. Someone I know suggested that I try Linux on the router and I was wondering if anyone out there knows/has experience/suggestions for doing something like this. The router is a Linksys BEFW11S4 v.4 The only client system I have is MacOS X 10.3.9 Check here: http://www.dslreports.com/forum/linksys Regards, Ralph -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Linux on a Router
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Bob escreveu: ArcticFox wrote: On Jul 10, 2007, at 11:32 PM, Douglas Allan Tutty wrote: On Tue, Jul 10, 2007 at 11:20:09PM -0500, ArcticFox wrote: The problem with DD-WRT is that as far as I can tell it only works on WRT-routers, I don't have one of those I can mess with. As far as I can tell, there isn't a Linux dest that will run on the router I do have. That's not quite right, it runs on quite a wide variety of kit, including i386, some atheros stuff and most of the broadcom chips. Does anyone know if any of these Linux firmwares could be flashed into a 3COM OfficeConnect ADSL Modem/Router? Cheers, Cassiano Leal -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGlSBzq4Bz51JiUuERAjG9AJ9thbjURjV6h484onRdvtzOOgWToACgpKRF b3yJcs/Y1jRImTIwqrXgXao= =48y7 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Linux on a Router
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Cassiano Bertol Leal escreveu: Bob escreveu: ArcticFox wrote: On Jul 10, 2007, at 11:32 PM, Douglas Allan Tutty wrote: On Tue, Jul 10, 2007 at 11:20:09PM -0500, ArcticFox wrote: The problem with DD-WRT is that as far as I can tell it only works on WRT-routers, I don't have one of those I can mess with. As far as I can tell, there isn't a Linux dest that will run on the router I do have. That's not quite right, it runs on quite a wide variety of kit, including i386, some atheros stuff and most of the broadcom chips. Does anyone know if any of these Linux firmwares could be flashed into a 3COM OfficeConnect ADSL Modem/Router? Cheers, Cassiano Leal Connection the provider is PPPoA our PPPoE? -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGlS0QbjyCr4Ixg0wRApKoAJ4+qJozgo6jJqfUhJkJTXBqQlrIPACeO/B2 TW9wiFAUkbo9RKm22/o82LY= =pZ1F -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Linux on a Router
I've been having a heck of a time trying to keep my internet connection active. It likes to drop on me for no apparent reason. I've managed to narrow the problem down to the router, but Linksys wants to charge me ~$30 to troubleshoot the router. Someone I know suggested that I try Linux on the router and I was wondering if anyone out there knows/has experience/suggestions for doing something like this. The router is a Linksys BEFW11S4 v.4 The only client system I have is MacOS X 10.3.9 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Linux on a Router
On Tue, Jul 10, 2007 at 10:06:53PM -0500, ArcticFox wrote: I've been having a heck of a time trying to keep my internet connection active. It likes to drop on me for no apparent reason. I've managed to narrow the problem down to the router, but Linksys wants to charge me ~$30 to troubleshoot the router. Someone I know suggested that I try Linux on the router and I was wondering if anyone out there knows/has experience/suggestions for doing something like this. The router is a Linksys BEFW11S4 v.4 The only client system I have is MacOS X 10.3.9 I think that OpenWRT can be made to load on many (most?) Linksys routers. I would start there. However, I've not personally used it, so I am not positive about whether it is the right thing for you. Regards, -Roberto -- Roberto C. Sánchez http://people.connexer.com/~roberto http://www.connexer.com signature.asc Description: Digital signature
Re: Linux on a Router
On Jul 10, 2007, at 10:09 PM, Roberto C. Sánchez wrote: On Tue, Jul 10, 2007 at 10:06:53PM -0500, ArcticFox wrote: I've been having a heck of a time trying to keep my internet connection active. It likes to drop on me for no apparent reason. I've managed to narrow the problem down to the router, but Linksys wants to charge me ~$30 to troubleshoot the router. Someone I know suggested that I try Linux on the router and I was wondering if anyone out there knows/has experience/suggestions for doing something like this. The router is a Linksys BEFW11S4 v.4 The only client system I have is MacOS X 10.3.9 I think that OpenWRT can be made to load on many (most?) Linksys routers. I would start there. However, I've not personally used it, so I am not positive about whether it is the right thing for you. Regards, -Roberto You gave me somewhere to start though, and for that I thank you.
Re: Linux on a Router
On Jul 10, 2007, at 9:10 PM, ArcticFox wrote: On Jul 10, 2007, at 10:09 PM, Roberto C. Sánchez wrote: On Tue, Jul 10, 2007 at 10:06:53PM -0500, ArcticFox wrote: I've been having a heck of a time trying to keep my internet connection active. It likes to drop on me for no apparent reason. I've managed to narrow the problem down to the router, but Linksys wants to charge me ~$30 to troubleshoot the router. Someone I know suggested that I try Linux on the router and I was wondering if anyone out there knows/ has experience/suggestions for doing something like this. The router is a Linksys BEFW11S4 v.4 The only client system I have is MacOS X 10.3.9 I think that OpenWRT can be made to load on many (most?) Linksys routers. I would start there. However, I've not personally used it, so I am not positive about whether it is the right thing for you. Regards, -Roberto You gave me somewhere to start though, and for that I thank you. OpenWRT being the more open of the options, is a good place to start, but might be a bit more manual than you want to set things up. I personally like DD-WRT, which has a bit more effort put into it from the standpoint of the web interface, etc... But they're both good options. -- Nate Duehr [EMAIL PROTECTED]
Re: Linux on a Router
On Tue, Jul 10, 2007 at 09:18:43PM -0600, Nate Duehr wrote: On Jul 10, 2007, at 9:10 PM, ArcticFox wrote: On Jul 10, 2007, at 10:09 PM, Roberto C. Sánchez wrote: On Tue, Jul 10, 2007 at 10:06:53PM -0500, ArcticFox wrote: I've been having a heck of a time trying to keep my internet connection active. It likes to drop on me for no apparent reason. I've managed to narrow the problem down to the router, but Linksys wants to charge me ~$30 to troubleshoot the router. Someone I know suggested that I try Linux on the router and I was wondering if anyone out there knows/ has experience/suggestions for doing something like this. The router is a Linksys BEFW11S4 v.4 The only client system I have is MacOS X 10.3.9 I think that OpenWRT can be made to load on many (most?) Linksys routers. I would start there. However, I've not personally used it, so I am not positive about whether it is the right thing for you. Regards, -Roberto You gave me somewhere to start though, and for that I thank you. OpenWRT being the more open of the options, is a good place to start, but might be a bit more manual than you want to set things up. I have been using openWRT for over 2 years and I have had not problems, my setup includes 2 uplinks and load balancing between the 2. They have 2 version 2.4 stream which they have come to end on and 2.6 there new release. Check out their wiki, it will have a table of hardware that work. I personally like DD-WRT, which has a bit more effort put into it from the standpoint of the web interface, etc... But they're both good options. -- Nate Duehr [EMAIL PROTECTED] signature.asc Description: Digital signature
Re: Linux on a Router
On Jul 10, 2007, at 11:00 PM, Alex Samad wrote: On Tue, Jul 10, 2007 at 09:18:43PM -0600, Nate Duehr wrote: On Jul 10, 2007, at 9:10 PM, ArcticFox wrote: On Jul 10, 2007, at 10:09 PM, Roberto C. Sánchez wrote: On Tue, Jul 10, 2007 at 10:06:53PM -0500, ArcticFox wrote: I've been having a heck of a time trying to keep my internet connection active. It likes to drop on me for no apparent reason. I've managed to narrow the problem down to the router, but Linksys wants to charge me ~$30 to troubleshoot the router. Someone I know suggested that I try Linux on the router and I was wondering if anyone out there knows/ has experience/suggestions for doing something like this. The router is a Linksys BEFW11S4 v.4 The only client system I have is MacOS X 10.3.9 I think that OpenWRT can be made to load on many (most?) Linksys routers. I would start there. However, I've not personally used it, so I am not positive about whether it is the right thing for you. Regards, -Roberto You gave me somewhere to start though, and for that I thank you. OpenWRT being the more open of the options, is a good place to start, but might be a bit more manual than you want to set things up. I have been using openWRT for over 2 years and I have had not problems, my setup includes 2 uplinks and load balancing between the 2. They have 2 version 2.4 stream which they have come to end on and 2.6 there new release. Check out their wiki, it will have a table of hardware that work. I personally like DD-WRT, which has a bit more effort put into it from the standpoint of the web interface, etc... But they're both good options. The problem with DD-WRT is that as far as I can tell it only works on WRT-routers, I don't have one of those I can mess with. As far as I can tell, there isn't a Linux dest that will run on the router I do have.
Re: Linux on a Router
On Tue, Jul 10, 2007 at 11:20:09PM -0500, ArcticFox wrote: The problem with DD-WRT is that as far as I can tell it only works on WRT-routers, I don't have one of those I can mess with. As far as I can tell, there isn't a Linux dest that will run on the router I do have. What about using an old computer? If you need wireless then it has to have the bus to take a wireless NIC but if its wired then almost any computer will do. What is it you need your router to do? Doug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Linux on a Router
On Jul 10, 2007, at 11:32 PM, Douglas Allan Tutty wrote: On Tue, Jul 10, 2007 at 11:20:09PM -0500, ArcticFox wrote: The problem with DD-WRT is that as far as I can tell it only works on WRT-routers, I don't have one of those I can mess with. As far as I can tell, there isn't a Linux dest that will run on the router I do have. What about using an old computer? If you need wireless then it has to have the bus to take a wireless NIC but if its wired then almost any computer will do. What is it you need your router to do? Doug. Allow 3 computers access to the internet plus my Vonage device. One of them is a server and there should be a firewall to stop/deter hackers. Wireless would be a plus, but not strictly necessary. I do have an old PC that could be used, would I need two NIC to do this? Or could I just use one? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Failing to use Linux PC as router
On Sun, Nov 12, I asked for help connecting my new AMD 64 to the Internet. The help I got. The postings I received were printed and then deleted. so please excuse that i do neither top quote nor post quote. Douglas Tutty suggested to use ipmasq or shorewall for the basic firewall and dnsmasq for resolv.conf of computer OLD and not to try to do too much in /etc/network/interfaces. He was right, of course. Ipmasq produced a battery of filtering rules, including the NAT rules and forwarding rules I needed, and all those rules look quite plausible. Forwarding is on in sysctl of both compu- ters. I simply was not sure if this would be the case after a reboot, too. My attempts to formulate iptable rules were weird indeed, as Jochen Schulz quite correctly wrote. Russel L. Harris suggested SmoothWall and thought I should recon- figure or reinstall Debian on the AMD 64. Well, I was not quite content with the partitioning on my first install. So I reinstal- led and even dared to reduce the XP Partition I hardly ever shall use from about 150 to about 40 GB - well, and this time the net install made me select a Debian mirror and loaded file after file an Etch system including Xorg and Openoffice and Firefox etc. etc. instead of the minimal system before. Well, there is Gnome which I shall have a hard time to get rid of next week or so, and the net connection is a hotplug one which I still must find out how to launch. But the weeks of running in circles through matters I prac- tically nothing knew of have passed, and now I can move along on familiar grounds. Thank you, all of you. I liked to read that Hugo Vanwoerkom can't tell whether his third computer is losing flexibility and efficiency. The Debian user community will be glad if he goes on posting interesting things for long years. As far as I am concerned, I think I remember that I, too, did not feel such a loss when I was as a young man that much below seventy. But my memory is not too strong, you know - wasn't that in a millenium long gone? Yours Hans -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Failing to use Linux PC as router
Hans Vogelsberger wrote: Some weeks ago I bought an AMD64 X2 which now I must connect to the internet, using my old Pentium 4 as router to the dynamic address I receive from my cable provider whenever I boot. Having used Testing since it came up in Potato times, I never needed and never acquired networking knowledge. Debian did all that for me, After three weeks of studying books, manuals and HOWTOS and try- ing to configure the two computers, I am constantly running in circles. I can ping from one computer to the other and from the old computer to the internet, and I can do everything I did be- fore with my old computer, but there is no connection at all between the new one and the internet. This I need urgently be- cause the AMD 64 has only a daily build netinst Etch I downloa- ded and burned to disk on October 17th. It is terribly castra- ted (even using 'more' instead of 'less'), but there is no way out of the networking circles without apt-get or aptitude which seem to be unreachable. My third computer, the one within the skull, seems to be rapidly loosing flexibility and efficiency after an uptime of more than 75 years. My third computer's version is 7 years younger, but I can't tell whether it's losing flexibility + efficiency or interested in different things... Hugo snip -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Failing to use Linux PC as router
Some weeks ago I bought an AMD64 X2 which now I must connect to the internet, using my old Pentium 4 as router to the dynamic address I receive from my cable provider whenever I boot. Having used Testing since it came up in Potato times, I never needed and never acquired networking knowledge. Debian did all that for me, After three weeks of studying books, manuals and HOWTOS and try- ing to configure the two computers, I am constantly running in circles. I can ping from one computer to the other and from the old computer to the internet, and I can do everything I did be- fore with my old computer, but there is no connection at all between the new one and the internet. This I need urgently be- cause the AMD 64 has only a daily build netinst Etch I downloa- ded and burned to disk on October 17th. It is terribly castra- ted (even using 'more' instead of 'less'), but there is no way out of the networking circles without apt-get or aptitude which seem to be unreachable. My third computer, the one within the skull, seems to be rapidly loosing flexibility and efficiency after an uptime of more than 75 years. I have tried to sum up the important data using the names in the following paragraph. Real names are different, of course. All this is a bit lengthy, but since I avoid opening attach- ments wherever I can i think it is better to leave it in the body of the posting.. OLD - old computer, Intel Pentium 4 2.40 GHz, Debian Testing, Kernel 2.6.17-2-686 (Debian 2.6. 17-9); INTERFACES eth0 and eth1 NEW - new computer, AMD Athlon 64 X2 Dual Core 4200+. Debian Testing, Kernel 2.6.17-2-amd64 (Debian 2. 6.17-9); ETCH NETINST daily build 17.10.06; INTERFACES eth0 (?Firewire? - weird MAC-address) and eth1 WHICH I CHANGED TO oth0 and oth1 in /etc/udev/rules.d/z25_persistent-net.rules(and eth* to oth* in /etc/udev/rules.d/z45_persistent -net-generator.rules) to avoid ambivalent names when trying to configure bridge br0 ISP - my cable provider e0:0e:e0:0e:e0:0e MAC-address of eth1 interface in OLD xxx.xx.xxx. the first three dotted decimals of the address received from my provider (officially dynamic, but since years never changing) /etc/hosts OLD: 127.0.0.1 localhost 192.168.1.1 OLD.local OLD 192.168.1.2 OLD.ISP.at ISP 192.168.1.3 NEW.local NEW NEW: 127.0.0.1 localhost 192.168.1.3 NEW.local NEW 192.168.1.1 OLD.local OLD AND IN THE FILES /etc/hosts OF BOTH COMPUTERS another 6 IPv6 capable hosts which up to now are neither used nor commented out /etc/hosts.allow: /etc/hosts.deny: OLD ALL: OLD NEWOLD:ALL: ALL NEW ALL: NEW OLDNEW:ALL: ALL /etc/networks OLD: localnet 192.168.1.0 NEW: localnet 192.168.1.0 /etc/network/interfaces OLD: # The loopback interface auto lo iface lo inet loopback # The first network card up sysctl -w net.ipv4.ip_forward=1 auto eth0 iface eth0 inet dhcp address 192.168.1.2 netmask 255.255.255.0 inet_route add default gw 192.168.1.0/24 up iptables -t nat -A POSTROUTING -s 192.168.1.0/24 -o eth0\ -j MASQUERADE #*# Shouldn't these two lines be enough to guarantee dhcp access for BOTH computers ??? #*# # The second network card auto eth1 iface eth1 inet static address 192.168.1.1 netmask 255.255.255.0 up iptables -A FORWARD -s 192.168.1.3 -d 192.168.1.2 up iptables -A FORWARD -s 192.168.1.2 -d 192.168.1.3 #*# Two lines added because route and MASQUERADE of eth0 seemed useless, but didn't help either #*# #*# TRIED after setting eth0 to inet static, but TOTALLY COMMENTED OUT after resetting eth0 to dhcp because the br0 did not find oth0: #*# # auto br0 # iface br0 inet dhcp # inet_route add default gw 192.168.1.0/24 # bridge_ports eth0 eth1 oth1 # bridge_hw e0:0e:e0:0e:e0:0e NEW: # The loopback interface auto lo iface lo inet loopback # The second network card up sysctl -w net.ipv4.ip_forward=1
Re: Failing to use Linux PC as router
* Hans Vogelsberger [EMAIL PROTECTED] [061112 14:52]: Some weeks ago I bought an AMD64 X2 which now I must connect to the internet, using my old Pentium 4 as router to the dynamic address I receive from my cable provider whenever I boot. Having used Testing since it came up in Potato times, I never needed and never acquired networking knowledge. Debian did all that for me, After three weeks of studying books, manuals and HOWTOS and try- ing to configure the two computers, I am constantly running in circles. I can ping from one computer to the other and from the old computer to the internet, and I can do everything I did be- fore with my old computer, but there is no connection at all between the new one and the internet. This I need urgently be- cause the AMD 64 has only a daily build netinst Etch I downloa- ded and burned to disk on October 17th. It is terribly castra- ted (even using 'more' instead of 'less'), but there is no way out of the networking circles without apt-get or aptitude which seem to be unreachable. My third computer, the one within the skull, seems to be rapidly loosing flexibility and efficiency after an uptime of more than 75 years. Hans, Download a ISO of SmoothWall Express 2.0 from www.smoothwall.org, burn it to CD, and install it on your old machine. This takes less than an hour, and can be done easily even by a novice. SmoothWall Express 2.0 is mature and trouble-free. This will leave you with a reliable firewall/router/DHCP server for your local area network (LAN). No manuals and no detailed configuration are required. Then reconfigure (if necessary, reinstall) Debian on the AMD64, and take your choice of DHCP or a static IP address within your LAN. As you know, network configuration in Debian is trivial. But properly configuring a firewall/router has many pitfalls. RLH -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Failing to use Linux PC as router
Hans Vogelsberger: Some weeks ago I bought an AMD64 X2 which now I must connect to the internet, using my old Pentium 4 as router to the dynamic address I receive from my cable provider whenever I boot. Having used Testing since it came up in Potato times, I never needed and never acquired networking knowledge. Debian did all that for me, :) OLD: # The loopback interface auto lo iface lo inet loopback # The first network card up sysctl -w net.ipv4.ip_forward=1 This looks suspicious to me. Which entry does that line belong to? Have you tried running it manually? You may try putting it into /etc/sysctl.conf (but I am not sure whether sarge already reads this file). auto eth0 iface eth0 inet dhcp address 192.168.1.2 netmask 255.255.255.0 inet_route add default gw 192.168.1.0/24 up iptables -t nat -A POSTROUTING -s 192.168.1.0/24 -o eth0\ -j MASQUERADE #*# Shouldn't these two lines be enough to guarantee dhcp access for BOTH computers ??? #*# This looks weird. If eth0 is card connected to the internet (or modem) you don't need to set any addresses or routes by hand. Additionally, I would put that iptables line in another script and put it in /etc/network/if-pre-up.d/. J. -- I want to look younger than my friends so I will fight ageing as long as I can. [Agree] [Disagree] http://www.slowlydownward.com/NODATA/data_enter2.html signature.asc Description: Digital signature
Re: Failing to use Linux PC as router
On Sun, Nov 12, 2006 at 09:48:03PM +0100, Hans Vogelsberger wrote: After three weeks of studying books, manuals and HOWTOS and try- ing to configure the two computers, I am constantly running in circles. I can ping from one computer to the other and from the old computer to the internet, and I can do everything I did be- fore with my old computer, but there is no connection at all between the new one and the internet. This I need urgently be- cause the AMD 64 has only a daily build netinst Etch I downloa- ded and burned to disk on October 17th. It is terribly castra- ted (even using 'more' instead of 'less'), but there is no way out of the networking circles without apt-get or aptitude which seem to be unreachable. My third computer, the one within the skull, seems to be rapidly loosing flexibility and efficiency after an uptime of more than 75 years. /etc/network/interfaces OLD: # The loopback interface auto lo iface lo inet loopback # The first network card up sysctl -w net.ipv4.ip_forward=1 auto eth0 iface eth0 inet dhcp address 192.168.1.2 netmask 255.255.255.0 inet_route add default gw 192.168.1.0/24 up iptables -t nat -A POSTROUTING -s 192.168.1.0/24 -o eth0\ -j MASQUERADE #*# Shouldn't these two lines be enough to guarantee dhcp access for BOTH computers ??? #*# # The second network card auto eth1 iface eth1 inet static address 192.168.1.1 netmask 255.255.255.0 up iptables -A FORWARD -s 192.168.1.3 -d 192.168.1.2 up iptables -A FORWARD -s 192.168.1.2 -d 192.168.1.3 #*# Two lines added because route and MASQUERADE of eth0 seemed useless, but didn't help either #*# #*# TRIED after setting eth0 to inet static, but TOTALLY COMMENTED OUT after resetting eth0 to dhcp because the br0 did not find oth0: #*# NEW: # The loopback interface auto lo iface lo inet loopback # The second network card up sysctl -w net.ipv4.ip_forward=1 auto oth1 iface oth1 inet static address 192.168.1.3 netmask 255.255.255.0 I am unfamiliar with trying to set up a firewall from within /etc/network/interfaces, although I see that the debian-reference does this. I have a similar setup where my 486 has the modem (although ppp). I think that the dhcp from your ISP should set the gateway; you don't need to. If running sarge, ipforward is set in /etc/network/options, and if Etch is in /etc/sysctl.conf For a basic firewall, at least until things work and you want to tweak, I use ipmasq. Out of the box it sets up a basic forwarding firewall. Later, if you want more control, use shorewall. What nameserver setup are you using for the new computer? I use dnsmasq on the 486 and point my new computer's resolv.conf at the 486. To summarize; you may be trying to do too much in /etc/network/interfaces when Debian has default ways of doing this differently. Doug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Probleme, Linux zum DSL Router umzuwandeln
Hi! Ich habe einen Linux Rechner mit einer statischen IP-Adresse von meinen ISP gekriegt die in meinem rechner folgende eintragungen hat: # The primary network interface iface eth0 inet static address 81.10.53.22 netmask 255.255.255.252 network 81.10.53.20 broadcast 81.10.53.23 gateway 81.10.53.21 # dns-* options are implemented by the resolvconf package, if installed dns-nameservers 163.121.128.134 212.103.160.18 und will aber das ein zweiter rechner über mein Linux Rechner ins Netz springt. Also, habe ich ein eth0:0 Alias erstellt, IP-Forwarding aktiviert und mit route den Befehl gegeben, die alle Packete ins Netz zu routen.. ifconig eth0:0 192.168.215.2 sudo route add 192.168.215.0 gateway 81.10.53.21 Der Befehl route -n spuckt folgende Konfiguraiton aus: [EMAIL PROTECTED]:~$ route -n Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 192.168.215.0 81.10.53.21 255.255.255.255 UGH 0 00 eth0 81.10.53.20 0.0.0.0 255.255.255.252 U 0 00 eth0 192.168.215.0 0.0.0.0 255.255.255.0 U 0 00 eth0 0.0.0.0 81.10.53.21 0.0.0.0 UG0 00 eth0 und mit ifconfig sieht die Konfiguration so aus: eth0 Link encap:Ethernet HWaddr 00:0C:6E:FF:B0:2A inet addr:81.10.53.22 Bcast:81.10.53.23 Mask:255.255.255.252 inet6 addr: fe80::20c:6eff:feff:b02a/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:9763 errors:0 dropped:0 overruns:0 frame:0 TX packets:9098 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:7758590 (7.3 MiB) TX bytes:1069826 (1.0 MiB) Interrupt:23 Base address:0xa400 eth0:0Link encap:Ethernet HWaddr 00:0C:6E:FF:B0:2A inet addr:192.168.215.1 Bcast:192.168.215.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:23 Base address:0xa400 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:224 errors:0 dropped:0 overruns:0 frame:0 TX packets:224 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:11570 (11.2 KiB) TX bytes:11570 (11.2 KiB) Welche konfiguration habe ich auf den Windows Rechner mit der IP-Addresse 192.168.215.2 vorzunehmen, damit dieser über meinen Linux Rechner ins Netz springen kann?! -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Probleme, Linux zum DSL Router umzuwandeln
On 09.03.06 17:15:02, Tamer Higazi wrote: Ich habe einen Linux Rechner mit einer statischen IP-Adresse von meinen ISP gekriegt die in meinem rechner folgende eintragungen hat: Wo ist da DSL? und will aber das ein zweiter rechner über mein Linux Rechner ins Netz springt. Also, habe ich ein eth0:0 Alias erstellt, IP-Forwarding aktiviert und mit route den Befehl gegeben, die alle Packete ins Netz zu routen.. Damit ich das richtig verstehe: eth0 ist deine Verbindung ins Internet, da haengt ein DSL-Modem oder sonstirgendwas dran richtig? Wie willst du denn an diesselbe Netzwerkkarte noch einen 2. Rechner anschliessen? Wenn deine Linux-Box Router spielen soll brauchst du im Normalfall 2 Netzwerkkarten da drin. Welche konfiguration habe ich auf den Windows Rechner mit der IP-Addresse 192.168.215.2 vorzunehmen, damit dieser über meinen Linux Rechner ins Netz springen kann?! Wie sind denn der Windows-Rechner und die Linux-Kiste verbunden (netzwerkmaessig)? Andreas -- You will be surprised by a loud noise. -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Probleme, Linux zum DSL Router umzuwandeln
Topoplogie: Switch - DSL-Router Switch - Linux Rechner mit eth0: iface eth0 inet static address 81.10.53.22 netmask 255.255.255.252 network 81.10.53.20 broadcast 81.10.53.23 gateway 81.10.53.21 und alias eth0:0: 192.168.215.1 mit route Netz 192.158.215.0 auf gateway 81.10.53.21 und rechner2 sollte mit der IP-Addresse 192.168.215.2 über den Linux Rechner ins Internet geforwarded werden. Wo ist DSL?! In Ägypten! Wenn du anregungen hast, wie ich ohne einer zweiten NIC über ein alias das ganze lösen könnte wäre ich dir dankbar. Tamer Andreas Pakulat wrote: On 09.03.06 17:15:02, Tamer Higazi wrote: Ich habe einen Linux Rechner mit einer statischen IP-Adresse von meinen ISP gekriegt die in meinem rechner folgende eintragungen hat: Wo ist da DSL? und will aber das ein zweiter rechner über mein Linux Rechner ins Netz springt. Also, habe ich ein eth0:0 Alias erstellt, IP-Forwarding aktiviert und mit route den Befehl gegeben, die alle Packete ins Netz zu routen.. Damit ich das richtig verstehe: eth0 ist deine Verbindung ins Internet, da haengt ein DSL-Modem oder sonstirgendwas dran richtig? Wie willst du denn an diesselbe Netzwerkkarte noch einen 2. Rechner anschliessen? Wenn deine Linux-Box Router spielen soll brauchst du im Normalfall 2 Netzwerkkarten da drin. Welche konfiguration habe ich auf den Windows Rechner mit der IP-Addresse 192.168.215.2 vorzunehmen, damit dieser über meinen Linux Rechner ins Netz springen kann?! Wie sind denn der Windows-Rechner und die Linux-Kiste verbunden (netzwerkmaessig)? Andreas -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Probleme, Linux zum DSL Router umzuwandeln
am 09.03.2006, um 17:15:02 +0200 mailte Tamer Higazi folgendes: und will aber das ein zweiter rechner über mein Linux Rechner ins Netz springt. Also, habe ich ein eth0:0 Alias erstellt, IP-Forwarding aktiviert und mit route den Befehl gegeben, die alle Packete ins Netz zu routen.. Das reicht nicht, du brauchst IP_Masquerade. Iptables ist Dein Freund. Du kannst das nachlesen, z.B. in meinem iptables-Vortrag zum LinuxInfoTag 2004 in Dresden. Ansonsten http://netfilter.org, Google, ... Welche konfiguration habe ich auf den Windows Rechner mit der IP-Addresse 192.168.215.2 vorzunehmen, damit dieser über meinen Linux Rechner ins Netz springen kann?! Nix außer Gateway. Andreas -- Andreas Kretschmer(Kontakt: siehe Header) Heynitz: 035242/47215, D1: 0160/7141639 GnuPG-ID 0x3FFF606C http://wwwkeys.de.pgp.net ===Schollglas Unternehmensgruppe=== -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Probleme, Linux zum DSL Router umzuwandeln
Gruesse! * Andreas Pakulat [EMAIL PROTECTED] schrieb am [09.03.06 16:44]: On 09.03.06 17:15:02, Tamer Higazi wrote: Ich habe einen Linux Rechner mit einer statischen IP-Adresse von meinen ISP gekriegt die in meinem rechner folgende eintragungen hat: Wo ist da DSL? und will aber das ein zweiter rechner über mein Linux Rechner ins Netz springt. Also, habe ich ein eth0:0 Alias erstellt, IP-Forwarding aktiviert und mit route den Befehl gegeben, die alle Packete ins Netz zu routen.. Damit ich das richtig verstehe: eth0 ist deine Verbindung ins Internet, da haengt ein DSL-Modem oder sonstirgendwas dran richtig? Wie willst du denn an diesselbe Netzwerkkarte noch einen 2. Rechner anschliessen? Netzwerk-Kabel spleißen (mit feinem Crimpzangen-Messeraufsatz kein Problem) ;-) dann die losen Drähte kreuzen und ab in die andere Büchse? Andreas Gruß Gerhard -- @[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED] Don't panic! \* Greetings from Gerhard Brauer, \|/ \|/ \* 55411 Bingen am Rhein, Germany @~/ ,. \~@ \*.*** /_( \__/ )_\ |* IM: gerbra at jabber dot org \__U_/|* PGP: 96A08062 ___|*___ -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Probleme, Linux zum DSL Router umzuwandeln
am 09.03.2006, um 17:54:01 +0200 mailte Tamer Higazi folgendes: Topoplogie: Lern quoten. Andreas -- Andreas Kretschmer(Kontakt: siehe Header) Heynitz: 035242/47215, D1: 0160/7141639 GnuPG-ID 0x3FFF606C http://wwwkeys.de.pgp.net ===Schollglas Unternehmensgruppe=== -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Probleme, Linux zum DSL Router umzuwandeln
Hallo Tamer, * Tamer Higazi schrieb [09-03-06 17:15]: und will aber das ein zweiter rechner über mein Linux Rechner ins Netz $Suchmaschinen-Stichwort: Masquerading. springt. Also, habe ich ein eth0:0 Alias erstellt, IP-Forwarding aktiviert und mit route den Befehl gegeben, die alle Packete ins Netz zu routen.. [...] ifconig eth0:0 192.168.215.2 sudo route add 192.168.215.0 gateway 81.10.53.21 eth0:0 ist nur ein Alias der eth0, an der das Kabel zu deinem Provider steckt. Hast du deinen zweiten Rechner an einer zweiten Netzwerkkarte angeschlossen, musst du (wahrscheinlich) eth1 einrichten. Ausserdem ist es Unsinn, ein privates Netz (192.168.*) direkt ins Internet zu routen. Welche konfiguration habe ich auf den Windows Rechner mit der IP-Addresse 192.168.215.2 vorzunehmen, damit dieser über meinen Linux Rechner ins Netz springen kann?! Erst mal musst du den Linux-Rechner richtig einrichten, bevor du dir darüber Gedanken machen solltest. Sobald der Linux-Rechner richtig eingerichtet ist, musst du auf der Windows-Krücke nur den Gateway 192.168.215.1 einstellen. Mit freundlichen Grüßen Udo Müller -- ComputerService Udo Müller Tel.: 0441-36167578 Schöllkrautweg 16 Fax.: 0441-36167579 26131 Oldenburg [EMAIL PROTECTED] Mobil: 0162-4365411 -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Probleme, Linux zum DSL Router umzuwandeln
Andreas Kretschmer wrote: am 09.03.2006, um 17:54:01 +0200 mailte Tamer Higazi folgendes: Topoplogie: Lern quoten. Andreas Kapiere ich nicht! Aber ich ziehe mir gerade die netfilter doku rein. Was meinst du mit Quoten im Bezug der Stern topologie die ich für mein Heimnetzwerk gewählt habe?! Liege ich hier auch voll daneben? Tamer -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Probleme, Linux zum DSL Router umzuwandeln
Tamer Higazi [EMAIL PROTECTED]: Andreas Kretschmer wrote: Lern quoten. Kapiere ich nicht! Aber ich ziehe mir gerade die netfilter doku rein. Was meinst du mit Quoten im Bezug der Stern topologie die ich für mein Heimnetzwerk gewählt habe?! Liege ich hier auch voll daneben? http://www.afaik.de/usenet/faq/zitieren/ -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Probleme, Linux zum DSL Router umzuwandeln
Gruesse! * Tamer Higazi [EMAIL PROTECTED] schrieb am [09.03.06 16:54]: Topoplogie: Switch - DSL-Router Switch - Linux Rechner mit Wenn du anregungen hast, wie ich ohne einer zweiten NIC über ein alias das ganze lösen könnte wäre ich dir dankbar. Ich weiß nicht, ob das über aliase überhaupt geht. Installiere dir iptables (apt-get install iptables). Dann versuch es mal mit folgendem Firewall/NAT-Skript: --- #!/bin/bash iptables -X INPUT iptables -X FORWARD iptables -t nat -X POSTROUTING iptables -P INPUT DROP iptables -P FORWARD DROP iptables -I INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT iptables -I INPUT -i lo -j ACCEPT iptables -I INPUT -i eth0:0 -s 192.168.215.0/24 -j ACCEPT iptables -I FORWARD -m state --state ESTABLISHED,RELATED -j ACCEPT iptables -I FORWARD -i eth0:0 -s 192.168.215.0/24 -j ACCEPT iptables -t nat -I POSTROUTING -o eth0 -s 192.168.215.0/24 -j SNAT --to 81.10.53.22 echo 1 /proc/sys/net/ipv4/ip_forward --- Am Win-Rechner dann 192.168.215.1 als Gateway eintragen + DNS-Server etc. Alles ohne Gewähr. Die sauberste Lösung wäre, den Linux-Rechner mit einer zweiten Nic als richtigen Router auszustatten. Tamer Gruß Gerhard -- @[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED] Don't panic! \* Greetings from Gerhard Brauer, \|/ \|/ \* 55411 Bingen am Rhein, Germany @~/ ,. \~@ \*.*** /_( \__/ )_\ |* IM: gerbra at jabber dot org \__U_/|* PGP: 96A08062 ___|*___ -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Probleme, Linux zum DSL Router umzuwandeln
On 09.03.06 17:54:01, Tamer Higazi wrote: Topoplogie: Switch - DSL-Router Switch - Linux Rechner mit Wenn ich mich nicht irre dann hat doch dein DSL-Router aufm externen IF die oeffentliche statische IP. Was du auf der internen Seite fuer IP's einstellst ist erstmal egal. Wieso muss der Linux-Rechner denn Router spielen wenn du schon einen DSL-Router hast? Stoepsel den Windows-Rechner an den Switch und gib ihm ne IP im selben Subnetz wie der DSL-Router (also wohl 81.10.53.2x) und gut ist. und rechner2 sollte mit der IP-Addresse 192.168.215.2 über den Linux Rechner ins Internet geforwarded werden. Warum? Wo ist DSL?! In Ägypten! So meinte ich das nicht, in deiner Beschriebenen Konfiguration fehlte der DSL-Router. Wenn du anregungen hast, wie ich ohne einer zweiten NIC über ein alias das ganze lösen könnte wäre ich dir dankbar. Nein, ob sowas mit Aliasen und einem Switch geht entzieht sich meiner Kenntniss. Solche Spielchen hab ich noch nicht gebraucht (zumal ne NIC grad mal 10 Euro kostet).. BTW: ToFu ist hier unerwuenscht (Text Oben Fullquote Unten) Andreas -- Stay away from hurricanes for a while. -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Probleme, Linux zum DSL Router umzuwandeln
Am Donnerstag, 9. März 2006 16:44 schrieb Andreas Pakulat: [...] Damit ich das richtig verstehe: eth0 ist deine Verbindung ins Internet, da haengt ein DSL-Modem oder sonstirgendwas dran richtig? Wie willst du denn an diesselbe Netzwerkkarte noch einen 2. Rechner anschliessen? Das könnte funktionieren. Die Verbindung zwischen Linux- und Windowsrechner würde über IP hergestellt, welches auf dem Ethernet-Protokoll aufsetzt und die zwischen Linuxrechner und DSL-Modem würde über PPPoE hergestellt, welches ebenfalls auf dem Ethernet-Protokoll aufsetzt. Letztendlich würde also in beiden Fällen die Kommunikation über das Ethernet-Protokoll stattfinden, welches ja bekanntlich dazu in der Lage ist, damit umzugehen, dass mehrere Instanzen versuchen, gleichzeitig über das gleiche Medium zu senden. Empfehlenswert ist so eine Konfiguration allerdings m.W. nicht. [...] Viele Grüße Wolfgang
Re: Probleme, Linux zum DSL Router umzuwandeln
Hi, hast du mal dnsmasq und masquerade ausprobiert? Brauchst allerdings 2 Netzwerkkarten in dem Rechner, der ins Internet geht, ist aber eine saubere Lösung. ;-) Eigentlich musst du nur das Skript /usr/sbin/masquerade für deine Internet-Schnittstelle (z.B. eth0) anpassen und die IP davon in den Clients für DNS anpassen. DHCP brauchste ja eigentlich nicht. # remove-gateway # /etc/init.d/dnsmasq start # /usr/sbin/masquerade Steve
Re: Probleme, Linux zum DSL Router umzuwandeln (gelöst)
Es hat funktioniert! topologie und konfiguration: Linux Rechner an der switch mit eth0: 81.10.53.22 gateway: 81.10.53.23 eth0:0 192.168.215.1 DNS: DSL Modem an der switch Windows Machine an der Switch: 192.168.215.2 Gateway: 192.168.215.1 DNS mit ifconfig die routing tabelle manipulieren, so dass vom 192.168.215.0 netzwerk alles ins 81.10.53.21 weitergeleitet wird. Ich habe es nur mit dem Winows client probiert, nicht gleichzeitig mit dem Linux rechner im Internet zu surfen. Man sagte mir, ich sollte davon die Finger lassen, da es zu kolaisionen käme (was mit sicherheit auch der Fall wäre. Der ganze Datenverkehr wäre nicht vom DSL Modem (ich habe einen router) direkt über die Switch, sondern über die Linuxbox zum windows rechner rübergeflossen. Ich habe zu allerletzt den DSL-Router richtig konfiguriert (mit support von meinem ISP). Konfigurationsdatei in den Router hochladen, damit der win rechner mit einer 10.0.0.1 Addresse vom Router aus ins Netz kommt und mein Linux rechner dessen Konfiguration beibehalten kann. Danke an alle die mich mit hilfe unterstützt haben! Ihr Debian Jungs seit alle Spitzenleute Tamer Wolfgang Jeltsch wrote: Am Donnerstag, 9. März 2006 16:44 schrieb Andreas Pakulat: [...] Damit ich das richtig verstehe: eth0 ist deine Verbindung ins Internet, da haengt ein DSL-Modem oder sonstirgendwas dran richtig? Wie willst du denn an diesselbe Netzwerkkarte noch einen 2. Rechner anschliessen? Das könnte funktionieren. Die Verbindung zwischen Linux- und Windowsrechner würde über IP hergestellt, welches auf dem Ethernet-Protokoll aufsetzt und die zwischen Linuxrechner und DSL-Modem würde über PPPoE hergestellt, welches ebenfalls auf dem Ethernet-Protokoll aufsetzt. Letztendlich würde also in beiden Fällen die Kommunikation über das Ethernet-Protokoll stattfinden, welches ja bekanntlich dazu in der Lage ist, damit umzugehen, dass mehrere Instanzen versuchen, gleichzeitig über das gleiche Medium zu senden. Empfehlenswert ist so eine Konfiguration allerdings m.W. nicht. [...] Viele Grüße Wolfgang -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Como configurar Debian/Linux a un router DSL
El dom, 02-10-2005 a las 18:31 -0500, Marco Rangel escribió: Como configurar Debian/Linux a un router DSL Sere mas explicito. Tengo configurada mi Tarjeta de red sin problemas, mi red con los usuarios funciona bien. Dare mas aspectos tecnicos. IP Adress: 192.168.1.5 Submascara: 255.255.0.0 Gateway: 192.168.0.5 que es la IP del router Si estos datos son correctos es imposible que te funcione, pues tu maquina esta en una red distinta a la de la puerta (192.168.1 contra 192.168.0). Esta informacion esta en el archivo de interfase de /etc/network Tengo 4 usuarios mas conectados al router con Windows XP y por medio de estos no tengo problemas para entrar a Internet. Esta es la configuracion de una de las terminales Windows XP Direccion IP:192.168.1.11 Mascara de subred: 255.255.0.0 Puerta de enlace predeterminada: 192.168.0.1 Servidor DNS preferido: 192.168.0.1 En otras palabras no tengo idea de como configurar en Debian/Linux el gateway y el DNS para que pueda entrar a Internet por medio de Router/Modem DSL. Salu2 Marco Rangel __ Correo Yahoo! Espacio para todos tus mensajes, antivirus y antispam ¡gratis! Regístrate ya - http://correo.yahoo.com.mx/ -- Antonio Trujillo Carmona [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Como configurar Debian/Linux a un router DSL
Por lo que yo se las ip's estan bien configuradas y se encuentran en la misma red 192.168.0.0/16 aunque es poco habitual tener una red tan amplia para un router DSL Ahora debes comprobar la configuración del router si tiene la misma máscara de subred (255.255.0.0 si el fallo esta aquí tendrá 255.255.255.0). Puedes probar a poner la ip 192.168.0.11 en Debian y cambiar la máscara a 255.255.255.0 porque puede que el router utilice la red 192.168.0.0/24 Un saludo --- Pedro http://www.darelinux.com El mar, 04-10-2005 a las 10:38 +0200, Antonio Trujillo Carmona escribió: El dom, 02-10-2005 a las 18:31 -0500, Marco Rangel escribió: Como configurar Debian/Linux a un router DSL Sere mas explicito. Tengo configurada mi Tarjeta de red sin problemas, mi red con los usuarios funciona bien. Dare mas aspectos tecnicos. IP Adress: 192.168.1.5 Submascara: 255.255.0.0 Gateway: 192.168.0.5 que es la IP del router Si estos datos son correctos es imposible que te funcione, pues tu maquina esta en una red distinta a la de la puerta (192.168.1 contra 192.168.0). Esta informacion esta en el archivo de interfase de /etc/network Tengo 4 usuarios mas conectados al router con Windows XP y por medio de estos no tengo problemas para entrar a Internet. Esta es la configuracion de una de las terminales Windows XP Direccion IP:192.168.1.11 Mascara de subred: 255.255.0.0 Puerta de enlace predeterminada: 192.168.0.1 Servidor DNS preferido: 192.168.0.1 En otras palabras no tengo idea de como configurar en Debian/Linux el gateway y el DNS para que pueda entrar a Internet por medio de Router/Modem DSL. Salu2 Marco Rangel __ Correo Yahoo! Espacio para todos tus mensajes, antivirus y antispam ¡gratis! Regístrate ya - http://correo.yahoo.com.mx/ -- Antonio Trujillo Carmona [EMAIL PROTECTED]
Re: Como configurar Debian/Linux a un router DSL
El mar, 04-10-2005 a las 16:27 +0200, Pedro escribió: Por lo que yo se las ip's estan bien configuradas y se encuentran en la misma red 192.168.0.0/16 aunque es poco habitual tener una red tan amplia para un router DSL Ahora debes comprobar la configuración del router si tiene la misma máscara de subred (255.255.0.0 si el fallo esta aquí tendrá 255.255.255.0). Puedes probar a poner la ip 192.168.0.11 en Debian y cambiar la máscara a 255.255.255.0 porque puede que el router utilice la red 192.168.0.0/24 Un saludo Llevas razón no había visto que la mascara de red era la 255.255.0.0, aunque esto no venga al caso del problema este tipo de red rompe los estándares ya que las redes privadas de tipo C deben de ser 192.168.x.x con mascara 255.255.255.0 y las de tipo B 172.21.x.x con mascara 255.255.0.0, por eso al leer 192.168 automática mente pensé que eran redes C y no me fije en la mascara de red anómala. -- Antonio Trujillo Carmona [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Como configurar Debian/Linux a un router DSL
El 2/10/05, Marco Rangel[EMAIL PROTECTED] escribió: Como configurar Debian/Linux a un router DSL Sere mas explicito. Tengo configurada mi Tarjeta de red sin problemas, mi red con los usuarios funciona bien. Dare mas aspectos tecnicos. IP Adress: 192.168.1.5 Submascara: 255.255.0.0 Gateway: 192.168.0.5 que es la IP del router Esta informacion esta en el archivo de interfase de /etc/network Tengo 4 usuarios mas conectados al router con Windows XP y por medio de estos no tengo problemas para entrar a Internet. Esta es la configuracion de una de las terminales Windows XP Direccion IP:192.168.1.11 Mascara de subred: 255.255.0.0 Puerta de enlace predeterminada: 192.168.0.1 Servidor DNS preferido: 192.168.0.1 En otras palabras no tengo idea de como configurar en Debian/Linux el gateway y el DNS para que pueda entrar a Internet por medio de Router/Modem DSL. Salu2 Marco Rangel __ Correo Yahoo! Espacio para todos tus mensajes, antivirus y antispam ¡gratis! Regístrate ya - http://correo.yahoo.com.mx/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] Me nace un pregunta ¿estas seguro que las ips son estaticas? digo llevo un rato trabajando con router dsl y la mayoria trabajan con dhcp pero si tu ip es statica supongo que con un #apt-get install etherconf te vastaria para configurar todo correctamente incluso si es con DHCP en todo caso tambien estan las otras opiniones que te dieron que estan bastante acertadas -- Por favor, NO utilice formatos de archivo propietarios para el intercambio de documentos, como DOC y XLS, sino HTML, PDF, TXT, CSV o cualquier otro que no obligue a utilizar un programa de un fabricante concreto. Internet Explorer y Outlook son muy peligrosos por sus continuos problemas de seguridad. Utilice alternativas libres: http://www.mozillaes.org/ - usuario linux registrado #387231 http://counter.li.org --
Como configurar Debian/Linux a un router DSL
Como configurar Debian/Linux a un router DSL Sere mas explicito. Tengo configurada mi Tarjeta de red sin problemas, mi red con los usuarios funciona bien. Dare mas aspectos tecnicos. IP Adress: 192.168.1.5 Submascara: 255.255.0.0 Gateway: 192.168.0.5 que es la IP del router Esta informacion esta en el archivo de interfase de /etc/network Tengo 4 usuarios mas conectados al router con Windows XP y por medio de estos no tengo problemas para entrar a Internet. Esta es la configuracion de una de las terminales Windows XP Direccion IP:192.168.1.11 Mascara de subred: 255.255.0.0 Puerta de enlace predeterminada: 192.168.0.1 Servidor DNS preferido: 192.168.0.1 En otras palabras no tengo idea de como configurar en Debian/Linux el gateway y el DNS para que pueda entrar a Internet por medio de Router/Modem DSL. Salu2 Marco Rangel __ Correo Yahoo! Espacio para todos tus mensajes, antivirus y antispam ¡gratis! Regístrate ya - http://correo.yahoo.com.mx/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Como configurar Debian/Linux a un router DSL
El dom, 02-10-2005 a las 18:31 -0500, Marco Rangel escribió: Como configurar Debian/Linux a un router DSL Sere mas explicito. Tengo configurada mi Tarjeta de red sin problemas, mi red con los usuarios funciona bien. Dare mas aspectos tecnicos. IP Adress: 192.168.1.5 Submascara: 255.255.0.0 Gateway: 192.168.0.5 que es la IP del router Esta informacion esta en el archivo de interfase de /etc/network Tengo 4 usuarios mas conectados al router con Windows XP y por medio de estos no tengo problemas para entrar a Internet. Esta es la configuracion de una de las terminales Windows XP Direccion IP:192.168.1.11 Mascara de subred: 255.255.0.0 Puerta de enlace predeterminada: 192.168.0.1 Servidor DNS preferido: 192.168.0.1 En otras palabras no tengo idea de como configurar en Debian/Linux el gateway y el DNS para que pueda entrar a Internet por medio de Router/Modem DSL. Salu2 Marco Rangel Hola, si el gateway es 192.168.0.5 y podes hacerle un ping, entonces esa parte está bien. Ahora solo te falta los DNS, estos van configurados en /etc/resolv.conf y con líneas de la siguiente forma: nameserver 192.168.0.5 generalmente sirve poner el IP del router/gateway pero si no te funciona tendrás que averiguar cuales son los IPs de DNS de tu proveedor de internet. Saludos Anibal -- Anibal Kia Fenoglio Córdoba - Argentina ICQ: 24950258 Jabber: [EMAIL PROTECTED] Correo-e: [EMAIL PROTECTED] Blog: http://anibalf.blogspot.com http://www.aptech.com.ar/blog/ GPG id: B02DED4A -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Como configurar Debian/Linux a un router DSL
En /etc/network/interfaces cambia el Gateway por el que te dice Windows (192.168.0.1). Ésta es la IP del ruter. Seguramente con esto bastará. Saludos En/na Marco Rangel ha escrit: Como configurar Debian/Linux a un router DSL Sere mas explicito. Tengo configurada mi Tarjeta de red sin problemas, mi red con los usuarios funciona bien. Dare mas aspectos tecnicos. IP Adress: 192.168.1.5 Submascara: 255.255.0.0 Gateway: 192.168.0.5 que es la IP del router Esta informacion esta en el archivo de interfase de /etc/network Tengo 4 usuarios mas conectados al router con Windows XP y por medio de estos no tengo problemas para entrar a Internet. Esta es la configuracion de una de las terminales Windows XP Direccion IP:192.168.1.11 Mascara de subred: 255.255.0.0 Puerta de enlace predeterminada: 192.168.0.1 Servidor DNS preferido: 192.168.0.1 En otras palabras no tengo idea de como configurar en Debian/Linux el gateway y el DNS para que pueda entrar a Internet por medio de Router/Modem DSL. Salu2 Marco Rangel __ Correo Yahoo! Espacio para todos tus mensajes, antivirus y antispam ¡gratis! Regístrate ya - http://correo.yahoo.com.mx/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Linux als DECnet router ??
Hallo Debianer, Ich hoffe, das hier schonmal jemand was von DECNet gehört hat ;-) Ja ja .. sowas haben wir auch noch ... derzeit bastell ich gerade an einen DECNet-Router, welcher auf einer Firewall mit diversen VLANs laufen soll. Problem ist es, das wir Rechner haben, die im VLAN 12 sind und zu der DECNet-Area 1 und andere Rechner im VLAN 17 haben, die zur DECNet Area 6 gehören. Da im VLAN ja jedes Netz als eigenes Kabel betrachtet werden kann, bringt unser alter DECNet-Router da nichts. In meiner derzeitigen Testumgebung habe ich folgendes gemacht Rechner A mit VLANs konfiguriert (Kernel mit DECNet-Routing kompiliert) installierte Packete tcpdump iproute2 dnet-common dnet-progs vlan MAC-Adressen für eth1.12 und eth1.17 auf DECNet-Adressen 1.662 und 6.662 konfiguriert Forwarding für DECNet aktiviert echo 1 /proc/sys/net/decnet/conf/eth1.12/forwarding echo 1 /proc/sys/net/decnet/conf/eth1.17/forwarding Router-Priorität eingestellt echo 2 /proc/sys/net/decnet/conf/eth1.12/priority echo 2 /proc/sys/net/decnet/conf/eth1.17/priority Route auf die anderen Test-Rechner eingetragen ip -f dnet route add 1.661 dev eth1.12 ip -f dnet route add 6.661 dev eth1.17 Rechner B als DECNet-Node 1.661 Rechner C als DECNet-Node 6.661 dann auf Rechner A und B den Zielchner als Nachbarn eingetragen damit DECNet weiß wo es mit den Daten hin soll Rechner B ip -f dnet neigh add 6.662 dev eth0 Rechner C ip -f dnet neigh add 1.662 dev eth0 DECNet als solches funktioniert, zumindest kann ich in der gleichen Area eine Verbindung aufbauen, mnur das Routing will noch nicht :-( Hat da wer ne Idee Ich google schon seit Tagen durch das Internet ! Gruß Markus -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
ponerle linux a un router viejo
Hola: Llegaron a mis manos dos routers. Creo que tienen DOS, pero la persona que me los dió, no sabía el password, se va a fijar si puede darme los manuales (que no sabe donde estan, y creé que se tiraron). ¿Puedo ponerle debian? ¿Qué versión me recomiendan? Y lo que más me preocupa es ¿existe algún HOWTO, o algo parecido que me sirva de ayuda para configurarlo? Sé como configurar el ipchains/iptables, pero cuando abrí este router todo era bastante raro, estoy acostumbrado a ver 386, 486 y otras más nuevas (incluso tenía una XT que fue mi primer computadora), y por dentro es muy distinta (cables y placas). ¿Puede ser alguna otra arquitectura?¿cual? -- Atentamente, yo Matías Libertad para la Argentina -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: ponerle linux a un router viejo
era bastante raro, estoy acostumbrado a ver 386, 486 y otras más nuevas (incluso tenía una XT que fue mi primer computadora), y por dentro es muy distinta (cables y placas). ¿Puede ser alguna otra arquitectura?¿cual? Uff! A ver danos algun dato mas. Desde luego, si tenia DOS es bastante antiguo pero es muy posible que sea x86 ¿ Se porto el DOS a otras arquitecturas ? Un saludo. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Linux as a router
Brian Boonstra wrote: You might want to try the Debian-based Linux Router Project, at http://www.linuxrouter.org/ The whole thing runs off a write-protected floppy, so you can't be hacked as badly as with a HD. The docs on the official site are not too good, but here's a good one: http://www.geocities.com/Athens/Ithaca/9660/lrphowto.html OK, I'll check them out. BTW, would using a floppy for the system be better than a HD in terms of security? Or, it just means that a floppy will have less data so that even if the system badly hacked, the recovery would be pretty simple (just make a copy from the backup floppy, and the router will just run as before). Thanks again, Oki
Re: Linux as a router
On Fri, Nov 19, 1999 at 07:16:40AM +0700, Oki DZ wrote: BTW, would using a floppy for the system be better than a HD in terms of security? Or, it just means that a floppy will have less data so that even if the system badly hacked, the recovery would be pretty simple (just make a copy from the backup floppy, and the router will just run as before). I think it could be possible, using a large amount of ram, and ram disks. But a good firewall is working very well, and allow you to keep traces (logs) of the attack. JY -- Jean-Yves F. Barbier [EMAIL PROTECTED] All language designers are arrogant. Goes with the territory... (By Larry Wall)
Linux as a router
Hi, I have an Intel/486 and want to set it up as a router. I have installed the base slink system on it, but I'm still having problem with the NE2K network card; the module for it can't be loaded. But since Satan is not available for slink and the system is currently non functional (nowadays, if your computer can't connect to a network, basically it's not a computer), I'm going to install potato on it. (the download is currently in progress) Well, having a router with a network analyzer on board is slightly overboard. But the aim is for testing, and I think the 800M space on its disk can be made useful. BTW, is anyone already familiar with Satan? Does it need an enormous memory to do the scans? My machine has 8M of RAM. I need to scan only one system; the Sparc that has slink on it. I'd like to know whether I have set up the security settings of the system correctly. Speaking about routers, could a Linux system be set as an SNMP device? I read about snmp package in www.debian.org; does it the right package for converting a PC to an SNMP device? Thanks in advance, Oki
Re: Linux as a router
You wrote: I have an Intel/486 and want to set it up as a router. You might want to try the Debian-based Linux Router Project, at http://www.linuxrouter.org/ The whole thing runs off a write-protected floppy, so you can't be hacked as badly as with a HD. The docs on the official site are not too good, but here's a good one: http://www.geocities.com/Athens/Ithaca/9660/lrphowto.html - Brian