Hi,

I'm currently busy setting up a LAN in a classroom - for Linux learning
purposes - at the DRTFEP (Direction Régionale du Travail) in Montpellier
(F). I have some trouble accessing the internet with these machines, and
there seems to be some exotic configuration at work - at least one I've
never encountered. Here goes.

Machines are mostly configured via DHCP or - rarely - static, with an IP
that is either 10.34.22.* or 10.34.22.23.* / netmask 255.255.255.254.
Gateway machine is 10.34.22.1... but there's also a "proxy" machine out
there (can't remember the IP right now, I'm writing this message at home).
When I setup the LAN, machines can ping each other OK. Each one has the
gateway machine indicated at the appropriate line in
/etc/rc.d/rc.inet1.conf. Nameserver is also there (checked resolv.conf)...
but when I try to ping something out there on the internet, I get some
response like - as far as I remember - "Bad Error Code". What happens is
that all traffic has to pass through one machine that filters everything
(so employees at that department don't do chatting or skyping or view
porn, etcetera). The only explanation I could get from people
"administrating" that network (100% Windows for now), is that "the proxy
address has to be configured in Internet Explorer".

Now the concept of "proxy" is new to me, one of the things I don't know
and I sense I should.

Q: how is this configured in a base Slackware install? So eventually I can
browse the web with Lynx, or ping something, fire up lftp...?

Any suggestions?

Niki
--
Whereof one cannot speak, thereof one frequently goes ranting on and on
at ball-breaking length. -- Ludwig Wittgenstein, Tractatus logico-
philosophicus, first draft.

Le Fri, 26 Jan 2007 14:41:01 +0100, Niki Kovacs a écrit*:

> Machines are mostly configured via DHCP or - rarely - static, with an IP
> that is either 10.34.22.* or 10.34.22.23.* / netmask 255.255.255.254.

Ooops. This should read 255.255.254.0, of course.

Niki
--
Whereof one cannot speak, thereof one frequently goes ranting on and on
at ball-breaking length. -- Ludwig Wittgenstein, Tractatus logico-
philosophicus, first draft.

Niki Kovacs wrote:
> Hi,
>
> I'm currently busy setting up a LAN in a classroom - for Linux learning
> purposes - at the DRTFEP (Direction Régionale du Travail) in Montpellier
> (F). I have some trouble accessing the internet with these machines, and
> there seems to be some exotic configuration at work - at least one I've
> never encountered. Here goes.
>
> Machines are mostly configured via DHCP or - rarely - static, with an IP
> that is either 10.34.22.* or 10.34.22.23.* / netmask 255.255.255.254.
> Gateway machine is 10.34.22.1... but there's also a "proxy" machine out
> there (can't remember the IP right now, I'm writing this message at home).
> When I setup the LAN, machines can ping each other OK. Each one has the
> gateway machine indicated at the appropriate line in
> /etc/rc.d/rc.inet1.conf. Nameserver is also there (checked resolv.conf)...
> but when I try to ping something out there on the internet, I get some
> response like - as far as I remember - "Bad Error Code". What happens is
> that all traffic has to pass through one machine that filters everything
> (so employees at that department don't do chatting or skyping or view
> porn, etcetera). The only explanation I could get from people
> "administrating" that network (100% Windows for now), is that "the proxy
> address has to be configured in Internet Explorer".
>
> Now the concept of "proxy" is new to me, one of the things I don't know
> and I sense I should.
>
If it is an ISA proxy, you're out of luck. Every station must be
authenticated to Active Directory (the windows username/password) to
access the internet.
If you are installing Linux clients, the only option you have is to
install a NTML client
on the box, that will rewrite requests as if they were coming from
Internet Explorer.
I don't know if there's such a thing for Slackware, I know there is for
Debian.

Then it is important to know the proxy's IP address; if it is on an
external subnet, it could be bypassed.

I need more details, ip adress and so on

Ottavio
http://www.pledgebank.com/boycottvista

In <pan.2007.01.26.13.42.57.541114@mouse.com>, Niki Kovacs wrote:

> Le Fri, 26 Jan 2007 14:41:01 +0100, Niki Kovacs a écrit*:
>
>> Machines are mostly configured via DHCP or - rarely - static, with an IP
>> that is either 10.34.22.* or 10.34.22.23.* / netmask 255.255.255.254.
>
> Ooops. This should read 255.255.254.0, of course.
>
> Niki

Never needed it, but this will be what you want:
http://docs.kde.org/stable/en/kdebas...x.html#proxies

or
http://www.yolinux.com/TUTORIALS/GNOME.html#GNOMEPROXY

or in firefox there is preferences setting: connections

Good luck

Franz

"Ottavio Caruso" typed:

> If it is an ISA proxy, you're out of luck. Every station must be
> authenticated to Active Directory (the windows username/password) to
> access the internet.
> If you are installing Linux clients, the only option you have is to
> install a NTML client
> on the box, that will rewrite requests as if they were coming from
> Internet Explorer.
> I don't know if there's such a thing for Slackware, I know there is for
> Debian.

May I know which tool or set of tools accomplish NTLM-based request
redirection under Debian?

--
Ayaz Ahmed Khan

A witty saying proves nothing, but saying something pointless gets
people's attention.

Ayaz Ahmed Khan wrote:
> "Ottavio Caruso" typed:
>
> > If it is an ISA proxy, you're out of luck. Every station must be
> > authenticated to Active Directory (the windows username/password) to
> > access the internet.
> > If you are installing Linux clients, the only option you have is to
> > install a NTML client
> > on the box, that will rewrite requests as if they were coming from
> > Internet Explorer.
> > I don't know if there's such a thing for Slackware, I know there is for
> > Debian.
>
> May I know which tool or set of tools accomplish NTLM-based request
> redirection under Debian?

NTML Authorization Proxy Server:
http://packages.debian.org/stable/web/ntlmaps

Ottavio
http://www.pledgebank.com/boycottvista

"Ottavio Caruso" typed:
> Ayaz Ahmed Khan wrote:
>> May I know which tool or set of tools accomplish NTLM-based request
>> redirection under Debian?
>
> NTML Authorization Proxy Server:
> http://packages.debian.org/stable/web/ntlmaps

Thanks. That looks useful. Almost all of the local Cable Internet service
providers in my area use an ISA-based network setup which makes it
difficult, even impossible, for Linux clients to do anything behind an ISA
server.

--
Ayaz Ahmed Khan

A witty saying proves nothing, but saying something pointless gets
people's attention.