I was able to resolve this. I found a tiny reference to the file at

 etc/default where the  eth number was set to eth2 rather than the new eth1.





On Sun, Sep 2, 2012 at 8:04 PM, Robert Lefebvre <robert.r.lefeb...@gmail.com
> wrote:

> Hi,
> Now I get the different error that "No DHCP or ProxyDHCP offers were
> received"
>
> Re: "usually I just delete /etc/udev/rules.d/70-
>
>> persistent-net.rules  , and on
>> reboot it gets recreated"
>
>
> I tried renaming persistent-net.rules instead but that didn't work and it
> didn't recreate the file after being renamed and rebooted. I commented out
> eth1 and changed eth2 (assigned to the new gigabit nic) to eth1.
>
> I basically started over and ran sudo ifconfig eth1 192.168.0.0 netmask
> 255.255.255.0
> I ran sudo ifconfig eth0 24.73.154.245 netmask 255.255.255.248 to make
> sure eth0 was right.
>
>
> ----------------------------------------------------------------------------------------
> You mentioned etc/network/interfaces
>
> Here is what it has
>
> auto lo eth0
> iface lo inet loopback
> iface eth0 inet static
>     address 24.73.154.245
>     netmask 255.255.255.248
>     broadcast 24.73.154.255
>     network 24.73.154.240
>
> ----------------------------------------------------------------------------------------
> I installed and ran ethtool and it reported this about eth1
>
> Settings for eth1:
>     Supported ports: [ TP MII ]
>     Supported link modes:   10baseT/Half 10baseT/Full
>                             100baseT/Half 100baseT/Full
>                             1000baseT/Half 1000baseT/Full
>     Supported pause frame use: No
>     Supports auto-negotiation: Yes
>     Advertised link modes:  10baseT/Half 10baseT/Full
>                             100baseT/Half 100baseT/Full
>                             1000baseT/Half 1000baseT/Full
>     Advertised pause frame use: Symmetric Receive-only
>     Advertised auto-negotiation: Yes
>     Link partner advertised link modes:  10baseT/Half 10baseT/Full
>                                          100baseT/Half 100baseT/Full
>                                          1000baseT/Full
>     Link partner advertised pause frame use: Symmetric
>     Link partner advertised auto-negotiation: Yes
>     Speed: 1000Mb/s
>     Duplex: Full
>     Port: MII
>     PHYAD: 0
>     Transceiver: internal
>     Auto-negotiation: on
>     Supports Wake-on: pumbg
>     Wake-on: g
>     Current message level: 0x00000033 (51)
>                    drv probe ifdown ifup
>     Link detected: yes
>
> ----------------------------------------------------------------------------------------
> ran ifconfig
>
>
> eth0      Link encap:Ethernet  HWaddr 00:24:8c:a9:d0:cd
>           inet addr:24.73.154.245  Bcast:24.73.154.247
> Mask:255.255.255.248
>
>           inet6 addr: fe80::224:8cff:fea9:d0cd/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:7579 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:7041 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:4765006 (4.7 MB)  TX bytes:1534151 (1.5 MB)
>           Interrupt:44 Base address:0xa000
>
> eth1      Link encap:Ethernet  HWaddr 00:0a:cd:1f:bb:95
>           inet addr:192.168.0.0  Bcast:192.168.0.255  Mask:255.255.255.0
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:78 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:691 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:22452 (22.4 KB)  TX bytes:33419 (33.4 KB)
>
>           Interrupt:43 Base address:0xa000
>
> lo        Link encap:Local Loopback
>           inet addr:127.0.0.1  Mask:255.0.0.0
>           inet6 addr: ::1/128 Scope:Host
>           UP LOOPBACK RUNNING  MTU:16436  Metric:1
>           RX packets:3565 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:3565 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:1328495 (1.3 MB)  TX bytes:1328495 (1.3 MB)
>
> lxcbr0    Link encap:Ethernet  HWaddr 2a:6d:3f:e7:1c:66
>           inet addr:10.0.3.1  Bcast:10.0.3.255  Mask:255.255.255.0
>           inet6 addr: fe80::286d:3fff:fee7:1c66/64 Scope:Link
>
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:157 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:0 (0.0 B)  TX bytes:14031 (14.0 KB)
> _____________________________________________________________
>
> I ran ltsp-update-sshkeys,
> ________________________________________________________
>
> I GOT AN ERROR
>  when I ran sudo ltsp-update-image
>
> Regenerating kernel...
> chroot:* failed to run command `/usr/share/ltsp/update-kernels': No such
> file or directory*
> Done.
> Updating /var/lib/tftpboot directories for chroot: /opt/ltsp/i386bak
> Updating /var/lib/tftpboot directories for chroot: /opt/ltsp/i386
> Removing /var/lib/tftpboot/ltsp/i386/vmlinuz-3.2.0-29-generic
> Updating /var/lib/tftpboot directories for chroot: /opt/ltsp/i386fat
> Updating /var/lib/tftpboot directories for chroot: /opt/ltsp/i386bakfat2
> __________________________________________________________
>
> Lastly, I ran
> sudo service isc-dhcp-server start
> and got
> isc-dhcp-server start/running, process 11617
>
> Then I rebooted and got the same - No DHCP
>
> Any help will be greatly appreciated.
>
>
>
>
> On Sun, Sep 2, 2012 at 2:38 PM, rob <r...@fantinibakery.com> wrote:
>
>>   I am not sure that this will solve the issue, but it is what I'd try:
>>
>>   Usually when a nic is added a new line for that card is put to this
>> file:
>> /etc/udev/rules.d/70-persistent-net.rules .
>>   you could edit that file and
>>    1- delete the line for the old usb nic [ assuming you are not going to
>> use it ].
>>    2- change the new nic line to eth1  [ it is probably assigned to be
>>  eth2 ]
>>    3- reboot.
>>
>>   Unless you edited /etc/network/interfaces ?
>>
>>
>> PS: usually I just delete /etc/udev/rules.d/70-persistent-net.rules  ,
>> and on
>> reboot it gets recreated. The thing is you never know for sure which of
>> the 2
>> nics is eth0 or eth1 . But swapping the patch cable fixes that.
>>
>>
>>
>> On Sun, 2 Sep 2012, Robert Lefebvre wrote:
>>
>> > Hey all,
>> >
>> > I'm a noob at networking and Edubuntu but am starting to grasp it (I
>> think
>> > :-).
>> >
>> > I just changed the server over from using a USB to rj45 ethernet
>> connector
>> > to a pci express gigabit network card and am having problems getting it
>> > re-connected to the clients. At the client I'm getting the EdUbuntu
>> > landing/login page but w/o the input for just a couple of seconds and
>> then
>> > get this error :
>> >
>> > BusyBox v1.18.5 (Ubuntu 1:1.18.5-1ubuntu4) built-in shell (ash)
>> > Enter 'help' for a list of built-in commands.
>> > (initramfs)
>> >
>> >
>> >
>> > I'm attempting to use "eth2" (i.e. the new gigabit card) connected to
>> the
>> > client network. I was able to get onboard eth0 connected to the
>> Internet.
>> >
>> >
>> > I've got the /etc/ltsp/dhcpd.conf file set like this
>> >
>> > #
>> > # Default LTSP dhcpd.conf config file.
>> > #
>> >
>> > authoritative;
>> >
>> > subnet 192.168.0.0 netmask 255.255.255.0 {
>> >    range 192.168.0.20 192.168.0.250;
>> >    option domain-name "example.com";
>> >    option domain-name-servers 192.168.0.0;
>> >    option broadcast-address 192.168.0.255;
>> >    option routers 192.168.0.0;
>> > #    next-server 192.168.0.1;
>> > #    get-lease-hostnames true;
>> >    option subnet-mask 255.255.255.0;
>> >    option root-path "/opt/ltsp/i386";
>> >    if substring( option vendor-class-identifier, 0, 9 ) = "PXEClient" {
>> >        filename "/ltsp/i386/pxelinux.0";
>> >    } else {
>> >        filename "/ltsp/i386/nbi.img";
>> >    }
>> >
>> > I ran the "ifconfig" command on the cl and got this:
>> > eth0      Link encap:Ethernet  HWaddr 00:24:8c:a9:d0:cd
>> >          inet addr:24.73.154.245  Bcast:24.73.154.255
>>  Mask:255.255.255.248
>> >          inet6 addr: fe80::224:8cff:fea9:d0cd/64 Scope:Link
>> >          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>> >          RX packets:1499 errors:0 dropped:0 overruns:0 frame:0
>> >          TX packets:1527 errors:0 dropped:0 overruns:0 carrier:0
>> >          collisions:0 txqueuelen:1000
>> >          RX bytes:762797 (762.7 KB)  TX bytes:253913 (253.9 KB)
>> >          Interrupt:44 Base address:0x8000
>> >
>> > eth2      Link encap:Ethernet  HWaddr 00:0a:cd:1f:bb:95
>> >          inet addr:192.168.0.0  Bcast:192.168.0.255  Mask:255.255.255.0
>> >          inet6 addr: fe80::20a:cdff:fe1f:bb95/64 Scope:Link
>> >          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>> >          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>> >          TX packets:110 errors:0 dropped:0 overruns:0 carrier:0
>> >          collisions:0 txqueuelen:1000
>> >          RX bytes:0 (0.0 B)  TX bytes:9061 (9.0 KB)
>> >          Interrupt:43 Base address:0xa000
>> >
>> > lo        Link encap:Local Loopback
>> >          inet addr:127.0.0.1  Mask:255.0.0.0
>> >          inet6 addr: ::1/128 Scope:Host
>> >          UP LOOPBACK RUNNING  MTU:16436  Metric:1
>> >          RX packets:590 errors:0 dropped:0 overruns:0 frame:0
>> >          TX packets:590 errors:0 dropped:0 overruns:0 carrier:0
>> >          collisions:0 txqueuelen:0
>> >          RX bytes:82713 (82.7 KB)  TX bytes:82713 (82.7 KB)
>> >
>> > lxcbr0    Link encap:Ethernet  HWaddr 8a:3b:78:9d:e9:f7
>> >          inet addr:10.0.3.1  Bcast:10.0.3.255  Mask:255.255.255.0
>> >          inet6 addr: fe80::883b:78ff:fe9d:e9f7/64 Scope:Link
>> >          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>> >          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>> >          TX packets:76 errors:0 dropped:0 overruns:0 carrier:0
>> >          collisions:0 txqueuelen:0
>> >          RX bytes:0 (0.0 B)  TX bytes:8116 (8.1 KB)
>> >
>> > *I ran *
>> >
>> > sudo service isc-dhcp-server start
>> >
>> > *
>> > Might this all be related to my previous botched attempt at setting the
>> > server up to create fat clients?*
>> >
>> > I Googled the error and it was saying the error was tied to a block
>> being
>> > wrong or broken. When the fat client change was reversed the network was
>> > still up afterward.
>> >
>> > Thanks in advance
>> >
>> >
>> >
>> >
>>
>>
>> ------------------------------------------------------------------------------
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond. Discussions
>> will include endpoint security, mobile security and the latest in malware
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> _____________________________________________________________________
>> Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
>>       https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
>> For additional LTSP help,   try #ltsp channel on irc.freenode.net
>>
>
>
>
> --
> BungeeBones.com - A B2B Link Exchange - Free Links in limited locations -
> human edited and reviewed - Networked online advertising business
> opportunities available through our free, distributed web directory script
>



-- 
BungeeBones.com - A B2B Link Exchange - Free Links in limited locations -
human edited and reviewed - Networked online advertising business
opportunities available through our free, distributed web directory script
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_____________________________________________________________________
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
      https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help,   try #ltsp channel on irc.freenode.net

Reply via email to