Re: ip address on dhcp client
On 7/17/14, rajiv chavan <rc214105@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 <mett@pmars.jp> wrote:
>> On Mon, 14 Jul 2014 22:33:11 +0530
>> rajiv chavan <rc214105@gmail.com> wrote:
>>
>>> On Mon, 14 Jul 2014 07:53:06 +0530
>>> - Hide quoted text -
>>> rajiv chavan <rc214105@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 UH 0 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 <mett@pmars.jp> wrote:
>>> > > On Mon, 14 Jul 2014 00:31:43 +0530
>>> > > rajiv chavan <rc214105@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-REQUEST@lists.debian.org
>>> > > with a subject of "unsubscribe". Trouble? Contact
>>> > > listmaster@lists.debian.org
>>> > > Archive:
>>> > > [🔎] 20140714091211.3c1fd4cd@asus.tamerr">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.
>>>
>>> PC----modem-----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.ADD 0.0.0.0 255.255.255.255 UH 0 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, did not install any routes or ip address on the
>>> ppp0 interface.
>>>
>>> then ip a
>>>
>>> 2: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
>>> state UP qlen 1000
>>> link/ether 00:22:cf:6b:68:0d brd ff:ff:ff:ff:ff:ff
>>>
>>> 3: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
>>> state UP qlen 1000
>>> link/ether 00:07:95:d5:2f:da brd ff:ff:ff:ff:ff:ff
>>> inet 192.168.1.1/24 brd 192.168.1.255 scope global eth0
>>> 190: ppp0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1454 qdisc
>>> pfifo_fast state UNKNOWN qlen 3
>>> link/ppp
>>> inet PUB.LIC.IP.ADD peer ISP.AGG.IP.ADD/32 scope global ppp0
>>>
>>> hth
>>>
>>> ====
>>>
>>> Mon, 14 Jul 2014 13:38:51 +0530
>>>
>>> one interface eth0.
>>> + adsl modem-router
>>>
>>> Three possible states:
>>>
>>> 1
>>> (Rare) output normal as in your eth0,ppp0
>>> ppp0 address can be used to connect to host on all ports.
>>>
>>> 2
>>> Usual,: only eth0 address 192.168.1.2 is visible, modem will be on
>>> 192.168.1.1 No ppp link: traceroute to some address first hops at
>>> 192.168.1.1 second hop at ppp-peer (117.x.x.1).
>>> 192.168.1.1-2 can be pinged. Public IP address maps to
>>> modem-router(ISP-provided). Can check with nmap
>>> Host unreachable on ssh, cannot be pinged from other hosts.
>>> Tcpdump cannot capture any packet tp/from public-ip addr: probably
>>> ppp0 on router itself (bridged mode)
>>> Public ip addr visible on modem web interface as WAN IP address ( and
>>> to interent hosts as ENV{REMOTE_ADDR})
>>> >route -n
>>> Destination Gateway Genmask Flags Metric Ref
>>> Use Iface 0.0.0.0 192.168.1.1 0.0.0.0 UG
>>> 0 0 0 eth0 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
>>>
>>>
>>> 3
>>> Infrequent: Public ip 117.222.13.120 (ppp0) /192.168.1.2 cannot be
>>> pinged. 192.168.1.1(modem) can be pinged
>>> Pulblic ip (ppp0) does not map to modem-router/localhost. Nmap returns
>>> all ports filtered.
>>> Traceroute to other hosts -
>>> first hop at 117.222.8.1.( ppp peer)
>>> Tcpdump detects pppoe session traffic from/to ppp0 [ether header
>>> absent - this is not localhost]
>>>
>>> >netstat -rn
>>> 117.0.0.0 routed thro' eth0
>>> 192.168.1.0 routed thro' ppp0
>>> - - -
>>> Second and Third state : cannot connect to host from other hosts[ ssh
>>> telnet} Only localhost can initiate connection.
>>> DHCP lease is <24 hours. Can be a few hours or few minutes at times.
>>> Connectivity loss is random and frequent.
>>>
>>> pppoe stats on modem:
>>> Service VPI/VCI Protocol Interface
>>> Received Transmitted Bytes Pkts Errs
>>> Drops Bytes Pkts Errs Drops
>>> pppoe_0_35_1 0/0/35 PPPoE ppp_0_0_35_1
>>> 3162509 4204 0 0 312523
>>> 3994 0 0 br_0_32 0/0/32 Bridge
>>> nas_0_0_32 0 0 0 0 3992916
>>> 56909 0 283 br_0_100 0/0/100
>>> Bridge nas_0_0_100 0 0 0 0
>>> 3992902 56909 0 282 br_8_81 0/8/81
>>> Bridge nas_0_8_81 0 0 0 0
>>> 3993320 56910 0 280 br_8_35 0/8/35
>>> Bridge nas_0_8_35 0 0 0 0
>>> 3992951 56909 0 280 br_14_34
>>> 0/14/34 Bridge nas_0_14_34 0 0
>>> 0 0 3992951 56909 0 279
>>> br_1_41 0/1/41 Bridge nas_0_1_41 0
>>> 0 0 0 3993377 56910 0 277
>>>
>>> Modem replacement does not alter the options.
>>>
>>> ====
>>> Apologies for all earlier errors
>>> ====
>>>
>>>
>>
>> Hey Rajiv,
>> No prob at all.
>>
>> You're talking about a modem-router. Are you trying to run your ISP
>> modem-router in bridge-mode? Or only NAT?
>>
>> If NAT, then you don't need ppp on your PC's eth0, usually the
>> router_modem is providing dhcp services on its local interface.
>>
>> But you will need to do port-forwarding to be able to ssh or anything
>> from outside.
>>
>> hth
>>
>>
>> --
>> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
>> with a subject of "unsubscribe". Trouble? Contact
>> listmaster@lists.debian.org
>> Archive: [🔎] 20140715102307.4382c23c@asus.tamerr">https://lists.debian.org/[🔎] 20140715102307.4382c23c@asus.tamerr
>>
>>
>
Reply to: