On Wednesday 13 October 2004 05:45 am, Sebastiaan wrote:
> Hi,
>
> On Wed, 13 Oct 2004, Mark Maas wrote:
> > Thanks for reading!
> >
> > I hope someone can help me with a routing issue:
> >
> > I've attached a situation scetch.
> >
> > The thing is, my road warriors connect via a pptp connection
>
Hi,
On Wed, 13 Oct 2004, Mark Maas wrote:
> Thanks for reading!
>
> I hope someone can help me with a routing issue:
>
> I've attached a situation scetch.
>
> The thing is, my road warriors connect via a pptp connection
> to my VPN server via GW2.
> This fails because the default gateway (GW) on
Thanks for reading!
I hope someone can help me with a routing issue:
I've attached a situation scetch.
The thing is, my road warriors connect via a pptp connection
to my VPN server via GW2.
This fails because the default gateway (GW) on the VPN is
GW1, so all request attempts end up beeing sent t
On Mon, Jan 07, 2002 at 05:57:19PM +, Alan Chandler wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Monday 07 January 2002 2:57 pm, Serge Rey wrote:
snip
> > thanks for the tips. with these and alan's suggestions i've got it
> > working now.
> >
> > one thing i noticed is that
On Sun, Jan 06, 2002 at 10:41:02PM +, Alan Chandler wrote:
|
| On Sunday 06 January 2002 8:22 pm, dman wrote:
| >
| > I wrote /etc/init.d/FIREWALL, a shell script I wrote to configure
| > iptables. Then I added a symlink to it
| >
| > $ ls -l /etc/rc2.d
| > lrwxrwxrwx1 root root
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday 08 January 2002 02:23 pm, dman wrote:
> On Mon, Jan 07, 2002 at 08:59:03PM +, Alan Chandler wrote:
> | On Monday 07 January 2002 7:20 pm, Ron Johnson wrote:
> | > I wonder why you have S39ifupdown, but I have S40networking?
> | > "S40net
On Mon, Jan 07, 2002 at 08:59:03PM +, Alan Chandler wrote:
| On Monday 07 January 2002 7:20 pm, Ron Johnson wrote:
|
| > I wonder why you have S39ifupdown, but I have S40networking?
| > "S40networking start" basically only does "ifup -a". Likewise,
| > "stop" just does "ifdown -a".
|
| I hav
On Mon, Jan 07, 2002 at 02:49:16PM -0600, Ron Johnson did this all over the
keyboard:
> > why do you care about your ip address?
> >
> > iface=
> >
> > ifconfig ${iface} | grep 'inet' | cut -d: -f2 | cut -d " " -f1
>
> So, to block port 1524, I can say
> ipchains -A input -p tcp -s 0/0 1524 -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday 07 January 2002 7:20 pm, Ron Johnson wrote:
> I wonder why you have S39ifupdown, but I have S40networking?
> "S40networking start" basically only does "ifup -a". Likewise,
> "stop" just does "ifdown -a".
I have both - ifupdown just clears
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday 07 January 2002 7:20 pm, Ron Johnson wrote:
>
> However, with a dhcp-assigned fully-routable IP address, how
> can you create rules on it without 1st knowing the address?
You don't need the IP address, just use the -i interface parameter in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday 07 January 2002 01:22 pm, Willi Dyck wrote:
> On Mon, Jan 07, 2002 at 01:20:48PM -0600, Ron Johnson did this all
over the keyboard:
> > However, with a dhcp-assigned fully-routable IP address, how
> > can you create rules on it without 1st k
On Mon, Jan 07, 2002 at 01:20:48PM -0600, Ron Johnson wrote:
| However, with a dhcp-assigned fully-routable IP address, how
| can you create rules on it without 1st knowing the address?
You know the interface, so specify the interface instead. Then you
never need to stick the IP in the firewall
On Mon, Jan 07, 2002 at 01:20:48PM -0600, Ron Johnson did this all over the
keyboard:
>
> However, with a dhcp-assigned fully-routable IP address, how
> can you create rules on it without 1st knowing the address?
> So, mustn't you make it S38firewall?
>
> Of course, if you have a dhcp-assigned a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday 07 January 2002 12:50 pm, Alan Chandler wrote:
> On Monday 07 January 2002 6:32 pm, Ron Johnson wrote:
> > As for the firewall script, I put it in /etc/init.d, and execute
> > it from /etc/init/networking, just after the "ifup -a".
> >
> > If
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday 07 January 2002 6:32 pm, Ron Johnson wrote:
> As for the firewall script, I put it in /etc/init.d, and execute
> it from /etc/init/networking, just after the "ifup -a".
>
> If you have a better place to put it, I'd love to hear it...
>
As I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Maybe the Cox networking in your town isn't up to snuff.
I have a h/w configuration just like yours, using dhcp-client
2.0pl4-2, and it works like a charm.
I did have to create /etc/dhclient.conf :
interface "eth0" {
send host-name "cx9-X
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday 07 January 2002 2:57 pm, Serge Rey wrote:
> On Sun, Jan 06, 2002 at 03:22:13PM -0500, dman wrote:
> > On Sun, Jan 06, 2002 at 09:22:49AM -0800, Serge Rey wrote:
> > | now i'm trying to figure out the best way to automate this. i think my
> >
On Sun, Jan 06, 2002 at 03:22:13PM -0500, dman wrote:
> On Sun, Jan 06, 2002 at 09:22:49AM -0800, Serge Rey wrote:
>
> | now i'm trying to figure out the best way to automate this. i think my
> | problems the last few days were in the sequencing of configuring the
> | following mix of things
> |
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sunday 06 January 2002 8:22 pm, dman wrote:
>
> I wrote /etc/init.d/FIREWALL, a shell script I wrote to configure
> iptables. Then I added a symlink to it
>
> $ ls -l /etc/rc2.d
> lrwxrwxrwx1 root root 20 Aug 19 16:59 S13FIREWALL
On Sun, Jan 06, 2002 at 09:22:49AM -0800, Serge Rey wrote:
| now i'm trying to figure out the best way to automate this. i think my
| problems the last few days were in the sequencing of configuring the
| following mix of things
|
| eth1 - lan
| eth0 - dhcp
| firewall script
|
| the latter runs
On Sun, Jan 06, 2002 at 09:51:07AM +, Alan Chandler wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Saturday 05 January 2002 3:47 pm, Serge Rey wrote:
> > hi,
> >
> ... [snip]
> > i'm wondering if this is a routing problem? this is what the routing
> > table looks like for box
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Saturday 05 January 2002 3:47 pm, Serge Rey wrote:
> hi,
>
... [snip]
> i'm wondering if this is a routing problem? this is what the routing
> table looks like for box C:
[snip]
> any clues as how to debug this further would be most appreciated.
Wh
hi,
i'm working on a new firewall box that will have a cable modem
connection to replace my current box that uses dial up. the cable box
gets its ip via dhcp from @home. for what follows, firewall box on cable
will be referred to as C, firewall on dial-up as D.
the two firewall boxes are running
Subject: routing help
Date: Thu, Jun 17, 1999 at 12:38:14AM -0500
In reply to:Robert Rati
Quoting Robert Rati([EMAIL PROTECTED]):
> I need some help with setting up a firewall for a router. Basically, I
> just want to set it up to forward packets on to other machines
On Thu, Jun 17, 1999 at 12:38:14AM -0500, Robert Rati wrote:
> I need some help with setting up a firewall for a router. Basically, I
> just want to set it up to forward packets on to other machines on the
> network. I read the manpage for ipfwadm, and it looks like ipfwadm -F -p
> deny is where
I need some help with setting up a firewall for a router. Basically, I
just want to set it up to forward packets on to other machines on the
network. I read the manpage for ipfwadm, and it looks like ipfwadm -F -p
deny is where I want to begin. Setting the default rule to deny. Problem
is, when
Hi, folks --
I have successfully set up DHCP client (dhcpcd) on my Debian Linux box. I
was then able to make a connection to my Road Runner service through my
cable modem, and reached machines on the server's network. However, I was
not able to reach beyond the immediate network - I could not se
6520 x4237
[EMAIL PROTECTED], [EMAIL PROTECTED]
--
> From: Randy Edwards <[EMAIL PROTECTED]>
> To: Henrique Almeida <[EMAIL PROTECTED]>
> Cc: Debian User
> Subject: Re: REPOST: Diald routing (Help!)
> Date: Wednesday, July 08, 1998 6:44 AM
>
> > > Diald
i'm having the same problem with slirp/ppp connection (connection gets
dropped). pon scripts log in OK and slirp starts up but LCP negotiation
fails with error message "No Network Protocols Running"
tried disabling 'defaultroute' and adding the default route myself before
running pon, but doing
> > Diald is already dialing when it should but the routing table is not
> > being updated.
I've had the same problem. Somewhere (either a HOWTO or a Linux Journal
article) I
found advice about setting the routing manually. This is what I'm doing now.
In /etc/ppp/ip-up (the script) I put
> Hi!
>
> Im using Debian for a year on 2 of my home boxes. One is my workstation
> and the other is a 486. This second box serves the local net with samba
> and internet connection through masquerading and squid.
>
> Last week I upgraded to 2.0 and started to play with diald so my father
> don't
31 matches
Mail list logo
