Re: Trying to replace my router with a Debian machine - but I can't understand my existing setup
Aneurin Price wrote: > > Yeah, it's amazing how often restarting things will magically fix > problems. I really ought to remember to try that more often. > > Nye there's a joke about this and a car, so here it is an engineer, el. technician and computer guy are driving a car and it suddenly stops. the engineer says it must be the engine. the el. guy says it's something on the el. installation. the comp. guy says, can we just get off and get on and just restart the system ... it usually helps :-D -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Trying to replace my router with a Debian machine - but I can't understand my existing setup
On Thu, Feb 5, 2009 at 11:41 PM, Emanoil Kotsev wrote: > Aneurin Price wrote: > >> On Wed, Feb 4, 2009 at 10:47 PM, Emanoil Kotsev >> wrote: >> >>> >>> they could be configured to take the mac address and obtain the ip ... >>> same mac, same IP ?? do you think its possible. check >>> >> >> This is an interesting point. >> I've just managed to get the connection to work by re-entering the >> connection details in the modem (without changing anything) and restarting >> it. I suspect that it may have learned the MAC address of the router it >> was connected to and been continuing to attempt to bridge the connection >> to that device. Restarting would then have given it the opportunity to >> detect that it's connected to a different device. >> >> So it turns out that the config of my new machine I'd set up was fine >> after all, and I just needed to restart the modem. Tch. Why didn't I try >> that in the first place? >> >> Thanks, >> Nye > > hehe, this was fun in respect to the 1000 lines you wrote. I can not help > you answer the question why you did not try this first ;-) > Yeah, it's amazing how often restarting things will magically fix problems. I really ought to remember to try that more often. Nye -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Trying to replace my router with a Debian machine - but I can't understand my existing setup
Aneurin Price wrote: > On Wed, Feb 4, 2009 at 10:47 PM, Emanoil Kotsev > wrote: > >> >> they could be configured to take the mac address and obtain the ip ... >> same mac, same IP ?? do you think its possible. check >> > > This is an interesting point. > I've just managed to get the connection to work by re-entering the > connection details in the modem (without changing anything) and restarting > it. I suspect that it may have learned the MAC address of the router it > was connected to and been continuing to attempt to bridge the connection > to that device. Restarting would then have given it the opportunity to > detect that it's connected to a different device. > > So it turns out that the config of my new machine I'd set up was fine > after all, and I just needed to restart the modem. Tch. Why didn't I try > that in the first place? > > Thanks, > Nye hehe, this was fun in respect to the 1000 lines you wrote. I can not help you answer the question why you did not try this first ;-) regards -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Trying to replace my router with a Debian machine - but I can't understand my existing setup
On Wed, Feb 4, 2009 at 10:47 PM, Emanoil Kotsev wrote: > > they could be configured to take the mac address and obtain the ip ... same > mac, same IP ?? do you think its possible. check > This is an interesting point. I've just managed to get the connection to work by re-entering the connection details in the modem (without changing anything) and restarting it. I suspect that it may have learned the MAC address of the router it was connected to and been continuing to attempt to bridge the connection to that device. Restarting would then have given it the opportunity to detect that it's connected to a different device. So it turns out that the config of my new machine I'd set up was fine after all, and I just needed to restart the modem. Tch. Why didn't I try that in the first place? Thanks, Nye -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Trying to replace my router with a Debian machine - but I can't understand my existing setup
Aneurin Price wrote: Sorry for not answering exactly your question, but at some point it got too long for me. Read about rtlinux. Why do you need this router? I think the modem can provide you more then 1 IP. I think great things are simple, so I would just remove the router, or configure it to be just a hub. Anyway. If you want to replace it with a debian system there are great small devices now for about 100+ € - I mean mini and micro mainboards or pcs. I use one from acrosser with geode CPU and installed I've debian on a flash card 4GB or USB stick 256MB. both can run the router and it has never failed for about 4 years. so I don't understand why you should run the dhcp/dns server on both ... both of them must be configured properly. besides the router can have a modem but it is not likely that the modem is connected to the first modem. It would be the case if your provider has some kind of strange configuration ... and in this case you would need both. the answer here is My problem lies in that I can't understand how the connection between the router and the modem is actually working. The beginning of my confusion is that these machines both claim to have the same external IP address. they could be configured to take the mac address and obtain the ip ... same mac, same IP ?? do you think its possible. check may be it is using nat or smth I don't know. regards -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
RE: Trying to replace my router with a Debian machine - but I can't understand my existing setup
> > > > Original Message >From: aneurin.pr...@gmail.com >To: debian-user@lists.debian.org >Subject: RE: Trying to replace my router with a Debian machine - but >I can't understand my existing setup >Date: Wed, 4 Feb 2009 12:03:53 + > >>Hello all, >> >>This is only tangentially Debian related, but I can't really think >of anywhere >>better to ask, so maybe somebody can help. >> >>I have an ADSL connection set up as follows: D-Link DSL-300G+ modem >connected >>to the ADSL line - well it calls itself a modem, but it connects to >the rest of >>our network via ethernet and appears to have both an external and an >internal IP >>address, which sounds rather more like a router to me, but more on >that later. I >>don't know what OS it runs; it has telnet access but the environment >is >>unfamiliar to me, so I've only used the web-based config. Its >internal address >>is 192.168.0.1. >> >>Connected to this (via ethernet) is a device calling itself >"RouteFinder SOHO >>VPN Gateway". Once again I don't know what OS this is running, and >I've not >>found any telnet/ssh access to it. This has an internal IP address >192.168.2.1, >>and is connected to the main switch for our intranet (where all >machines have IP >>addresses in the 192.168.2.0/24 subnet). I'd like to replace this >router with a >>PC running Lenny. >> >>My problem lies in that I can't understand how the connection >between the router >>and the modem is actually working. The beginning of my confusion is >that these >>machines both claim to have the same external IP address. So, the >setup looks >>like this: >> >> >-- >>--- | Modem| | Router | | >Network | >>ADSL|---|$extip : 192.168.0.1|---|$extip : >192.168.2.1|---|192.168.2.0/24| >>--- >-- >> >>The modem does have a setting for "RFC 1483 Bridge", but it's >disabled. Instead, >>it's just set to the standard PPPoA. >> >>The router claims to be getting its IP address, default gateway, and >DNS via >>DHCP, and it can be set up to do port forwarding, etc. I didn't set >the network >>up, and it was only when I physically followed along all the cabling >that I >>realised that the modem even *existed* - since the router appears to >be >>publically adressable I'd assumed that it included its own modem. >> >>Reasoning that the modem must be somehow forwading the DHCP >connection, I had a >>short attempt (I don't want to cause too much downtime through >experimentation) >>to replace the router with the machine I've set up to be its >replacement. When >>that started up, it got the IP address 192.168.0.2 via DHCP, DNS >server >>192.168.0.1 (the modem doesn't actually provide DNS though) and no >default >>gateway. It did occur to me - after I'd replaced the original router >- that >>possibly I'd made some Shorewall configuration mistake, but it's >definitely >>configured to allow connections from '$FW' to 'net' - ie. all >outgoing >>connections from that machine, so I can't really see how there would >be a >>problem. >> >>With the original setup, traceroute to $extip goes straight there, >without any >>hops, and traceroute to google.com looks something like this: >> >>Tracing route to google.com [209.85.171.100] >>over a maximum of 30 hops: >> >> 1<1 ms<1 ms<1 ms 192.168.2.1 >> 2 520 ms 555 ms 596 ms 62.241.160.185 >> ... >> Numerous internet addresses >> ... >> 16 172 ms 174 ms 179 ms cg-in-f100.google.com >[209.85.171.100] >> >>No mention in there of 192.168.0.1, or $extip. >> >>So in a nutshell, when I'm using the dedicated router, the modem >appears to be >>completely transparent, but when I'm trying to use the computer >replacement, it >>acts like a normal router which has been misconfigured. >> >>Does anyone have any idea how the existing setup actually works, or >how I can >>investigate further? Is there some common setup here which I'm >completely >>unaware of? Would it be worth temporarily allowing all connections >from 'net' to >>'$FW' in my Shorewall config and seeing what happens? >> >>I'm quite stuck here so anyone with
Trying to replace my router with a Debian machine - but I can't understand my existing setup
Hello all, This is only tangentially Debian related, but I can't really think of anywhere better to ask, so maybe somebody can help. I have an ADSL connection set up as follows: D-Link DSL-300G+ modem connected to the ADSL line - well it calls itself a modem, but it connects to the rest of our network via ethernet and appears to have both an external and an internal IP address, which sounds rather more like a router to me, but more on that later. I don't know what OS it runs; it has telnet access but the environment is unfamiliar to me, so I've only used the web-based config. Its internal address is 192.168.0.1. Connected to this (via ethernet) is a device calling itself "RouteFinder SOHO VPN Gateway". Once again I don't know what OS this is running, and I've not found any telnet/ssh access to it. This has an internal IP address 192.168.2.1, and is connected to the main switch for our intranet (where all machines have IP addresses in the 192.168.2.0/24 subnet). I'd like to replace this router with a PC running Lenny. My problem lies in that I can't understand how the connection between the router and the modem is actually working. The beginning of my confusion is that these machines both claim to have the same external IP address. So, the setup looks like this: -- --- | Modem| | Router | |Network | ADSL|---|$extip : 192.168.0.1|---|$extip : 192.168.2.1|---|192.168.2.0/24| --- -- The modem does have a setting for "RFC 1483 Bridge", but it's disabled. Instead, it's just set to the standard PPPoA. The router claims to be getting its IP address, default gateway, and DNS via DHCP, and it can be set up to do port forwarding, etc. I didn't set the network up, and it was only when I physically followed along all the cabling that I realised that the modem even *existed* - since the router appears to be publically adressable I'd assumed that it included its own modem. Reasoning that the modem must be somehow forwading the DHCP connection, I had a short attempt (I don't want to cause too much downtime through experimentation) to replace the router with the machine I've set up to be its replacement. When that started up, it got the IP address 192.168.0.2 via DHCP, DNS server 192.168.0.1 (the modem doesn't actually provide DNS though) and no default gateway. It did occur to me - after I'd replaced the original router - that possibly I'd made some Shorewall configuration mistake, but it's definitely configured to allow connections from '$FW' to 'net' - ie. all outgoing connections from that machine, so I can't really see how there would be a problem. With the original setup, traceroute to $extip goes straight there, without any hops, and traceroute to google.com looks something like this: Tracing route to google.com [209.85.171.100] over a maximum of 30 hops: 1<1 ms<1 ms<1 ms 192.168.2.1 2 520 ms 555 ms 596 ms 62.241.160.185 ... Numerous internet addresses ... 16 172 ms 174 ms 179 ms cg-in-f100.google.com [209.85.171.100] No mention in there of 192.168.0.1, or $extip. So in a nutshell, when I'm using the dedicated router, the modem appears to be completely transparent, but when I'm trying to use the computer replacement, it acts like a normal router which has been misconfigured. Does anyone have any idea how the existing setup actually works, or how I can investigate further? Is there some common setup here which I'm completely unaware of? Would it be worth temporarily allowing all connections from 'net' to '$FW' in my Shorewall config and seeing what happens? I'm quite stuck here so anyone with experience of this would be very welcome. Thanks, Nye -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
