public inbox for ecos-bugs@sourceware.org help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org To: unassigned@bugs.ecos.sourceware.org Subject: [Bug 1001690] New: PPP can only route to subnet if using a null modem Date: Wed, 17 Oct 2012 15:16:00 -0000 [thread overview] Message-ID: <bug-1001690-777@http.bugs.ecos.sourceware.org/> (raw) Please do not reply to this email. Use the web interface provided at: http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001690 Summary: PPP can only route to subnet if using a null modem Product: eCos Version: 3.0 Platform: All OS/Version: All Status: UNCONFIRMED Severity: major Priority: low Component: TCP/IP AssignedTo: unassigned@bugs.ecos.sourceware.org ReportedBy: kenkyee@excite.com CC: ecos-bugs@ecos.sourceware.org Class: Advice Request If you bring up pppd on a Linux machine connected to a null modem to eCos, eCos only seems to know how to route to the local subnet. pppd was started as follows (the local subnet is 192.168.50.x): pppd noauth nodetach nocrtscts nobsdcomp nodeflate ms-dns 66.189.0.100 local lock persist debug dump logfd 1 proxyarp defaultroute 192.168.50.251:192.168.50.252 /dev/ttyS0 9600 You can't ping a remote server (e.g., Google's DNS server at 8.8.8.8). Packets seem to go out and come back onto the interface (tested w/ serial port breakout) and eCos doesn't see them. Might be related to this bug setting neg_accm in the PPP options made no difference: http://sources.redhat.com/ml/ecos-discuss/2004-12/msg00041.html -- Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
next reply other threads:[~2012-10-17 15:16 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-10-17 15:16 bugzilla-daemon [this message] -- strict thread matches above, loose matches on Subject: below -- 2012-10-17 15:16 bugzilla-daemon
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-1001690-777@http.bugs.ecos.sourceware.org/ \ --to=bugzilla-daemon@bugs.ecos.sourceware.org \ --cc=unassigned@bugs.ecos.sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).