[ncolug] Re: Endian Firewall Question
- From: "M. Knisely" <charon79m@xxxxxxxxx>
- To: ncolug@xxxxxxxxxxxxx
- Date: Sat, 24 Mar 2012 10:11:48 -0400
In an effort to keep the Internet clean of broken links, here's a new link
to this old file.
http://dl.dropbox.com/u/9141946/tools.tar.gz
I actually needed this again a few weeks ago, and had to go find it off
archived media. For reference, this still works with even the most recent
version of Endian.
Mike K.
On Wed, Aug 8, 2007 at 10:49 PM, Michael Knisely <
mknisely@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
> I knew I was forgetting something.
>
> Grab this file:
> http://www.mrknisely.is-a-**geek.org/tools.tar.gz<http://www.mrknisely.is-a-geek.org/tools.tar.gz>
>
> Toss it on your endian. When you unzip it you'll find a few apps, iftop
> and htop; both are great. There is also a lib you need.
>
> Toss the apps in one of your binary locations in the path. Toss the lib
> in the associated directory and you're golden.
>
> The setterm app I used to shut off the "sceensaver" that shuts off the
> screen in 5 minutes. I've forgotten the command to do it, but you'll have
> the app if you need it.
>
> Hope this is helpful.
>
>
> Mike K.
>
> Michael Goracke wrote:
>
>> I got it up and running. I connected it to my router (DHCP Disabled)
>> instead of the switch and it's working fine.
>>
>> Hey Mike K.; Was the network monitoring command that you were talking
>> about "iftop"? I'm trying to run it on the console and it's not found.
>> Do I need to install it somehow?
>>
>> Mike G.
>>
>>
>>
>> On Tue, 2007-08-07 at 12:03 -0400, Michael Goracke wrote:
>>
>>> I changed the router IP to 192.168.1.7 and turned off DHCP before
>>> installing.
>>> I reinstalled Endian and was able to get to the set up wizard again
>>> through the web browser but it acts like it doesn't finish applying the
>>> changes (step 7). I'm able to log on to the console with the new root
>>> password but still can't access the web interface.
>>> I "redownloaded" the ISO and burned it again thinking maybe I had bad
>>> media and still get the same results.
>>> I'm going to try using a different switch this evening and see if maybe
>>> that's the culprit.
>>>
>>>
>>> Mike G.
>>>
>>>
>>> On Tue, 2007-08-07 at 08:33 -0400, Michael Knisely wrote:
>>>
>>>> Sounds like when you associated the network cards the interface you
>>>> were using to get to it was assigned to the "RED" interface.
>>>>
>>>> You should be able to ping the inside interface by default. Also, you
>>>> should be able to web to the internal IP directly.
>>>>
>>>> Does Endian hand out your addresses on you LAN? If so, are you getting
>>>> a DHCP server with the right IP?
>>>>
>>>> Next up, what address space are you handing out? Might it be that you
>>>> have another device on your network that is using the same IP address? For
>>>> example, if you setup your Endian box to be 192.168.1.1 and you have a
>>>> Linksys router that also thinks that it is 192.168.1.1 on it's LAN
>>>> interface the one that ARPs back to you that it own 192.168.1.1 is the one
>>>> that you will try to get to. Since you can't ping the address nor web into
>>>> it, I doubt this is the issue, but I figure I'd ask anyway.
>>>>
>>>> Mike K.
>>>>
>>>> Michael Goracke wrote:
>>>>
>>>>> I've installed Endian 2.1.2 on a 800 MHz PIII, 512 MB's of RAM and two
>>>>> network cards (one NetGear and one Linksys to avoid confusion). I have
>>>>> it connected to the network via a Linksys 16 port workgroup switch (not
>>>>> using the "uplink" port).
>>>>> I'm able access the set up wizard through the web browser interface
>>>>> from another computer on the network. I'm able set the red and green
>>>>> interfaces and change the admin and root passwords for the console and
>>>>> web interface. After the set up wizard completes I'm unable to access
>>>>> the admin page again or ping the address I set for the green interface.
>>>>>
>>>>> What am I missing?
>>>>>
>>>>> Mike Goracke
>>>>>
>>>>>
>>>>> To unsubscribe send to ncolug-request@xxxxxxxxxxxxx with
>>>>> 'unsubscribe' in the Subject field.
>>>>>
>>>>>
>>>> To unsubscribe send to ncolug-request@xxxxxxxxxxxxx with 'unsubscribe'
>>>> in the Subject field.
>>>>
>>>
>>> To unsubscribe send to ncolug-request@xxxxxxxxxxxxx with 'unsubscribe'
>>> in the Subject field.
>>>
>>
>>
>> To unsubscribe send to ncolug-request@xxxxxxxxxxxxx with 'unsubscribe'
>> in the Subject field.
>>
>>
>
> To unsubscribe send to ncolug-request@xxxxxxxxxxxxx with 'unsubscribe' in
> the Subject field.
>
>
Other related posts:
