Hi Martin,
It is the 192.168.10.0 subnet behind office fw that was the issue
As for route commands in the winxp config, I tried several lines:
route 192.168.10.0 255.255.255.0
(default next hop should be second parm of winxp ifconfig line =
10.1.1.1, see below)
route 192.168.10.0 255.255.255.0 1
Hi Richard,
Tibbs, Richard wrote:
Thanks very much, Tom. That route on officefw was all that was needed.
One additional note:
Although I tried this command in the winxp openvpn.conf
route 192.168.10.0 255.255.255.0
It did not insert a route into winxp's table (see below)
I had to do that by hand.
S
Thanks very much, Tom. That route on officefw was all that was needed.
One additional note:
Although I tried this command in the winxp openvpn.conf
route 192.168.10.0 255.255.255.0
It did not insert a route into winxp's table (see below)
I had to do that by hand.
Still mysterious on that one.
Ri
Tibbs, Richard wrote:
>
>
> firewall: -root-
> # ip route
> 10.1.10.1 dev tun0 proto kernel scope link src 10.1.10.2
> 192.168.1.0/24 via 10.1.10.1 dev tun0
> 192.168.10.0/24 dev eth1 proto kernel scope link src 192.168.10.254
> 137.x.y.0/24 dev eth0 proto kernel scope link src 137.x.y
Yes, that is correct no drops/rejects from either fw.
And, yes, I was assuming that the home fw was the problem... (which
would be the left fw in my ascii art, but lets not quibble ;-)
config files, route table and pings from office fw below.
Thanks for all this help, Tom.
Rick
So here is t
Tibbs, Richard wrote:
> I see no reject or drop messages in Shorewall.log.
On either firewall/router, right.
> BTW, thanks for your clarification on transitivity I assume that
> applies also to policy entries.
Yes.
>
> Is it possible that Shorewall or the routing process could be silently
I see no reject or drop messages in Shorewall.log.
BTW, thanks for your clarification on transitivity I assume that
applies also to policy entries.
Is it possible that Shorewall or the routing process could be silently
dropping some packets?
Rick.
The various Shorewall files are
/etc/Shore
Tom Eastep wrote:
> Tibbs, Richard wrote:
>
>>Dear list, sorry for long post.
>>Bottom line is I can ping everything except machines on 192.168.10.0
>>from winxp.
>>
>>I have the config below, with this arrangement:
>>winxp -- wlan --Linuxfw1 -- Internet -- LinuxFw2 -- 192.168.10.0/24
>>openv
Tibbs, Richard wrote:
>
> Dear list, sorry for long post.
> Bottom line is I can ping everything except machines on 192.168.10.0
> from winxp.
>
> I have the config below, with this arrangement:
> winxp -- wlan --Linuxfw1 -- Internet -- LinuxFw2 -- 192.168.10.0/24
> openvpn openv
Dear list, sorry for long post.
Bottom line is I can ping everything except machines on 192.168.10.0
from winxp.
I have the config below, with this arrangement:
winxp -- wlan --Linuxfw1 -- Internet -- LinuxFw2 -- 192.168.10.0/24
openvpn openvpnopenvpn
2.0.15beta
Tibbs, Richard wrote:
Charles,
I tried everything you suggested, but to no avail. Any ideas what to try
next?
I still think you've got a problem with properly setting up the connection
on both ends (check especially the required service-packs, updates, and
registry patches required to implement N
I have the following kernel and modules installed:
Kernel:
Linux version 2.2.19-3-LEAF ([EMAIL PROTECTED]) (gcc version 2.7.2.3) #1 Sat
Dec 1
12:15:05 CST 2001
Installed Modules:
ip_masq_vdolive 1180 0
ip_masq_user3708 0 (unused)
ip_masq_raudio 2980 0
ip_masq_
12 matches
Mail list logo
