As an addendum,
I have tracked down the random breaks in communications to the remote
box rebooting. After a bit more testing I found that my m0n0-4511 was
rebooting periodically as well. Upon a quick flash back to pb18r522 and
the rebooting problem has reared its ugly head again. It is only when
utilizing encryption.
I can transfer up firmware images without a problem as it is not
dependent upon the IPSEC tunnel. As soon as anything more demanding
than icmp traffic is generated through the tunnel the remote m0n0-4511
reboots itself. It sounds like a hardware problem, the kind I really
love being a poor student.
Another oddity is that I can not reach a remote host by ping unless they
attempt to ping me back, then the connection is established and
everything ok. This leads me to believe that there is a routing problem
somewhere along the way. The route can not be established until both
ends have attempted the connection.
--Michael I.
> -----Original Message-----
> From: Michael Iedema [mailto:iedemam at pluto dot dsu dot edu]
> Sent: Tuesday, November 11, 2003 7:14 PM
> To: m0n0wall at lists dot m0n0 dot ch
> Subject: [m0n0wall] Wireless Bridge Problem
>
>
> Hello all,
> I've setup a wireless bridge between two houses and am having trouble
> getting connectivity.
>
> Setup Breakdown:
>
> Each side has a 4511 rooftop box & a m0n0wall internet
> gateway. Traffic
> destined for the other side's subnet is statically routed up
> to the roof
> to be transmitted across. The wireless devices are WAN, and
> the link is
> being established via IPSEC.
>
>
> Subnets:
>
> Local Subnet 192.168.0.0/24
> Remote Subnet 192.168.2.0/24
> Rooftop Subnet 192.168.50.0/24
>
>
> Problem:
>
> The system logs show that the link is being established correctly. I
> can bring up the remote 4511's m0n0wall GUI (NAT forwarded
> 80). Trying
> to reach a remote host fails indicating a destination host
> unreachable.
>
>
> Tracert:
> Tracing route to 192.168.2.40 over a maximum of 30 hops
>
> 1 <1 ms <1 ms <1 ms m0n0wall.undergroup.com [192.168.0.1]
> 2 1 ms 6 ms 5 ms 192.168.50.2
> 3 192.168.50.2 reports: Destination host unreachable.
>
> Trace complete.
>
> Ping yields the same thing.
>
>
> Hypothesis:
> I believe it to be a firewall problem. In previous versions
> of m0n0wall
> this link was established correctly and network traffic was
> being passed
> correctly. More leaves grew, wireless went away, now the leaves are
> gone and I'm using a newer version of m0n0wall which is not passing
> traffic correctly. With the rather large modifications to
> the firewall
> I'm thinking it is the culprit.
>
> Any thoughts, further explanation needed?
>
> Thanks,
> --Michael I.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
> For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch
>
| 