Re: ip stack broken?

From: slave-mike (slave-mike_at_rv1.dynip.com)
Date: 10/19/03

  • Next message: mjoyner: "Re: -march athlon breaks my networking was: ip stack broken?"
    Date: Sun, 19 Oct 2003 01:34:33 -0400
    To: mjoyner <mjoyner@rv1.dynip.com>
    
    
    

    Follows is my arp table entries and interface while running a -current
    kernel.

    My system can see the default gateway etc, and appears to be
    transmitting packets (based on activity of hub lights), but does not
    seem to be receiving them back or knowing they are received back beyond
    the arp/rarp packets or it just plain eats them. :)

    192.168.0.1 is my default gw

    I have tried both fxp0 and dc0.
    I have tried both with and without vmnet being loaded.

    ? (10.255.255.255) at ff:ff:ff:ff:ff:ff on vmnet1 permanent [ethernet]
    ? (192.168.0.0) at ff:ff:ff:ff:ff:ff on dc0 permanent [ethernet]
    ? (192.168.0.1) at 00:a0:c5:e6:58:00 on dc0 [ethernet]
    ? (192.168.0.253) at 00:06:25:54:2a:20 on dc0 [ethernet]
    ? (192.168.0.255) at ff:ff:ff:ff:ff:ff on dc0 permanent [ethernet]

    dc0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
             inet6 fe80::2c0:f0ff:fe48:7562%dc0 prefixlen 64 scopeid 0x1
             inet 192.168.0.2 netmask 0xffffff00 broadcast 192.168.0.255
             ether 00:c0:f0:48:75:62
             media: Ethernet autoselect (100baseTX <full-duplex>)
             status: active

    mjoyner wrote:
    > It works fine with a 5.1 kernel.
    >
    > Doug White wrote:
    >
    >> On Fri, 17 Oct 2003, mjoyner wrote:
    >>
    >>
    >>> When I use a current kernel, my system will obtain an ip address via
    >>> dhclient, but thereafter, it cannot see the network.
    >>>
    >>> I have tried switching ethernet cards. (used both a dc0 and an fxp0)
    >>> Am currently using a 5.1-RELEASE kernel to have network access.
    >>>
    >>> Advice?
    >>
    >>
    >>
    >> Perhaps your DHCP server is handing out bogus info?
    >>
    >
    > _______________________________________________
    > freebsd-current@freebsd.org mailing list
    > http://lists.freebsd.org/mailman/listinfo/freebsd-current
    > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"

    
    

    ? (10.255.255.255) at ff:ff:ff:ff:ff:ff on vmnet1 permanent [ethernet]
    ? (192.168.0.0) at ff:ff:ff:ff:ff:ff on dc0 permanent [ethernet]
    ? (192.168.0.1) at 00:a0:c5:e6:58:00 on dc0 [ethernet]
    ? (192.168.0.253) at 00:06:25:54:2a:20 on dc0 [ethernet]
    ? (192.168.0.255) at ff:ff:ff:ff:ff:ff on dc0 permanent [ethernet]

    dc0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
            inet6 fe80::2c0:f0ff:fe48:7562%dc0 prefixlen 64 scopeid 0x1
            inet 192.168.0.2 netmask 0xffffff00 broadcast 192.168.0.255
            ether 00:c0:f0:48:75:62
            media: Ethernet autoselect (100baseTX <full-duplex>)
            status: active

    
    

    _______________________________________________
    freebsd-current@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-current
    To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"


  • Next message: mjoyner: "Re: -march athlon breaks my networking was: ip stack broken?"

    Relevant Pages

    • Re: RFC: get_maintainer.pl: append reason for cc to the name by default
      ... This can be unexpected for the receiving side and can and does provoke ... As get_maintainer.pl is frequently used by kernel newcomers who _can_ ... By appending a a note of the reason for the cc in the name, ... cc'list to their liking. ...
      (Linux-Kernel)
    • RFC: get_maintainer.pl: append reason for cc to the name by default
      ... This can be unexpected for the receiving side and can and does provoke ... As get_maintainer.pl is frequently used by kernel newcomers who _can_ ... By appending a a note of the reason for the cc in the name, ... cc'list to their liking. ...
      (Linux-Kernel)
    • completely lost as to what to do, or where to look.
      ... I'm lost as to where to look in the kernel, ... receiving a black screen with startx ... DRI seems to be fine, I'm noticing a sema_init but am not sure if this ...
      (Linux-Kernel)
    • Re: hd error after kernel upgrade
      ... I've been receiving those ... messages after booting the new kernel. ... To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx ...
      (Debian-User)
    • kernel freeze with Fritz!PCI v2.0 ISDN after update
      ... The recent kernel update "SuSE Security Announcement: ... " causes a system freeze when sending or receiving ... When sending a fax (or receiving, I can not test, because I can only ... The other system even has a Fritz!PCI v1.0 ISDN card. ...
      (alt.os.linux.suse)