Hi Matias,
> ( If I understand you, you are not using pppoe, you are trying to route the
> packets, is it ok? ).
>
Yes.
> You should have a rule in the output chain that ACCEPT packets to the
> destination ( 0.0.0.0 or what you want ) for the interface eth0.
> In your output chain you only accept
Hi Markus,
The packets go trought eth0 interface, You show it in the other email.
>route
>Kernel IP Routentabelle
>ZielRouter Genmask Flags Metric RefUse Iface
>192.168.1.254 * 255.255.255.255 UH0 00 eth0
>192.168.2.0 *
Hi Markus,
The packets go trought eth0 interface, You show it in the other email.
>route
>Kernel IP Routentabelle
>ZielRouter Genmask Flags Metric RefUse Iface
>192.168.1.254 * 255.255.255.255 UH0 00 eth0
>192.168.2.0 *
> I think that your problem is that you have some filter in your output chain
> of you firewall configuration.
> If you use iptable, you can view the filter with the command "iptables -L
> OUTPUT -n -v"
This is the output - seems to be completely open:
iptables -L OUTPUT -n -v
Chain OUTPUT (polic
> I think that your problem is that you have some filter in your output chain
> of you firewall configuration.
> If you use iptable, you can view the filter with the command "iptables -L
> OUTPUT -n -v"
This is the output - seems to be completely open:
iptables -L OUTPUT -n -v
Chain OUTPUT (polic
Hi Markus,
I think that your problem is that you have some filter in your output chain of
you firewall configuration.
If you use iptable, you can view the filter with the command "iptables -L OUTPUT
-n -v"
regards,
Matias Lambert
Markus Lechner wrote:
> Hello,
>
> first, i'm not on this list, so
> 192.168.1.0 is my net.
> Starting IP Address : 192.168.0.100
Should this be the same?
(Or show us your ifconfig.)
Jeremy C. Reed
...
BSD software, documentation, resources, news...
http://bsd.reedmedia.net/
> > 192.168.1.0 is my net.
> >
> > Starting IP Address : 192.168.0.100
>
> Should this be the same?
>
> (Or show us your ifconfig.)
>
Ah, this is a relict from the original address of the router - it was
192.168.0.1. But this should not be a problem - DHCP is disabled, so the
range is not a param
Hi Markus,
I think that your problem is that you have some filter in your output chain of
you firewall configuration.
If you use iptable, you can view the filter with the command "iptables -L OUTPUT
-n -v"
regards,
Matias Lambert
Markus Lechner wrote:
> Hello,
>
> first, i'm not on this list, so
Hello,
first, i'm not on this list, so please cc me if you think you know what my
problem is.
I have a dlink DI-804 switch/DSL-Router and want to use it without it's
integrated DHCP funktionality.
So i disabled DHCP.
I can ping it, use it's web-interface to configure it or do this via it's
t
> > 192.168.1.0 is my net.
> >
> > Starting IP Address : 192.168.0.100
>
> Should this be the same?
>
> (Or show us your ifconfig.)
>
Ah, this is a relict from the original address of the router - it was
192.168.0.1. But this should not be a problem - DHCP is disabled, so the
range is not a param
> 192.168.1.0 is my net.
> Starting IP Address : 192.168.0.100
Should this be the same?
(Or show us your ifconfig.)
Jeremy C. Reed
...
BSD software, documentation, resources, news...
http://bsd.reedmedia.net/
--
To UNSUBSCRIBE, e
Hello,
first, i'm not on this list, so please cc me if you think you know what my
problem is.
I have a dlink DI-804 switch/DSL-Router and want to use it without it's
integrated DHCP funktionality.
So i disabled DHCP.
I can ping it, use it's web-interface to configure it or do this via it's
t
13 matches
Mail list logo
