Re: ip address on dhcp client
Thu, 17 Jul 2014 13:21:19 +0530 Mett: Modem has ports 23,80,5431. Ssh may not be an option. On 7/15/14, mett m...@pmars.jp wrote: On Mon, 14 Jul 2014 22:33:11 +0530 rajiv chavan rc214...@gmail.com wrote: On Mon, 14 Jul 2014 07:53:06 +0530 - Hide quoted text - rajiv chavan rc214...@gmail.com wrote: Mon, 14 Jul 2014 07:26:20 +0530 Thank you Mett. Traceroute packets from another host dropped by ISP netwoek at 218.248.0.0 netstat -rn Destination Gateway Genmask Flags MSS Window irtt Iface 0.0.0.0 0.0.0.0 0.0.0.0 U 0 0 0 ppp0 117.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 eth0 117.222.8.1 0.0.0.0 255.255.255.255 UH0 0 0 ppp0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 224.0.0.0 0.0.0.0 240.0.0.0 U 0 0 0 eth0 ifconfig eth0:0 yields: ip a 2: eth0: link/ether inet 192.168.1.2/24 brd 192.168.1.255 scope global eth0 inet 117.222.15.189/8 brd 117.255.255.255 scope global eth0:0 3: ppp0: link/ppp inet 117.222.15.189 peer 117.222.8.1/32 scope global ppp0 This is a lone host - no network. Address 117.222.15.189 does not map to modem-router. Nmap on modem returns ports 23,80,5431 open. All ports on 117.222.15.189 filtered. The state may not be reproducible. Oftentiimes eth0 gets only 192.168.1.2 address (which can be pinged ),and ppp0 does not exist. On 7/14/14, mett m...@pmars.jp wrote: On Mon, 14 Jul 2014 00:31:43 +0530 rajiv chavan rc214...@gmail.com wrote: Sun, 13 Jul 2014 23:34:41 +0530 ip a output on an adsl+ (pppoe) client: =snip= 2: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 inet 192.168.1.2/24 brd 192.168.1.255 scope global eth0 3: ppp0: POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP mtu 1460 qdisc pfifo_fast state UNKNOWN group default qlen 3 link/ppp inet 117.222.15.189 peer 117.222.8.1/32 scope global ppp0 =snip= Can ping 127.0.0.1 and 192.168.1.1 but not 117.222.15.189 nor 192.168.1.2 tcpdump on eth0 detcts pppoe packets from 117.222.15.189 to hosts except 192.168.1.1-2 nmap reports 117.222.15.189 ip but all posrt 1-1000 filtered. Hi, Everything is on the same interface? I don't think Eth0 can be routing for your local network and at the same time become ppp0 and route for a global network. I think you'll need some kind of subinterfaces if you want to use only one physical interface for your local network and the outside one. Maybe try a traceroute and you'll see where the packets are going. Also, check the routes(netstat -nr or route -ne). You might give a try one by one to see at what point it stops working: -try only the local network first and once it's working try to set up your pppoe link. hth -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140714091211.3c1fd4cd@asus.tamerr No prob, by the way, better to answer to the list than PM to my address, as sby who might have same problem can see this thread and benefit of the info as well. Also, on this mailing list, generally you post down the thread, like this other persons reading the thread can get an idea of the whole thing, easily by scrolling down. Regarding the issue, if this is a lone host and you are not NATing, one easy way of trblshooting would be : -no manual ip address at all on eth0 -no manual routes as well, -then run pppoeconf, it's quite straight forward and tells you if it finds an aggregator on your ISP side. With the following top. PCmodem-Internet Did you try to set up route manually, as I can see many routes under netstat -nr ? By the way, I never tried with subinterfaces on same phy for outside and inside, but I don't understand why you have a route for multicast(224 smtg) and also a route for the 117.0.0.0 network and at the same time one for 192.168, all that on eth0. Even if eth0 is showing eth0:0, I don't think you need a route for 117.0.0.0., neither one for multicast(224). Try to remove them and see what happened but would be better, faster and easier to just run pppoeconf with an eth0 interface without any IP address. Also, I was talking about traceroute from your host to outside. If it doesn't go anywhere, you will be sure the problem is on your side. Also, you said your host is alone, no network but eth0 on 192.168.1.2 can be pinged. I don't understand how that is possible. As a ref, I paste mine down here # netstat -nr Kernel IP routing table Destination Gateway Genmask Flags MSS Window
Re: ip address on dhcp client
On 7/17/14, rajiv chavan rc214...@gmail.com wrote: Thu, 17 Jul 2014 13:21:19 +0530 Mett: Modem has ports 23,80,5431. Ssh may not be an option. On 7/15/14, mett m...@pmars.jp wrote: On Mon, 14 Jul 2014 22:33:11 +0530 rajiv chavan rc214...@gmail.com wrote: On Mon, 14 Jul 2014 07:53:06 +0530 - Hide quoted text - rajiv chavan rc214...@gmail.com wrote: Mon, 14 Jul 2014 07:26:20 +0530 Thank you Mett. Traceroute packets from another host dropped by ISP netwoek at 218.248.0.0 netstat -rn Destination Gateway Genmask Flags MSS Window irtt Iface 0.0.0.0 0.0.0.0 0.0.0.0 U 0 0 0 ppp0 117.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 eth0 117.222.8.1 0.0.0.0 255.255.255.255 UH0 0 0 ppp0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 224.0.0.0 0.0.0.0 240.0.0.0 U 0 0 0 eth0 ifconfig eth0:0 yields: ip a 2: eth0: link/ether inet 192.168.1.2/24 brd 192.168.1.255 scope global eth0 inet 117.222.15.189/8 brd 117.255.255.255 scope global eth0:0 3: ppp0: link/ppp inet 117.222.15.189 peer 117.222.8.1/32 scope global ppp0 This is a lone host - no network. Address 117.222.15.189 does not map to modem-router. Nmap on modem returns ports 23,80,5431 open. All ports on 117.222.15.189 filtered. The state may not be reproducible. Oftentiimes eth0 gets only 192.168.1.2 address (which can be pinged ),and ppp0 does not exist. On 7/14/14, mett m...@pmars.jp wrote: On Mon, 14 Jul 2014 00:31:43 +0530 rajiv chavan rc214...@gmail.com wrote: Sun, 13 Jul 2014 23:34:41 +0530 ip a output on an adsl+ (pppoe) client: =snip= 2: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 inet 192.168.1.2/24 brd 192.168.1.255 scope global eth0 3: ppp0: POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP mtu 1460 qdisc pfifo_fast state UNKNOWN group default qlen 3 link/ppp inet 117.222.15.189 peer 117.222.8.1/32 scope global ppp0 =snip= Can ping 127.0.0.1 and 192.168.1.1 but not 117.222.15.189 nor 192.168.1.2 tcpdump on eth0 detcts pppoe packets from 117.222.15.189 to hosts except 192.168.1.1-2 nmap reports 117.222.15.189 ip but all posrt 1-1000 filtered. Hi, Everything is on the same interface? I don't think Eth0 can be routing for your local network and at the same time become ppp0 and route for a global network. I think you'll need some kind of subinterfaces if you want to use only one physical interface for your local network and the outside one. Maybe try a traceroute and you'll see where the packets are going. Also, check the routes(netstat -nr or route -ne). You might give a try one by one to see at what point it stops working: -try only the local network first and once it's working try to set up your pppoe link. hth -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140714091211.3c1fd4cd@asus.tamerr No prob, by the way, better to answer to the list than PM to my address, as sby who might have same problem can see this thread and benefit of the info as well. Also, on this mailing list, generally you post down the thread, like this other persons reading the thread can get an idea of the whole thing, easily by scrolling down. Regarding the issue, if this is a lone host and you are not NATing, one easy way of trblshooting would be : -no manual ip address at all on eth0 -no manual routes as well, -then run pppoeconf, it's quite straight forward and tells you if it finds an aggregator on your ISP side. With the following top. PCmodem-Internet Did you try to set up route manually, as I can see many routes under netstat -nr ? By the way, I never tried with subinterfaces on same phy for outside and inside, but I don't understand why you have a route for multicast(224 smtg) and also a route for the 117.0.0.0 network and at the same time one for 192.168, all that on eth0. Even if eth0 is showing eth0:0, I don't think you need a route for 117.0.0.0., neither one for multicast(224). Try to remove them and see what happened but would be better, faster and easier to just run pppoeconf with an eth0 interface without any IP address. Also, I was talking about traceroute from your host to outside. If it doesn't go anywhere, you will be sure the problem is on your side. Also, you said your host is alone, no network but eth0 on 192.168.1.2 can be pinged. I don't understand how that is possible. As a ref, I paste mine down here # netstat -nr Kernel IP routing table Destination
Re: ip address on dhcp client
On Mon, 14 Jul 2014 22:33:11 +0530 rajiv chavan rc214...@gmail.com wrote: On Mon, 14 Jul 2014 07:53:06 +0530 - Hide quoted text - rajiv chavan rc214...@gmail.com wrote: Mon, 14 Jul 2014 07:26:20 +0530 Thank you Mett. Traceroute packets from another host dropped by ISP netwoek at 218.248.0.0 netstat -rn Destination Gateway Genmask Flags MSS Window irtt Iface 0.0.0.0 0.0.0.0 0.0.0.0 U 0 0 0 ppp0 117.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 eth0 117.222.8.1 0.0.0.0 255.255.255.255 UH0 0 0 ppp0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 224.0.0.0 0.0.0.0 240.0.0.0 U 0 0 0 eth0 ifconfig eth0:0 yields: ip a 2: eth0: link/ether inet 192.168.1.2/24 brd 192.168.1.255 scope global eth0 inet 117.222.15.189/8 brd 117.255.255.255 scope global eth0:0 3: ppp0: link/ppp inet 117.222.15.189 peer 117.222.8.1/32 scope global ppp0 This is a lone host - no network. Address 117.222.15.189 does not map to modem-router. Nmap on modem returns ports 23,80,5431 open. All ports on 117.222.15.189 filtered. The state may not be reproducible. Oftentiimes eth0 gets only 192.168.1.2 address (which can be pinged ),and ppp0 does not exist. On 7/14/14, mett m...@pmars.jp wrote: On Mon, 14 Jul 2014 00:31:43 +0530 rajiv chavan rc214...@gmail.com wrote: Sun, 13 Jul 2014 23:34:41 +0530 ip a output on an adsl+ (pppoe) client: =snip= 2: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 inet 192.168.1.2/24 brd 192.168.1.255 scope global eth0 3: ppp0: POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP mtu 1460 qdisc pfifo_fast state UNKNOWN group default qlen 3 link/ppp inet 117.222.15.189 peer 117.222.8.1/32 scope global ppp0 =snip= Can ping 127.0.0.1 and 192.168.1.1 but not 117.222.15.189 nor 192.168.1.2 tcpdump on eth0 detcts pppoe packets from 117.222.15.189 to hosts except 192.168.1.1-2 nmap reports 117.222.15.189 ip but all posrt 1-1000 filtered. Hi, Everything is on the same interface? I don't think Eth0 can be routing for your local network and at the same time become ppp0 and route for a global network. I think you'll need some kind of subinterfaces if you want to use only one physical interface for your local network and the outside one. Maybe try a traceroute and you'll see where the packets are going. Also, check the routes(netstat -nr or route -ne). You might give a try one by one to see at what point it stops working: -try only the local network first and once it's working try to set up your pppoe link. hth -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140714091211.3c1fd4cd@asus.tamerr No prob, by the way, better to answer to the list than PM to my address, as sby who might have same problem can see this thread and benefit of the info as well. Also, on this mailing list, generally you post down the thread, like this other persons reading the thread can get an idea of the whole thing, easily by scrolling down. Regarding the issue, if this is a lone host and you are not NATing, one easy way of trblshooting would be : -no manual ip address at all on eth0 -no manual routes as well, -then run pppoeconf, it's quite straight forward and tells you if it finds an aggregator on your ISP side. With the following top. PCmodem-Internet Did you try to set up route manually, as I can see many routes under netstat -nr ? By the way, I never tried with subinterfaces on same phy for outside and inside, but I don't understand why you have a route for multicast(224 smtg) and also a route for the 117.0.0.0 network and at the same time one for 192.168, all that on eth0. Even if eth0 is showing eth0:0, I don't think you need a route for 117.0.0.0., neither one for multicast(224). Try to remove them and see what happened but would be better, faster and easier to just run pppoeconf with an eth0 interface without any IP address. Also, I was talking about traceroute from your host to outside. If it doesn't go anywhere, you will be sure the problem is on your side. Also, you said your host is alone, no network but eth0 on 192.168.1.2 can be pinged. I don't understand how that is possible. As a ref, I paste mine down here # netstat -nr Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface ISP.AGG.IP.ADD0.0.0.0 255.255.255.255 UH0 0 0 ppp0 192.168.1.0 0.0.0.0
Re: ip address on dhcp client
On Mon, 14 Jul 2014 00:31:43 +0530 rajiv chavan rc214...@gmail.com wrote: Sun, 13 Jul 2014 23:34:41 +0530 ip a output on an adsl+ (pppoe) client: =snip= 2: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 inet 192.168.1.2/24 brd 192.168.1.255 scope global eth0 3: ppp0: POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP mtu 1460 qdisc pfifo_fast state UNKNOWN group default qlen 3 link/ppp inet 117.222.15.189 peer 117.222.8.1/32 scope global ppp0 =snip= Can ping 127.0.0.1 and 192.168.1.1 but not 117.222.15.189 nor 192.168.1.2 tcpdump on eth0 detcts pppoe packets from 117.222.15.189 to hosts except 192.168.1.1-2 nmap reports 117.222.15.189 ip but all posrt 1-1000 filtered. Hi, Everything is on the same interface? I don't think Eth0 can be routing for your local network and at the same time become ppp0 and route for a global network. I think you'll need some kind of subinterfaces if you want to use only one physical interface for your local network and the outside one. Maybe try a traceroute and you'll see where the packets are going. Also, check the routes(netstat -nr or route -ne). You might give a try one by one to see at what point it stops working: -try only the local network first and once it's working try to set up your pppoe link. hth -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140714091211.3c1fd4cd@asus.tamerr
Re: ip address on dhcp client
On Mon, 14 Jul 2014 07:53:06 +0530 rajiv chavan rc214...@gmail.com wrote: Mon, 14 Jul 2014 07:26:20 +0530 Thank you Mett. Traceroute packets from another host dropped by ISP netwoek at 218.248.0.0 netstat -rn Destination Gateway Genmask Flags MSS Window irtt Iface 0.0.0.0 0.0.0.0 0.0.0.0 U 0 0 0 ppp0 117.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 eth0 117.222.8.1 0.0.0.0 255.255.255.255 UH0 0 0 ppp0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 224.0.0.0 0.0.0.0 240.0.0.0 U 0 0 0 eth0 ifconfig eth0:0 yields: ip a 2: eth0: link/ether inet 192.168.1.2/24 brd 192.168.1.255 scope global eth0 inet 117.222.15.189/8 brd 117.255.255.255 scope global eth0:0 3: ppp0: link/ppp inet 117.222.15.189 peer 117.222.8.1/32 scope global ppp0 This is a lone host - no network. Address 117.222.15.189 does not map to modem-router. Nmap on modem returns ports 23,80,5431 open. All ports on 117.222.15.189 filtered. The state may not be reproducible. Oftentiimes eth0 gets only 192.168.1.2 address (which can be pinged ),and ppp0 does not exist. On 7/14/14, mett m...@pmars.jp wrote: On Mon, 14 Jul 2014 00:31:43 +0530 rajiv chavan rc214...@gmail.com wrote: Sun, 13 Jul 2014 23:34:41 +0530 ip a output on an adsl+ (pppoe) client: =snip= 2: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 inet 192.168.1.2/24 brd 192.168.1.255 scope global eth0 3: ppp0: POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP mtu 1460 qdisc pfifo_fast state UNKNOWN group default qlen 3 link/ppp inet 117.222.15.189 peer 117.222.8.1/32 scope global ppp0 =snip= Can ping 127.0.0.1 and 192.168.1.1 but not 117.222.15.189 nor 192.168.1.2 tcpdump on eth0 detcts pppoe packets from 117.222.15.189 to hosts except 192.168.1.1-2 nmap reports 117.222.15.189 ip but all posrt 1-1000 filtered. Hi, Everything is on the same interface? I don't think Eth0 can be routing for your local network and at the same time become ppp0 and route for a global network. I think you'll need some kind of subinterfaces if you want to use only one physical interface for your local network and the outside one. Maybe try a traceroute and you'll see where the packets are going. Also, check the routes(netstat -nr or route -ne). You might give a try one by one to see at what point it stops working: -try only the local network first and once it's working try to set up your pppoe link. hth -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140714091211.3c1fd4cd@asus.tamerr No prob, by the way, better to answer to the list than PM to my address, as sby who might have same problem can see this thread and benefit of the info as well. Also, on this mailing list, generally you post down the thread, like this other persons reading the thread can get an idea of the whole thing, easily by scrolling down. Regarding the issue, if this is a lone host and you are not NATing, one easy way of trblshooting would be : -no manual ip address at all on eth0 -no manual routes as well, -then run pppoeconf, it's quite straight forward and tells you if it finds an aggregator on your ISP side. With the following top. PCmodem-Internet Did you try to set up route manually, as I can see many routes under netstat -nr ? By the way, I never tried with subinterfaces on same phy for outside and inside, but I don't understand why you have a route for multicast(224 smtg) and also a route for the 117.0.0.0 network and at the same time one for 192.168, all that on eth0. Even if eth0 is showing eth0:0, I don't think you need a route for 117.0.0.0., neither one for multicast(224). Try to remove them and see what happened but would be better, faster and easier to just run pppoeconf with an eth0 interface without any IP address. Also, I was talking about traceroute from your host to outside. If it doesn't go anywhere, you will be sure the problem is on your side. Also, you said your host is alone, no network but eth0 on 192.168.1.2 can be pinged. I don't understand how that is possible. As a ref, I paste mine down here # netstat -nr Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface ISP.AGG.IP.ADD0.0.0.0 255.255.255.255 UH0 0 0 ppp0 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 0.0.0.0 0.0.0.0 0.0.0.0 U 0 0 0 ppp0 Thing is I have 2 phy interfaces, so ppp0 is not running on eth0 but eth1, that you cannot see here. I only ran pppoeconf,
