[kwlug disc.] tricky situation

[Joe Wennechuk]

yes.. I have gotten around this problem.. the modem boxes(CSU/DSU), are also a little gatewat device that blocks all incomming traffic. This makes it impossible to remote in that way, so when ifconfig is looked at the address is usually a private class c range 192.168.2.1 or somthing like that, so keep this connection,  and setup a second PPPoE connection thru the modem to bell directly and this will leave you exposed on the net like a tunnel thru the port blocking on the CSU/DSU(router). there is no way to block any ports once exposed, which could be kind of dangerous, so you'll have to use a software firewall.



Date: Wed, 5 Dec 2007 13:20:33 -0500
From: cbruner at quadro.net
To: kwlug-disc at kwlug.org
Subject: Re: [kwlug disc.] tricky situation






  


John Van Ostrand wrote:

  
  
> I've got a friend who is trying to set up a network between his
office 

  > and his house. He's self employed. At the office he
is on a cheap bell 

> arrangement, dsl, no port forwarding, no static ip. At home he is
on 

> Rogers.

  
  

It sounds like Bell has provided a modem/router device. I've seen these
before and they really are featureless. The ones I've seen have custom
Bell firmware on them. Our solution with these has been to reset them
at which point they act as a bridges and you Linux box can do the PPPoE
and firewall or you can get a cheap internet gateway.


It's true. It is a modem/router device, that from the factory has port
forwarding and other features available. From bell it has dhcp and
that's pretty well it.  



I did try reseting to factory defaults, but the Bell web pages still
come up on it, which have no way of getting to the portforwarding.



-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://listserv.ccjclearline.com/pipermail/kwlug-disc/attachments/20071205/e41ec328/attachment.htm