News: This forum is now permanently frozen.
Pages: [1] 2
Topic: Please Help - Weird Issue  (Read 6820 times)
« on: February 09, 2011, 20:55:24 »
andy8 *
Posts: 30

Hi,

I have previously written monowall on a CF card and used in on an ALIX board.
But after a few weeks I tried connecting my board to the PC and couldn't connect to the (192.168.1.1)
configuration site.

So I tried writing the embedded image on the CF card again and many more times repeatedly with no success
of entering the configuration mode on site (192.168.1.1)

My usual practice is to connect the CF card on a card reader. Then entering the command :
gzcat embedded-1.32.img | dd of=/dev/disk1s1 bs=16k on terminal application.
Then there would be a message denoting a successful data transfer to the CF card.

After that the card is plugged into the board and connected to the laptop/PC - and then I should be able to
connect to site 192.168.1.1.
Although it worked for me previously; but for some mysterious reasons , I couldn't now and I don't know the cause.

B.T.W my system is a Mac OSX. What could be the issue here ?
Please help
« Reply #1 on: February 09, 2011, 23:26:55 »
Fred Grayson *****
Posts: 994

Although the default LAN IP is 192.168.1.1, I don't think it will work until you have defined interfaces. Did you do that?

--
Google is your friend and Bob's your uncle.
« Reply #2 on: February 10, 2011, 00:32:39 »
andy8 *
Posts: 30

Defining  interface..
How do I do that ?..

Any help would be greatly appreciated..


« Reply #3 on: February 10, 2011, 01:36:00 »
Fred Grayson *****
Posts: 994

Let's back up a bit.

Which image are you writing to CF for use on a PC?

--
Google is your friend and Bob's your uncle.
« Reply #4 on: February 10, 2011, 20:08:07 »
andy8 *
Posts: 30

HI,

The  image  is  an  embedded-1.32 used on ALIX2D3 board.
The  image  is  written  onto  the  CF  card  on  a  card  reader  and  the  system  used  is  MAC  OSX.
« Reply #5 on: February 10, 2011, 20:20:51 »
Fred Grayson *****
Posts: 994

I am still not sure exactly what you are trying to do.

What machine will the CF card be plugged into? If it's not an IBM type PC, it will not work.

Also, an embedded image is not the one to use on an IBM type PC, you need the generic PC image for that.

--
Google is your friend and Bob's your uncle.
« Reply #6 on: February 10, 2011, 22:06:01 »
andy8 *
Posts: 30

The  CF  card  is  plugged  into  an  embedded  ALIX2D3  board.
It  was  working  perfectly  well  for  me  until  recently  as  I'm  unable  to  enter  
the  configuration  mode  on  192.168.1.1 - the  [WebGUI]

The  image  format  is  correct  because  it's  meant  for  embedded  platforms  which  I'm  currently  using.
« Last Edit: February 10, 2011, 22:22:00 by andy8 »
« Reply #7 on: February 10, 2011, 22:28:53 »
Fred Grayson *****
Posts: 994

Are you following the installation instructions here?:

http://m0n0.ch/wall/installation_embedded.php

I don't have the hardware to run embedded.

On x86 PC, you have to have a monitor and keyboard attached to do the minimal initial configuration. You have to tell it which ethernet interface will be LAN, which one will be WAN, and which if any will be OPT. There are no default settings for this. Once initially configured, you can detach the monitor and keyboard and continue with the rest of configuration thru the GUI via another LAN PC and web browser.

On embedded, I am fairly certain you need to do initial configuration thru the serial console port. This is also how you can reset the LAN IP address if you forgot it, or reset it to the as freshly installed defaults.

Try talking to it via the console.

--
Google is your friend and Bob's your uncle.
« Reply #8 on: February 10, 2011, 22:40:05 »
andy8 *
Posts: 30

I'm  currently  trying  to  connect  to  my  embedded  board  through  a  console (serial-usb)  connection.
But  being  unable  to  even  enter  the  initial  configuration  screen  makes  it  tougher  to  reset  LAN  IP  address.

I've  followed  exactly -  the  tutorial  presented  on  monowall  site  for  embedded  system.
I  have  made  it  work  in  the  past;  but  the  present  issue  is  quite  baffling.
« Last Edit: February 10, 2011, 22:43:36 by andy8 »
« Reply #9 on: February 11, 2011, 03:59:54 »
Fred Grayson *****
Posts: 994

I'm not sure what the exact requirements are for serial console comms with embedded image.

Something tells me it's serial to serial, and maybe even null modem at that, but the exact spec seems to be undocumented. Not setting the correct serial comm parameters is all it takes to be hosed. Not sure your serial-USB fits in or not.

Maybe someone with more expertise on embedded will chime in.


--
Google is your friend and Bob's your uncle.
« Reply #10 on: February 11, 2011, 10:01:08 »
andy8 *
Posts: 30

I'll try changing the current serial-usb with another one which comes along with a driver.
That could probably solve the issue.

But, Thank You for your help along the way. Really appreciate it.
« Last Edit: February 11, 2011, 22:13:08 by andy8 »
« Reply #11 on: February 13, 2011, 11:56:21 »
brushedmoss ****
Posts: 446

There is a whole section on this in the handbook.

http://doc.m0n0.ch/quickstartwrap/#id11553596

If your board is working, you should get bios info etc via serial at power on, no matter what is wrong with monowall, so start there to get your console working.
« Reply #12 on: February 21, 2011, 11:33:26 »
andy8 *
Posts: 30

Hello,

First  of  all  thank  you  to  everyone  who  has  been  very  helpful  in  
helping  me  to  solve  my  problem.

But,  I  have  not  been  able  to  get  my  Monowall  system  running.
I  still  cannot  enter  the  webGUI  of  monowall  on  192.168.1.1
I  have  already  used  the  steps  provided  on  the  handbook  and  etc.

I'm  just  running  out  of  ideas  at  the  moment. I  tried  to  ping  192.168.1.1  and  
the  response  I  got :    

dinesh-andys-macbook-pro:~ dineshandy$ ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
ping: sendto: No route to host
Request timeout for icmp_seq 4
ping: sendto: Host is down
Request timeout for icmp_seq 5
ping: sendto: Host is down

It  seems  that  the  embedded  PC  is  not  up. But  since,  the  interface  is  fine  (LAN),
what  could  cause  a  problem ?
« Last Edit: February 21, 2011, 12:32:31 by andy8 »
« Reply #13 on: February 21, 2011, 15:07:59 »
Fred Grayson *****
Posts: 994

Just a sanity check at this point.

What if anything has changed since this was working last?

Are you using the same identical CF card as before?

Is there any way to boot the ALIX into BIOS and have a look around; does it even have an accessible BIOS?

--
Google is your friend and Bob's your uncle.
« Reply #14 on: February 21, 2011, 17:10:53 »
andy8 *
Posts: 30

The  only  thing  that  changed  since  the  last  time  it  worked  was (a  re-install  of  my  Mac OSX).
I've  used  the  same  CF  card. I've  also  changed  the  CF  card  to  another  one  assuming  something
may  have  gone  wrong  with  the  card  but  still  failed  in  getting  it  to  run.

I've  tried   booting  on  BIOS  mode  using  Hyperterminal  on  correct  baud  rates  and  still  failed.
It  is  supposed  to  be  bootable  on  BIOS  mode  but  its  not  working  for  me.

I'm  using  a  proper  serial-USB  cable,  could  there  be  any  issues  with  driver ?
But,  apparently  there  drivers  are  fine  -  I'm  using  Prolific  Serial-USB  driver.
 
 
Pages: [1] 2
 
 
Powered by SMF 1.1.20 | SMF © 2013, Simple Machines