* iptables or routing problem
@ 2003-10-22 5:03 Fritz Mesedilla
2003-10-22 5:33 ` netfilter
0 siblings, 1 reply; 7+ messages in thread
From: Fritz Mesedilla @ 2003-10-22 5:03 UTC (permalink / raw)
To: netfilter
I dunno if this is a routing problem or my iptables.
route:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.9.0 * 255.255.255.0 U 0 0 0 eth0
192.168.0.0 * 255.255.0.0 U 0 0 0 eth1
127.0.0.0 * 255.0.0.0 U 0 0 0 lo
default 192.168.10.240 0.0.0.0 UG 0 0 0 eth1
ifconfig:
eth0 Link encap:Ethernet HWaddr 00:02:55:EE:C3:91
inet addr:192.168.9.1 Bcast:192.168.255.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:377635 errors:0 dropped:0 overruns:0 frame:0
TX packets:7192 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:216836627 (206.7 Mb) TX bytes:808284 (789.3 Kb)
Interrupt:10 Base address:0xa000
eth1 Link encap:Ethernet HWaddr 00:10:5A:D0:19:16
inet addr:192.168.8.232 Bcast:192.168.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1914380 errors:0 dropped:0 overruns:0 frame:0
TX packets:1522009 errors:0 dropped:0 overruns:0 carrier:1
collisions:2946 txqueuelen:100
RX bytes:480613108 (458.3 Mb) TX bytes:1246359355 (1188.6 Mb)
Interrupt:10 Base address:0xb800
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:40969 errors:0 dropped:0 overruns:0 frame:0
TX packets:40969 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:5714853 (5.4 Mb) TX bytes:5714853 (5.4 Mb)
iptables:
LOGGED: IN=eth1 OUT= MAC=00:10:5a:d0:19:16:00:09:6b:e2:31:d7:08:00 SRC=192.168.8.11 DST=192.168.9.1 LEN=48 TOS=0x00 PREC=0x00 TTL=128 ID=63630 DF PROTO=TCP SPT=2138 DPT=3128 WINDOW=64240 RES=0x00 SYN URGP=0
LOGGED: IN=eth1 OUT= MAC=00:10:5a:d0:19:16:00:09:6b:e2:31:d7:08:00 SRC=192.168.8.11 DST=192.168.9.1 LEN=48 TOS=0x00 PREC=0x00 TTL=128 ID=63746 DF PROTO=TCP SPT=2140 DPT=3128 WINDOW=64240 RES=0x00 SYN URGP=0
LOGGED: IN=eth1 OUT= MAC=00:10:5a:d0:19:16:00:09:6b:e2:31:d7:08:00 SRC=192.168.8.11 DST=192.168.9.1 LEN=48 TOS=0x00 PREC=0x00 TTL=128 ID=63825 DF PROTO=TCP SPT=2142 DPT=3128 WINDOW=64240 RES=0x00 SYN URGP=0
How come iptables still says eth1 is being used by 192.168.9.1? This has been my biggest problem. I hope to restrict in iptables that eth0 is used by 192.168.9.1 for security reasons.
I have no forwarding or any routing settings yet with iptables but a simple logging just to find out if the network interfaces work properly.
fritz <www.mesedilla.com>
---
+ Basta Ikaw Lord
----------------------------------------------------------------------
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the sender immediately by e-mail and delete this e-mail from your
system. Please note that any views or opinions presented in this
email are solely those of the author and do not necessarily represent
those of the company. Finally, the recipient should check this email
and any attachments for the presence of viruses. The company accepts
no liability for any damage caused by any virus transmitted by this
email.
Overture Media, Inc.
Direct Line: (632) 635-4785
Trunkline: (632) 631-8971 Local 146
Fax: (632) 637-2206
Level 1 Summit Media Offices, Robinsons Galleria EDSA Cor. Ortigas Ave., Quezon City 1100
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: iptables or routing problem
2003-10-22 5:03 Fritz Mesedilla
@ 2003-10-22 5:33 ` netfilter
0 siblings, 0 replies; 7+ messages in thread
From: netfilter @ 2003-10-22 5:33 UTC (permalink / raw)
To: Fritz Mesedilla; +Cc: [netfilter] Mailing List
Fritz,
eth1 is getting these packets because the destination MAC address of
those packets match eth1's MAC address. The subnets you have defined for
eth0 and eth1 overlap, so you may still be experiencing ARP problems. Since
the default gateway you are using has an IP of 198.168.10.240, might I
suggest that you limit the subnet of eth1 to be 198.168.10.*/24? If you
make this change, you should be able to get your ARP problems straitened
out.
Brandon Broyles
----- Original Message -----
From: "Fritz Mesedilla" <fritz.mesedilla@overturemedia.com>
To: <netfilter@lists.netfilter.org>
Sent: Wednesday, October 22, 2003 1:03 AM
Subject: iptables or routing problem
I dunno if this is a routing problem or my iptables.
route:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
192.168.9.0 * 255.255.255.0 U 0 0 0 eth0
192.168.0.0 * 255.255.0.0 U 0 0 0 eth1
127.0.0.0 * 255.0.0.0 U 0 0 0 lo
default 192.168.10.240 0.0.0.0 UG 0 0 0 eth1
ifconfig:
eth0 Link encap:Ethernet HWaddr 00:02:55:EE:C3:91
inet addr:192.168.9.1 Bcast:192.168.255.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:377635 errors:0 dropped:0 overruns:0 frame:0
TX packets:7192 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:216836627 (206.7 Mb) TX bytes:808284 (789.3 Kb)
Interrupt:10 Base address:0xa000
eth1 Link encap:Ethernet HWaddr 00:10:5A:D0:19:16
inet addr:192.168.8.232 Bcast:192.168.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1914380 errors:0 dropped:0 overruns:0 frame:0
TX packets:1522009 errors:0 dropped:0 overruns:0 carrier:1
collisions:2946 txqueuelen:100
RX bytes:480613108 (458.3 Mb) TX bytes:1246359355 (1188.6 Mb)
Interrupt:10 Base address:0xb800
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:40969 errors:0 dropped:0 overruns:0 frame:0
TX packets:40969 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:5714853 (5.4 Mb) TX bytes:5714853 (5.4 Mb)
iptables:
LOGGED: IN=eth1 OUT= MAC=00:10:5a:d0:19:16:00:09:6b:e2:31:d7:08:00
SRC=192.168.8.11 DST=192.168.9.1 LEN=48 TOS=0x00 PREC=0x00 TTL=128 ID=63630
DF PROTO=TCP SPT=2138 DPT=3128 WINDOW=64240 RES=0x00 SYN URGP=0
LOGGED: IN=eth1 OUT= MAC=00:10:5a:d0:19:16:00:09:6b:e2:31:d7:08:00
SRC=192.168.8.11 DST=192.168.9.1 LEN=48 TOS=0x00 PREC=0x00 TTL=128 ID=63746
DF PROTO=TCP SPT=2140 DPT=3128 WINDOW=64240 RES=0x00 SYN URGP=0
LOGGED: IN=eth1 OUT= MAC=00:10:5a:d0:19:16:00:09:6b:e2:31:d7:08:00
SRC=192.168.8.11 DST=192.168.9.1 LEN=48 TOS=0x00 PREC=0x00 TTL=128 ID=63825
DF PROTO=TCP SPT=2142 DPT=3128 WINDOW=64240 RES=0x00 SYN URGP=0
How come iptables still says eth1 is being used by 192.168.9.1? This has
been my biggest problem. I hope to restrict in iptables that eth0 is used by
192.168.9.1 for security reasons.
I have no forwarding or any routing settings yet with iptables but a simple
logging just to find out if the network interfaces work properly.
fritz <www.mesedilla.com>
---
+ Basta Ikaw Lord
----------------------------------------------------------------------
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the sender immediately by e-mail and delete this e-mail from your
system. Please note that any views or opinions presented in this
email are solely those of the author and do not necessarily represent
those of the company. Finally, the recipient should check this email
and any attachments for the presence of viruses. The company accepts
no liability for any damage caused by any virus transmitted by this
email.
Overture Media, Inc.
Direct Line: (632) 635-4785
Trunkline: (632) 631-8971 Local 146
Fax: (632) 637-2206
Level 1 Summit Media Offices, Robinsons Galleria EDSA Cor. Ortigas Ave.,
Quezon City 1100
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: iptables or routing problem
[not found] <F22386C3FEB012449238672E38ED61E70A8D76@overlord.overturemedia.com>
@ 2003-10-22 5:41 ` netfilter
2003-10-22 5:51 ` netfilter
0 siblings, 1 reply; 7+ messages in thread
From: netfilter @ 2003-10-22 5:41 UTC (permalink / raw)
To: Fritz Mesedilla; +Cc: [netfilter] Mailing List
Fritz,
Change the IPADDR to be 192.168.10.? and the NETMASK to be
255.255.255.0.
Brandon Broyles
----- Original Message -----
From: "Fritz Mesedilla" <fritz.mesedilla@overturemedia.com>
To: <netfilter@drbroyles.com>
Sent: Wednesday, October 22, 2003 1:38 AM
Subject: RE: iptables or routing problem
Sorry for being ignorant... but how do I limit the subnet of eth1 to
192.168.10.*/24?
here is my current ifcfg-eth1:
BOOTPROTO=none
GATEWAY=192.168.10.240
DEVICE=eth1
MTU=1500
NETMASK=255.255.0.0
BROADCAST=192.168.255.255
IPADDR=192.168.8.232
NETWORK=192.168.0.0
ONBOOT=yes
fritz <www.mesedilla.com>
---
+ Basta Ikaw Lord
> -----Original Message-----
> From: netfilter@drbroyles.com [mailto:netfilter@drbroyles.com]
> Sent: Wednesday, October 22, 2003 1:33 PM
> To: Fritz Mesedilla
> Cc: [netfilter] Mailing List
> Subject: Re: iptables or routing problem
>
>
> Fritz,
> eth1 is getting these packets because the destination MAC
> address of
> those packets match eth1's MAC address. The subnets you have
> defined for
> eth0 and eth1 overlap, so you may still be experiencing ARP
> problems. Since
> the default gateway you are using has an IP of 198.168.10.240, might I
> suggest that you limit the subnet of eth1 to be
> 198.168.10.*/24? If you
> make this change, you should be able to get your ARP problems
> straitened
> out.
>
> Brandon Broyles
>
> ----- Original Message -----
> From: "Fritz Mesedilla" <fritz.mesedilla@overturemedia.com>
> To: <netfilter@lists.netfilter.org>
> Sent: Wednesday, October 22, 2003 1:03 AM
> Subject: iptables or routing problem
>
>
>
> I dunno if this is a routing problem or my iptables.
>
> route:
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric
> Ref Use
> Iface
> 192.168.9.0 * 255.255.255.0 U 0
> 0 0 eth0
> 192.168.0.0 * 255.255.0.0 U 0
> 0 0 eth1
> 127.0.0.0 * 255.0.0.0 U 0
> 0 0 lo
> default 192.168.10.240 0.0.0.0 UG 0
> 0 0 eth1
>
>
> ifconfig:
> eth0 Link encap:Ethernet HWaddr 00:02:55:EE:C3:91
> inet addr:192.168.9.1 Bcast:192.168.255.255
> Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:377635 errors:0 dropped:0 overruns:0 frame:0
> TX packets:7192 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
> RX bytes:216836627 (206.7 Mb) TX bytes:808284 (789.3 Kb)
> Interrupt:10 Base address:0xa000
>
> eth1 Link encap:Ethernet HWaddr 00:10:5A:D0:19:16
> inet addr:192.168.8.232 Bcast:192.168.255.255
> Mask:255.255.0.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:1914380 errors:0 dropped:0 overruns:0 frame:0
> TX packets:1522009 errors:0 dropped:0 overruns:0 carrier:1
> collisions:2946 txqueuelen:100
> RX bytes:480613108 (458.3 Mb) TX bytes:1246359355
> (1188.6 Mb)
> Interrupt:10 Base address:0xb800
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:40969 errors:0 dropped:0 overruns:0 frame:0
> TX packets:40969 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:5714853 (5.4 Mb) TX bytes:5714853 (5.4 Mb)
>
> iptables:
> LOGGED: IN=eth1 OUT= MAC=00:10:5a:d0:19:16:00:09:6b:e2:31:d7:08:00
> SRC=192.168.8.11 DST=192.168.9.1 LEN=48 TOS=0x00 PREC=0x00
> TTL=128 ID=63630
> DF PROTO=TCP SPT=2138 DPT=3128 WINDOW=64240 RES=0x00 SYN URGP=0
> LOGGED: IN=eth1 OUT= MAC=00:10:5a:d0:19:16:00:09:6b:e2:31:d7:08:00
> SRC=192.168.8.11 DST=192.168.9.1 LEN=48 TOS=0x00 PREC=0x00
> TTL=128 ID=63746
> DF PROTO=TCP SPT=2140 DPT=3128 WINDOW=64240 RES=0x00 SYN URGP=0
> LOGGED: IN=eth1 OUT= MAC=00:10:5a:d0:19:16:00:09:6b:e2:31:d7:08:00
> SRC=192.168.8.11 DST=192.168.9.1 LEN=48 TOS=0x00 PREC=0x00
> TTL=128 ID=63825
> DF PROTO=TCP SPT=2142 DPT=3128 WINDOW=64240 RES=0x00 SYN URGP=0
>
>
> How come iptables still says eth1 is being used by
> 192.168.9.1? This has
> been my biggest problem. I hope to restrict in iptables that
> eth0 is used by
> 192.168.9.1 for security reasons.
>
> I have no forwarding or any routing settings yet with
> iptables but a simple
> logging just to find out if the network interfaces work properly.
>
>
> fritz <www.mesedilla.com>
> ---
> + Basta Ikaw Lord
>
> ----------------------------------------------------------------------
> This email and any files transmitted with it are confidential and
> intended solely for the use of the individual or entity to whom they
> are addressed. If you have received this email in error please notify
> the sender immediately by e-mail and delete this e-mail from your
> system. Please note that any views or opinions presented in this
> email are solely those of the author and do not necessarily represent
> those of the company. Finally, the recipient should check this email
> and any attachments for the presence of viruses. The company accepts
> no liability for any damage caused by any virus transmitted by this
> email.
>
> Overture Media, Inc.
> Direct Line: (632) 635-4785
> Trunkline: (632) 631-8971 Local 146
> Fax: (632) 637-2206
> Level 1 Summit Media Offices, Robinsons Galleria EDSA Cor.
> Ortigas Ave.,
> Quezon City 1100
>
>
>
>
----------------------------------------------------------------------
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the sender immediately by e-mail and delete this e-mail from your
system. Please note that any views or opinions presented in this
email are solely those of the author and do not necessarily represent
those of the company. Finally, the recipient should check this email
and any attachments for the presence of viruses. The company accepts
no liability for any damage caused by any virus transmitted by this
email.
Overture Media, Inc.
Direct Line: (632) 635-4785
Trunkline: (632) 631-8971 Local 146
Fax: (632) 637-2206
Level 1 Summit Media Offices, Robinsons Galleria EDSA Cor. Ortigas Ave.,
Quezon City 1100
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: iptables or routing problem
2003-10-22 5:41 ` iptables or routing problem netfilter
@ 2003-10-22 5:51 ` netfilter
0 siblings, 0 replies; 7+ messages in thread
From: netfilter @ 2003-10-22 5:51 UTC (permalink / raw)
To: Fritz Mesedilla; +Cc: [netfilter] Mailing List
Fritz,
Sorry, I forgot to mention that you would need to change the BROADCAST
to 192.168.10.255 and the NETWORK to 192.168.10.0.
Brandon Broyles
----- Original Message -----
From: <netfilter@drbroyles.com>
To: "Fritz Mesedilla" <fritz.mesedilla@overturemedia.com>
Cc: "[netfilter] Mailing List" <netfilter@lists.netfilter.org>
Sent: Wednesday, October 22, 2003 1:41 AM
Subject: Re: iptables or routing problem
> Fritz,
> Change the IPADDR to be 192.168.10.? and the NETMASK to be
> 255.255.255.0.
>
> Brandon Broyles
>
> ----- Original Message -----
> From: "Fritz Mesedilla" <fritz.mesedilla@overturemedia.com>
> To: <netfilter@drbroyles.com>
> Sent: Wednesday, October 22, 2003 1:38 AM
> Subject: RE: iptables or routing problem
>
>
>
> Sorry for being ignorant... but how do I limit the subnet of eth1 to
> 192.168.10.*/24?
>
> here is my current ifcfg-eth1:
> BOOTPROTO=none
> GATEWAY=192.168.10.240
> DEVICE=eth1
> MTU=1500
> NETMASK=255.255.0.0
> BROADCAST=192.168.255.255
> IPADDR=192.168.8.232
> NETWORK=192.168.0.0
> ONBOOT=yes
>
>
> fritz <www.mesedilla.com>
> ---
> + Basta Ikaw Lord
>
>
>
> > -----Original Message-----
> > From: netfilter@drbroyles.com [mailto:netfilter@drbroyles.com]
> > Sent: Wednesday, October 22, 2003 1:33 PM
> > To: Fritz Mesedilla
> > Cc: [netfilter] Mailing List
> > Subject: Re: iptables or routing problem
> >
> >
> > Fritz,
> > eth1 is getting these packets because the destination MAC
> > address of
> > those packets match eth1's MAC address. The subnets you have
> > defined for
> > eth0 and eth1 overlap, so you may still be experiencing ARP
> > problems. Since
> > the default gateway you are using has an IP of 198.168.10.240, might I
> > suggest that you limit the subnet of eth1 to be
> > 198.168.10.*/24? If you
> > make this change, you should be able to get your ARP problems
> > straitened
> > out.
> >
> > Brandon Broyles
> >
> > ----- Original Message -----
> > From: "Fritz Mesedilla" <fritz.mesedilla@overturemedia.com>
> > To: <netfilter@lists.netfilter.org>
> > Sent: Wednesday, October 22, 2003 1:03 AM
> > Subject: iptables or routing problem
> >
> >
> >
> > I dunno if this is a routing problem or my iptables.
> >
> > route:
> > Kernel IP routing table
> > Destination Gateway Genmask Flags Metric
> > Ref Use
> > Iface
> > 192.168.9.0 * 255.255.255.0 U 0
> > 0 0 eth0
> > 192.168.0.0 * 255.255.0.0 U 0
> > 0 0 eth1
> > 127.0.0.0 * 255.0.0.0 U 0
> > 0 0 lo
> > default 192.168.10.240 0.0.0.0 UG 0
> > 0 0 eth1
> >
> >
> > ifconfig:
> > eth0 Link encap:Ethernet HWaddr 00:02:55:EE:C3:91
> > inet addr:192.168.9.1 Bcast:192.168.255.255
> > Mask:255.255.255.0
> > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> > RX packets:377635 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:7192 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:100
> > RX bytes:216836627 (206.7 Mb) TX bytes:808284 (789.3 Kb)
> > Interrupt:10 Base address:0xa000
> >
> > eth1 Link encap:Ethernet HWaddr 00:10:5A:D0:19:16
> > inet addr:192.168.8.232 Bcast:192.168.255.255
> > Mask:255.255.0.0
> > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> > RX packets:1914380 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:1522009 errors:0 dropped:0 overruns:0 carrier:1
> > collisions:2946 txqueuelen:100
> > RX bytes:480613108 (458.3 Mb) TX bytes:1246359355
> > (1188.6 Mb)
> > Interrupt:10 Base address:0xb800
> >
> > lo Link encap:Local Loopback
> > inet addr:127.0.0.1 Mask:255.0.0.0
> > UP LOOPBACK RUNNING MTU:16436 Metric:1
> > RX packets:40969 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:40969 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:0
> > RX bytes:5714853 (5.4 Mb) TX bytes:5714853 (5.4 Mb)
> >
> > iptables:
> > LOGGED: IN=eth1 OUT= MAC=00:10:5a:d0:19:16:00:09:6b:e2:31:d7:08:00
> > SRC=192.168.8.11 DST=192.168.9.1 LEN=48 TOS=0x00 PREC=0x00
> > TTL=128 ID=63630
> > DF PROTO=TCP SPT=2138 DPT=3128 WINDOW=64240 RES=0x00 SYN URGP=0
> > LOGGED: IN=eth1 OUT= MAC=00:10:5a:d0:19:16:00:09:6b:e2:31:d7:08:00
> > SRC=192.168.8.11 DST=192.168.9.1 LEN=48 TOS=0x00 PREC=0x00
> > TTL=128 ID=63746
> > DF PROTO=TCP SPT=2140 DPT=3128 WINDOW=64240 RES=0x00 SYN URGP=0
> > LOGGED: IN=eth1 OUT= MAC=00:10:5a:d0:19:16:00:09:6b:e2:31:d7:08:00
> > SRC=192.168.8.11 DST=192.168.9.1 LEN=48 TOS=0x00 PREC=0x00
> > TTL=128 ID=63825
> > DF PROTO=TCP SPT=2142 DPT=3128 WINDOW=64240 RES=0x00 SYN URGP=0
> >
> >
> > How come iptables still says eth1 is being used by
> > 192.168.9.1? This has
> > been my biggest problem. I hope to restrict in iptables that
> > eth0 is used by
> > 192.168.9.1 for security reasons.
> >
> > I have no forwarding or any routing settings yet with
> > iptables but a simple
> > logging just to find out if the network interfaces work properly.
> >
> >
> > fritz <www.mesedilla.com>
> > ---
> > + Basta Ikaw Lord
> >
> > ----------------------------------------------------------------------
> > This email and any files transmitted with it are confidential and
> > intended solely for the use of the individual or entity to whom they
> > are addressed. If you have received this email in error please notify
> > the sender immediately by e-mail and delete this e-mail from your
> > system. Please note that any views or opinions presented in this
> > email are solely those of the author and do not necessarily represent
> > those of the company. Finally, the recipient should check this email
> > and any attachments for the presence of viruses. The company accepts
> > no liability for any damage caused by any virus transmitted by this
> > email.
> >
> > Overture Media, Inc.
> > Direct Line: (632) 635-4785
> > Trunkline: (632) 631-8971 Local 146
> > Fax: (632) 637-2206
> > Level 1 Summit Media Offices, Robinsons Galleria EDSA Cor.
> > Ortigas Ave.,
> > Quezon City 1100
> >
> >
> >
> >
>
> ----------------------------------------------------------------------
> This email and any files transmitted with it are confidential and
> intended solely for the use of the individual or entity to whom they
> are addressed. If you have received this email in error please notify
> the sender immediately by e-mail and delete this e-mail from your
> system. Please note that any views or opinions presented in this
> email are solely those of the author and do not necessarily represent
> those of the company. Finally, the recipient should check this email
> and any attachments for the presence of viruses. The company accepts
> no liability for any damage caused by any virus transmitted by this
> email.
>
> Overture Media, Inc.
> Direct Line: (632) 635-4785
> Trunkline: (632) 631-8971 Local 146
> Fax: (632) 637-2206
> Level 1 Summit Media Offices, Robinsons Galleria EDSA Cor. Ortigas Ave.,
> Quezon City 1100
>
>
>
>
^ permalink raw reply [flat|nested] 7+ messages in thread
* RE: iptables or routing problem
@ 2003-10-22 6:41 Fritz Mesedilla
2003-10-22 7:50 ` netfilter
0 siblings, 1 reply; 7+ messages in thread
From: Fritz Mesedilla @ 2003-10-22 6:41 UTC (permalink / raw)
To: netfilter; +Cc: [netfilter] Mailing List
Oh I can't change the subnets. Our parent company is using a class-b system. 255.255.0.0
Would this be possible in a class-b system?
eth0: 192.167.8.1
eth1: 192.168.8.232
Just to make them on different subnets?
fritz <www.mesedilla.com>
---
+ Basta Ikaw Lord
> -----Original Message-----
> From: netfilter@drbroyles.com [mailto:netfilter@drbroyles.com]
> Sent: Wednesday, October 22, 2003 1:51 PM
> To: Fritz Mesedilla
> Cc: [netfilter] Mailing List
> Subject: Re: iptables or routing problem
>
>
> Fritz,
> Sorry, I forgot to mention that you would need to change
> the BROADCAST
> to 192.168.10.255 and the NETWORK to 192.168.10.0.
>
> Brandon Broyles
>
> ----- Original Message -----
> From: <netfilter@drbroyles.com>
> To: "Fritz Mesedilla" <fritz.mesedilla@overturemedia.com>
> Cc: "[netfilter] Mailing List" <netfilter@lists.netfilter.org>
> Sent: Wednesday, October 22, 2003 1:41 AM
> Subject: Re: iptables or routing problem
>
>
> > Fritz,
> > Change the IPADDR to be 192.168.10.? and the NETMASK to be
> > 255.255.255.0.
> >
> > Brandon Broyles
> >
> > ----- Original Message -----
> > From: "Fritz Mesedilla" <fritz.mesedilla@overturemedia.com>
> > To: <netfilter@drbroyles.com>
> > Sent: Wednesday, October 22, 2003 1:38 AM
> > Subject: RE: iptables or routing problem
> >
> >
> >
> > Sorry for being ignorant... but how do I limit the subnet of eth1 to
> > 192.168.10.*/24?
> >
> > here is my current ifcfg-eth1:
> > BOOTPROTO=none
> > GATEWAY=192.168.10.240
> > DEVICE=eth1
> > MTU=1500
> > NETMASK=255.255.0.0
> > BROADCAST=192.168.255.255
> > IPADDR=192.168.8.232
> > NETWORK=192.168.0.0
> > ONBOOT=yes
> >
> >
> > fritz <www.mesedilla.com>
> > ---
> > + Basta Ikaw Lord
> >
> >
> >
> > > -----Original Message-----
> > > From: netfilter@drbroyles.com [mailto:netfilter@drbroyles.com]
> > > Sent: Wednesday, October 22, 2003 1:33 PM
> > > To: Fritz Mesedilla
> > > Cc: [netfilter] Mailing List
> > > Subject: Re: iptables or routing problem
> > >
> > >
> > > Fritz,
> > > eth1 is getting these packets because the destination MAC
> > > address of
> > > those packets match eth1's MAC address. The subnets you have
> > > defined for
> > > eth0 and eth1 overlap, so you may still be experiencing ARP
> > > problems. Since
> > > the default gateway you are using has an IP of
> 198.168.10.240, might I
> > > suggest that you limit the subnet of eth1 to be
> > > 198.168.10.*/24? If you
> > > make this change, you should be able to get your ARP problems
> > > straitened
> > > out.
> > >
> > > Brandon Broyles
> > >
> > > ----- Original Message -----
> > > From: "Fritz Mesedilla" <fritz.mesedilla@overturemedia.com>
> > > To: <netfilter@lists.netfilter.org>
> > > Sent: Wednesday, October 22, 2003 1:03 AM
> > > Subject: iptables or routing problem
> > >
> > >
> > >
> > > I dunno if this is a routing problem or my iptables.
> > >
> > > route:
> > > Kernel IP routing table
> > > Destination Gateway Genmask Flags Metric
> > > Ref Use
> > > Iface
> > > 192.168.9.0 * 255.255.255.0 U 0
> > > 0 0 eth0
> > > 192.168.0.0 * 255.255.0.0 U 0
> > > 0 0 eth1
> > > 127.0.0.0 * 255.0.0.0 U 0
> > > 0 0 lo
> > > default 192.168.10.240 0.0.0.0 UG 0
> > > 0 0 eth1
> > >
> > >
> > > ifconfig:
> > > eth0 Link encap:Ethernet HWaddr 00:02:55:EE:C3:91
> > > inet addr:192.168.9.1 Bcast:192.168.255.255
> > > Mask:255.255.255.0
> > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> > > RX packets:377635 errors:0 dropped:0 overruns:0 frame:0
> > > TX packets:7192 errors:0 dropped:0 overruns:0 carrier:0
> > > collisions:0 txqueuelen:100
> > > RX bytes:216836627 (206.7 Mb) TX bytes:808284
> (789.3 Kb)
> > > Interrupt:10 Base address:0xa000
> > >
> > > eth1 Link encap:Ethernet HWaddr 00:10:5A:D0:19:16
> > > inet addr:192.168.8.232 Bcast:192.168.255.255
> > > Mask:255.255.0.0
> > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> > > RX packets:1914380 errors:0 dropped:0 overruns:0 frame:0
> > > TX packets:1522009 errors:0 dropped:0
> overruns:0 carrier:1
> > > collisions:2946 txqueuelen:100
> > > RX bytes:480613108 (458.3 Mb) TX bytes:1246359355
> > > (1188.6 Mb)
> > > Interrupt:10 Base address:0xb800
> > >
> > > lo Link encap:Local Loopback
> > > inet addr:127.0.0.1 Mask:255.0.0.0
> > > UP LOOPBACK RUNNING MTU:16436 Metric:1
> > > RX packets:40969 errors:0 dropped:0 overruns:0 frame:0
> > > TX packets:40969 errors:0 dropped:0 overruns:0 carrier:0
> > > collisions:0 txqueuelen:0
> > > RX bytes:5714853 (5.4 Mb) TX bytes:5714853 (5.4 Mb)
> > >
> > > iptables:
> > > LOGGED: IN=eth1 OUT= MAC=00:10:5a:d0:19:16:00:09:6b:e2:31:d7:08:00
> > > SRC=192.168.8.11 DST=192.168.9.1 LEN=48 TOS=0x00 PREC=0x00
> > > TTL=128 ID=63630
> > > DF PROTO=TCP SPT=2138 DPT=3128 WINDOW=64240 RES=0x00 SYN URGP=0
> > > LOGGED: IN=eth1 OUT= MAC=00:10:5a:d0:19:16:00:09:6b:e2:31:d7:08:00
> > > SRC=192.168.8.11 DST=192.168.9.1 LEN=48 TOS=0x00 PREC=0x00
> > > TTL=128 ID=63746
> > > DF PROTO=TCP SPT=2140 DPT=3128 WINDOW=64240 RES=0x00 SYN URGP=0
> > > LOGGED: IN=eth1 OUT= MAC=00:10:5a:d0:19:16:00:09:6b:e2:31:d7:08:00
> > > SRC=192.168.8.11 DST=192.168.9.1 LEN=48 TOS=0x00 PREC=0x00
> > > TTL=128 ID=63825
> > > DF PROTO=TCP SPT=2142 DPT=3128 WINDOW=64240 RES=0x00 SYN URGP=0
> > >
> > >
> > > How come iptables still says eth1 is being used by
> > > 192.168.9.1? This has
> > > been my biggest problem. I hope to restrict in iptables that
> > > eth0 is used by
> > > 192.168.9.1 for security reasons.
> > >
> > > I have no forwarding or any routing settings yet with
> > > iptables but a simple
> > > logging just to find out if the network interfaces work properly.
> > >
> > >
> > > fritz <www.mesedilla.com>
> > > ---
> > > + Basta Ikaw Lord
> > >
> > >
> ----------------------------------------------------------------------
> > > This email and any files transmitted with it are confidential and
> > > intended solely for the use of the individual or entity
> to whom they
> > > are addressed. If you have received this email in error
> please notify
> > > the sender immediately by e-mail and delete this e-mail from your
> > > system. Please note that any views or opinions presented in this
> > > email are solely those of the author and do not
> necessarily represent
> > > those of the company. Finally, the recipient should check
> this email
> > > and any attachments for the presence of viruses. The
> company accepts
> > > no liability for any damage caused by any virus
> transmitted by this
> > > email.
> > >
> > > Overture Media, Inc.
> > > Direct Line: (632) 635-4785
> > > Trunkline: (632) 631-8971 Local 146
> > > Fax: (632) 637-2206
> > > Level 1 Summit Media Offices, Robinsons Galleria EDSA Cor.
> > > Ortigas Ave.,
> > > Quezon City 1100
> > >
> > >
> > >
> > >
> >
> >
> ----------------------------------------------------------------------
> > This email and any files transmitted with it are confidential and
> > intended solely for the use of the individual or entity to whom they
> > are addressed. If you have received this email in error
> please notify
> > the sender immediately by e-mail and delete this e-mail from your
> > system. Please note that any views or opinions presented in this
> > email are solely those of the author and do not necessarily
> represent
> > those of the company. Finally, the recipient should check this email
> > and any attachments for the presence of viruses. The company accepts
> > no liability for any damage caused by any virus transmitted by this
> > email.
> >
> > Overture Media, Inc.
> > Direct Line: (632) 635-4785
> > Trunkline: (632) 631-8971 Local 146
> > Fax: (632) 637-2206
> > Level 1 Summit Media Offices, Robinsons Galleria EDSA Cor.
> Ortigas Ave.,
> > Quezon City 1100
> >
> >
> >
> >
>
>
----------------------------------------------------------------------
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the sender immediately by e-mail and delete this e-mail from your
system. Please note that any views or opinions presented in this
email are solely those of the author and do not necessarily represent
those of the company. Finally, the recipient should check this email
and any attachments for the presence of viruses. The company accepts
no liability for any damage caused by any virus transmitted by this
email.
Overture Media, Inc.
Direct Line: (632) 635-4785
Trunkline: (632) 631-8971 Local 146
Fax: (632) 637-2206
Level 1 Summit Media Offices, Robinsons Galleria EDSA Cor. Ortigas Ave., Quezon City 1100
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: iptables or routing problem
2003-10-22 6:41 Fritz Mesedilla
@ 2003-10-22 7:50 ` netfilter
0 siblings, 0 replies; 7+ messages in thread
From: netfilter @ 2003-10-22 7:50 UTC (permalink / raw)
To: Fritz Mesedilla; +Cc: [netfilter] Mailing List
Fritz,
No that will not work. The B-class subnet of 192.168.x.x is a privately
available group of IPs that are not allowed onto the Internet. 192.167.8.1
is a real-world IP address though. In fact, the entire 192.167.x.x/16
address space are real IPs.
Any routers connected to the Internet will not route these private
addresses without some sort of NAT or MASQUERADING. If your parent company
doesn't own IPs that you can use (which is what I suspect to be the case)
you'll need to use a different private address space. If you need to use a
private IP space, then you have two other choices.
You can use 172.16.x.x or you can use some portion of 10.x.x.x. This
all depends on the intended use of your router. How many clients will you
be servicing?
I would suggest you read over the following Howto to get a better sense
of how you want to structure your network.
http://www.tldp.org/HOWTO/IP-Subnetworking.html
Brandon Broyles
----- Original Message -----
From: "Fritz Mesedilla" <fritz.mesedilla@overturemedia.com>
To: <netfilter@drbroyles.com>
Cc: "[netfilter] Mailing List" <netfilter@lists.netfilter.org>
Sent: Wednesday, October 22, 2003 2:41 AM
Subject: RE: iptables or routing problem
Oh I can't change the subnets. Our parent company is using a class-b system.
255.255.0.0
Would this be possible in a class-b system?
eth0: 192.167.8.1
eth1: 192.168.8.232
Just to make them on different subnets?
fritz <www.mesedilla.com>
^ permalink raw reply [flat|nested] 7+ messages in thread
* RE: iptables or routing problem
@ 2003-10-22 9:36 Fritz Mesedilla
0 siblings, 0 replies; 7+ messages in thread
From: Fritz Mesedilla @ 2003-10-22 9:36 UTC (permalink / raw)
To: netfilter; +Cc: [netfilter] Mailing List
Thank you so much Brandon!
I'll check on that. I really appreciate your help!
Someday I too will be able to help someone as you have helped me.
fritz <www.mesedilla.com>
---
+ Basta Ikaw Lord
> -----Original Message-----
> From: netfilter@drbroyles.com [mailto:netfilter@drbroyles.com]
> Sent: Wednesday, October 22, 2003 3:50 PM
> To: Fritz Mesedilla
> Cc: [netfilter] Mailing List
> Subject: Re: iptables or routing problem
>
>
> Fritz,
> No that will not work. The B-class subnet of 192.168.x.x
> is a privately
> available group of IPs that are not allowed onto the
> Internet. 192.167.8.1
> is a real-world IP address though. In fact, the entire 192.167.x.x/16
> address space are real IPs.
> Any routers connected to the Internet will not route these private
> addresses without some sort of NAT or MASQUERADING. If your
> parent company
> doesn't own IPs that you can use (which is what I suspect to
> be the case)
> you'll need to use a different private address space. If you
> need to use a
> private IP space, then you have two other choices.
> You can use 172.16.x.x or you can use some portion of
> 10.x.x.x. This
> all depends on the intended use of your router. How many
> clients will you
> be servicing?
> I would suggest you read over the following Howto to get
> a better sense
> of how you want to structure your network.
> http://www.tldp.org/HOWTO/IP-Subnetworking.html
>
> Brandon Broyles
>
> ----- Original Message -----
> From: "Fritz Mesedilla" <fritz.mesedilla@overturemedia.com>
> To: <netfilter@drbroyles.com>
> Cc: "[netfilter] Mailing List" <netfilter@lists.netfilter.org>
> Sent: Wednesday, October 22, 2003 2:41 AM
> Subject: RE: iptables or routing problem
>
>
>
> Oh I can't change the subnets. Our parent company is using a
> class-b system.
> 255.255.0.0
>
> Would this be possible in a class-b system?
>
> eth0: 192.167.8.1
> eth1: 192.168.8.232
>
> Just to make them on different subnets?
>
> fritz <www.mesedilla.com>
>
>
----------------------------------------------------------------------
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the sender immediately by e-mail and delete this e-mail from your
system. Please note that any views or opinions presented in this
email are solely those of the author and do not necessarily represent
those of the company. Finally, the recipient should check this email
and any attachments for the presence of viruses. The company accepts
no liability for any damage caused by any virus transmitted by this
email.
Overture Media, Inc.
Direct Line: (632) 635-4785
Trunkline: (632) 631-8971 Local 146
Fax: (632) 637-2206
Level 1 Summit Media Offices, Robinsons Galleria EDSA Cor. Ortigas Ave., Quezon City 1100
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2003-10-22 9:36 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <F22386C3FEB012449238672E38ED61E70A8D76@overlord.overturemedia.com>
2003-10-22 5:41 ` iptables or routing problem netfilter
2003-10-22 5:51 ` netfilter
2003-10-22 9:36 Fritz Mesedilla
-- strict thread matches above, loose matches on Subject: below --
2003-10-22 6:41 Fritz Mesedilla
2003-10-22 7:50 ` netfilter
2003-10-22 5:03 Fritz Mesedilla
2003-10-22 5:33 ` netfilter
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.