Derek Broughton wrote:
>Oooh.. You would have to point that out. Somewhere about 3 months after I
>got _this_ laptop, it occurred to me that I was really supposed to report
>the MAC to the network centre, so that they could do that. Of course, I
>never got around to it. Now, I know they'll app
Nic Ferrier wrote:
>But you're right, it's really a question of getting your sysadmins to
>turn the 192 dhcp server off (or at least give you a static mapping on
>the 142 dhcp server).
>
>
If it's rogue, they may not have visibility to it or even know it's there.
Had a video phone doing this
On Thursday 08 September 2005 16:18, Andrew McMillan wrote:
> On Thu, 2005-09-08 at 09:59 -0300, Derek Broughton wrote:
> > When I connect to my network at home through the lan (wired) connection
> > of a Linksys WRT54G router, I get an address in the 192.168.1.* range,
> > assigned by the DHCP ser
Nic Ferrier wrote:
> Derek Broughton <[EMAIL PROTECTED]> writes:
>
>> The thing is, I can prevent dhclient from even seeing 192.168.1.1 - but
>> then
>> it won't work at home. I could change the router address at home, so it
>> wouldn't conflict, but I'd still run the risk of coming across anoth
My last mail contained a small error. Under 2.) I should have written
that the interface shoulc be eth1 (not eth0).
Also, I was asked whether I use wireless-tools: I have them installed
and configured (taken over from woody). So, I guess I'm using them.
Any suggestions for my problem?
Andreas Gö
On Thu, 2005-09-08 at 09:59 -0300, Derek Broughton wrote:
> When I connect to my network at home through the lan (wired) connection of a
> Linksys WRT54G router, I get an address in the 192.168.1.* range, assigned
> by the DHCP server in the router. Next morning when I connect at work,
> dhclient
Derek Broughton <[EMAIL PROTECTED]> writes:
> The thing is, I can prevent dhclient from even seeing 192.168.1.1 - but then
> it won't work at home. I could change the router address at home, so it
> wouldn't conflict, but I'd still run the risk of coming across another
> rogue dhcp server on anot
Nic Ferrier wrote:
> Derek Broughton <[EMAIL PROTECTED]> writes:
>
>> When I connect to my network at home through the lan (wired) connection
>> of a Linksys WRT54G router, I get an address in the 192.168.1.* range,
>> assigned
>> by the DHCP server in the router. Next morning when I connect at
Nico Golde wrote:
> Hi,
> * <[EMAIL PROTECTED]> [2005-09-08 15:54]:
>> Nic Ferrier ??:
> [...]
>> >>One final question, why wasn't there a lease from 142.2.*.* (there's at
>> >>least two different DHCP servers there) in my lease file already, from
>> >>yesterday?
I never used this processor, so I don't, but the two may solve the
processor problem. It seems the processor slows down to save
battery, and the BogoMIPS is calculated with a slow speed, and then the
processor speeds up and it is too slow (or so I think.) The only
thing might be a kernel paramete
Hi,
* <[EMAIL PROTECTED]> [2005-09-08 15:54]:
> Nic Ferrier ??:
[...]
> >>One final question, why wasn't there a lease from 142.2.*.* (there's at
> >>least two different DHCP servers there) in my lease file already, from
> >>yesterday? They give lease times of on
Nic Ferrier пишет:
>Derek Broughton <[EMAIL PROTECTED]> writes:
>
>
>
>>When I connect to my network at home through the lan (wired) connection of a
>>Linksys WRT54G router, I get an address in the 192.168.1.* range, assigned
>>by the DHCP server in the router. Next morning when I connect at wo
Derek Broughton <[EMAIL PROTECTED]> writes:
> When I connect to my network at home through the lan (wired) connection of a
> Linksys WRT54G router, I get an address in the 192.168.1.* range, assigned
> by the DHCP server in the router. Next morning when I connect at work,
> dhclient immediately g
Hi folks,
I am running a custom-built kernel 2.6.10 on an Intel Mobile P3 processor.
(Acer
TravelMate 620, Debian 3.1)
>From time to time it happens to me that on boot-up the USB mouse doesn't
work.
When I try a USB camera in this situation it doesn't work either.
I discovered that when the USB d
When I connect to my network at home through the lan (wired) connection of a
Linksys WRT54G router, I get an address in the 192.168.1.* range, assigned
by the DHCP server in the router. Next morning when I connect at work,
dhclient immediately gives me the same IP.
Sep 8 08:44:18 othello dhclie
Hi!
Under Debian woody I had a working prism54 install. I updated to sarge
and the card isn't working any more. The problem seems to be related
to the fact, that when I hotplug the card the system tries to load a
sound module.
Any suggestion what I could do?
Here some further information. Please
16 matches
Mail list logo
