ethernet after boot problem - Debian

This is a discussion on ethernet after boot problem - Debian ; averatec 3200 series with 2.6.12 kernal. dchp3-client works on boot to give me internet etc iff ethernet cable is plugged into the laptop. If i plug in the ethernet cable after boot there seems to be no way to get ...

+ Reply to Thread
Results 1 to 10 of 10

Thread: ethernet after boot problem

  1. ethernet after boot problem

    averatec 3200 series with 2.6.12 kernal. dchp3-client works on boot to give
    me internet etc iff ethernet cable is plugged into the laptop. If i plug
    in the ethernet cable after boot there seems to be no way to get internet.
    i don't know my way around network configuration and the suggestions given
    in deb. manual etc. and through user groups dont seem to help. i haven't
    included any information about the connection because 1. i probably dont
    know what i am looking for and 2. i dont know what is needed to solve this
    problem. tell me what would help you and i will send what ever it is.

    The laptop has dhcp3-common, dhcpd, dhcp3-client, laptop-net (which I am not
    using presently) installed.

    Any help would just be great,

    Yigal Weinstein


  2. Re: ethernet after boot problem

    On Thu, 2005-12-08 at 17:58 -0800, Yigal Weinstein wrote:
    > averatec 3200 series with 2.6.12 kernal. dchp3-client works on boot
    > to give me internet etc iff ethernet cable is plugged into the laptop.
    > If i plug in the ethernet cable after boot there seems to be no way to
    > get internet. i don't know my way around network


    Something like 'ifup eth0' should probably get the network set up. If
    you want to automate it (so the network gets configures as soon as you
    plug in the cable), have a look at the ifplugd package.

    Koen


    --
    To UNSUBSCRIBE, email to debian-laptop-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

  3. Re: ethernet after boot problem

    On 12/9/05, Koen Vermeer wrote:
    >
    > On Thu, 2005-12-08 at 17:58 -0800, Yigal Weinstein wrote:
    > > averatec 3200 series with 2.6.12 kernal. dchp3-client works on boot
    > > to give me internet etc iff ethernet cable is plugged into the laptop.
    > > If i plug in the ethernet cable after boot there seems to be no way to
    > > get internet. i don't know my way around network

    >
    > Something like 'ifup eth0' should probably get the network set up. If
    > you want to automate it (so the network gets configures as soon as you
    > plug in the cable), have a look at the ifplugd package.
    >
    > Koen



    Thanks but no thanks. You see this is the problem, nothing normal gives me
    internet access if I dont have the ethernet cable in the computer when I
    boot up. ifup, dhcp3-client etc. none of this works. So if there is
    something I can give this group that would help in diagnosing my problem
    please reply to this. I want to have simple things like be able to plug my
    laptop when on into a dhcp server and start to work on the internet.

    Yigal

    --
    > To UNSUBSCRIBE, email to debian-laptop-REQUEST@lists.debian.org
    > with a subject of "unsubscribe". Trouble? Contact
    > listmaster@lists.debian.org
    >
    >



  4. Re: ethernet after boot problem

    (No need to cc me, I'm on the list!)

    On Fri, 2005-12-09 at 01:13 -0800, Yigal Weinstein wrote:
    > Thanks but no thanks. You see this is the problem, nothing normal
    > gives me internet access if I dont have the ethernet cable in the
    > computer when I boot up. ifup, dhcp3-client etc. none of this works.
    > So if there is something I can give this group that would help in
    > diagnosing my problem please reply to this. I want to have simple
    > things like be able to plug my laptop when on into a dhcp server and
    > start to work on the internet.


    At least provide /etc/network/interfaces, and a log of what happens on
    boot when the cable is plugged in. Also, if the cable isn't plugged in,
    the output of 'ifconfig eth0', and the output of 'ifup eth0'.

    Koen


    --
    To UNSUBSCRIBE, email to debian-laptop-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

  5. Re: ethernet after boot problem


    On Fri, 9 Dec 2005 01:13:22 -0800
    Yigal Weinstein wrote:

    > On 12/9/05, Koen Vermeer wrote:
    > >
    > > On Thu, 2005-12-08 at 17:58 -0800, Yigal Weinstein wrote:
    > > > averatec 3200 series with 2.6.12 kernal. dchp3-client works on boot
    > > > to give me internet etc iff ethernet cable is plugged into the laptop.
    > > > If i plug in the ethernet cable after boot there seems to be no way to
    > > > get internet. i don't know my way around network

    > >
    > > Something like 'ifup eth0' should probably get the network set up. If
    > > you want to automate it (so the network gets configures as soon as you
    > > plug in the cable), have a look at the ifplugd package.
    > >
    > > Koen

    > # interface nonet



    I have in /etc/network/interfaces the following

    iface eth0 inet static
    address 192.168.254.2
    netmask 255.255.255.255

    just to have the interface running after boot.
    (I manually start DHCP or static assigned IP addresses (sudo ofcourse) depending on the location)

    Regards,

    Rob de Graaf



    --
    To UNSUBSCRIBE, email to debian-laptop-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

  6. Re: ethernet after boot problem

    Ok, bellow are /etc/network/interfaces, ifconfig eth0 and ifup eth0
    messages, and /var/log/dmesg. Hopefully this will help. Thank you for
    your time.

    Yigal

    Here is /etc/network/interfaces:

    auto lo

    iface lo inet loopback

    auto eth0
    iface eth0 inet dhcp
    hostname yigal
    name Ethernet LAN card
    __________________________________________________ ____________________
    Here is the message for ifup when cable is inserted after boot:
    yigal:/var/log# ifup eth0
    Internet Systems Consortium DHCP Client V3.0.3
    Copyright 2004-2005 Internet Systems Consortium.
    All rights reserved.
    For info, please visit http://www.isc.org/products/DHCP

    Listening on LPF/eth0/00:40:45:25:f1:80
    Sending on LPF/eth0/00:40:45:25:f1:80
    Sending on Socket/fallback
    DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
    DHCPOFFER from 134.139.119.5
    DHCPREQUEST on eth0 to 255.255.255.255 port 67
    DHCPACK from 134.139.119.5
    bound to 134.139.119.109 -- renewal in 264580 seconds.
    __________________________________________________ ______________________
    it seams to connect but I don't have access to the internet.
    __________________________________________________ ______________________
    Here is the message for ifconfig eth0 when cable is inserted after boot:

    yigalepw@yigal:~$ ifconfig eth0
    eth0 Link encap:Ethernet HWaddr 00:40:45:25:F1:80
    inet addr:134.139.119.109 Bcast:134.139.119.255 Mask:
    255.255.255.0
    inet6 addr: fe80::240:45ff:fe25:f180/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:156 errors:0 dropped:0 overruns:0 frame:0
    TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:17595 (17.1 KiB) TX bytes:1746 (1.7 KiB)
    Interrupt:11 Base address:0xd800
    __________________________________________________ ______________________
    again it seams there it is connected but I can't get onto the internet
    __________________________________________________ ______________________
    Here is /var/log/dmesg when ethernet cable is plugged in at boot:

    Linux version 2.6.12-1-k7 (horms@tabatha.lab.ultramonkey.org) (gcc version
    4.0.2 20050917 (prerelease) (Debian 4.0.1-8)) #1 Tue Sep 27 13:22:07 JST
    2005
    BIOS-provided physical RAM map:
    BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
    BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
    BIOS-e820: 00000000000d0000 - 00000000000d6000 (reserved)
    BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
    BIOS-e820: 0000000000100000 - 000000001dff0000 (usable)
    BIOS-e820: 000000001dff0000 - 000000001dff8000 (ACPI data)
    BIOS-e820: 000000001dff8000 - 000000001e000000 (ACPI NVS)
    BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved)
    0MB HIGHMEM available.
    479MB LOWMEM available.
    On node 0 totalpages: 122864
    DMA zone: 4096 pages, LIFO batch:1
    Normal zone: 118768 pages, LIFO batch:31
    HighMem zone: 0 pages, LIFO batch:1
    DMI 2.3 present.
    ACPI: RSDP (v000 AMI ) @ 0x000fa2d0
    ACPI: RSDT (v001 AMIINT VIA_K7 0x00000010 MSFT 0x00000097) @ 0x1dff0000
    ACPI: FADT (v001 AMIINT VIA_K7 0x00000011 MSFT 0x00000097) @ 0x1dff0030
    ACPI: DSDT (v001 VIA VIA_K7 0x00001000 INTL 0x02002024) @ 0x00000000
    ACPI: PM-Timer IO Port: 0x808
    Allocating PCI resources starting at 1e000000 (gap: 1e000000:e1f80000)
    Built 1 zonelists
    Kernel command line: root=/dev/hda1 ro vga=775
    Local APIC disabled by BIOS -- you can enable it with "lapic"
    mapped APIC to ffffd000 (013c2000)
    Initializing CPU#0
    PID hash table entries: 2048 (order: 11, 32768 bytes)
    Detected 1658.692 MHz processor.
    Using pmtmr for high-res timesource
    Console: colour dummy device 80x25
    Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
    Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
    Memory: 482276k/491456k available (1692k kernel code, 8540k reserved, 721k
    data, 176k init, 0k highmem)
    Checking if this processor honours the WP bit even in supervisor mode... Ok..
    Calibrating delay loop... 3276.80 BogoMIPS (lpj=1638400)
    Security Framework v1.0.0 initialized
    SELinux: Disabled at boot.
    Mount-cache hash table entries: 512
    CPU: After generic identify, caps: 0383f9ff c1cbf9ff 00000000 00000000
    00000000 00000000 00000000
    CPU: After vendor identify, caps: 0383f9ff c1cbf9ff 00000000 00000000
    00000000 00000000 00000000
    CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
    CPU: L2 Cache: 512K (64 bytes/line)
    CPU: After all inits, caps: 0383f9ff c1cbf9ff 00000000 00000020 00000000
    00000000 00000000
    Intel machine check architecture supported.
    Intel machine check reporting enabled on CPU#0.
    CPU: AMD mobile AMD Athlon(tm) XP-M (LV) 2200+ stepping 00
    Enabling fast FPU save and restore... done.
    Enabling unmasked SIMD FPU exception support... done.
    Checking 'hlt' instruction... OK.
    ACPI: setting ELCR to 0200 (from 0c00)
    checking if image is initramfs...it isn't (bad gzip magic numbers); looks
    like an initrd
    Freeing initrd memory: 1448k freed
    NET: Registered protocol family 16
    PCI: PCI BIOS revision 2.10 entry at 0xfdb51, last bus=1
    PCI: Using configuration type 1
    mtrr: v2.0 (20020519)
    ACPI: Subsystem revision 20050309
    ACPI: Interpreter enabled
    ACPI: Using PIC for interrupt routing
    ACPI: PCI Root Bridge [PCI0] (0000:00)
    PCI: Probing PCI hardware (bus 00)
    Boot video device is 0000:01:00.0
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
    ACPI: Embedded Controller [ECD] (gpe 4)
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGP_._PRT]
    ACPI: PCI Interrupt Link [LNKA] (IRQs 4 *11 14 15)
    ACPI: PCI Interrupt Link [LNKB] (IRQs 3 5 9 14 15) *0, disabled.
    ACPI: PCI Interrupt Link [LNKC] (IRQs *10 12)
    ACPI: PCI Interrupt Link [LNKD] (IRQs 6 7) *0, disabled.
    Linux Plug and Play Support v0.97 (c) Adam Belay
    pnp: PnP ACPI init
    pnp: PnP ACPI: found 8 devices
    PnPBIOS: Disabled by ACPI PNP
    PCI: Using ACPI for IRQ routing
    PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a
    report
    VFS: Disk quotas dquot_6.5.1
    Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
    devfs: 2004-01-31 Richard Gooch (rgooch@atnf.csiro.au)
    devfs: boot_options: 0x0
    Initializing Cryptographic API
    isapnp: Scanning for PnP cards...
    isapnp: No Plug & Play device found
    PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
    i8042.c: Detected active multiplexing controller, rev 1.1.
    serio: i8042 AUX0 port at 0x60,0x64 irq 12
    serio: i8042 AUX1 port at 0x60,0x64 irq 12
    serio: i8042 AUX2 port at 0x60,0x64 irq 12
    serio: i8042 AUX3 port at 0x60,0x64 irq 12
    serio: i8042 KBD port at 0x60,0x64 irq 1
    Serial: 8250/16550 driver $Revision: 1.90 $ 48 ports, IRQ sharing enabled
    io scheduler noop registered
    io scheduler anticipatory registered
    io scheduler deadline registered
    io scheduler cfq registered
    RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
    NET: Registered protocol family 2
    IP: routing cache hash table of 4096 buckets, 32Kbytes
    TCP established hash table entries: 16384 (order: 5, 131072 bytes)
    TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
    TCP: Hash tables configured (established 16384 bind 16384)
    ACPI wakeup devices:
    SLPB PCI0 USB1 USB2 USB3 EHCI MC9 ILAN
    ACPI: (supports S0 S3 S4 S5)
    RAMDISK: cramfs filesystem found at block 0
    RAMDISK: Loading 1448KiB [1 disk] into ram disk...
    |/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-done.
    VFS: Mounted root (cramfs filesystem) readonly.
    Freeing unused kernel memory: 176k freed
    Capability LSM initialized
    vesafb: framebuffer at 0xd8000000, mapped to 0xde880000, using 2560k, total
    32768k
    vesafb: mode is 1280x1024x8, linelength=1280, pages=24
    vesafb: protected mode interface info at c000:785f
    vesafb: scrolling: redraw
    vesafb: Pseudocolor: size=8:8:8:8, shift=0:0:0:0
    mtrr: 0xd8000000,0x2000000 overlaps existing 0xd8000000,0x200000
    mtrr: 0xd8000000,0x1000000 overlaps existing 0xd8000000,0x200000
    mtrr: 0xd8000000,0x800000 overlaps existing 0xd8000000,0x200000
    mtrr: 0xd8000000,0x400000 overlaps existing 0xd8000000,0x200000
    fb0: VESA VGA frame buffer device
    Console: switching to colour frame buffer device 160x64
    NET: Registered protocol family 1
    Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
    ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
    input: AT Translated Set 2 keyboard on isa0060/serio0
    VP_IDE: IDE controller at PCI slot 0000:00:11.1
    ACPI: PCI Interrupt 0000:00:11.1[A]: no GSI
    PCI: Via IRQ fixup for 0000:00:11.1, from 255 to 15
    VP_IDE: chipset revision 6
    VP_IDE: not 100% native mode: will probe irqs later
    VP_IDE: VIA vt8235 (rev 00) IDE UDMA133 controller on pci0000:00:11.1
    ide0: BM-DMA at 0xfc00-0xfc07, BIOS settings: hdaMA, hdbio
    ide1: BM-DMA at 0xfc08-0xfc0f, BIOS settings: hdcMA, hddio
    Probing IDE interface ide0...
    hda: IC25N080ATMR04-0, ATA DISK drive
    ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
    Probing IDE interface ide1...
    hdc: Slimtype DVDRW SOSW-852S, ATAPI CD/DVD-ROM drive
    ide1 at 0x170-0x177,0x376 on irq 15
    Probing IDE interface ide2...
    Probing IDE interface ide3...
    Probing IDE interface ide4...
    Probing IDE interface ide5...
    hda: max request size: 1024KiB
    hda: 156301488 sectors (80026 MB) w/7884KiB Cache, CHS=16383/255/63,
    UDMA(100)
    hda: cache flushes supported
    /dev/ide/host0/bus0/target0/lun0: p1 p2 < p5 >
    kjournald starting. Commit interval 5 seconds
    EXT3-fs: mounted filesystem with ordered data mode.
    input: PC Speaker
    hdc: ATAPI 24X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33)
    Uniform CD-ROM driver Revision: 3.20
    Real Time Clock Driver v1.12
    mice: PS/2 mouse device common for all mice
    Linux agpgart interface v0.101 (c) Dave Jones
    agpgart: Detected VIA KM400/KM400A chipset
    agpgart: AGP aperture is 64M @ 0xe0000000
    pci_hotplug: PCI Hot Plug PCI Core version: 0.5
    shpchp: shpc_init : shpc_cap_offset == 0
    shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
    irda_init()
    NET: Registered protocol family 23
    Synaptics Touchpad, model: 1, fw: 5.1, id: 0x8f40b1, caps: 0x80471b/0x0
    input: SynPS/2 Synaptics TouchPad on isa0060/serio4
    usbcore: registered new driver usbfs
    usbcore: registered new driver hub
    Linux Kernel Card Services
    options: [pci] [cardbus] [pm]
    ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 10
    PCI: setting IRQ 10 as level-triggered
    ACPI: PCI Interrupt 0000:00:0a.0[A] -> Link [LNKC] -> GSI 10 (level, low) ->
    IRQ 10
    Yenta: CardBus bridge found at 0000:00:0a.0 [14ff:c602]
    Yenta O2: res at 0x94/0xD4: 00/ea
    Yenta O2: enabling read prefetch/write burst
    Yenta: ISA IRQ mask 0x00b8, PCI irq 10
    Socket status: 30000006
    ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 7
    PCI: setting IRQ 7 as level-triggered
    ACPI: PCI Interrupt 0000:00:10.3[D] -> Link [LNKD] -> GSI 7 (level, low) ->
    IRQ 7
    PCI: Via IRQ fixup for 0000:00:10.3, from 0 to 7
    ehci_hcd 0000:00:10.3: VIA Technologies, Inc. USB 2.0
    ehci_hcd 0000:00:10.3: new USB bus registered, assigned bus number 1
    ehci_hcd 0000:00:10.3: irq 7, io mem 0xdfffdf00
    ehci_hcd 0000:00:10.3: USB 2.0 initialized, EHCI 1.00, driver 10 Dec 2004
    hub 1-0:1.0: USB hub found
    hub 1-0:1.0: 6 ports detected
    via-rhine.c:v1.10-LK1.2.0-2.6 June-10-2004 Written by Donald Becker
    ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11
    PCI: setting IRQ 11 as level-triggered
    ACPI: PCI Interrupt 0000:00:12.0[A] -> Link [LNKA] -> GSI 11 (level, low) ->
    IRQ 11
    eth0: VIA Rhine II at 0x1d800, 00:40:45:25:f1:80, IRQ 11.
    eth0: MII PHY found at address 1, status 0x7849 advertising 05e1 Link 0000.
    USB Universal Host Controller Interface driver v2.2
    ACPI: PCI Interrupt 0000:00:10.0[A] -> Link [LNKD] -> GSI 7 (level, low) ->
    IRQ 7
    PCI: Via IRQ fixup for 0000:00:10.0, from 0 to 7
    uhci_hcd 0000:00:10.0: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1Controller
    uhci_hcd 0000:00:10.0: new USB bus registered, assigned bus number 2
    uhci_hcd 0000:00:10.0: irq 7, io base 0x0000e400
    hub 2-0:1.0: USB hub found
    hub 2-0:1.0: 2 ports detected
    ACPI: PCI Interrupt 0000:00:10.1[B] -> Link [LNKD] -> GSI 7 (level, low) ->
    IRQ 7
    PCI: Via IRQ fixup for 0000:00:10.1, from 0 to 7
    uhci_hcd 0000:00:10.1: VIA Technologies, Inc. VT82xxxxx UHCI USB
    1.1Controller (#2)
    uhci_hcd 0000:00:10.1: new USB bus registered, assigned bus number 3
    uhci_hcd 0000:00:10.1: irq 7, io base 0x0000e800
    hub 3-0:1.0: USB hub found
    hub 3-0:1.0: 2 ports detected
    ACPI: PCI Interrupt 0000:00:10.2[C] -> Link [LNKD] -> GSI 7 (level, low) ->
    IRQ 7
    PCI: Via IRQ fixup for 0000:00:10.2, from 0 to 7
    uhci_hcd 0000:00:10.2: VIA Technologies, Inc. VT82xxxxx UHCI USB
    1.1Controller (#3)
    uhci_hcd 0000:00:10.2: new USB bus registered, assigned bus number 4
    uhci_hcd 0000:00:10.2: irq 7, io base 0x0000ec00
    hub 4-0:1.0: USB hub found
    hub 4-0:1.0: 2 ports detected
    ACPI: PCI Interrupt 0000:00:11.6[C] -> Link [LNKC] -> GSI 10 (level, low) ->
    IRQ 10
    PCI: Setting latency timer of device 0000:00:11.6 to 64
    via82xx: Assuming DXS channels with 48k fixed sample rate.
    Please try dxs_support=1 or dxs_support=4 option
    and report if it works on your machine.
    ACPI: PCI Interrupt 0000:00:11.5[C] -> Link [LNKC] -> GSI 10 (level, low) ->
    IRQ 10
    PCI: Setting latency timer of device 0000:00:11.5 to 64
    Adding 1445808k swap on /dev/hda5. Priority:-1 extents:1
    EXT3 FS on hda1, internal journal
    device-mapper: 4.4.0-ioctl (2005-01-12) initialised: dm-devel@redhat.com
    eth0: link down
    NET: Registered protocol family 17
    eth0: link up, 10Mbps, half-duplex, lpa 0x0021
    NET: Registered protocol family 10
    Disabled Privacy Extensions on device c032f880(lo)
    IPv6 over IPv4 tunneling driver
    cs: IO port probe 0x100-0x4ff: excluding 0x408-0x40f 0x4d0-0x4d7
    cs: IO port probe 0x800-0x8ff: excluding 0x810-0x87f
    cs: IO port probe 0xc00-0xcff: clean.
    cs: IO port probe 0xa00-0xaff: clean.
    ip_tables: (C) 2000-2002 Netfilter core team
    ip_conntrack version 2.1 (3839 buckets, 30712 max) - 248 bytes per conntrack



    On 12/9/05, Koen Vermeer wrote:

    (No need to cc me, I'm on the list!)

    On Fri, 2005-12-09 at 01:13 -0800, Yigal Weinstein wrote:
    > Thanks but no thanks. You see this is the problem, nothing normal
    > gives me internet access if I dont have the ethernet cable in the
    > computer when I boot up. ifup, dhcp3-client etc. none of this works.
    > So if there is something I can give this group that would help in
    > diagnosing my problem please reply to this. I want to have simple
    > things like be able to plug my laptop when on into a dhcp server and
    > start to work on the internet.


    At least provide /etc/network/interfaces, and a log of what happens on
    boot when the cable is plugged in. Also, if the cable isn't plugged in,
    the output of 'ifconfig eth0', and the output of 'ifup eth0'.

    Koen


    --
    To UNSUBSCRIBE, email to debian-laptop-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact
    listmaster@lists.debian.org


  7. Re: ethernet after boot problem

    On Fri, 9 Dec 2005 11:47:37 -0800
    Yigal Weinstein wrote:

    > Ok, bellow are /etc/network/interfaces, ifconfig eth0 and ifup eth0
    > messages, and /var/log/dmesg. Hopefully this will help. Thank you for
    > your time.
    >
    > Yigal
    >
    > Here is /etc/network/interfaces:
    >
    > auto lo
    >
    > iface lo inet loopback
    >
    > auto eth0
    > iface eth0 inet dhcp
    > hostname yigal
    > name Ethernet LAN card
    > __________________________________________________ ____________________
    > Here is the message for ifup when cable is inserted after boot:
    > yigal:/var/log# ifup eth0
    > Internet Systems Consortium DHCP Client V3.0.3
    > Copyright 2004-2005 Internet Systems Consortium.
    > All rights reserved.
    > For info, please visit http://www.isc.org/products/DHCP
    >
    > Listening on LPF/eth0/00:40:45:25:f1:80
    > Sending on LPF/eth0/00:40:45:25:f1:80
    > Sending on Socket/fallback
    > DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
    > DHCPOFFER from 134.139.119.5
    > DHCPREQUEST on eth0 to 255.255.255.255 port 67
    > DHCPACK from 134.139.119.5
    > bound to 134.139.119.109 -- renewal in 264580 seconds.
    > __________________________________________________ ______________________
    > it seams to connect but I don't have access to the internet.
    >


    Hi Yigal,

    mmm,...

    - are you running a firewall?
    # iptables -nL
    or
    # ipchains -nL

    - is routing ok?
    # netstat -atrn

    - what happens when you ping, resolve etc.
    # ping google.com
    # ping 64.233.187.99 (is google.com)
    # host google.com

    Regards,

    Rob de Graaf


    --
    To UNSUBSCRIBE, email to debian-laptop-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

  8. Re: ethernet after boot problem

    On Fri, 9 Dec 2005 11:47:37 -0800
    Yigal Weinstein wrote:

    > Ok, bellow are /etc/network/interfaces, ifconfig eth0 and ifup eth0
    > messages, and /var/log/dmesg. Hopefully this will help. Thank you for
    > your time.
    >
    > Yigal


    Hi Yigal,

    also, I forgot; some dhcp-server require you to have ident running, otherwise they drop the service within 30 seconds.

    That is: in /etc/inetd.conf have ident unquoted, make sure the rest is quoted.
    Start inetd using:
    /etc/init.d/inetd start

    Regards,

    Rob de Graaf


    --
    To UNSUBSCRIBE, email to debian-laptop-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

  9. Re: ethernet after boot problem

    Thank you both Koen and Rob for the help. Rob it was iptables that was
    messing me up. I don't know how to properly use a firewall like that.
    After I removed it I have no problem using the internet after putting the
    cable in after boot. Although I will have to find a way of protecting this
    computer. Anyways thank you again,
    Yigal


  10. Re: ethernet after boot problem

    Yigal Weinstein writes:

    G'day Yigal.

    > Thank you both Koen and Rob for the help. Rob it was iptables that
    > was messing me up. I don't know how to properly use a firewall like
    > that. After I removed it I have no problem using the internet after
    > putting the cable in after boot. Although I will have to find a way
    > of protecting this computer.


    I would suggest you investigate a relatively simple firewall toolkit
    like 'firehol' or 'shorewall', both of which are available in
    Debian/stable.

    They can provide a secure system without your needing to understand the
    lowest level details of the iptables system, which is a good way to be
    safer while you learn there.

    Regards,
    Daniel


    --
    To UNSUBSCRIBE, email to debian-laptop-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

+ Reply to Thread