On 17/12/19 5:06 pm, Richard Hector wrote:
> Hi all,
>
> I've got a networking issue that's confusing me.
Got it, I think.
I had previously been applying rules before switching to iptables-legacy
- so I'd been adding nftables rules. Then I switched, without flushing
(or rebooting), so both
Hi all,
I've got a networking issue that's confusing me.
When I try to ssh out, I can see the packets being accepted by the rule
in the OUTPUT chain, but I can't see them with TCPDUMP. Nothing is
hitting the rules in the nat POSTROUTING chain, either.
I can see from the ACCEPT rule (in the
Cameron Kerr [EMAIL PROTECTED] writes:
I installed Stable, got the interfaces up and running, both interfaces
work fine. I enable /proc/sys/net/ipv4/ip_forward (via
/etc/network/options, and manually), in order to enable routing of the two
subnets.
What's Stable?
Heres the topology
Hello, I'm trying to set up a router for my friend (he wants to firewall
his forwarded ports from the ADSL router, and prioritize traffic).
I installed Stable, got the interfaces up and running, both interfaces
work fine. I enable /proc/sys/net/ipv4/ip_forward (via
/etc/network/options, and
Mike,
so...did you find a solution?
On 14 Aug 2001 05:51:16 +, john smith wrote:
Something's weird..whenever I log into a console and connect to the
internet
I get this: (from syslog and messages too) continuously while I am
connected
to the internet
LEN=28 TOS=0x00 PREC=0x00
I see...so what is the problem and how do I fix it?
A long time ago, in a galaxy far, far way, someone said...
Something's weird..whenever I log into a console and connect to the
internet
I get this: (from syslog and messages too) continuously while I am
connected
to the internet
On 15 Aug 2001 04:46:37 +, john smith wrote:
Mike,
so...did you find a solution?
I just added a ipchains firewall rule to block igmp (protocol 2 packets)
going to 224.0.0.1 from anywhere and not log. ie:
ipchains -I input -p igmp -d 224.0.0.1
No more annoying packet logs. I'm more
I am not sure where they come from and I am using iptables...
On 15 Aug 2001 04:46:37 +, john smith wrote:
Mike,
so...did you find a solution?
I just added a ipchains firewall rule to block igmp (protocol 2 packets)
going to 224.0.0.1 from anywhere and not log. ie:
ipchains -I
On 15 Aug 2001 05:06:52 +, john smith wrote:
I am not sure where they come from and I am using iptables...
On 15 Aug 2001 04:46:37 +, john smith wrote:
Mike,
so...did you find a solution?
I just added a ipchains firewall rule to block igmp (protocol 2 packets)
Something's weird..whenever I log into a console and connect to the internet
I get this: (from syslog and messages too) continuously while I am connected
to the internet
LEN=28 TOS=0x00 PREC=0x00 TTL=1 ID=36242 PROTO=2
Aug 13 22:52:28 wats kernel: IN=ppp0 OUT= MAC= SRC=209.247.5.159
On 14 Aug 2001 05:51:16 +, john smith wrote:
Something's weird..whenever I log into a console and connect to the internet
I get this: (from syslog and messages too) continuously while I am connected
to the internet
LEN=28 TOS=0x00 PREC=0x00 TTL=1 ID=36242 PROTO=2
Aug 13 22:52:28 wats
A long time ago, in a galaxy far, far way, someone said...
Something's weird..whenever I log into a console and connect to the internet
I get this: (from syslog and messages too) continuously while I am connected
to the internet
LEN=28 TOS=0x00 PREC=0x00 TTL=1 ID=36242 PROTO=2
Aug 13
Sorry to insist, but does somebody reading this mailing
list have any ideas of the way to resolv this problem.
Or can you give me links or else to help me !
It a project on with I had to figth for Linux to be
considered as an alternative rather than a commercial
router product ! It would be a
On Fri, Apr 20, 2001 at 09:58:02AM +, fr ml wrote:
Sorry to insist, but does somebody reading this mailing
list have any ideas of the way to resolv this problem.
Or can you give me links or else to help me !
It a project on with I had to figth for Linux to be
considered as an
Hi,
I have some troubles with kernel routes on my Debian Linux
box (Ip @ 192.168.1.100).
This message migth not be a particular debian problem,
but I don't know other mailing list that could help me !
So, I've got two default gateway
Route Gateway Metric
default 192.168.1.254 0
default
Quoting Derrick (Thrawn01) ([EMAIL PROTECTED]):
I have a debian machine on a network, and has a modem.
Both of theses links could be up at anytime. when the ppp link is down i
wan't to use a gatway on the network to access.
but when the ppp is up I wan't it to access the ppp first before
I have a debian machine on a network, andhas
a modem.
Both of theses links could be up at anytime. when
the ppp link is down i wan't to use a gatway on the network to
access.
but when the ppp is up I wan't it to access the ppp
first before it trys the network.
I thought about seting up my
I'm having trouble with adapting the ISDN device to a 2.0.38 system. A
helpful person told me that the routing table lacks of some
information but he couldn't help me further.
The kernel correctly detects the AVM ISDN PCI device .
Hoping that Debian users have more knowledge in system internals
On Thu, Oct 19, 2000 at 12:49:57PM +0200, robert_wilhelm_land wrote:
I'm having trouble with adapting the ISDN device to a 2.0.38 system. A
helpful person told me that the routing table lacks of some
information but he couldn't help me further.
...
GOOFY:[rland] #route -n
Kernel IP
Phil wrote:
GOOFY:[rland] #route -n
Kernel IP routing table
Destination GatewayGenmask Flags Metric RefUse Iface
192.168.1.0 0.0.0.0255.255.255.0 U 0 03 eth0
127.0.0.00.0.0.0255.0.0.0 U 0 02 lo
Would someone
I'm having some problems getting my local network up and running again ever
since I've upgraded my system from RH5.1 to Debian 2.1. Even ping cannot get
throught to my local network... here's my routing table and eth0 configuration
Destination Gateway Genmask Flags Metric Ref
Loek Engels wrote:
I'm having some problems getting my local network up and running again ever
since I've upgraded my system from RH5.1 to Debian 2.1. Even ping cannot get
throught to my local network... here's my routing table and eth0 configuration
Destination Gateway Genmask
I have got a problem here that's been driving me nuts for about a week or so.
I did a dselect upgrade last week and now I can no longer reach sites that are
beyond my local subnets.
I can ping any of the machines on my little toaster-box home network.
I can ping loopback.
I can ping any of the
Thanks, I feel pretty dumb for not looking at poff. I had a file called
ppp.info that contains my current ( dynamic) ip address.
The suggestion that it is timing problem may be correct. It is able to
connect with either pon or diald, but diald is never successful after
getting my pap
I wrote:
pppd looks in /var/run to find out how many ppp's are running.
That should read: poff looks in ...
--
John Hasler
[EMAIL PROTECTED] (John Hasler)
Dancing Horse Hill
Elmwood, WI
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] .
Trouble?
I have a similar? problem. After a system crash from disk errors, a
working diald/ppp setup will not connect correctly. The error message
received is serial line looped back. I could not find a description of
this message anywhere. After uninstalling diald and using pon, I am
connected now.
Joe Stewart writes:
After a system crash from disk errors, a working diald/ppp setup will not
connect correctly. The error message received is serial line looped
back. I could not find a description of this message anywhere.
This should be in a FAQ somewhere. It almost always means that ppp
This did the trick. Thanks Phil!
This disrupted my operations here for a few days, and seems like it could
impact other people upgrading to hamm from bo. So should I file a bug
report on this, and if so how do I do it?
--ken
I very recently upgraded my home system from bo to hamm. As soon
There were some problems reported with the /etc/nsswitch.conf.
The networks line says files dns which means that when resolving a
network address, libc will try first /etc/networks, then ask on DNS.
However route tries to resolve the net diald passes to it and blocks in
there (the
Philippe Troin [EMAIL PROTECTED] writes:
On Tue, 04 Nov 1997 10:45:10 CST Ken Lauffenburger ([EMAIL PROTECTED]) wrote:
Hello,
I very recently upgraded my home system from bo to hamm. As soon
as I installed the netbase package, diald stopped working. The
PPP link would connect, but
Oops! My so-called solution has a symptom looking for a problem.
From the syslog:
kernel: sl0: transmit timed out, bad line quality?
kernel: sl0: transmit timed out, bad line quality?
last message repeated 2 times
[EMAIL PROTECTED] route -n
Kernel IP routing table
Destination Gateway Genmask
these messages too. But when I cleared up my
routing problems by changing the nsswitch.conf file, those messages
disappeared also. I haven't received a good explanation for them yet.
Maybe you have an additional problem with your diald/ppp configuration?
I'll be happy to share my configuration files
On Tue, 04 Nov 1997 10:45:10 CST Ken Lauffenburger ([EMAIL PROTECTED]) wrote:
Hello,
I very recently upgraded my home system from bo to hamm. As soon
as I installed the netbase package, diald stopped working. The
PPP link would connect, but the PPP link no longer was selected
as the
Hello,
I very recently upgraded my home system from bo to hamm. As soon
as I installed the netbase package, diald stopped working. The
PPP link would connect, but the PPP link no longer was selected
as the default route. However, I could establish the link using
the 'pon' command. (I was
On Jun 24, Shaya Potter wrote
:
: I somehow did something that affects route. I have the simple settings
: that the debian installer automatically sets up in my /etc/init.d/network
: file.
:
: This ifconfig's the eth0 interface appropriatly, set's up the network, but
: when it tries to set the
I don't know what happened, but everything works now, my network.bak
script (the original one) works perfectly, and the modified version
doesn't work. well, since everythings working fine right now (crossed
fingers), hopefully it will stay that way.
On Wed, 25 Jun 1997, Heiko Schlittermann
I somehow did something that affects route. I have the simple settings
that the debian installer automatically sets up in my /etc/init.d/network
file.
This ifconfig's the eth0 interface appropriatly, set's up the network, but
when it tries to set the default route, I get.
chum# route add
On Sat, 21 Dec 1996, Kevin Traas wrote:
The router at the ISP is pretty non-configurable. It only supports
dynamic routing, so the only thing that can be configured on it is the
IP address of the port I'm connecting to. All routing information is
supposed to be learned via RIP. But,
I do have access to their router, but there is nothing, besides the
interface IP address, to configure on it - all routing is learned via RIP.
I can't establish any static routes and it's not learning them dynamically
and I can't figure out why. I don't want Box_A to be a firewall (yet)
I do have access to their router, but there is nothing, besides the
interface IP address, to configure on it - all routing is learned via
RIP.
I can't establish any static routes and it's not learning them
dynamically
and I can't figure out why. I don't want Box_A to be a firewall
[EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
On Sat, 21 Dec 1996, Kevin Traas wrote:
The router at the ISP is pretty non-configurable. It only supports
dynamic routing, so the only thing that can be configured on it is the
IP address of the port I'm connecting to.
-BEGIN PGP SIGNED MESSAGE-
On Sat, 21 Dec 1996, Kevin Traas wrote:
The router at the ISP is pretty non-configurable. It only supports
dynamic routing, so the only thing that can be configured on it is the
IP address of the port I'm connecting to. All routing information is
I'm having some problems getting my network connected to the Internet and I'm
hoping you can help I'm pretty good at TCP/IP, but something with the
routing has got me stumped.
PLEASE HELP! grin
I've got two Linux boxes connected via a serial cable (about 50'). The first
box (Box_A) is
-BEGIN PGP SIGNED MESSAGE-
On Mon, 11 Nov 1996, Kevin Traas wrote:
Whenever I try viewing the current routing tables by typing route or
netstat -r at the command prompt I only get the standard header - no
information. The command just hangs and I must Ctrl-C to get out. I've
Whenever I try viewing the current routing tables by typing route or
netstat -r at the command prompt I only get the standard header - no
information. The command just hangs and I must Ctrl-C to get out. I've
heard from someone that this occassionally happens to him - but I've never
On Mon, 11 Nov 1996 21:00:11 PST Kevin Traas ([EMAIL PROTECTED])
wrote:
Whenever I try viewing the current routing tables by typing route or
netstat -r at the command prompt I only get the standard header - no
information. The command just hangs and I must Ctrl-C to get out. I've
46 matches
Mail list logo
