News: This forum is now permanently frozen.
linktree m0n0wall Forum  >  m0n0wall Support (English)  >  General Questions
linktree Topic: not responding to ping on LAN interface
Pages: [1]
Topic: not responding to ping on LAN interface  (Read 1745 times)
« on: June 29, 2009, 22:36:26 »
bazzapage *
Posts: 5
Yesterday my m0n0wall 3.16b on VMWare worked fine. It was at the end of an IPSEC tunnel.
I rebooted the VM Host, now I can't see the LAN interface anymore (ping or webgui). I have tried a number of things:
- rebooting several times
- changing the LAN to a different ip address
- setting a static ARP on my PC to the MAC address of the LAN interface
- disabling and re-enabling the VMWare virtual NIC

Although somewhat unconventional, I have both interfaces on the same LAN, as all it is is an IPSEC termination point. Not using any other firewall or routing functioanlity. I can see the WAN interface on the network although obviously it doesn't repond to a ping.

The IPSEC tunnel isn't running either because it needs traffic from the LAN side to get it up.

I truly cannot understand why something that was working fine would stop after a reboot. Can anybody give me more hints or a possible solution?
« Last Edit: June 29, 2009, 23:17:17 by bazzapage »
« Reply #1 on: June 30, 2009, 13:03:08 »
bazzapage *
Posts: 5
I fixed this by resetting to factory defaults and starting fresh. All I can think is that at some stage I must have made a config change that hadn't happened yet, waiting to reboot. Then I rebooted, and the latent change stuffed the m0n0wall.
Aah, another several hours wasted, never to be seen again...
This time I snapshotted the 'known good' config in VM. I'll back up the config now too.
 
Pages: [1]
 
 
Powered by SMF 1.1.20 | SMF © 2013, Simple Machines