Eureka!
Determined to resolve this issue, I attempted to access the weblet over
the VPN, and checked to see if any log file was touched.
Just one. daemon.log. Which told me that I had failed to place a
carriage return after the second entry in hosts.allow for my ipsec'd
subnet. One carria
gt; loc fw ACCEPT
>
> and the same for all invoqued interfaces wlan0 and wlan1 zone aliases.
>
> I hope this could help. If not, let me know what you want more.
>
> Good Luck.
> Best Regards,
> Francois BERGERET,
> France.
>
> > -Message d&#
Sean:
I have a very similar setup to the one you propose. The only difference
is that my internet is delivered via dialup instead of cable modem. Other
than that (and that's a fairly small distinction), I've managed to get it
up and running (with a goodish amount of help from the other list
The 192.168.3.0 subnet is my IPSec vpn. Hence, in /etc/shorewall/rules:
ACCEPT loc fw tcp 80
ACCEPT vpn fw tcp 80
No weblet over the vpn, and no hits in the firewall log, so I surmise that
it's not a Shorewall issue. But I've been wrong before.
-
Tried both of these before posting. 192.168.1.0 is my wired subnet,
192.68.3.0 is my wireless subnet.
hosts.allow:
ALL: 192.168.1.0/255.255.255.0
ALL: 192.168.3.0/255.255.255.0
sh-httpd.conf (pertinent parts)
# Who are we - used for CGI scripts
SERVER_NAME=ice.rawdata.lab
SERVER_ADDR=192.168
I have finally (through the alignment of planets, presumably) set up IPSec
on the wifi connection to my Bering box. All works well (browse Samba
shares with no problems, net access, etc. The only thing that fails to
load over the ipsec tunnel is the weblet. It works fine from any wired
local
Folks, I have just about everything up and running. I'd like to thank
everyone for their input thus far.
Just minor issues:
Since my net connection is dialup, Shorewall chokes on the
ppp0ipsec0
line in my masq file, since the ppp connection isn't up at boot time. Can
someone help with
Lynn:
I've read about the differing subnets; in fact, it was your doc that has
helped to get me thus far. However, changing the laptop IP to
192.168.3.9 produces the following result:
Laptop: "Negotiating IP Security" ad infinitum
Bering auth.log:
Dec 6 18:15:11 ice pluto[16903]: "w2kwifi"
Good day to all:
I'm still fighting the good fight attempting to configure IPSec over my
wireless link. For those playing along at home, the pertinent machines
are:
ice 192.168.1.99
voodoo 192.168.1.1
hex 192.168.1.3
hijinx 192.168.1.69
Alright. hijinx is my wifi router; since ic
Good day to all:
As the subject might imply, I am trying to get an IPSec wireless VPN up
and running on my Bering 1.2 box. Before this venture, the Bering box (ice)
served as a dial-up router/firewall for my home lan. A little background info:
ice 192.168.1.99
voodoo 192.168.1.1
hex
Thank you for your reply. I neverintended to back up all of the files in
the ramdisk, just the .lrps and such. i.e., to
mount -t msdos /dev/hda1 /mnt
and then copy everything from the /mnt directory to another machine.
Since I'm doing this from a Windows machine, I found WS_FTP, and it does
q
I finally have my Bering 1.0 stable box running just the way I like it,
booting from the hard drive. Now... what's the easiest way to back it
up? I have sftp installed, but it doesn't seem to allow multiple file
downloads, and I'd rather not get one... file... at a time.
I could back it up
12 matches
Mail list logo
